SRS- Software Requirement Management
- 1. Software requirements specification (SRS) Presented by: Muhammad Ahmad BSIT-5th University of Okara 1
- 2. Table of Contents • Definition • Purpose of SRS • SRS Format • Characteristics of SRS • Importance of SRS 2
- 3. What is an SRS ? • SRS is the official statement of what the system developers should implement. • SRS is a complete description of the behavior of the system to be developed. • SRS should include both a definition of user requirements and a specification of the system requirements. • The SRS fully describes what the software will do and how it will be expected to perform. 3
- 4. Purpose of SRS – The SRS precisely defines the software product that will be built. – SRS used to know all the requirements for the software development and thus that will help in designing the software. – It provides feedback to the customer. 4
- 5. SRS Format Introduction • Purpose • Document Conventions • Product Scope • References Overall Description • Product Perspective • Product functions • User Classes and Characteristics • Operating Environment • Design and Implementation 5
- 6. 6 External Interface Requirements • User Interfaces • Hardware interface • Software interfaces • User Documentation Other Nonfunctional Requirements • Performance requirement • Safety requirement • Security requirement • Software Quality attributes • Business rules
- 7. Characteristics of SRS Correct: Every requirement given in SRS is a requirement of the software. Unambiguous: Every requirement has exactly one interpretation. Complete: Includes all functional, performance, design, external interface requirements; definition of the response of the software to all inputs. Consistent: Internal consistency Ranked importance: Essential vs desirable 7
- 8. Characteristics of SRS 8 Verifiable: A requirement is verifiable if and only f there exists some that finite cost meets the process requirement with a person or machine can check. Modifiable: SRS must be structured to permit effective modifications(e.g. don t be redundant, keep requirements separate). Traceable: Origin of each requirement is clear.
- 9. what are the benefits of a great SRS? The IEEE 830 standard defines the benefits of a good SRS: • Establish the basis for agreement between the customers and the suppliers on what the software product is to do. • Reduce the development effort. • Provide a basis for estimating costs and schedules. • Provide a baseline 1for validation and verification. • Serve as a basis for enhancement. 9