System Integration and Architecture 1 Page |1

Lesson 11

The software system needs to be checked for its intended behavior and direction of
progress at each development stage to avoid duplication of efforts, time and cost
overruns, and to assure completion of the system within stipulated time.The software
system needs to be checked for its intended behavior and direction of progress at each
development stage to avoid duplication of efforts, time and cost overruns, and to
assure 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.

Testing
Testing is the process or activity that checks the functionality and correctness of
software according to specified user requirements in order to improve the quality and
reliability of system. It is an expensive, time consuming, and critical approach in system
development which requires proper planning of overall testing process.

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 begins at the module level and proceeds towards the integration of the
entire software system. Different testing techniques are used at different times while
testing the system. It is conducted by 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 provides information about the various levels, methods, tools, and
techniques used for testing the system. It should satisfy all 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, facilities, and test libraries
System Integration and Architecture 1 Page |2

 Procedures and standards required for planning and conducting the tests
 Factors responsible for successful completion of testing 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 test plan are documented as a part of a system
specification document or in a separate document called test
specification or test description.

Test Procedures
It consists of the steps that should be followed to execute each of the test cases.
These procedures are specified in a separate document called test procedure
specification. This document also specifies any special requirements and formats for
reporting the result of testing.

Test Result Documentation

Test result file contains brief information about the total number of test cases executed,
the number of errors, and nature of errors. These results are then assessed against
criteria in the test specification to determine the overall outcome of the test.

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

Unit Testing
Also known as Program Testing, it is a type of testing where the analyst tests or
focuses on each program or module independently. It is carried out with the intention of
executing each statement of the module at least once.
 In unit testing, accuracy of program cannot be assured and it is difficult to
conduct testing of various input combination in detail.
 It identifies maximum errors in a program as compared to other testing
techniques.

Integration Testing
In Integration Testing, the analyst tests multiple module working together. It is used to
find discrepancies between the system and its original objective, current specifications,
and systems documentation.
 Here the analysts are try to find areas where modules have been designed with
different specifications for data length, type, and data element name.
 It verifies that file sizes are adequate and that indices have been built properly.

Functional Testing
Function testing determines whether the system is functioning correctly according to its
specifications and relevant standards documentation. Functional testing typically starts
System Integration and Architecture 1 Page |3

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 involves testing the system with valid inputs to
verify that the outputs produced are correct.
 Negative Functional Testing − It involves 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 −
 Testing should be based on the requirements of user.
 Before writing testing scripts, understand the business logic should be
understood thoroughly.
 Test plan should be done as soon as possible.
 Testing should be done by the third party.
 It should be performed on static software.
 Testing should be done for valid and invalid input conditions.
 Testing should be reviewed and examined to reduce the costs.
 Both static and dynamic testing should be conducted on the software.
 Documentation of test cases and test results should 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 constant delivery of
product according to specification.
 Software quality Assurance (SQA) is a techniques that includes procedures and
tools applied by the software professionals to ensure that software meet the
specified standard for its intended use and performance.
 The main aim of SQA is to provide proper 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 life
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 standards and
procedures set by the management.
 To notify groups and individuals about the SQA activities and results of these
activities.
 To ensure that the issues, which are not solved within the software are
addressed by the upper management.
 To identify deficiencies in the product, process, or the standards, and fix them.
System Integration and Architecture 1 Page |4

Levels of Quality Assurance

There are several levels of QA and testing that need to be performed in order to certify
a software product.

Level 1 − Code Walk-through

At this level, offline software is examined or checked for any violations of the official
coding rules. In general, the emphasis is placed on examination 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 under a variety of
conditions such as certain 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 specified performance level.

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.

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
welldesigned 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.
System Integration and Architecture 1 Page |5

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.
 Most user training deals with the operation of the system itself. The training
courses must be designed to help the user with fast mobilization for the
organization.

Training Guidelines
 Establishing measurable objectives
 Using appropriate training methods
 Selecting suitable training sites
 Employing understandable training materials

Training Methods
Instructor-led training
It involves both trainers and trainees, who have to meet at the same time, but not
necessarily at the same place. The training session could be one-on-one or
collaborative. It is of two types −

Virtual Classroom
In this training, trainers must meet the trainees at the same time, but are not required
to be at the same place. The primary tools used here are: video conferencing, text
based Internet relay chat tools, or virtual reality packages, etc.

Normal Classroom
The trainers must meet the trainees at the same time and at the same place. They
primary tools used here are blackboard, overhead projectors, LCD projector, etc.
Self-Paced Training
It involves both trainers and trainees, who do not need to meet at the same place or at
the same time. The trainees learn the skills themselves by accessing the courses at
their own convenience. It is of two types −

Multimedia Training
In this training, courses are presented in multimedia format and stored on CD-ROM. It
minimizes the cost in developing an in-house training course without assistance from
external programmers.

Web-based Training
In this training, courses are often presented in hyper media format and developed to
support internet and intranet. It provides just–in-time training for end users and allow
organization to tailor training requirements.
System Integration and Architecture 1 Page |6

Conversion
It is a process of migrating from the old system to the new one. It provides
understandable and structured approach to improve the communication between
management and project team.

Conversion Plan
It contains description of all the activities that must occur during implementation of the
new system and put it into operation. It anticipates possible problems and solutions to
deal with them.

It includes the following activities −

 Name all files for conversions.
 Identifying the data requirements to develop new files during conversion.
 Listing all the new documents and procedures that are required.
 Identifying the controls to be used in each activity.
 Identifying the responsibility of person for each activity.
 Verifying conversion schedules.

Conversion Methods
The four methods of conversion are −
 Parallel Conversion
 Direct Cutover Conversion
 Pilot Approach
 Phase-In Method
Method Description Advantages Disadvantages
Provides fallback Causes cost
when new system overruns.
fails. New system may
Parallel Old and new systems are
Offers greatest not get fair trail.
Conversion used simultaneously.
security and
ultimately testing of
new system.
Forces users to make No fall back if
New system is
Direct new system work problems arise with
implemented and old
Cutover Immediate benefit new system
system is replaced
Conversion from new methods Requires most
completely.
and control. careful planning
Allows training and A long term phasein
installation without causes a problem of
Supports phased approach unnecessary use of whether conversion
Pilot
that gradually implement resources. goes well or not.
Approach
system across all users Avoid large
contingencies from
risk management.
System Integration and Architecture 1 Page |7

Provides experience Gives impression

Working version of system
and line test before that old system is
implemented in one part of
implementation erroneous and it is
organization based on
Phase-In When preferred new not reliable.
feedback, it is installed
Method system involves new
throughout the
technology or drastic
organization all alone or
changes in
stage by stage.
performance.

File Conversion
It is a process of converting one file format into another. For example, file in
WordPerfect format can be converted into Microsoft Word.
For successful conversion, a conversion plan is required, which includes −
 Knowledge of the target system and understanding of the present system
 Teamwork
 Automated methods, testing and parallel operations
 Continuous support for correcting problems
 Updating systems/user documentation, etc

Many popular applications support opening and saving to other file formats of the same
type. For example, Microsoft Word can open and save files in many other word
processing formats.

Post-Implementation Evaluation Review (PIER)

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.

PIER ensures that the project has met its goals by evaluating the development and
management processes of the project.

Objectives of PIER
The objectives of having a PIER are as follows −
 To determine the success of a project against the projected costs, benefits, and
timelines.
 To identify the opportunities to add additional value to the project.
 To determine strengths and weaknesses of the project for future reference and
appropriate action.
 To make recommendations on the future of the project by refining cost
estimating techniques.

The following staff members should be included in the review process −

 Project team and Management
 User staff
 Strategic Management Staff
 External users
System Integration and Architecture 1 Page |8

System Maintenance / Enhancement

Maintenance means restoring something to its original conditions. Enhancement
means adding, modifying the code to support the changes in the user specification.
System maintenance conforms the system to its original requirements and
enhancement adds to system capability by incorporating new requirements.
Thus, maintenance changes the existing system, enhancement adds features to the
existing system, and development replaces the existing system. It is an important part
of system development that includes the activities which corrects errors in system
design and implementation, updates the documents, and tests the data.

Maintenance Types
System maintenance can be classified into three types −
 Corrective Maintenance − Enables user to carry out the repairing and
correcting leftover problems.
 Adaptive Maintenance − Enables user to replace the functions of the programs.
 Perfective Maintenance − Enables user to modify or enhance the programs
according to the users’ requirements and changing needs.