System Analysis and Design

Lesson 5

Dileeka Alwis
NSBM - School of Computing

System Analysis & Design - Lesson 5 1

 System Testing
• The process of checking that the software
system meets specifications and fulfills its
intended purpose.

• Cost of fixing bugs can be immense.

• Most organizations spend more time and attention on

testing than on writing the programs in the first place.

• A test plan should be developed and run on a given set of

test data. The output of the test run should match the
expected results.
System Analysis & Design - Lesson 5 2
 Test Plan
Consists of:

• Testing Strategy
• Scope
• Constraints
• Test Scenarios and Test Cases
• Testing Approach
• Testing Requirements

System Analysis & Design - Lesson 5 3

 Test Cases
Test Cases are based on,
• Valid Data
• Invalid Data
• Boundary Data

Example:
Student age is between 18 – 25.
Valid - 20, 21
Invalid - 15, 30
Boundary - 18 and 25
System Analysis & Design - Lesson 5 4
• Test Scenario 1 : User Login Screen

• Test Cases
Test
Inputs Expected Results Actual Result Comment
Case No
1 Valid Data Welcome message
User Name: Student Main Menu
Password: NSBM123
2 Invalid Data Error message:
User Name: ABC “Incorrect Login”
Password: 12345
3

System Analysis & Design - Lesson 5 5

 System Implementation
The process of installing the new system.

(1) Direct Implementation

– Fully removing the existing system and installing the new
system.

System Analysis & Design - Lesson 5 6

(2) Parallel Implementation
–Running the existing system and the new system parallel for
a particular duration.
– If the new system is successful, the old system can be
discontinued and the new system be continued.

System Analysis & Design - Lesson 5 7

(3) Pilot Implementation
–A selected part of the old system is directed to the new
system and implement.
–Try out the new system in only one part of the organization
first.
–If every thing is favorable, then the new system is gradually
rolled out across the organization.

System Analysis & Design - Lesson 5 8

(4) Phased Implementation
–The selected parts of the old system are established in the
new system step by step.

System Analysis & Design - Lesson 5 9

System Analysis & Design - Lesson 5 10
 Project Deliverables

• Software Product
• Documentation
• User Training

System Analysis & Design - Lesson 5 11

 Documentation
User Documentation/ User Manual
• A complete description of the system from the user’s point of view
detailing how to use the system.
• Includes the major error messages likely to be encountered by the
users.

System Documentation / Technical Guide

• Contains the details of system design, programs, data dictionary,
process description, etc.
• Helps to understand the system and permit changes to be made to
satisfy new user needs.
System Analysis & Design - Lesson 5 12
 System Maintenance
• The process of fixing errors and adapting the system to
the changing requirements.

• In a well-designed system, the systems analyst has

considered ease of maintenance and, to a certain extent,
designed the system to adapt to the changing needs of
the business.

System Analysis & Design - Lesson 5 13

 Corrective Maintenance
• Develop solutions to problems ("bugs") that arise during
the use of software.

• Users will notice performance problems with the software.

• Reasons:
- when the system does not meet the stated user requirements.

- due to incorrect capturing of user requirements, poor system

design or bad implementation.

System Analysis & Design - Lesson 5 14

 Preventive Maintenance

• Try to prevent problems with the software before they

occur.

• Programmers seek to prevent corrective maintenance as

much as possible, or expecting adaptive maintenance
needs before users experience problems.

System Analysis & Design - Lesson 5 15

 Perfective Maintenance
• Improve the way software functions without affecting its
basic functionality.

• Certain inefficiencies of the system can arise when using

the new system.

Examples:
- Improve file access methods
- Use new algorithms to speed up numerical calculations
- Improve menu layouts and command interfaces.

System Analysis & Design - Lesson 5 16

 Adaptive Maintenance

• Over the long term the initial user requirements for the
system may change.

• Adaptive maintenance will change the basic functionality

of the system to meet additional or changed
requirements.

System Analysis & Design - Lesson 5 17

 SDLC Models

•Waterfall Model
•Spiral Model
•Incremental Model
•Evolutionary Development Model
•Agile Software Development Model
•Rapid Prototyping Model

System Analysis & Design - Lesson 5 18

Waterfall
Model

System Analysis & Design - Lesson 5 19

 V Model

System Analysis & Design - Lesson 5 20

 Incremental Development Model

System Analysis & Design - Lesson 5 21

Spiral
Model

System Analysis & Design - Lesson 5 22

Agile Model

System Analysis & Design - Lesson 5 23