Assignment 1 defect prevention through inspection example

Quality Attributes of SRS Document:

QUALITY ATTRIBUTES CHECKLIST
 Every stated requirement has only one interpretation
Unambiguous  In case there is a term used with multiple meanings, the
requirements document should specify the meanings in
the SRS so that it is clear and easy to understand

 The requirements completely and clearly define what the

software is required to do
Complete  All the requirements related to performance, design and
functionality

 SRS is correct when all user requirements are stated in the

Correct requirements document

 All requirements are not equally important, hence each

requirement is identified to make differences among other
requirements
Ranked for importance/stability
 Stability implies the probability of changes in the
requirement in future.

 Requirements can be modified easily, maintaining the

Modifiable structure and style of the SRS

 The source of each requirement is clear and facilitates the

reference of each requirement in future
 Each requirement should be traceable to design and code
Traceable elements i.e Forward Tracing
 Each requirement explicitly referencing its source i.e
Backward Tracing

 SRS is consistent when the subsets of individual

Consistent
requirements defined do not conflict with each other
 Requirements can be verified with a process to check
whether the final software meets those requirements
Verifiable
 The requirements are verified with the help of reviews
 Faulty SRS Document Example: Ad Posting Website/App
QUALITY
SRS REQQUIREMENT CHECKLIST CORRECTION
ATTRIBUTE
The system should have a good Requirement cannot be The system UI must be
user interface verified with a process to easy to use, responsive
check whether the final and should be compatible
Verifiability
software meets those with all the devices and
requirements browsers

User should be able to start Requirement cannot be User should be able to

chat with ad poster usually verified with a process to start chat with ad poster
acceptable time check whether the final within 5 seconds
Verifiability
software meets those
requirements

There should be a method to Stated requirement does Users should be able to

authenticate users Unambiguity not have only one authenticate with their
interpretation email id

User’s facebook id should be All user requirements are Users should be able to
stored in database not stated in the login with their facebook
requirements document account.
Correctness
Users’s fb id should be
stored in database

User should be able to view a Requirement cannot be User should be able to

pie chart that is built using a modified easily, view chart of
specific technology Modifiability maintaining the structure performance of their ad
and style of the SRS

User information should be Requirement is not User information should

maintained and mapped like in referencing its source be maintained and
BRD requirement Traceability clearly mapped like in BRD
requirement 4.1

An admin should be able to The requirements do not An admin should be able

login to system with his/her clearly define what the to login to system with
username , password and other software is required to do his/her username ,
Completeness
relevant information password and other
authorization code

Registered user-Priority 1 More than one Registered user-Priority 1

Maintain User Information- requirement is given Maintain User
Priority 1 priority 1 Information-Priority 2
Prioritization
Add category-Priority 1 Add category-Priority 3
View Reports-Priority 1 View Reports-Priority 4

An ad must be viewable by Requirement does not An ad must be viewable

many users at once describe completely the by 1000 users at once
Completeness
performance
requirement of system