45N_CDRL_A008.doc

CONTRACT DATA REQUIREMENTS LIST

FORM APPROVED

OMB No.0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instruction, searching existing data sources, gathering and maintaining the data needed and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to, Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contract Office for the Contract/PR No. listed in Block E.

TBD

1. DATA ITEM NO.

A008

2. TITLE OF DATA ITEM

Requirements Traceability Verification Matrix (RTVM)

3. SUBTITLE

4. AUTHORITY (DATA ACQUISITION DOCUMENT NO.)

DI-MGMT-82133

5. CONTRACT REFERENCE

SOW Para 3.3.1.9, 3.3.2.4

6. REQUIRING OFFICE

AD4.5.14

7. DD 250 REQ

LT

9. DIST STATEMENT REQUIRED

10. FREQUENCY

ONE/R

12 DATE OF FIRST

See BLK 16

14. DISTRIBUTION

b. COPIES

8. APP CODE

A

13. DATE OF SUBSEQUENT See BLK 16

Reg Repro

16. REMARKS

BLOCK 4: Contractor format acceptable. Data Item Description cited as a guide only.

BLOCK 8: and 13: The Government has 45 working days for review and acceptance or rejection. Contractor has 30 days for re-submittal if accepted with comments or rejected.

BLOCK 9: DISTRIBUTION STATEMENT D, Department of Defense and U.S. DoD contractors only (Critical Technology) (Date). Other requests shall be referred to (Cognizant Program Office assigned at time of award).

BLOCK 12: Report to be submitted NLT 45 days after completing studies, research, development, test and evaluation.

BLOCK 14: One (1) soft copy (Reg). Soft copy shall be delivered in the original and modifiable application (e.g., Microsoft Office, AutoCAD, etc.) to:

Building 2185 RM 1130

22347 Cedar Point Road

Patuxent River, MD 20670

DESTRUCTION NOTICE: Follow the procedures in DoD 5220.22-M, NISPOM, Section 5-705.

4.5.14 (See Block 16)

15.TOTAL

G. PREPARED BY

H. DATE

14 September 2018

I. APPROVED BY

J. DATE

DD FORM 1423, JUN 90 Previous editions are obsolete Page of Pages

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

_1598689177.pdf

DATA ITEM DESCRIPTION

Title: REQUIREMENTS TRACEABILITY VERIFICATION MATRIX (RTVM)

Number: DI-MGMT-82133 Approval Date: 20170615

AMSC Number: N9820 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: AS Project Number: MGMT-2017-025

Applicable Forms: N/A

Use/relationship: The Requirements Traceability Verification Matrix (RTVM) provides bidirectional traceability from high-level system performance requirements, to the lowest-level requirements. The RTVM shows the traceability and allocation of the requirements contained in the specification tree (i.e. performance specification, detailed specification, subsystem specification, software requirements specification, interface specification and design documentation). The RTVM is also used to verify how each requirement is verified.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract SOW.

Requirements:

1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices and revisions, shall be as specified in the contract.

2. Format: The RTVM shall be in an electronic relational database format that can be manipulated to show bidirectional requirements traceability and track the verification of each requirement.

3. Content: The RTVM package shall contain the following:

3.1. Cover Page and Documentation. The RTVM software database files shall contain the following:

3.1.1. Cover Page: Enter the Title, Data of Issue, Revision Date Contract Number, Contractor’s name and address, Distribution Statement (as delineated in the contract), Export Control

Warning Label (as delineated in the contract and if applicable), and Security classification

3.1.2. Record of Change Page: Enter a record of all changes made to the RTVM.

3.1.3. Database Architecture Description Pages: Enter a detailed description of the database, show relationships and define all the terms, acronyms used in the database fields.

3.2. Data Description: This Section describes the data to be contained in the RTVM relational database.

Source: https://assist.dla.mil -- Downloaded: 2018-09-17T15:31Z Check the source to verify that this is the current version before use.

3.2.1. Unique Identification Number (UID): Enter the UID for every requirement in the system configuration baseline (functional and physical).

3.2.2. Source document: For each specification and source document enter the document number and title for the source of each requirement statement.

3.2.3. Specification or Source Document Paragraph Number: Enter the specification or source document paragraph number for each requirement.

3.2.4. Requirement Text: Enter the specification or source document requirement text.

3.2.5. Requirement Traceability: For each requirement, identify and show the traces between all other requirements for within specification tree layers and the system configuration items.

3.2.6. Requirement Type: The RTVM database shall identify if the requirement is derived or decomposed.

3.2.7. Requirement Attribute: For each requirement define whether the requirement is a measure of performance, design parameter, software functional requirement, interface requirement, physical parameter, environmental and cybersecurity (This data field can encompassother data attributes if needed.)

3.2.8. Requirement Status: Identify the Requirement status for each requirement, as approved, under review. The status should identify the latest revision number.

3.2.9. Non-Conforming Requirements: For non-conforming requirements enter the System

Trouble Report (STR) and Deficiency Report (DR) number and title.

3.2.9.1.Hyperlink: Provide hyper-link to the STR and DR databases.

3.2.10. Design Reference: Enter the specific piece of design information (e.g., design document section, drawing, etc.) associated with each requirement.

3.2.11. Requirement Allocation: Enter the specific system, subsystem, hardware item, component, Computer Software Configuration Item, Computer Software Component and

Computer Software Unit that each requirement has been allocated. System level requirements shall be allocated to all Configuration Items defined for the system.

3.2.12. Form of End Product: Enter the form and maturity level of the end product used for verification. For example the form can be the system, subsystem, unit level, software configuration Item and the maturity level can be the first article, production representative, prototype or final configuration item.

3.2.13. Verification Method: For each requirement, enter the verification method as follows:

a. “Analysis” – An element of verification that uses established technical or mathematical models or simulations, algorithms, charts, graphs, circuit diagrams, or other scientific principles and procedures to provide evidence that stated requirements were met. [Source: MIL-STD-961E with Change 2]

b. “Demonstration” – An element of verification that involves the actual operation of an item to provide evidence that the required functions were accomplished under specific scenarios. The items may be instrumented and performance monitored. [Source: MIL-STD-961E with Change

2]

c. “Examination” – An element of verification that is generally nondestructive and typically includes the use of sight, hearing, smell, touch, and taste; simple physical manipulation; and mechanical and electrical gauging and measurement. [Source: MIL-STD-961E with Change 2]

d. “Test” – An element of verification in which scientific principles and procedures are applied to determine the properties or functional capabilities of items. [Source: MIL-STD-961E with

Change 2]

3.2.14. Verification Document: Enter the document number, title, and date of the verification document that contains the verification method.

3.2.15. Verification Document Paragraph: Enter the verification document paragraph number that provides the verification method.

3.2.16. Verification Procedure: Enter the verification procedure section, and verification procedure step(s) that provides the verification method for each requirement.

3.2.17. Other Tests: Enter the names of other tests conducted, prior to verification of the requirement, where the requirement is being tested.

3.2.18. Verification Results: Enter the results of the verification for each requirement. Did system under test conform to the requirement? (Yes, No).

3.2.19. Corrective Actions: Enter all corrective actions taken and the results of the corrective actions.

3.2.20. Comments: Enter explanatory notes as required.

End of DI-MGMT-82133