INFORMATION SYSTEMS MANAGEMENT Name:
PROFESSOR CHEN
PHASE ONE
Phase Name: PROBLEM RECOGNITION
Major Function: To establish that a problem exists.
Output: Authorization to conduct a feasibility study.
Principle Tools: None.
Personel and
Tasks: A user or manager notifies an analyst that a problem exists.
PHASE TWO
Phase Name: FEASIBILITY STUDY
Major Function: To define the problem and determine whether or not a new system is feasible.
Output: Feasibility study.
Principle Tools: Fact-gathering techniques and requirements estimation.
Personel and
Tasks: Users should be heavily involved in the process.
1. The analyst collects information about the problem.
2. The analyst develops rough estimates of requirements for possible solutions.
3. The analyst develops more precise estimates of requirements for the analysis phase to follow.
4. Management decides whether or not to continue the project.
PHASE THREE
Phase Name: (Requirements) ANALYSIS
Major Function: To determine the requirements of a proposed new system.
Output: Problem specifications.
Principal Tools: Fact-gathering techniques, data dictionary, data flow diagrams, process specifications, data models, system models, prototyping, system flowcharts, and Warnier-Orr diagrams.
Personal and
Tasks: Users must continue to be heavily involved.
1. The analyst studies and documents the current system in order to understand both its flaws and its strong points.
2. The analyst prepares a list of requirements for a new system.
3. The analyst diagrams the functions of the system without specifying exactly how those functions are performed.
4. The analyst may prepare a prototype of the system.

PHASE FOUR
Phase Name: DESIGN
Major Function: To design a new system that fulfills the requirements of users and management.
Output: Design specifications.
Principle Tools: Data dictionary, data flow diagrams, process specifications, data models, system models, prototyping, system flowcharts,
Warnier-Orr diagrams, structure charts, HIPO charts, and input and output design forms.
Personnel and
Tasks: 1. The analyst decides on and orders all necessary hardware and software.
2. The analyst transforms the functional diagrams of the analysis phase into the hierarchical diagrams of the design phase.
3. The analyst incorporates security measures into the system design.
4.
5.
The analyst designs input and output formats.
The analyst determines staffing requirements and designs procedures and work flow.
6. The data base designer designs an appropriate data base.
7. Users, managers, and analyst review the design specifications for accuracy and completeness.
PHASE FIVE
Phase Name: CONSTRUCTION
Major Functions: To write and test the computer programs.
Outputs: Coded and tested programs that have been verified by the users and user documentation and training materials.
Principal Tools: Various programmer's tools, structured walkthroughts, testing procedures, and documentation procedures.
Personnel and
Tasks: 1. The analyst oversees preparation of the site and installation of the necessary equipment.
2. The analyst plans and supervises the writing, testing, and correction of the programs and/or prototype.
3. The programmers write the new programs and, if necessary, modify any purchased programs.
4. The analyst plans the testing procedures.
5.
6.
The testing team tests the programs.
The users verify that the system functions as intended.
7. The analyst supervises the preparation of user documentation and the training of users.
SDLC-2

PHASE SIX
Phase Name: CONVERSION
Major Function: To convert from the old system to new.
Output: The system in operation.
Principle Tools: Automatic data transfer programs.
Personnel and
Tasks: 1. The analyst plans and supervises conversion.
2.
3. new system.
The programmers install the software.
The data entry staff enters new data into the
4. The operations staff begins using the new system on the day of changeover.
PHASE SEVEN
Phase Name: MAINTENANCE
Major Function: To repair and upgrade the system as necessary.
Outputs: Updated system and user documentation and revised programs.
Principle Tools: Incremental models consisting of data dictionary, data flow diagrams, process specifications, data models, system models, system flowcharts, Warnier-Orr diagrams, structure charts, HIPO charts, and input and output design forms.
Personnel and
Tasks: 1. A user or manager notifies an analyst of a proposed change to the system.
2. The analyst prepares an incremental model assessing the impact of the modification.
3. Management or a change control board decides whether or not to implement the change.
4. If the change is approved, the analyst modifies all system documentation to reflect the change.
5. The programmers modify the programs.
6. The testing team tests the modified programs.
7. The operations staff begins using the modified system.
SDLC-3

SDLC-4

SDLC-5