Development, Testing and Implementation Stage

Development Stage

Development stage is the second step after the design stage is done. If the system contains files then the file structure needs to be finalized at this stage. Once the file structure has been determined, it is then created and fully tested to make sure it is robust when the system actually goes live.

There are 4 stages of development:

•          Creating a file structure to store data

Data is stored in the system with 4 parts:

-          Tables

-          Fields

-          Field Properties

-          Record

•          Creating Validation Rules/Checks

The use of validation checks is to make sure that only the correct data will be entered to the system. Validation checks are tested in two ways:

-          Entering data that should be accepted

-          Purposely entering data that should not accepted

•          Creating Input Methods

To input the data in the system, user-interface is needed. To enter the data into the system, users type it in the Data Entry Form which include:

-          Entries for all of the required files

-          Appropriate Form Controls

-          Clear instructions

-          Adequate text boxes

-          Well-designed and easy to use

•          Creating Output Formats

Output like bills has 2 systems to be created:

-          On screen outputs

-          Printed outputs

Outputs should be clear, easy to read, complete and correct

Testing Stage

                After a system is developed, it should be tested to ensure that it works like how the users expect the system to work. Testing avoids data clashes, incompatibility and memories issues. There are three categories of testing:

·         Normal

The data will normally be entered to the system which will accept, process and check the data whether it is correct or not.

·         Extreme

The data is still considered as normal but it is in the limit line. This is to ensure that the normal data are acceptable.

·         Abnormal

The data is outside the limits and are considered as rejected. The values are invalid and this helps to test and ensure that invalid data will not break the system.

There are two stages of testing which are used primarily in the technology industry (software and hardware):

·         Alpha Testing

Alpha testing is the stage before Beta Testing. This stage improves the quality of the product. Usually, this test is performed by test engineers.

Advantages:

-          Provides better view about the reliability of the software at an early stage

-          Detects a lot of errors

Disadvantages:

-          May lead to dissatisfied

-          In depth functionality cannot be tested as software is still under development stage

·         Beta Testing

Beta testing is the stage after Alpha Testing. It integrates customer input on the complete product. There are 4 types of it:

-          Traditional (product is distributed to the target market)

-          Public (product is publicly released to the outside world via online channels)

-          Technical (product is released to the internal group of an organization)

-          Focused (product is released to the market for gathering feedback on specific features of the program)

-          Post Release (product is released to the market and data is gathered to make improvements for the future release of the product)

Advantages:

-          Reduces product failure risk

-          Improves product quality

-          Cost saving

Disadvantage:

-          Finding the right beta users and maintaining their participation could be a challenge

Implementation Stage

                        Once the system is fully tested, the next stage is to fully implement it.

There are 4 methods to carry out the new stages:

·         Direct Changeover

The old system is immediately changed to the new system.

                                    Advantages:

-          Very simple

-          Cost saving

Disadvantages:

-          Risky

-          May turn out to be a disaster

·         Parallel Running

Running both the old and new system until you are certain the new system is working correctly.

Advantages:

-          Safest of all methods

-          There is a backup data (the old system)

Disadvantages:

-          Very expensive

-          Needs extra staff to work on

·         Pilot Implementation

The new system is introduced into one part of the company. It is a method of changing over in a small part of the company to start with.

Advantages:

-          If the new system fails, only one part of the company is affected

-          Cost saving

Disadvantages:

-          No back-up system

-          Pilot scheme needs to be evaluated before the next stage is introduced

·         Phased Implementation

A compromise between parallel and direct changeovers. It gradually replace the old system.

Advantages:

-          Low cost

-          Isolated errors

Disadvantages:

-          Long time process

-          It is necessary to evaluate each phase before moving to the next stage

References:

http://www.ictlounge.com/html/development_and_testing.htm

http://www.bbc.co.uk/schools/gcsebitesize/ict/system/1implementingrev3.shtml

http://www.centercode.com/blog/2011/01/alpha-vs-beta-testing/

http://smallbusiness.chron.com/changeover-techniques-34890.html

http://www.teachict.com/as_a2_ict_new/ocr/A2_G063/331_systems_cycle/slc_stages/miniweb/pg15.htm

http://www.igcseict.info/theory/8/test/

http://www.guru99.com/alpha-beta-testing-demystified.html

http://www.igcseict.info/theory/8/implem/

Thank you for reading this blog