Implementation Phase

Purpose

- Aim to create database using database software by system developers than provide training to the user after system installed and construct the new or modified system and then deliver it to use

Activities

I) Coding

- For translating system design and writing program code for every module

- example: Structured Programming, Functional Programming

Structured Programming

- encourages the developer to use subroutines and loops instead of using simple jumps in the code, thereby bringing clarity in the code and improving its efficiency and reduce coding time and organize code properly

Functional Programming

- provides means of computation as mathematical functions, which produces results irrespective of program state

Types of errors

1) Syntax error	- Errors due to the fact the syntax of the language is not respected
2) Logical error	- Errors due to the fact that the specification is not respected
3) Semantic error	- Errors due to an improper use of program statements
4) Compile time error	- Syntax errors and static semantic errors indicated by the compiler
5) Runtime error	- Dynamic semantic errors, and logical errors, that cannot be detected by a compiler

II) Testing

- to detect only errors that still appear in the system

Testing Approaches

A) Functionality testing

- being tested without taking the actual implementation in concern

Equivalence class

- The input is divided into similar classes. If one element of a class passes the test, it is assumed that all the class is passed.

Boundary values

- The input is divided into higher and lower end values. If these values pass the test, it is assumed that all values in between may pass too.

Cause-effect graphing

- A testing technique where combinations of input values are tested in a systematic way.

Pair-wise Testing

- The behavior of software depends on multiple parameters. In pairwise testing, the multiple parameters are tested pair-wise for their different values.

State-based testing

- The system changes state on provision of input. These systems are tested based on their states and input.

B) Implementation testing

- Testing the functionality and the way it is implemented is also analyzed

Control-flow testing

- The purpose of the control-flow testing to set up test cases which covers all statements and branch conditions. The branch conditions are tested for both being true and false, so that all statements can be covered.

Data-flow testing

- This testing technique emphasis to cover all the data variables included in the program. It tests where the variables were declared and defined and where they were used or changed.

Testing Level

1) Unit Test	- verifies that each individual program or object work by itself
2) System Test	- verifies that all program in an application work together properly
3) Acceptance Test	- Checks the new system to ensure that it works with actual data
4) Integration Test	- verifies that an application works with other application

III) Installation

- The specific system is ready for installation after the database is designed and every modules code are written and test successfully

IV) Documentation

- Comprehensive approach of training

- It provides solution for system users for any trouble shooting

V) Support

- Provide assistant to solve unexpected problems that fail to overcome by the system users or operations

VI) Training

- Ready to train the users to use or manage the system after system installed completely

- Types of training

A) In-house Training	- Trainers can customize running modules to accommodate the immediate needs of company
B) Online Training	- Offer convenience because employees can access the training modules at any time
C)Training Video	- Cost-effective way to offer employee training

VII) Data Conversion

- To convert the data from an old system to a new system

Direct Conversion Approach

- Users direct using the new system on a certain time

Parallel Conversion Approach

- Operates the old system parallel with the new system for a period of time. Results from both systems are compared. Users must work fully in both systems to reap the benefits of a parallel conversion. This causes it is least risky but the most expensive approach compared to others.

Phased Conversion Approach

- Implements subsystems of the new system gradually over a period of time or, alternatively, the system is implemented in only a few departments, branch officers, or plant locations at a time

Pilot Conversion Approach

- implements the new system in one location in the organization, this means the new system is used and modified at this test site until the systems analyst believes the system can be successfully implemented.

If you have any comments, please leave them below!
Don't forget to follow me and share! Thank you!