Term
| Definition of the problem |
|
Definition
The feasibility of the system is considered and so this stage is often know as the feasibility stage.
1. Identify the problem
2. Is it economically feasible & economically disirable to the end user? |
|
|
Term
| Investigation & Analysis Stage |
|
Definition
Follows the definition stage and must be fully completed before the design stage.
1. Nature of the problem is investigated & the results form the basis of the analysis.
2. User requirements are defined and agree by the end user. (Ascertaining user requirements are the most important element of the analysts role, these requirements are constantly refered to throughout the lifecycle if the system is to be successful). |
|
|
Term
|
Definition
Design comes after the investigation & analysis stage this stage must be complete before the implementation stage is started.
1. The design stage follows the objectives that have been determined by the requirements specification.
The designs ofbthe system include:
1. Methods of data capture (forms)
2. Input & output (Screen layout & form & report design)
3. Data structure (data dictionaries & ERDs )
4. Validation & data structure (validation rules & query design) |
|
|
Term
|
Definition
Also known as the development stage. Comes after design and must be complete before testing stage.
1. Programmers create the code require required for the software solution.
2. Interface, macros, processing & querys in line with designs are implemented. |
|
|
Term
|
Definition
This stage comes after the implementation & must be complete before installation.
1. The 2 main functions sof this satge are
a) to find any bugs or errors in the code
b) if the system meets the user needs (requirements spec has been met).
2. Alpha testing - testing by the developers
Beta testing - testing by the end user |
|
|
Term
|
Definition
Comes after the testing stage and runs in conjunction with the Documentation stage.
The strategy of installation needs to be discussed and decided.
Statergies include
a) parrellel - runs along side the old system
b) phased - subsystems are introduced one at a time to make sure each one works before the next is implemented.
c) pilot - used in large organisations. Involves the system being tested in small portions within the organiation over a determined period of time.
d) Direct - is most likely to be the most appropriate. The old system stops and the new one begins. |
|
|
Term
|
Definition
After implementation documentation supports the training given to staff.
Document ion includes:
a) recovery procedures
b) user manuals
c) test plans
d) technical manuals. |
|
|
Term
| Evaluation & Maintainance Stage |
|
Definition
The final stage of the lifecycle, this forms the basis as to whether the cycle needs to be repeated, this demonstates the iterative nature of the life cycle.
Maintenance is performed for the following reasons.
1. Perfecting - to perfect an aspect of the system to make something do something better.
2. Adaptive - to adapt an aspect if the system to make it do something slightly different.
3. Corrective - to correct an aspect of the system these is not working properly. |
|
|
