Scribd
Upload
199 views3 pages

Introduction To System Analysis and Design:: 7

Implementation is when the developed system is put into practice after user acceptance. It involves acquiring hardware and software, converting data from the old system, training users, and documenting the system. There are different strategies for changing over to the new system like direct changeover, parallel run where both systems run simultaneously, or pilot run where the new system is tested on past data before full implementation. Proper documentation is also important to ensure continuity of the system and allow for future changes.

Uploaded by

Horacio Stella
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
199 views3 pages

Introduction To System Analysis and Design:: 7

Implementation is when the developed system is put into practice after user acceptance. It involves acquiring hardware and software, converting data from the old system, training users, and documenting the system. There are different strategies for changing over to the new system like direct changeover, parallel run where both systems run simultaneously, or pilot run where the new system is tested on past data before full implementation. Proper documentation is also important to ensure continuity of the system and allow for future changes.

Uploaded by

Horacio Stella
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Introduction to System Analysis and Design :: 7

(h) Implementation After having the user acceptance of the new system developed, the

8 :: Computer Applications

implementation phase begins. Implementation is the stage of a project during which theory is turned into practice. The major steps involved in this phase are: Acquisition and Installation of Hardware and Software Conversion User Training Documentation The hardware and the relevant software required for running the system must be made fully operational before implementation. The conversion is also one of the most critical and expensive activities in the system development life cycle. The data from the old system needs to be converted to operate in the new format of the new system. The database needs to be setup with security and recovery procedures fully defined. During this phase, all the programs of the system are loaded onto the users computer. After loading the system, training of the user starts. Main topics of such type of training are: How to execute the package How to enter the data How to process the data (processing details) How to take out the reports After the users are trained about the computerized system, working has to shift from manual to computerized working. The process is called Changeover. The following strategies are followed for changeover of the system. (i) Direct Changeover: This is the complete replacement of the old system by the new system. It is a risky approach and requires comprehensive system testing and training. (ii) Parallel run: In parallel run both the systems, i.e., computerized and manual, are executed simultaneously for certain defined period. The same data is processed by both the systems. This strategy is less risky but more expensive because of the following: Manual results can be compared with the results of the computerized system.

Introduction to System Analysis and Design :: 9

The operational work is doubled. Failure of the computerized system at the early stage does not affect the working of the organization, because the manual system continues to work, as it used to do. (iii) Pilot run: In this type of run, the new system is run with the data from one or more of the previous periods for the whole or part of the system. The results are compared with the old system results. It is less expensive and risky than parallel run approach. This strategy builds the confidence and the errors are traced easily without affecting the operations. The documentation of the system is also one of the most important activity in the system development life cycle. This ensures the continuity of the system. There are generally two types of documentation prepared for any system. These are: User or Operator Documentation System Documentation The user documentation is a complete description of the system from the users point of view detailing how to use or operate the system. It also includes the major error messages likely to be encountered by the users. The system documentation contains the details of system design, programs, their coding, system flow, data dictionary, process description, etc. This helps to understand the system and permit changes to be made in the existing system to satisfy new user needs.

You might also like