08-05-2012, 02:45 PM
Applied Software Project Management
06 requirements(1).ppt (Size: 342 KB / Downloads: 48)
Software Requirements
Software requirements are documentation that completely describes the behavior that is required of the software-before the software is designed built and tested.
Requirements analysts (or business analysts) build software requirements specifications through requirements elicitation.
Interviews with the users, stakeholders and anyone else whose perspective needs to be taken into account during the design, development and testing of the software
Observation of the users at work
Distribution of discussion summaries to verify the data gathered in interviews
Use Cases
A use case is a description of a specific interaction that a user may have with the system.
Use cases are deceptively simple tools for describing the functionality of the software.
Use cases do not describe any internal workings of the software, nor do they explain how that software will be implemented.
They simply show how the steps that the user follows to use the software to do his work.
All of the ways that the users interact with the software can be described in this manner.
Functional Requirements
Functional requirements define the outward behavior required of the software project.
The goal of the requirement is to communicate the needed behavior in as clear and unambiguous a manner as possible.
The behavior in the requirement can contain lists, bullets, equations, pictures, references to external documents, and any other material that will help the reader understand what needs to be implemented.
Software Requirements Specification
The software requirements specification (SRS) represents a complete description of the behavior of the software to be developed.
The SRS includes:
A set of use cases that describe all of the interactions that the users will have with the software.
All of the functional requirements necessary to define the internal workings of the software: calculations, technical details, data manipulation and processing, and other specific functionality that shows how the use cases are to be satisfied
Nonfunctional requirements, which impose constraints on the design or implementation (such as performance requirements, quality standards or design constraints).