L6 Sad System Implementation
L6 Sad System Implementation
L6 Sad System Implementation
In the system design phase the analyst designed a system specifications which will now serve
as base for constructing the new system. In the implementation phase the information
system department (IT) plans, develops, documents, integrates and test all the programs that
attribute to the new system.
The analyst must deliver a clear set of specification to the programmers. The programmer
then does the coding, test and documents the individual programs while the analysts plans
the integration of the functional units system to ensure they work together to meet the
requirements.
The following activities take place during system implementation
Coding
Testing
Training
Changeover/ conversion
Documentation of all the programs
Post implementation review
Coding:
This is where the design is translated into a computer program using suitable programming
languages and tools. It may be done using either; human programmers or software code
generators.
Human coding requires more personal supervision and therefore increases the cost of the
project.
Code generators are for users input code of the design to generate a source code for the
programmer. This source code can then be checked for possible errors.
Testing
Testing is done in order to identify faults in the system and correct them.
This stage begins with the presentation to the management the system developed and is
approached the term can begin to work on the system installation.
During testing the development team Prepare operational and testing environment
System verification
Verification is intended to check that a product, service, or system (or portion thereof, or set
thereof) meets a set of initial design requirements, specifications, and regulations. It is a
process that is used to evaluate whether a product, service, or system complies with
regulations, specifications, or conditions imposed at the start of a development phase.
Verification can be in development, scale-up, or production. This is often an internal process.
Quality control
Quality Control (QC) is a system of routine technical activities, to measure and control the
quality of the inventory as it is being developed.
The QC system is designed to:
1. Provide routine and consistent checks to ensure data integrity, correctness, and
completeness;
2. Identify and address errors and omissions;
3. Document and archive inventory material and record all QC activities.
QC activities include general methods such as accuracy checks on data acquisition and
calculations and the use of approved standardized procedures for emission calculations,
measurements, estimating uncertainties, archiving information and reporting. Higher tier
QC activities include technical reviews of source categories, activity and emission factor data,
and methods.
Quality assurance
Quality Assurance (QA) activities include a planned system of review procedures conducted
by personnel not directly involved in the inventory compilation/development process.
Reviews, preferably by independent third parties, should be performed upon a finalized
inventory following the implementation of QC procedures. Reviews verify that data quality
objectives were met, ensure that the inventory represents the best possible estimates of
emissions and sinks given the current state o f scientific knowledge and data available, and
support the effectiveness of the QC programme.
During the evaluation process the impact of the system to the organization structure is
evaluated and the quality of the product evaluated as well.
N/B: System post implementation review team writes a report that indicates specific areas
within the system that need improvement. This report acts as a reference during system
maintenance.
Poor documentation of a system
Makes it hard for one to understand the system and also change the system if need arises.
This implies that a system may change and the documentation written again in order to
improve its quality