System Implementation

Department of Computer Science & EngineeringHamdard University Bangladesh

2

Systems implementation is the construction of the new system and the delivery of that system into production.

System Implementation

3

System Implementation Six major activities:

Coding Testing Installation Documentation Training Support

4

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.

Purpose of System Implementation

System Development Life Cycle

5

6

The Process of Coding, Testing, and Installation

Coding Physical design specifications are turned into working

computer code. Testing

Tests are performed using various strategies. Installation

The current system is replaced by new system.

7

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.

Different Types of Tests Static or dynamic techniques

Static testing means that the code being tested is not executed. Dynamic testing involves execution of the code.

Test is automated or manual Automated means computer conducts the test. Manual means that people complete the test.

Inspection participants examine program code for predictable language-specific errors.

Desk checking program code is sequentially executed by the reviewer.

8

Different types of tests (cont.) Unit testing

Each module is tested alone in an attempt to discover any errors in its code.

Integration testing Individual software modules are combined and tested as a group.

System testing Designed to uncover weaknesses that were not found in earlier

tests. Stub testing

Performed on individual events or modules of a program.

9

The Testing Process

The purpose of testing is to confirm that the system satisfies

the requirements.

Testing must be planned.

Test case is a specific scenario of transactions, queries or

navigation paths.

10

11

Test cases are usually developed by analysts. Test cases should not be created by the programmers. Separate people should program and test in order to ensure

objectivity. Programmers use symbolic debuggers to isolate causes for

errors.

Combining Coding and Testing

12

Acceptance Testing by Users

Systems acceptance test is a final system test performed by end-users using real data over an extended time period.

• Verification testing• Validation testing• Audit testing.

13

Three levels for acceptance test :Verification testing runs the system in a simulated environment using simulated data.

Validation testing runs the system in a live environment using real data.

Audit testing certifies that the system is free of errors and is ready to be placed into operation.

14

Installation

Process of moving from old system to new system Conversion of data must be planned

Four installation strategies: Direct Installation. Parallel Installation. Single-location installation. Phased Installation.

Direct Installation

15

Parallel Installation

16

Single Location Installation

17

Phased Installation

18

Documenting the System

System documentation system’s design specifications, its internal workings, and its

functionality. User documentation

written or other visual information. Internal documentation:

program source code or is generated at compile time. External documentation

structured diagramming techniques such as data flow and E-R diagrams.

19

20

Supporting the End-user

Information Center / Help desk Automating support Resident expert Other things to consider:

Providing recovery and backup Disaster recovery PC maintenance

21

Training Information Systems Users

Potential training topics Use of the system. General computer concepts. Information system concepts. Organizational concepts. System management. System installation.

Developing Test Cases for WebStore

Test Case ID Category/Objective of Test Description System Version Completion Date Participants Machine Characteristics Test Result Comments

22

Bug Tracking and System Evolution

Bug Number (simple incremental number) Test Case ID that Generate the Bug Is the Bug Replicable? Effects Description Resolution Resolution Date Comments

23

WebStore Installation

WebStore was ready to go online and development team recommended to top management it was time to “flip the switch”.

24

25

Project Close-Down Evaluate team.

Reassign members to other projects. Notify all affected parties that the development

project is ending. Conduct post project reviews. Close out customer contract.

Formal signoff.

Thanks To All