- Preliminary Analysis: This first stage is intended for conducting a preliminary analysis, proposing alternative solutions, discuss costs and benefits and submit a preliminary plan with recommendations. You need to find out the organization's objectives and the nature and scope of the problem. Alternate proposals may come from interviewing employees, clients, suppliers, and/or consultants. You can also study what competitors are doing. With this data, you will have three choices: leave the system as is, improve it, or develop a new system.
- Requirements Definition: This step defines project goals into specific functions and operations of the intended application. It also analyzes end-user information needs.
- Systems Design: Here you describe desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
- Development: In this stage the actual code is written.
- Integration and Testing: This is where you put together all of the elements into a special testing environment, then check for errors, bugs and interoperability.
- Acceptance, Installation, Deployment: The final stage of initial development, where the software is put into production and runs actual business.
- Maintenance: This happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This is often the longest of the stages.
The Systems development life cycle is an efficient process used by a systems analyst to develop an information system and training. The objective aims to produce a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned IT infrastructure, and is inexpensive to maintain and cost-effective to enhance. 2. Requirements Analysis