System Analysis And Design Testing and Quality Assurance - System Analysis and Design

What is Testing and Quality Assurance?

The software system desires to be checked for its intended behavior and direction of progress at each improvement stage to avoid duplication of efforts, time and cost overruns, and to assure completion of the system within stipulated time.The software device needs to be checked for its intended behavior and direction of progress at each improvement stage to avoid duplication of efforts, time and cost overruns, and to assure of completion of the system within stipulated time.

System testing and quality assurance come to aid for checking the system. It includes −

  • Product level quality (testing)
  • Process level quality.

Let us go through them briefly-


Testing is the process or activity that checks the functionality and correctness of software according to specific user requirements for you to improve the nice and reliability of system. it is an costly, time consuming, and critical method in system development which calls for proper planning of overall testing procedure.

A successful test is one that finds the errors. It executes the program with explicit intention of finding error, i.e., making the program fail. it is a process of evaluating system with an intention of creating a strong system and mainly focuses on the weak areas of the system or software.

Characteristics of System Testing

System testing starts on the module level and proceeds towards the integration of the entire software system. different testing techniques are used at different times whilst testing the system. it is conducted by means of the developer for small projects and by independent testing groups for large projects.

Stages of System Testing

The following stages are involved in testing –

Test Strategy

it is a statement that gives data approximately the various levels, methods, tools, and techniques used for testing the system. It should satisfy all of the needs of an organization.

Test Plan

It provides a plan for testing the system and verifies that the system under testing fulfils all the design and functional specifications. The test plan provides the following information −

  • Objectives of each test phase
  • Approaches and tools used for testing
  • Responsibilities and time required for each testing activity
  • Availability of tools, centers, and test libraries
  • Procedures and requirements required for planning and conducting the tests
  • Factors responsible for successful of completion of checking out process

Test Case Design

  • Test cases are used to uncover as many errors as possible in the system.
  • A number of test cases are identified for each module of the system to be tested.
  • Each test case will specify how the implementation of a particular requirement or design decision is to be tested and the criteria for the success of the test.
  • The test cases along with the check plan are documented as part of a system specification document or in a separate record called test specification or test description.

Test Procedures

It includes the steps that have to be observed to execute each of the test cases. these procedures are specified in a separate file called test method specification. This file also specifies any unique requirements and formats for reporting the result of testing.
Test Result Documentation

Test result report carries brief information approximately the total number of test cases finished, the number of errors, and nature of errors. those results are then assessed against criteria in the check specification to determine the overall outcome of the test.

Types of Testing

Testing may be of various types and different types of tests are conducted depending on the kind of bugs one seeks to discover −

Unit Testing

Also called program testing, it is a type of testing where the analyst tests or focuses on each program or module independently. it is performed with the purpose of executing every statement of the module at the least once.

  • In unit trying out, accuracy of program cannot be assured and it's miles difficult to conduct trying out of various input combination in detail.
  • It identifies most errors in a program compared to different testing techniques.

Integration Testing

In Integration testing, the analyst tests multiple module working together. it is used to locate discrepancies between the system and its original objective, present day specifications, and systems documentation.

  • Here the analysts are try to find areas in which modules have been designed with different specifications for information length, kind, and data element name.
  • It verifies that record sizes are adequate and that indices have been constructed well.

Functional Testing

Feature testing determines whether the system is functioning effectively consistent with its specifications and relevant requirements documentation. functional testing commonly starts with the implementation of the system, which is very critical for the success of the system.

functional testing is divided into two categories −

  • Positive Functional Testing − It includes testing the device with valid inputs to verify that the outputs produced are correct.
  • Negative Functional Testing − It includes testing the software with invalid inputs and undesired operating conditions.

Rules for System Testing

To carry out system testing successfully, you need to follow the given rules −

  • Checking out should be based at the requirements of user.
  • Before writing testing scripts, recognize the business logic must be understood thoroughly.
  • Test plan must be done as quickly as possible.
  • Testing should be done by way of the third party.
  • It have to be performed on static software.
  • Checking out should be done for valid and invalid input conditions.
  • Checking out should be reviewed and tested to reduce the costs.
  • Both static and dynamic testing must be performed on the software.
  • Documentation of test cases and test results must be done.

Quality Assurance

It is the review of system or software products and its documentation for assurance that system meets the requirements and specifications.

  • Purpose of QA is to provide confidence to the customers by using constant delivery of product in step with specification.
  • Software quality assurance (SQA) is a strategies that consists of procedures and tools applied via the software experts to ensure that software meet the specified popular for its intended use and performance.
  • The main aim of SQA is to provide right and accurate visibility of software project and its developed product to the administration.
  • It reviews and audits the software product and its activities throughout the existence cycle of system development

Objectives of Quality Assurance

The objectives of conducting quality assurance are as follows −

  • To monitor the software development process and the final software developed.
  • To ensure whether the software project is implementing the requirements and procedures set by the management.
  • To notify groups and individuals about the SQA activities and effects of these activities.
  • To ensure that the problems, which are not solved in the software are addressed by the upper management.
  • To identify deficiencies within the product, procedure, or the standards, and fix them.

Levels of Quality Assurance

There are several levels of QA and testing that want to be performed with a view to certify a software product.

Level 1 Code walk-through

At this level, offline software is tested or checked for any violations of the official coding rules. In standard, the emphasis is placed on exam of the documentation and level of in-code comments.

Level 2 Compilation and Linking

At this level, it is checked that the software can compile and link all official platforms and operating systems.

Level 3 − Routine Running

At this level, it is checked that the software can run properly below a spread of conditions such as positive number of events and small and large event sizes etc.

Level 4 − Performance Test

At this final level, it is checked that the performance of the software satisfies the previously certain performance level.

All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd Protection Status

System Analysis and Design Topics