What is Software Requirement Specification Specification(SPS) ? Mention the characteristics and principle of SRS.
Software Requirement Specification
- The production of requirements stage of the software development process is Software Requirements Specifications (SRS) (also called a requirements document). This report lays a foundation for software engineering activities and is constructed when entire requirements are elicited and analyzed.
- SRS is a formal report, which acts as a representation of software that enables the customers to review whether it (SRS) is according to their requirements. Also, it comprises user requirements for a system as well as detailed specifications of the system requirements.
- The SRS is a specification for a specific software product, program, or set of applications that perform particular functions in a specific environment. It serves several goals depending on who is writing it.
- First, the SRS could be written by the client of a system. Second, the SRS could be written by a developer of the system. The two methods create entirely various situations and establish different purposes for the document altogether. The first case, SRS, is used to define the needs and expectations of the users. The second case, SRS, is written for various purposes and serves as a contract document between the customer and the developer.
Characteristics of good SRS(Software Requirement Specification) documents
• 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, and external interface requirements, and the definition of the response of the software to all inputs.
• Consistent: Internal consistency.
• Ranked importance: Essential vs. desirable.
• Verifiable: A requirement is verifiable if and only if there exists some finite cost-effective process with which a person or machine can check that the SW meets the requirement •
• Modifiable: SRS must be structured to permit effective modifications (e.g. don't be redundant, keep requirements separate)
• Traceable: The origin of each requirement is clear.
Principle of SRS
•Separate functionality from implementation
• Develop model of the desired behavior of the system
• Establish the context in which s/w operates
• Define the environment in which the system operates
• Create a cognitive model
• Specifications must be tolerant of incompleteness & augmentable
• Content & structure of a specification should be amenable to change
Comments
Post a Comment