Sad Lec19, 20 & 21_system Implementation & Maintenance (1)

7/28/2019 Sad Lec19, 20 & 21_system Implementation & Maintenance (1)

http://slidepdf.com/reader/full/sad-lec19-20-21system-implementation-maintenance-1 1/65

System Implementation

Modern Systems Analysisand Design



Learning Objectives

Describe the process of coding, testing, and systemconversion.

Prepare a test plan for an information system.

Apply four installation strategies.

List deliverables for documentation, training, and usersupport.

Distinguish between system and user documentation.

Compare different user training modes.

Discuss issues of end-user support.

Explain factors influencing implementation success.



Six

major activities:Coding

Testing

InstallationDocumentation

Training

Support



Purpose of System Implementation

To convert final physical system specifications into working and reliable software

To document work that has been done

To provide help for current and future users

Six major activities: Coding

Testing

Installation

Documentation

Training

Support



The Process of Coding, Testing and Installation

Coding

Physical design specifications are turned into working computer code.

Testing Tests are performed using various strategies.

Testing can be performed in parallel with coding.

Installation

The current system is replaced by the new system.



Deliverables



The Process of Documenting the System, Training

Users, and Supporting Users

Two audiences for final documentation Information systems personnel who will maintain

the system throughout its productive life People who will use the system as part of their

daily lives

User Training Application-specific

General: for operating system and off-the-shelf software



Deliverables



Software Application Testing

A master test plan is developed during theanalysis phase.

During the design phase, unit, system and

integration test plans are developed. The actual testing is done during

implementation.

Test plans provide improved communicationamong all parties involved in testing.



Test Classification Manual vs. Automated Static (syntax only) vs. Dynamic (execution)



Direct installation : changing over from

the old system to a new one by turning off

the old system when the new system isturned on.



Parallel installation : Running the old and new information

systems at the same time until management decides the old

system can be turned off



Single-location installation : Trying out an informationsystem at one site, then deciding if and how the new system

should be deployed throughout the organization. Also known

as location or pilot installation.



Phased Installation : Changing from the old information

system to the new one incrementally, starting with one or a fewfunctional components and then gradually extending the

installation to cover the whole new system



Planning Installation Considerations

Data conversion

Error correction

Loading from current system

Planned system shutdown

Business cycle of organization



Documenting the System

System documentation

Detailed information about a system’s design

specifications, its internal workings and its functionality Intended audience: maintenance programmers

Internal documentation: embedded in the program sourcecode or generated at compile time

External documentation: includes data flow and entity-relationship diagrams



Documenting the System (cont.)

User Documentation Written or other visual information about an application

system, how it works, and how to use it

Preparing user documentation Traditional source has been information systems

department

Application-oriented documentation is now often

supplied by vendors and users themselves



User documentation is typically in the

form of online help



1. Obtaining Maintenance

Requests

2. Transforming requests into

changes

3. Designing Changes

4. Implementing Changes.

Sad Lec19, 20 & 21_system Implementation & Maintenance (1)

Documents

Transcript of Sad Lec19, 20 & 21_system Implementation & Maintenance (1)