System Analysis & Design, Phase II SDLC
Objective of Phase II: The System Development Process
Phase II of the SDLC is the
Since we have already identified a need to make
a change to the existing business model, and, the concluding research has determined that this
project should be further analyzed.
During the Analysis Phase we will discover who will use the
system, what the system will do, and where and when it will be used.
The Project Sponsor, to
present to management, will use this information gathered to determine if the project should
The Analysis Phase starts with requirement gathering.
First we will create the requirement
This will define what exactly the new system will do from the business perspective.
These requirements are both
Functional requirements are
generally made up of two categories, process-oriented, and information-oriented.
oriented function would allow users to look up the available inventory.
function would allow users to find business costs and expenses.
Non-functional requirements in
the analysis phase are the behaviors the system will have.
That will define system performance,
security, and user controls.
For example, non-functional requirement states, which web
browsers, the system will use.
The analyst will determine how the system needs to change,
small changes like business process automation, (BPA), or larger changes such as business
process improvement (BPI), or a complete overhaul, business process engineering (BPR). Once
this determination has been made, the analyst will use several requirement-gathering techniques
to acquire information from the users.
These methods may be an array of questionnaires,
interviews, JAD sessions, and observation.