Planning:

This phase is most important. Describes desired features and operations in detail, including screen layouts, process diagrams, business rules, and other documentation. By outlining in advance the project and the phases in the life cycle, the project takes shape in this phase. The company may bring in a systems analyst to do this; in some cases the company already has one (CIO) on the payroll. As this phase develops, the outline of a proposed system and feasibility analysis are put into action.

System Analysis:

This is the process in which the analyst finds the problem in the company and submits a solution and puts the project goals into defined functions and operation of the intended application. Tools that are used in this phase include requirements gathering, structured analysis, and (CASE) A computer-aided systems (software) engineering. Planning may have to be considered and possible changes in feasibility may affect the budget or schedule.

Systems Design:

In this phase, the team submits in detail the specific functions and parts it will contain and what it will take to build it, and describes desired features including screen layouts, business rules, process diagrams, and other documentation. The two main areas of system designs, logical system design, which shows (such as blue prints) of system and a physical systems design, which shows in detail the cost and materials of system. Scope creep (job as specified) and feature creep (an open ticket in case the owner wants to add something) are also used.

Development:

This phase is where the company hires a programmer, data base developer and a network engineer; a programmer may use a flow chart for the process of system. This is final stage of the initial development, and the system is put into production. The occurrence of change is taking place. Instillation is a part of this phase. Training would benefit the company during the development phase.

Testing:

Once the system is built testing of the system must take place to ensure workability and Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability. Any problem that exists will be found and addressed. In this phase, verification and validation are used.

Implementation:

The real code is written here. Now the system is ready for an actual working environment (training is most important in this phase). Instillation of systems components and old data is moved to new system, a direct cutover is used in this process, but it could be risky and difficult. This direct cutover usually takes place during off-peak hours. A parallel conversion can also be used. Pilot testing is also one type of conversion, and a staged conversion.