Software Requirement Specification
Topic Outline
- SRS
- Purpose
- Levels of requirements
- Requirement statement
- Characteristics
- SRS
- Purpose
- Levels of requirements
- Requirement statement
- Characteristics
Software Requirement Specification
- 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 requirement.
- SRS fully describes what the software will do and how it will be expected to perform.
Purpose
SRS used to know all the requirements for software development and thus that will help in designing the software. It provides feedback to the customer.
Levels of Requirements
(1) Business Requirement
Define the business problems or opportunities about the product. Business requirements define why the software product is being developed. They are the objectives of the customer requesting the development of the software.
Users will be able to correct spelling errors in a document efficiently and it will be integrated with the existing system.
(2) User Requirement.
Written for users who are not experts in the software field. Highlights the overview of the system without a design description. We avoid these things.
- Complex language
- Design detail
- Technical terms and values
(3) Functional Requirement
Function requirements specify product features or functionality. Describe what the system has to do. What are the expectations from the software? Also, specify what the system should not do.
Examples:
Features of online gaming.
(4) Non-Functional Requirement
Basically tells us the quality of the software. Highlight how well the software performs its functions.
Two different perspectives of Non-Functional Requirement
- User Perspective
High performance, reliability, good interface
- Developer Perspective
Maintainability, Testability
Requirement Statement
In the requirement, statement the customer tells us information about software.
Characteristics
- Complete
Each requirement must fully describe the functionality to be delivered.
- Correct
Each requirement must accurately describe the functionality to be built.
- Feasible
It must be possible to implement each requirement within the known capabilities and limitations of the system.
- Prioritized
Assign an implementation priority to each requirement.
- Unambiguous
Every requirement has exactly one interpretation.
Comments
Post a Comment
If you have any doubts, please let me know