Requirements Analysis - DOC by KarinReid

VIEWS: 1,962 PAGES: 4

More Info
									Requirements Analysis / Specification Requirement is a capability that must be met or possessed by a system or a system component to satisfy a contract, standard, or desired feature. Simply put, requirements must satisfy one or more of the following criteria: 1. Contract obligations 2. Standards 3. Desired needs and features Process Describe the goals of the project / product / system. Identify the stake holders. Determine the stake holder’s needs. Use the needs to generate mapped set of features or characteristics. Translate the features and characteristics into functional capabilities and non functional qualities. Outline 1. 2. 3. 4. 5. 6. 7. Goal of the project Stake Holders Assumptions Needs Analysis Current System Key Features / Characteristics Proposed System Key Features / Characteristics Functional Requirements Functional requirements are the fundamental or essential subject matter of the product. They describe what the product has to do or what processing actions it is to take. This should encompass the following:


 

Use cases: Capture who (actor) does what (interaction) with the system, for what purpose (goal), without dealing with system internals. A complete set of use cases specifies all the different ways to use the system, and therefore defines all behaviour required of the system, bounding the scope of the system Functional capabilities Business rules

8. Non Functional Requirements Non-functional requirements define how a system is supposed to be. Non-functional requirements are often called qualities of a system. Other terms for non-functional requirements are "constraints", "quality attributes", "quality goals" and "quality of service requirements". Qualities, that is, non-functional requirements, can be divided into two main categories:   a. b. c. d. e. f. Execution qualities, such as security and usability, which are observable at run time. Evolution qualities, such as testability, maintainability, extensibility and scalability, which are embodied in the static structure of the software system. Usability Scalability Reliability Maintainability Testability Extensibility

g. h. i. j. k. l. m.

Performance Supportability Security Compliance Cost Interfacing Packaging

To top