Seven Phases Systems Development Life Cycle

Continues for 0 more pages »
Read full document

Seven Phases Systems Development Life Cycle

By | August 2010
Page 1 of 1
1. Planning Establishes a high-level view of the intended project and determines its goals. It involves determining what the goal is and how best to accomplish that goal. Several factors must be considered including equipment types, costs, employee willingness to learn, and employee knowledge. While the text becomes quite involved it has been my experience that this section, while time consuming, is not nearly as difficult as the text appears to make it.

2. Systems Analysis Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs. It follows Planning wherein after the scope of the project has been determined in planning it is necessary to determine the exact source of the problem that is being solved. In this step flow diagrams are created to pinpoint where an information systems can be used to solve any problems that may exist.

3. Systems Design: Once any problems have been identified it is possible to design a system to solve those problems. This step is broken into two sections; the creation of a logical design which explains what the new system will do; the creation of a physical systems design that lists the equipment needed to perform the logical design. System Design leads to Development where the information system is built and programmed.  It describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.

4. Testing Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability. It can be performed after the system is built. In this step the functionality of the individual sub systems are tested to ensure proper operation; this process is called stub testing. After successful testing of each subsystem the entire system is tested to ensure all subsystems work together properly; this is called unit testing.

Rate this document

What do you think about the quality of this document?

Share this document

Let your classmates know about this document and more at Studymode.com