Scribd
Upload
1K views3 pages

(SRS) Document Checklist

The document is a checklist for assessing a Software Requirements Specification document. It contains 31 criteria grouped into 4 sections: standards compliance, document content, general requirements, and information quality. Each criterion is to be marked as Yes, No, or Not Applicable, along with any comments. The checklist aims to ensure the SRS document is complete, unambiguous, testable, and follows any defined standards or guidelines.

Uploaded by

Nazeer Mohammed
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1K views3 pages

(SRS) Document Checklist

The document is a checklist for assessing a Software Requirements Specification document. It contains 31 criteria grouped into 4 sections: standards compliance, document content, general requirements, and information quality. Each criterion is to be marked as Yes, No, or Not Applicable, along with any comments. The checklist aims to ensure the SRS document is complete, unambiguous, testable, and follows any defined standards or guidelines.

Uploaded by

Nazeer Mohammed
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SQ Software Requirements Specification (SRS) Document Checklist

Date(s) of Assessment: ______________ Assessor(s): ______________________ _________________________________

Project: ___________________________________________ Document Examined: __________________________ __________________________________________________

(Y=Yes, N=No, NA=Not Applicable) (Y / N / NA) w/Comments # 1 1a 1b Standards Compliance Were standards/guidelines and naming conventions established for the document? Does the document format conform to the specified standard/guideline? Are the standards and naming conventions established followed throughout the document? Document Content Is there a high-level system overview? Do the high-level system diagrams depict the internal and external interfaces and data flows? Is the systems functional flow clearly and completely described? Has the software environment been specified (i.e., hardware, software resources, users)? Are all referenced documents listed? Are all definitions, acronyms, and abbreviations included? Is there a general description of the software system and operational concepts? Are the software functions described at a high-level? Are the user characteristics defined? Are general design and implementation constraints noted? Are general assumptions that affect implementation been stated? Are general dependencies noted? Are timing requirements provided? Are memory requirements provided? Are the timing and memory limits compatible with hardware constraints? Are all limits and restrictions on software performance defined? Is each function defined separately? Does each function fully define its purpose and scope? Have the functional requirements been stated in terms of inputs, outputs, and processing? Are the functional requirements clear and specific enough to be the basis for detailed design and functional test cases? Is there a description of the performance requirements for each function? Are the operational hardware limitations discussed for each function? Are any software limitations discussed for each function? Are safety-critical software requirements uniquely identified? Are security requirements identified? Are privacy requirements identified? Are software quality requirements identified (e.g., reliability, portability, reusability, maintainability)? Are personnel-related requirements identified? Revision: 1.2 Page 1 of 3

2 2a 2b 2c 3 4 5 5a 5b 5c 5d 5e 5f 5g 5h 5i 6 6a 6b 6c 6d 6e 6f 7 8 9 10 11

SQ Software Requirements Specification (SRS) Document Checklist


(Y / N / NA) 12 13 14 15 16 17 18 Are environmental requirements and conditions identified? Are all packaging requirements identified? Are all delivery requirements identified? Are requirements provided for the operational computer hardware? Are computer software resources identified (e.g., operating system, network software, databases, test software)? Have overall integration, test and acceptance criteria been established? Have test methods (e.g., test, demonstration, analysis, or inspection) been identified for requirements? General Are functional requirements uniquely numbered? Are interface requirements to other major functions or external entities clearly identified? Are all common functions identified? Does each software function trace to one or more higher-level system requirements? Are the requirements stated so that they are discrete, unambiguous, and testable? Has each decision, selection, and computational function that the software must perform been clearly defined? Is a dictionary for all data elements provided? Is the data dictionary complete? Information - Concise, Complete and Consistent Is the document concise and easy to follow? Does the level of detail provided reflect a level of detail appropriate to the purpose of the document? Are requirements stated consistently without contradicting themselves or other requirements? Is there evidence of documentation control? Was the document baselined prior to the Software Requirements Review? Reference IEEE/EIA 12207.1-1997. IEEE/EIA STANDARD: INDUSTRY IMPLEMENTATION OF INTERNATIONAL STANDARD ISO/IEC 12207:1995 STANDARD FOR INFORMATION TECHNOLOGY-SOFTWARE LIFE CYCLE PROCESSES--LIFE CYCLE DATA: Section 6.22 Software Requirements Description w/Comments #

19 20 21 22 23 24 25 26 27 28 29 30 31

Revision: 1.2 Page 2 of 3

SQ Software Requirements Specification (SRS) Document Checklist

Date(s) of Assessment: ______________ Assessor(s): ______________________ _________________________________

Project: ___________________________________________ Document Examined: __________________________ __________________________________________________

COMMENTS PAGE ____ of ____

Comments from assessment.

Revision: 1.2 Page 3 of 3

You might also like