Chapter: 7 System Testing and Implementation

7. SYSTEM TESTING AND IMPLEMENTATION

System testing and implementation is the last step in software development.
So this last chapter discusses the system testing and implementation.

7.1 System Testing

System testing is an essential step for the development of a reliable and error-free
system. Once source code has been generated, software must be tested to uncover and
correct as many errors as possible before delivery to your customer. Your goal is to
design a series of test cases that have a high likelihood finding errors but how, there
are different methods that provides a systematic guidance for designing tests that,

Exercise the internal logic of software components, and

Exercise the input and output domains of the program to uncover errors in the
program function, behaviour, and performance.

Software testing is a crucial element of software quality assurance and

represents the ultimate review of specification, design, and code generation.
The work product is a set of test cases designed to exercise both internal logic
and external requirements is designed and documented, expected results are
defined, and actual results are recorded. The primary objectives of testing
software are to execute a program with the intent of finding an error; a good
test case will find an as-yet-undercover error, and a successful that uncover an
as-yet-undercover error.

7.2 Testing Strategies

The basic strategies that were used for testing were following
• Specification Testing
• Black Box Testing
• White Box Testing
• Regression Testing
• Acceptance Testing
• Assertion Testing
• Unit Testing

Sales Tracking system

48
Chapter: 7 System Testing and Implementation

• System Testing

Unit testing

Module testing

Subsys testing

System testing

Acceptance testing

Component testing Integration testing User testing

Fig 7.1 Testing Strategies Diagram

7.2.1 Specification Testing

Even if the code testing is performed exclusively, it doesn’t ensure
against program failure. Code testing doesn’t answer whether the code meets
the agreed specifications document. It doesn’t also determine whether all
aspects of the design are implemented. Therefore, examining specifications
stating what program should do and how it should behave under various
conditions performs specification testing. Test cases are developed to test the

Sales Tracking system

49
Chapter: 7 System Testing and Implementation

range of values expected including both valid and invalid data. It helps in
finding discrepancies between the system and its original objective. During
this testing phase, all efforts were made to remove programming bugs and
minor design faults.

7.2.2 Black Box Testing

Black-box testing is conducted at the software interface. In Black Box
testing only the functionality was tested without any regard to the code
written. If the functionality, which was expected from a component, is
provided then black box testing is completed.

7.2.3 White Box Testing

White-box testing, sometimes called glass-box testing is a test case
design method hat uses the control structure of the procedural design to derive
test cases. In White Box testing internal code written in every component was
tested and it was checked that the code written is efficient in utilizing various
resources of the system like memory or the utilizing of input output

7.2.4 Regression Testing

In Regression testing the software was tested against the boundary
conditions. Various input fields were tested against abnormal values and it was
tested that the software does not behave abnormally at any time.

7.2.5 Acceptance Testing

In acceptance testing the software was checked for completeness that it
is ready. Normally the quality assurance department performs the acceptance
testing that the software is ready and can be exported.

7.2.6 Assertion Testing

Sales Tracking system

50
Chapter: 7 System Testing and Implementation

In assertion testing the software is tested against the possible

assertions. Assertions are used to check the program and various locations that
whether the state of the program at a particular point is the same as expected
or not.

7.2.7 Unit Testing

In unit testing we checked that all the individual components were
working properly. Before integration of the entire components unit testing is
essential because it gives a confidence that all the components individually are
working fine and ready to be integrated with the other ones.
7.2.8 System Testing
When all the units were working properly and unit testing was
performed then comes the time for system testing where we checked all the
integrated components as a whole and looked for possible discrepancies,
which could have arisen after the integration.

7.3 System Evaluation

The objectives of the system evaluation are to determine whether the desired
objective has been accomplished or not. Determining the merits or demerits of the
proposed system over the existing is also covered in the system evaluation. This is
concerned with the detailed study of the developed system, from implementation
point view. At the end, some suggestions for the improvement of the system are
coded.

7.4 Implementation
This phase consists of bringing the new system into operation and turning it over
the users. Briefly it involves following steps.

7.4.1 Training
It involves

Sales Tracking system

51
Chapter: 7 System Testing and Implementation

• User Groups.
• Administrators.
7.4.2 Installation of Computer Equipments
It involves
• Location.
• Power Supply.
• Space Requirement.

7.4.3Testing the New System

System testing of the developed system was performed in these three steps.

7.4.2.1 Unit Testing

In unit testing the different modules of software are tested
independently errors. This helps in locating errors, in coding and logic that
were contained within a particular module. For example testing of each tab
canvas individually for validates entries.

7.4.2.2 Integrated Testing

After unit testing, combined testing of all modules was carried out.
The purpose was to determine that all the modules are correctly interacting
with each other.

7.4.2.3 System Testing

Final testing was done on the entire system to check that whether
the desired specification and requirements are met or not. The main aim
here was to determine the inconsistencies in the developed system. Hence
the whole system was tested.

7.5 Put the New System into Operation

At this point, a final dress rehearsal sometimes runs. It is done in the following
ways.

Sales Tracking system

52
Chapter: 7 System Testing and Implementation

7.5.1 Direct/Crash Conversion

In this approach, an entire new system is installed. The old system is
completely dismantled, leaving the organization suddenly to rely on the new
system alone. The advantage of the crash conversion is that when the old
system is seriously inadequate or radically different from the new system and
when the conversion will be so rapid that it will not severely disrupt
operations. The crash conversion also has disadvantages i.e. the crash
conversion is risky, and even for minor problem can seriously delay the
implementation schedule. Careful planning and attention to detail are
necessary for a successful crash conversion.

7.5.2 Pilot Conversion

In this approach, the old manual system is replaced by the newly
computerized system stepwise. That is one subsystem is chosen as the lead or
prototype system and implemented before all others. Only when that
subsystem is completely operational can conversion of the next system can be
considered. This approach, reduce the chances of sudden ad total system
failure. But it may take along time and money than other approaches.

7.5.3 Parallel Conversion

In this approach the proposed system run concurrently with the
existing system, processing exactly the same data. If the new system has been
properly implemented, its results should be identical to the results of the
existing system. The parallel conversion should be conducted for a complete
processing cycle. The old system is available as a backup in the case of failure
of the new one. Result obtain from the new system can be compared to that
old system.

7.6 Proposed Change Over

Peeing in view the sensitivity of matter/data. It is suggested that system should
be run parallel to manual system.

Sales Tracking system

53
Chapter: 7 System Testing and Implementation

Sales Tracking system

54