{{project}} System Requirements and Traceability Matrix


error:Missing Template Item: "minimum_requirements"help_outline

  1. The software requirements shall include technical requirements including operating system, function, interfaces, performance, and security requirements, installation considerations, design inputs, and any design constraints.

  2. Identify applicable reference drawings, specifications, codes, standards, regulations, procedures, or instructions that establish software requirement test, inspection, and acceptance criteria.

  3. Software requirements shall be traceable throughout the life cycle.

  4. Security requirements shall be specified commensurate with the risk from unauthorized access or use.

The software test plan as part of the requirements traceability matrix document must include, as applicable:

  1. Required tests and test sequence.

  2. Required ranges of input parameters.

  3. Identification of stages when testing is required.

  4. Criteria for establishing test cases.

  5. Requirements for testing logic branches.

  6. Requirements for hardware integration.

  7. Expected results.

  8. Acceptance criteria.

  9. Reports, records, standard formatting, and conventions.

  10. Disposition unexpected results. Performance of system test is by personnel other than the development staff.


Software test records shall include:

  1. Computer program tested and support software used

  2. Computer hardware used

  3. Test equipment and calibrations, where applicable

  4. Date of test

  5. Tester or data recorder

  6. Simulation models used, where applicable

  7. Test problems. Results and applicability

  8. Action taken in connection with any deviations

  9. Person evaluating the test results 11. Customer approval.

System Purpose

error:Missing Template Item: "system-purpose"help_outline

Summarize the reason(s) for the system being developed or modified.

System Scope

error:Missing Template Item: "system-scope"help_outline

Delineate the following:

  1. Identify the product(s) to be produced by name (Network Infrastructure, Host DBMS, Report Generator, HPC Server, etc.)

  2. Explain what the product(s) will, and, if necessary, will not do

  3. Describe the application of the product being specified, including relevant benefits, objectives, and goals.


Be consistent with similar statements in higher level specifications (e.g., business requirements specification).

Assumptions and Dependencies

error:Missing Template Item: "assumptions-and-dependencies"help_outline

List each of the factors that affect the requirements and should be taken into consideration for derivation of lower level requirements and design. These factors should include design inputs, design constraints, and installation considerations. Changes to these can affect the requirements in the specification. For example, an assumption may be that a specific operating system will be available on the hardware designated for the product. If, in fact, the operating system is not available, the specification would then have to change accordingly.

Pre-test Instructions/Environment/Setup

error:Missing Template Item: "pre-test"help_outline

Provide a clear description of the test environment and any required instructions for setup. This includes:

  • Pre-test environment and setup requirements including computer hardware and system software used

  • How the test data is created and required ranges for input parameters

  • How the test case is executed (i.e., manual/automated tool)

  • The steps to validate the test result including any acceptance criteria.

System Requirements

Requirements Traceability Matrix

error:Missing Template Item: "requirements-traceability-matrix"help_outline

This section of the specification should contain all of the requirements to a level of detail sufficient to enable designers to design a system to satisfy those requirements, and testers to test that the system satisfies those requirements. Be sure to define the system security requirements. Examples of such requirements are data privacy, user access, user privilege, export control, system configuration, event logging and communications.

  1. Requirements must be stated in the form to be: - Correct - Unambiguous - Complete - Consistent - Verifiable - Traceable.

  2. Requirements must be uniquely identifiable.

  3. Requirements should be cross-referenced to earlier documents that relate (e.g., business requirements).

  4. Careful attention should be given to organizing the requirements to maximize readability.

  5. Requirements should address functionality, usability, performance, system interfaces, reliability, and security.