13-12-2012, 05:59 PM
Requirements Analysis
Requirements Analysis.ppt (Size: 129.5 KB / Downloads: 347)
Software engineering task bridging the gap between system requirements engineering and software design.
Provides software designer with a model of:
system information
function
behavior
Model can be translated to data, architectural, and component-level designs.
Expect to do a little bit of design during analysis and a little bit of analysis during design.
Analysis Objectives
Identify customer’s needs.
Evaluate system for feasibility.
Perform economic and technical analysis.
Allocate functions to system elements.
Establish schedule and constraints.
Create system definitions.
Software Requirements Analysis Phases
Problem recognition
Evaluation and synthesis
focus is on what not how
Modeling
Specification
Review
Management Questions
How much effort put towards analysis?
Who does the analysis?
Why is it so difficult?
Bottom line - who pays for it?
Feasibility Study
Economic feasibility
cost/benefit analysis
Technical feasibility
hardware/software/people, etc.
Legal feasibility
Alternatives
there is always more than one way to do it