Unit 5

System Testing, Implementation and Maintenance

Implementation is a process of ensuring that the information system is operational. It
involves −

 Constructing a new system from scratch

 Constructing a new system from the existing one.
Implementation allows the users to take over its operation for use and evaluation. It
involves training the users to handle the system and plan for a smooth conversion.

Software Testing
Software Testing is evaluation of the software against requirements gathered from users and
system specifications. Testing is conducted at the phase level in software development life
cycle or at module level in program code. Software testing comprises of Validation and
Verification.
Software Validation
Validation is process of examining whether or not the software satisfies the user
requirements. It is carried out at the end of the SDLC. If the software matches requirements
for which it was made, it is validated.

 Validation ensures the product under development is as per the user requirements.
 Validation answers the question – "Are we developing the product which attempts all
that user needs from this software?"
 Validation emphasizes on user requirements.
Software Verification
Verification is the process of confirming if the software is meeting the business
requirements, and is developed adhering to the proper specification and methodologies.

 Verification ensures the product being developed is according to design

specifications.
 Verification answers the question– "Are we developing this product by firmly
following all design specifications?”
 Verifications concentrate on the design and system specifications.
Target of the test are -

95
  Errors - These are actual coding mistakes made by developers. In addition, there is a
difference in output of software and desired output, is considered as an error.

 Fault - When error exists fault occurs. A fault, also known as a bug, is a result of an
error which can cause system to fail.

 Failure - failure is said to be the inability of the system to perform the desired task.
Failure occurs when fault exists in the system.

Manual Vs Automated Testing

Testing can either be done manually or using an automated testing tool:

 Manual - This testing is performed without taking help of automated testing tools.
The software tester prepares test cases for different sections and levels of the code,
executes the tests and reports the result to the manager.

Manual testing is time and resource consuming. The tester needs to confirm whether
or not right test cases are used. Major portion of testing involves manual testing.

 Automated This testing is a testing procedure done with aid of automated testing
tools. The limitations with manual testing can be overcome using automated test
tools.

A test needs to check if a webpage can be opened in Internet Explorer. This can be easily
done with manual testing. But to check if the web-server can take the load of 1 million
users, it is quite impossible to test manually.

There are software and hardware tools which helps tester in conducting load testing, stress
testing, regression testing.

Testing Approaches
Tests can be conducted based on two approaches –

 Functionality testing
 Implementation testing
When functionality is being tested without taking the actual implementation in concern it is
known as black-box testing. The other side is known as white-box testing where not only
functionality is tested but the way it is implemented is also analyzed.

96
Exhaustive tests are the best-desired method for a perfect testing. Every single possible
value in the range of the input and output values is tested. It is not possible to test each and
every value in real world scenario if the range of values is large.

Black-box testing
It is carried out to test functionality of the program. It is also called „Behavioral‟ testing. The
tester in this case, has a set of input values and respective desired results. On providing
input, if the output matches with the desired results, the program is tested „ok‟, and
problematic otherwise.

In this testing method, the design and structure of the code are not known to the tester, and
testing engineers and end users conduct this test on the software.

Black-box testing techniques:

 Equivalence class - The input is divided into similar classes. If one element of a
class passes the test, it is assumed that all the class is passed.

 Boundary values - The input is divided into higher and lower end values. If these
values pass the test, it is assumed that all values in between may pass too.

 Cause-effect graphing - In both previous methods, only one input value at a time
is tested. Cause (input) – Effect (output) is a testing technique where combinations
of input values are tested in a systematic way.

 Pair-wise Testing - The behavior of software depends on multiple parameters. In

pair-wise testing, the multiple parameters are tested pair-wise for their different
values.

 State-based testing - The system changes state on provision of input. These

systems are tested based on their states and input.

White-box testing
It is conducted to test program and its implementation, in order to improve code efficiency
or structure. It is also known as „Structural‟ testing.

97
In this testing method, the design and structure of the code are known to the tester.
Programmers of the code conduct this test on the code.

The below are some White-box testing techniques:

 Control-flow testing - The purpose of the control-flow testing to set up a test case
which covers all statements and branch conditions. The branch conditions are tested
for both being true and false, so that all statements can be covered.

 Data-flow testing - This testing technique emphasis to cover all the data variables
included in the program. It tests where the variables were declared and defined and
where they were used or changed.

Testing Levels
Testing itself may be defined at various levels of SDLC. The testing process runs parallel to
software development. Before jumping on the next stage, a stage is tested, validated and
verified.

Testing separately is done just to make sure that there are no hidden bugs or issues left in
the software. Software is tested on various levels -

Unit Testing
While coding, the programmer performs some tests on that unit of program to know if it is
error free. Testing is performed under white-box testing approach. Unit testing helps
developers decide that individual units of the program are working as per requirement and
are error free.

Integration Testing
Even if the units of software are working fine individually, there is a need to find out
wheather they work properly when they are integrated

System Testing
The software is compiled as product and then it is tested as a whole. This can be
accomplished using one or more of the following tests:

 Functionality testing - Tests all functionalities of the software against the

requirement.

98
  Performance testing - This test proves how efficient the software is. It tests the
effectiveness and average time taken by the software to do desired task. Performance
testing is done by means of load testing and stress testing where the software is put
under high user and data load under various environment conditions.

 Security & Portability - These tests are done when the software is meant to work
on various platforms and accessed by number of persons.

Acceptance Testing
When the software is ready to hand over to the customer it has to go through last phase of
testing where it is tested for user-interaction and response. This is important because even if
the software matches all user requirements and if user does not like the way it appears or
works, it may be rejected.

 Alpha testing - The team of developer themselves perform alpha testing by using
the system as if it is being used in work environment. They try to find out how user
would react to some action in software and how the system should respond to
inputs.

 Beta testing - After the software is tested internally, it is handed over to the users to
use it under their production environment only for testing purpose. This is not as yet
the delivered product. Developers expect that users at this stage will bring minute
problems, which were skipped to attend.

Regression Testing
Whenever a software product is updated with new code, feature or functionality, it is tested
thoroughly to detect if there is any negative impact of the added code. This is known as
regression testing.

Testing Documentation
Testing documents are prepared at different stages -

Before Testing
Testing starts with test cases generation. Following documents are needed for reference –

 SRS document - Functional Requirements document

99
  Test Policy document - This describes how far testing should take place before
releasing the product.

 Test Strategy document - This mentions detail aspects of test team, responsibility
matrix and rights/responsibility of test manager and test engineer.

 Traceability Matrix document - This is SDLC document, which is related to

requirement gathering process. As new requirements come, they are added to this
matrix. These matrices help testers know the source of requirement. They can be
traced forward and backward.

While Being Tested

The following documents may be required while testing is started and is being done:

 Test Case document - This document contains list of tests required to be

conducted. It includes Unit test plan, Integration test plan, System test plan and
Acceptance test plan.

 Test description - This document is a detailed description of all test cases and
procedures to execute them.

 Test case report - This document contains test case report as a result of the test.

 Test logs - This document contains test logs for every test case report.

After Testing
The following documents may be generated after testing :

 Test summary - This test summary is collective analysis of all test reports and logs.
It summarizes and concludes if the software is ready to be launched. The software is
released under version control system if it is ready to launch.

Testing vs. Quality Control, Quality Assurance and Audit

We need to understand that software testing is different from software quality assurance,
software quality control and software auditing.

Software quality assurance - These are software development process monitoring means,
by which it is assured that all the measures are taken as per the standards of organization.
This monitoring is done to make sure that proper software development methods were
followed.
100
Software quality control - This is a system to maintain the quality of software product. It
may include functional and non-functional aspects of software product, which enhance the
goodwill of the organization. This system makes sure that the customer is receiving quality
product for their requirement and the product certified as „fit for use‟.
Software audit - This is a review of procedure used by the organization to develop the
software. A team of auditors, independent of development team examines the software
process, procedure, requirements and other aspects of SDLC. The purpose of software audit
is to check that software and its development process, both conform standards, rules and
regulations.

Combating Resistance to Change

Training
The personnel in the system must know in detail what their roles will be, how they can use
the system, and what the system will or will not do. The success or failure of well designed
and technically elegant systems can depend on the way they are operated and used.

Training Systems Operators

Systems operators must be trained properly such that they can handle all possible
operations, both routine and extraordinary. The operators should be trained in what
common malfunctions may occur, how to recognize them, and what steps to take when
they come.

Training involves creating troubleshooting lists to identify possible problems and remedies
for them, as well as the names and telephone numbers of individuals to contact when
unexpected or unusual problems arise.

Training also involves familiarization with run procedures, which involves working through
the sequence of activities needed to use a new system.

User Training
 End-user training is an important part of the computer-based information system
development, which must be provided to employees to enable them to do their own
problem solving.

 User training involves how to operate the equipment, troubleshooting the system
problem, determining whether a problem that arose is caused by the equipment or
software.

101