6.

SYSTEM TESTING AND IMPLEMENTATION

6.1 TESTING INTRODUCTION

System Testing includes testing of a fully integrated software system. Generally,

a computer system is made with the integration of software (any software is only a single
element of a computer system). The software is developed in units and then interfaced with
other software and hardware to create a complete computer system. In other words, a computer
system consists of a group of software to perform the various tasks, but only software cannot
perform the task; for that software must be interfaced with compatible hardware. System testing
is a series of different type of tests with the purpose to exercise and examine the full working of
an integrated software computer system against requirements.

6.2 TESTING METHODS

There are two major type of testing they are

1) White Box Testing.

2) Black Box Testing.

WHITE BOX TESTING

White Box Testing is a testing technique in which software’s internal structure,

design, and coding are tested to verify input-output flow and improve design, usability, and
security. In white box testing, code is visible to testers, so it is also called Clear box testing,
Open box testing, Transparent box testing, Code-based testing, and Glass box testing.

BLACK BOX TESTING

 Black box testing is a technique of software testing which examines the
functionality of software without peering into its internal structure or coding. The primary
source of black box testing is a specification of requirements that is stated by the customer.

6.3 UNIT TESTING

Unit Testing is a type of software testing where individual units or components

of a software are tested. The purpose is to validate that each unit of the software code performs
as expected. Unit Testing is done during the development (coding phase) of an application by
the developers. Unit Tests isolate a section of code and verify its correctness. A unit may be an
individual function, method, procedure, module, or object.

In SDLC, STLC, V Model, Unit testing is first level of testing done before
integration testing. Unit testing is a White box testing technique that is usually performed by the
developer. Though, in a practical world due to time crunch or reluctance of developers to tests,
QA engineers also do unit testing.

6.4 INTEGRATION TESTING

Integration testing is the process of testing the interface between two software
units or modules. It focuses on determining the correctness of the interface. The purpose of
integration testing is to expose faults in the interaction between integrated units. Once all the
modules have been unit tested, integration testing is performed.

6.5 VALIDATION TESTING

Validation testing is the process of ensuring that the tested and developed
software satisfies the client /user’s needs. The business requirement logic or scenarios have to
be tested in detail. All the critical functionalities of an application must be tested here.As a
tester, it is always important to know how to verify the business logic or scenarios that are given
to you. One such method that helps in detailed evaluation of the functionalities is the Validation
Process.
User Acceptance Testing (UAT), or application testing, is the final stage of any software
development or change request lifecycle before go-live. UAT meaning the final stage of
anydevelopment process to determine that the software does what it was designed to do in real-
world situations. Actual users test the software to determine if it does what it was designed to do
in real-world situations, validating changes made and assessing adherence to their
organization’s business requirements. The main purpose of acceptance testing is to validate end-
to-end business flow.

6.7 SYSTEM IMPLEMENTATION

Implementation is the stage in the project where the theoretical design is turned into a
working system. The implementation phase constructs, installs, and operates the new system.
The most crucial stage in achieving a new successful system is that it will work efficiently and
effectively.

There are several activities involved while implementing a new project. They are

 End user training

 End user Education
 Training on the application software
 System Design
 Parallel Run and To New System
 Post implementation Review

END USER TRAINING

End User Implementation means only those specific portions of End User Products,
developed through the use of a Company Toolkit, that (a) implement and are compliant with all
or part of the required portions of Structured Storage for the sole purpose of implementing and
being compliant with such required portions of the AAF Specification; and (b) are branded with
a trademark owned or controlled by End User.

END USER EDUCATION

 End-user education is building awareness among employees by equipping them with the
necessary tools and skills required to protect themselves and the company data from loss or
attack.

TRAINING OF APPLICATION SOFTWARE

Software development is part of every business not just for software companies
themselves, but for every company which relies on software to deliver on their core business.
Thus, understanding the key tenets of Successful Software Implementation and Delivery is
valuable in any organization.

SYSTEM DESIGN

System design is the phase that bridges the gap between problem domain and the
existing system in a manageable way.

POST IMPLEMENTATION VIEW

PIER is a tool or standard approach for evaluating the outcome of the project and
determine whether the project is producing the expected benefits to the processes, products or
services. It enables the user to verify that the project or system has achieved its desired outcome
within specified time period and planned cost.