- The As-Is system is the current system and may or may not be computerized
- The To-Be system is the new system that is based on updated requirements
- The System Proposal is the key deliverable from the Analysis Phase
Key Ideas
- The goal of the analysis phase is to truly understand the requirements of the new system and develop a system that addresses them -- or decide a new system isn’t needed.
- The System Proposal is presented to the approval committee via a system walk-through.
- Systems analysis incorporates initial systems design.
- Requirements determination is the single most critical step of the entire SDLC.
What is a Requirement?
- A statement of what the system must do
- A statement of characteristics the system must have
- Focus is on business user needs during analysis phase
- Requirements will change over time as project moves from analysis to design to implementation
Requirement Types
- Functional Requirements
- A process the system hast to perform
- Information the system must contain
- Nonfunctional Requirements
- Behavioral properties the system must have
· Operational
· Performance
· Security
· Cultural and political
Documenting Requirements
- Requirements definition report
- Text document listing requirements in outline form
- Priorities may be included
- Key purpose is to define the project scope: what is and is not to be included.
Basic Steps of Determining Requirements
- Understand the “As-Is” system
- Identify improvement opportunities
- Develop the “To-Be” system concept
- Techniques vary in amount of change
- Business Process Automation (BPA) – small change
- Business Process Improvement (BPI) - moderate change
- Business Process Reengineering (BPR) – significant change
- Additional information gathering techniques are needed as well
No comments:
Post a Comment