Requirement Specification Review Template

After a requirement specification is prepared, it is necessary to review it, but it is often not operational. In this article, the review template of the requirement specification is summarized based on relevant experience, for your reference:

Project name:

Development Department:

Review time:

Reviewer:

Project Manager:

Remarks on Content Check of category check

1. Requirement Specification integrity:

1.1 All requirements recognized by the requirement provider have been analyzed

1.2 existing business processes are included in the Requirement Specification

1.3 existing business roles are included in the Requirement Specification

1.4 existing business objects are included in the Requirement Specification

1.5 no omissions in external hardware, software and communication interfaces

2. Requirement Specification consistency:

2.1 there is no conflict between the description of a requirement item

2.2 There are no conflicting expressions of certain requirements

2.3 do not describe conflicts with relevant standards or norms

3. the testability of the requirement specification, which can be modified:

3.1 there is no need for verification tests

3.2 CRS cannot be modified due to other situations

4. Traceability of Requirement Specification:

4.1 Each requirement item has a unique ID.

4.2 The granularity of requirement items is suitable for the establishment of the requirement tracking matrix.

4.3 The presentation of each requirement item is concise and independent and easy to identify

5. correctness of requirements:

5.1 requirement items accurately describe the functions that the user source must complete

5.2 There are no requirements that are inconsistent with the relevant business process

5.3 There are no requirements inconsistent with other systems

6. Feasibility (achievable) of requirements:

6.1 There are no requirements that cannot be fulfilled due to technical barriers

6.2 There are no requirements that cannot be fulfilled due to obstacles in the field (business, market, etc.)

6.3 There are no requirements that cannot be fulfilled due to resource shortage

7 necessity of demand items:

7.1 each requirement item can be traced back to the requirements put forward by the demand Source

7.2 There are no functional requirements that have not been approved by the demand Source

7.3 there are no non-functional requirements that have not been approved by the demand Source

8. Priority of requirement items:

8.1 principles and standards for priority assignment have been defined

8.2 Requirements are prioritized based on defined principles and standards

8.3 there is no requirement item with no priority set

9 standardization of requirement specification

9.1 CRS is created based on the template as agreed

9.2 compared with the template, CRS does not have a missing section that cannot be cropped.

9.3crs