1. (SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1

2. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics of an SRS Parts of SRS 2

3. What is an SRS? It is a document that you prepare: – After customer gives you their system specifications – before you design the system BACK 3

4. What is the purpose of an SRS? “ The SRS precisely defines the software product that will be built.” The SRS is your “response to the customer’s System Specification and tells a potential customer how you intend to solve their problem.” “The [SRS] specifies the requirements and the methods to be used to ensure that each requirement has been met.” 4

5. 1.“It provides feedback to the customer.” 2.“It decomposes the problem into component parts.” 3.“It serves as an input to the design specification.” 4.“It serves as a product validation check.” BACK 5

6. Who reads the SRS? The purpose of an SRS is to communicate with the customer:  The SRS must make clear to the customer whether you have understood their system specification correctly and completely. SRS is written in plain language (not a formal language). 6

7. The purpose of an SRS is to communicate with the designers:  SRS must be detailed enough that the designers can construct a design for the system from this document. BACK 7

8. Who writes the SRS? Developers – Architects – Programmers Technical writers Customer may be involved BACK 8

9. Basis for User Manual The SRS can serve as the basis for a User Manual for the software: – Use case descriptions in SRS describe required functionality of the system, from the perspective of a user. – This can be extended to become a description of how to carry out these required tasks with the finished system. BACK 9

10. Characteristics of a good SRS 1.Correct 2.Unambiguous 3.Complete 4.Consistent 5.Ranked for importance and/or stability 6.Verifiable 7.Modifiable 8.Traceable BACK 10

11. Parts of an SRS – Purpose delineate purpose of SRS intended audience for SRS – Scope identify software to be produced by name explain what will (not) do describe application of (benefits, objectives) 11

12. – Definitions/acronyms/abbreviations – References list documents referenced by name and source – Overview brief description of rest of SRS organization of SRS BACK 12

13. THANK YOU BACK 13