课程章节
培训 · 课程 2. 需求和验证 · 第 2.6 章,共 6 章
2.6 RVTM 和 VCRM 2:29
在 RVTM 中查看验证覆盖率,并将实时 VCRM 放入规格说明和 Word 中。
演示 Holarch 1.27。
您将学到
- 从 RVTM 卡片查看验证覆盖率,并筛选到某一状态
- 说明 RVTM 与 VCRM 的区别
- 将 RVTM 导出到 Excel
- 将实时验证矩阵插入规格说明,并将矩阵导出到 Word
为 Bike-Share Dock 报告验证情况:带覆盖率卡片和筛选的 RVTM 页面、Excel 导出、插入规格说明验证章节的实时 VCRM,以及导出到 Word 的同一矩阵。
练习
在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。
- 打开您的 EO-1 演示项目(或创建它:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程))。
- 打开 验证 → RVTM。单击 未通过 卡片,记下失败的测试 TC-04 和 TC-09 验证哪些需求。单击标签清除筛选。
- 将表格切换到 VCRM,找出在所有方法列中都没有 X 的需求。
- 单击 导出 ▾ → Excel (.xlsx) 并打开文件。
- 打开 EO-1 System Requirements Specification,选择章节 5 Communications,然后选择 编写 ▾ → 插入 ▸ → 矩阵…。选择 按验证级别的 VCRM,范围保持为此文档,然后单击 插入。
- 选择 交付 ▾ → 可追溯性矩阵…,选择 RVTM,在 导出为 下选择 矩阵 (Word),将 模型 设为 SRR Baseline,然后单击 导出。
当规格说明显示按级别的实时 VCRM,且您得到一份标题中注明 SRR Baseline 的 Word 版 RVTM 时,即完成练习。
自测
- 哪个矩阵回答每条需求将如何验证?哪个回答它是否已经验证?
- 为什么要将矩阵作为实时内容插入,而不是将表格粘贴到规格说明中?
- 为什么对于需签署的交付物要从基线导出矩阵?
显示答案
哪个矩阵回答每条需求将如何验证?哪个回答它是否已经验证?
VCRM 显示每条需求计划采用的方法。RVTM 显示方法、验证每条需求的测试及其结果。
为什么要将矩阵作为实时内容插入,而不是将表格粘贴到规格说明中?
实时矩阵根据模型构建。当方法更改或测试通过时,矩阵和文档的每次导出都会随之变化。
为什么对于需签署的交付物要从基线导出矩阵?
需签署的文档必须显示商定时的模型,而不是今天的模型。从基线导出的矩阵使用该基线的条目和关系。
延伸阅读
文字稿
显示文字稿 (旁白和屏幕内容)
Introduction
Chapter six: the RVTM and the VCRM. These two matrices answer the question every review asks: how will each requirement be verified, and has it been?
This is the last chapter of Requirements and Verification.
The matrices
The RVTM lists each requirement with its method, its level, the tests that verify it and their result. The VCRM is a cross-reference: a column per method, with a mark where that method is planned. Both are built from the model, so they are always current.
On screen: Card: RVTM and VCRM.
The RVTM page
Open Verification, then RVTM. The cards count the requirements by status: one verified, one with a method planned but no test yet, and seven with nothing planned.
On screen: Verification → RVTM.
Click Unverified to list only those seven. They are the work still to plan: each needs a method, and a test or another way to show it is met.
On screen: Unverified card.
Export sends the matrix to Excel, with gaps shaded red, for anyone outside the model.
On screen: Export ▾ → Excel (.xlsx).
A live VCRM in the specification
A specification usually carries its own verification matrix. Open the specification, and select section 11.1, Verification Matrix. Open Write, then Insert, and choose Matrix.
On screen: SRS → 11.1 → Write ▾ → Insert → Matrix…
Choose the Verification Cross-Reference Matrix, keep the scope on this document, and check the preview. Click Insert.
On screen: VCRM → Insert.
The matrix is now part of the section. It is live: when a test passes or a method changes, the matrix in the specification changes with it, and so does every export.
On screen: The VCRM in the document.
Export
To send it on its own, open Deliver, choose Traceability Matrix, pick the VCRM and Word, and click Export. In Word the method columns are narrow, with a legend, and gaps are shaded.
On screen: Deliver ▾ → Traceability Matrix… → VCRM, Matrix (Word) → Export.
Recap
Let's recap. You read verification coverage on the RVTM page, filtered the unverified requirements, exported to Excel, put a live VCRM in the specification, and exported it to Word.
That completes Requirements and Verification. You can now write and check requirements, trace them, take them through review and change, verify them, and report coverage.
On screen: Track complete card, then end card.