i) Feasibility Study.



  • Describes the scope of the new system.

  • Provides estimates of costs timescales and benefits of new system.

  • The feasibility report produced forms the basis of the decision whether more detailed work will commence.


ii) Requirements Analysis.



  • Produces detailed information on what the users want the system to do.


iii) Systems Analysis.



  • Produces an accurate record of what the current system can do.


iv) System Specification.



  • Involves the production of a complete written/drawn statement of what the new system is required to do.



  • Should be comprehensible to user and designer.



  • Should not include detail of how the system should be implemented.


v) System Design.



  • Considers how the work should be carried out.



  • Will identify one or more system that can be implemented.


vi) System Development.



  • Either in-house programming or the selection and installation of of-the-shelf packages.



  • Also includes the production of user procedures.


vii) Testing.



  • Should be an ongoing process throughout the lifecycle.



  • Also a specific stage after System Development to test new system meets specification.


viii) Implementation.



  • System becomes live after adequate testing.


ix) Maintenance.



  • When a system is implemented it is likely that errors will be detected that were.missed in testing. These errors must be corrected.



  • It is possible that there may have been a fundamental misunderstanding between users and systems analysis/development staff that requires major systems rework.


x) Review.



  • Carried out after system has had sufficient time as part of normal procedures.



  • Covers costs, ease of use, meeting operational requirements.



  • Report should be produced giving recommendations for improvements to the system.Senior management will review recommendations and a new systems development life cycle may begin.