Recently MeroSpark is lunched with more features and services, now you can ask your question, sell your books, share your notes and many more. Visit now and create your account to take full advantage of MeroSpark.

Characteristics of good Software Requirements Specification (SRS) Document

Download our Android App from Google Play Store and start reading Reference Notes Offline.

SRS documentSRS document’s good characteristics,
Software Engineering Notes | Sixth Semester,
BSc.CSIT | Tribhuvan University (TU)

Characteristics of good Software Requirement Specification (SRS) document
SRS is an official statement of what the system developers should implement which includes both the user requirements for a system and a detailed specification of the system requirements. Some of the characteristics are;

  • Complete
    Requirements must be complete such that all the required information to implement the requirement are included. SRS must precisely define all the real world situation that will be encountered and the capability response to them.
    Example: In case of an error, the system must show an error page to users, like the following message:
    “Oops! We have encountered some error. You can contact us at [email protected]
  • Consistent
    System functions and performance level must be compatible and the required features must not contradict the utility of the system. All inputs to any process must be processed similarly.
    For example: Requirement 1: Invoices will be generated and sent automatically based on milestone achieved with a copy to accounts dept.
    Requirement 2: Accounts dept will generate the invoice based on milestone achieved and will sent it to the customer.
    –> These are not consistent.
  • Feasible
    Requirements must be implementable within the given time frame and budget. It must be implementable using existing and chosen technology and features should be used by end users.
    For example: If a request is made to develop software free from defects. Then this is not feasible because there is no any software which can be 100% free from defect.
  • Modifiable
    It defines that related concerns must be grouped together and unrelated concerns must be separated and SRS must have a logical structure to be modifiable. In case of any change, specific requirement and dependent ones can be modified accordingly without impact to others.
  • unambiguous
    It defines that a statement should only be interpreted only one way. Weak phrases or poor sentence structure should not be used because they could be ambiguous.
    For example: All screen must load quickly.
    Here quickly doesn’t specify how quick. Better one would be
    “All screen must load within 5 second”
(Visited 778 times, 1 visits today)

Posted By : Digvijay | Comment RSS | Category : Sixth Semester
Tag :

Post a Comment

Your email is never published nor shared. Required fields are marked *


Wordpress DMCA
Community | Toolbar | Android App | Founder/Developer : Hari Prasad Chaudhary | CSIT Portal Manager : Digvijay Chaudhary