|System Devolpment Life Cycle|
|I.||Recgnition of need
Preliminary survey/initial investigation
|What is the problem or opportunity?||Statement of scope and objectives. Preformance criteria|
Evaluation of existing system and procedures. Analysis of alternative candidate systems. Cost estimates
|What are the user's demonstrable needs? Is the problem worth solving? How can the problem be redefined?||Technical/behavioral feasibility. Cost/benefit analysis. System scope and objectives. Statement of new scope and objectives.|
Detailed evaluation of present system. Data collection.
|What must be done to solve the problem? What are the facts?||Logical model of system -- e.g., data dictionary, data flow diagram. Pertinent data.|
General design specifications. Detailed design specifications: Output, Input, Files, Procedures.
|In general, how must the problem be solved? Specifically, how must the problem be solved? What is the system (processing) flow?
Does the user approve the system?
|Design of alternative solutions. Final cost/benefit analysis. Hardware specifications. Cost estimates. Implementation specifications. Implementation schedule. Approval of systems by user. Programs. Test plans. Security, audit, and operating procedures. Actual hardware use. Formal system test.|
Testing: Unit testing, Combined module testing, User acceptance testing
|How well do individual programs/modules test out? How ready are programs for acceptance test?|
User training. File/system conversion.
|What is the actual operation? Are user manuals ready? Are there delays in loading files?||Training program. User-friendly documentation|
|VI.||Post-implementation and maintenance
Evaluation. Maintenance. Enhancements.
|Is the key system running? Should the system be modified?||User requirements met. User standards me. Satisfied user.|