Title: Develop The Prototype of The System: Department of Computer Science and Engineering

Department of
Computer Science and Engineering
Title: Develop the prototype of the system
Information System and Design LAB

CSE 438
Green University of Bangladesh

Contents
1 Objective(s) 1
2 System Implementation 1
2.1 Coding, testing, and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.2 Documenting the system and training and supporting users . . . . . . . . . . . . . . . . . . . . . 2
3 Installation 2
3.1 Direct Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3.2 Parallel Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.3 Single-location Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.4 Phased Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4 Discussion & Conclusion 4
5 Lab Exercise (Submit as a report) 4
6 Policy 4
1 Objective(s)
• Provide an overview of the system implementation process.
• Apply four installation strategies: direct, parallel, single-location, and phased installation.
• List the deliverables for documenting the system and for training and supporting users.
2 System Implementation
In a traditional plan-driven systems development project, physical design specifications must be turned into
working computer code, and the code must be tested until most of the errors have been detected and corrected.
Regardless of methodology used, once coding and testing are complete and the system is ready to “go live,” it
must be installed (or put into production), user sites must be prepared for the new system, and users rely on
the new system rather than the existing one to get their work done.
We will discuss coding, testing, installation, documentation, user training, support for a system after it is
installed, and implementation success. Our intent is not to teach you how to program and test systems—most
of you have already learned about writing and testing programs in the courses you took before this one. Rather,
this lab experiment shows you where coding and testing fit in the overall scheme of implementation, especially
in a traditional, plan-driven context.
System implementation is made up of many activities. The six major activities we are concerned with in
this chapter are coding, testing, installation, documentation, training, and support (see Figure-1). The purpose
of these steps is to convert the physical system specifications into working and reliable software and hardware.
Figure 1: Systems development life cycle with the implementation phase highlighted
Next, we will briefly discuss these activities in two groups: (1) coding, testing, and installation and (2)
documenting the system and training and supporting users.
2.1 Coding, testing, and installation

Coding, as we mentioned before, is the process whereby the physical design specifications created by the analysis
team are turned into working computer code by the programming team. Depending on the size and complexity
of the system, coding can be an involved, intensive activity.
We should emphasize that, although testing is done during implementation, you must begin planning for
testing earlier in the project. Planning involves determining what needs to be tested and collecting test data.
This is often done during the analysis phase because testing requirements are related to system requirements.
Installation is the process during which the current system is replaced by the new system. This includes
conversion of existing data, software, documentation, and work procedures to those consistent with the new
system. Users must give up the old ways of doing their jobs, whether manual or automated, and adjust to
accomplishing the same tasks with the new system. Users will sometimes resist these changes, and you must
help them adjust.
2.2 Documenting the system and training and supporting users

The deliverables from the coding, testing, and installation processes are shown in Figure-2. Some programming
languages include utilities to generate documentation automatically, while others require more effort on the part
of the coder to establish good documentation.
Figure 2: Deliverables for Coding, Testing, and Installation
But even well-documented code can be mysterious to maintenance programmers who must maintain the
system for years after the original system was written and the original programmers have moved on to other
jobs. Therefore, clear, complete documentation for all individual modules and programs is crucial to the system’s
continued smooth operation.
The deliverables from documenting the system, training users, and supporting users are shown in Figure-3.
At the very least, the development team must prepare user documentation. For most modern information
systems, documentation includes any online help designed as part of the system interface. The development
team should think through the user training process: Who should be trained? How much training is adequate
for each training audience? What do different types of users need to learn during training?
Figure 3: Deliverables for Documenting the System, Training, and Supporting Users
3 Installation
The process of moving from the current information system to the new one is called installation. All employees
who use a system, whether they were consulted during the development process or not, must give up their
reliance on the current system and begin to rely on the new system. Four different approaches to installation
have emerged over the years: direct, parallel, single-location, and phased.
3.1 Direct Installation

The old system is turned off and the new system is turned on (Figure-4). Under direct installation, users
are at the mercy of the new system. Any errors resulting from the new system will have a direct impact on
the users and how they do their jobs and, in some cases—depending on the centrality of the system to the
organization—on how the organization performs its business. If the new system fails, considerable delay may
occur until the old system can again be made operational and business transactions are reentered to make the
database up to date. For these reasons, direct installation can be very risk.
Figure 4: Direct installation
3.2 Parallel Installation

Parallel installation is as riskless as direct installation is risky. Under parallel installation, the old system
continues to run alongside the new system until users and management are satisfied that the new system is
effectively performing its duties and the old system can be turned off (Figure-5). All of the work done by the
old system is concurrently performed by the new system.
Figure 5: Parallel Installation
3.3 Single-location Installation

Single-location installation, also known as location or pilot installation, is a middleof-the-road approach com-
pared with direct and parallel installation. Rather than convert all of the organization at once, single-location
installation involves changing from the current to the new system in only one place or in a series of separate
sites over time. (Figure-6 depicts this approach for a simple situation of two locations.) The single location
may be a branch office, a single factory, or one department, and the actual approach used for installation in
that location may be any of the other approaches.
3.4 Phased Installation

Phased installation, also called staged installation, is an incremental approach. With phased installation, the
new system is brought online in functional components; different parts of the old and new systems are used in
cooperation until the whole new system is installed. (Figure-7 shows the phase-in of the first two modules of
a new system.) Phased installation, like single-location installation, is an attempt to limit the organization’s
exposure to risk, whether in terms of cost or disruption of the business.
Figure 6: Single-location Installation
Figure 7: Phased Installation
4 Discussion & Conclusion

Based on the focused objective(s) to understand about developing prototype of the system, the additional lab
exercise made me more confident towards the fulfilment of the objectives(s).
5 Lab Exercise (Submit as a report)

• Develop a prototype of your own system with the proper system implementation techniques and submit
it as a report by documenting all the necessaries.
6 Policy
Copying from internet, classmate, seniors, or from any other source is strongly prohibited. 100% marks will be
deducted if any such copying is detected

Title: Develop The Prototype of The System: Department of Computer Science and Engineering

Uploaded by

Copyright:

Available Formats

Title: Develop The Prototype of The System: Department of Computer Science and Engineering

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Title: Develop The Prototype of The System: Department of Computer Science and Engineering

Uploaded by

Copyright:

Available Formats

Department of

Computer Science and Engineering

Title: Develop the prototype of the system

Information System and Design LAB

Green University of Bangladesh

4 Discussion & Conclusion 4

5 Lab Exercise (Submit as a report) 4

2.1 Coding, testing, and installation

2.2 Documenting the system and training and supporting users

Figure 2: Deliverables for Coding, Testing, and Installation

3.1 Direct Installation

3.2 Parallel Installation

Figure 5: Parallel Installation

3.3 Single-location Installation

3.4 Phased Installation

Figure 7: Phased Installation

4 Discussion & Conclusion

5 Lab Exercise (Submit as a report)

You might also like