PWS Appendix 5, RVTM_Template_v2.0.xlsx
XLSX spreadsheet 14 KB Posted
- Attached to
- Internal Collaboration Network and History Hub
- Solicitation number
- NAMA-17-R-0001
About this file
Not Listed
View the file
Other files
| File | Type | Posted |
|---|---|---|
| NAMA-17-R-0001_Amendment_002_FINAL.doc | DOC document | |
| PWS Appendix 1, NARA SDLC v1.6.pdf | ||
| NAMA-17-R-0001_ICN_-_HH_CSS_Attachments_1-12.docx | DOCX document | |
| PWS Appendix 6, Test_Plan_Template.docx | DOCX document | |
| PWS Appendix 2, NARA IT Security Requirements v6.5.pdf | ||
| PWS Appendix 8, Test_Report_Template.docx | DOCX document | |
| StRS,_RVTM_-_Contractor_Technical_Response_Worksheet,_ICN.xlsx | XLSX spreadsheet | |
| StRS,_RVTM_Contractor_Technical_Response_Worksheet,_HH.xlsx | XLSX spreadsheet | |
| PWS Appendix 4, StRS_HistoryHub_v1.1_FINAL Redacted.docx | DOCX document | |
| PWS Appendix 3, StRS_ICN_v1.1_FINAL Redacted.docx | DOCX document | |
| PWS Appendix 11, Cloud_CMDB_Template.xlsx | XLSX spreadsheet | |
| GFI_-_PWS_Appendices_1_-_8,_and_11.zip | ZIP file | |
| PWS Appendix 7, Test_Procedures_Template.xlsx | XLSX spreadsheet |
Show all 13
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Requirements
| REQUIREMENTS | DESIGN | DEVELOPMENT | VERIFICATION | DEPLOYMENT PREPARATION | MISC | |||||||||||
| Req # | Requirement Text | Type | Category | Feature | Req Priority | |||||||||||
| Source | Use Case | Status | Element | Target Release | Iteration | Verification Method | Verification Test Case / Step | Verification Status | Verification Criteria | UAT Test Case | UAT Status | Validation Criteria | Comments | |||
| <required> | ||||||||||||||||
| <unique requirement identifier> | <required> | |||||||||||||||
| <text of the requirement> | <required> |
<type of requirement> <Business | Stakeholder | System> <required> <category of requirement> <Functional | Non-functional | Constraint | N/A>
| <N/A is to be used only when Type=Business> | <required> |
| <function, capability, feature or other grouping that makes sense to the stakeholders> | <required> |
<requirement priority> <stakeholder-assigned priority MoSCoW:
Must | Should | Could | Would> <optional but encouraged> <source of the stakeholder requirement (e.g., working sessions or a specific document)> <when the column is not needed, delete it> <required when use cases will be defined for the project> <mapping to the business or system use cases that are appropriate to the stakeholder requirement> <If use cases will not be developed for the project, delete this column; if use cases will be developed but have not yet been defined, use the value "TBD".> <when the column is not needed, delete it> <optional> <Approved, Deferred, Draft, Obsolete> <when the column is not needed, delete it> <required> <indication of design elements (e.g., subsystem or class) that are relevant to the requirement> <may map to more than one design element, in which case abbreviations or IDs are preferred over names> <use "N/A" for business or stakeholder requirements> < at least one column (tracing) is required>
| <when appropriate to the project, you may use multiple columns, one per type of design entity (e.g., subsystem)> | <required> |
| <identifier of release in which the requirement will be / is developed> | <required when iterations are used for the project> |
<identifier of iteration in which the requirement will be / is developed> <"N/A" for business and stakeholder requirements> <when the column is not needed, delete it> <required> <inspection, analysis, test, demonstration, or certification> <use "N/A" for business or stakeholder requirements> <required> <identification of the test cases to be used by NARA to verify the requirement> <"N/A" for business and stakeholder requirements> <required> <Pending, Not Delivered, Obsolete, Verified> <use "N/A" for business and stakeholder requirements> <optional> <attributes to be verified to determine if the system element meets the requirement and satisfies the design.> <use "N/A" for business and stakeholder requirements> <when the column is not needed, delete it> <required> <identification of the test cases to be used by NARA to validate the requirement> <use "N/A" for business and system requirements> <required> <Pending, Not Delivered, Obsolete, Validated> <use "N/A" for system requirements> <optional> <attributes to be validated to determine if the stakeholder requirement meets the business need> <use "N/A" for business and system requirements> <when the column is not needed, delete it> <optional> <additional pertinent information which does not fit into one of the other columns> <do not delete this column, just leave it empty if notes are not needed> <example> <example> System Functional <example> Would <example> <example> Draft <example> <example> <example> N/A <example> Pending <example> <example> Not delivered <example> <example>
&"+,Bold"&10<Project Name> Requirements Verification Traceability Matrix (RVTM)
&"+,Regular"&10&F &"+,Regular"&10Page &P of &N
StandardValues
| Type | Category | Priority | |||||||
| Status | Verification Method | Verification Status | UAT Status | ||||||
| Business | Functional | Must | Requirements that are CRITICAL to meeting the project's objectives | Approved | Inspection | Pending | Pending | ||
| Stakeholder | Non-functional | Should | Requirements that are critical and should be included if possible, but which can be excluded | Deferred | Analysis | Not Delivered | Not Delivered | ||
| System | Constraint | Could | Requirements that are part of the project's scope and add or enhance project benefits | Draft | Test | Obsolete | Obsolete | ||
| N/A | Would | Requirements that do not have a significant impact on project benefits or could be considered as a “would like to have” | Obsolete | Demonstration | Validated | Validated | |||
| Certification | N/A | N/A | |||||||
| N/A |
&"+,Bold"&10<Project Name> Requirements Verification Traceability Matrix (RVTM) - Standard Values
&"+,Regular"&10&F &"+,Regular"&10Page &P of &N
File details come from the government source that posted it. Updated .