Implementation
The final phase in
the SDLC is the implementation phase, during which the system is
actually built (or purchased, in the case of a packaged software design). This
is the phase that usually gets the most attention, because for most systems it
is the longest and most expensive single part of the development process. This
phase has three steps:
1. System construction
is the first step. The system is built and tested to ensure it performs as
designed. Because the cost of bugs can be immense, testing is one of the most
critical steps in mplementation.Most organizations give more time and attention
to testing than to writing the programs in the first place.
2. The system is
installed. Installation is the process by which the old system is turned
off and the new one is turned on. It may include a direct cutover approach (in which
the new system immediately replaces the old system), a parallel conversion approach
(in which both the old and new systems are operated for a month or two until it
is clear that there are no bugs in the new system), or a phased conversion strategy
(in which the new system is installed in one part of the organization as an initial
trial and then gradually installed in others). One of the most important aspects
of conversion is the development of a training plan to teach users how
to use the new system and help manage the changes caused by the new system.
3. The analyst team
establishes a support plan for the system. This plan usually includes a
formal or informal post-implementation review as well as a systematic way for
identifying major and minor changes needed for the system.
Ref:
System Analysis and Design
No comments:
Post a Comment