Академический Документы
Профессиональный Документы
Культура Документы
Chapter 3
Page 1 of 11
Chapter 3
Page 2 of 11
Chapter 3
System Request
Phase 1
System
Planning
Preliminary
Investigation
Report
Stop
Project
Development
Phase 2
System
Analysis
System
Requirement
Document
Stop
Project
Development
Phase 3
System
Design
System
Design
Specification
Stop
Project
Development
Phase 4
System
Implementation
Complete
Functioning IS
Phase 5
System Operation,
Support and
Security
Operational
Information
System
Page 3 of 11
Phase Name:
Major Function:
Output:
Principal Tools:
Personnel and Tasks:
Chapter 3
PRELIMINARY INVESTIGATION
To establish that a problem/opportunity
exists.
Authorization to conduct feasibility
study.
None.
A user or manager notifies an analyst that
a problem exists.
Feasibility Study
2)
3)
Page 4 of 11
Phase Name:
Major Function:
Output:
Principal Tools:
Personnel and Tasks:
Chapter 3
FEASIBILITY STUDY
To define problem/opportunity and
determine whether or not a new system is
feasible.
Feasibility study.
Fact-gathering
techniques
and
requirement estimation.
User should be heavily involved in the
process.
1. The analyst collects information about
the problem/opportunity.
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.
After gathering the facts, S/A will analyse them carefully. This
process is called requirements analysis.
Page 5 of 11
Phase Name:
Major Function:
Output:
Principal Tools:
Chapter 3
ANALYSIS
To determine the requirements of a
proposed new system.
Problem specification.
Fact-gathering
techniques,
datadictionary, data flow diagrams, process
specifications, data models, system
models, prototyping, system flowcharts
and also Computer-Aided Software
Engineering (CASE) for implementing
these tools.
User 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 new system without specifying
exactly how those functions are
performed.
4. The analyst may prepare a prototype
of the system.
Page 6 of 11
Phase Name:
Major Function:
Output:
Principal Tools:
Chapter 3
DESIGN
To design a new system that fulfills the
requirement of users and management.
Design specification.
Data dictionary, data flow diagrams,
process specifications, data models,
system models, prototyping, system
flowcharts, structure charts, HIPO charts,
and input and output design forms. Also
Computer-Aided Software Engineering
(CASE) for implementing these tools.
User must continue to be heavily
involved.
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. The analyst designs the user interface,
including input and output formats.
5. The analyst determines staffing
requirements and designs procedures
and work flow.
6. The database designer designs an
appropriate database.
7. Users, managers, and analyst review
the design specifications for accuracy
and completeness.
Page 7 of 11
Chapter 3
Phase Name:
Major Function:
Output:
Principal Tools:
IMPLEMENTATION
To write and test the computer programs.
To convert from the old system
(computerized or manual) to the new
system.
Coded and tested programs that have
been verified by the users and user
documentation and training materials.
Various programmers tools, structured
walkthroughs,
testing
procedures,
automated
regression
testing,
documentation procedures, application
generators, fourth-generation languages,
and various CASE products.
Page 8 of 11
Chapter 3
11. The operation staff begins using the new system on the day of
the changeover.
12. Once the new system is operational, IT staffs must perform two
additional tasks: prepare a post-implementation evaluation and
deliver a final report to management.
MAINTENANCE
To repair and upgrade the system as
necessary
Updated system and user documentation
and revised programs.
Incremental models consisting of data
dictionary, data flow diagrams, process
specifications, data models, system
models, system flowcharts, structure
charts, HIPO charts, and input and output
design forms. Also CASE products,
application generators, and fourthgeneration languages.
Page 9 of 11
6.
7.
Chapter 3
Thus, the document should strive for strong content and high
quality.
Page 10 of 11
Chapter 3
This will also helps you to best delegate the task among the
development team members.
3.4 Automated Tools For System Development
Page 11 of 11