Chapter 11 Analysis Concepts and Principles. Introduction: What Are the Real Problems?. the customer has only a vague idea of what is. required. the developer is willing to proceed with the. "vague idea" on the assumption that "we'll fill in. the details as we go".
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
the customer has only a vague idea of what is
the developer is willing to proceed with the
"vague idea" on the assumption that "we'll fill in
the details as we go"
the customer keeps changing requirements
the developer is "ratcheted" by these changes,
making errors in specifications and development
and so it goes ...
Requirements Analysis - is a software engineering task that bridges the gap between system level requirements engineering and software design
Analysis a bridge between system engineering and software design
1. Initiating the process – conduct a meeting or interview.
Some questions to ask by the analyst:
2. Facilitated Application Specification Techniques (FAST)
3. Quality Function Deployment
The essential view of a software requirements presents the function to be accomplished and information to be processed without regard to the implementation details.
Prototyping helps Clarify requirements, Identify missing requirements and Help define user interfaces.
1. Selecting the prototyping approach
2. Methods and tools