课程章节
培训 · 课程 4. 文档和交付物 · 第 4.2 章,共 5 章
4.2 文档中的实时矩阵 2:48
插入可根据模型自动重建的 RVTM 和 RTM 表格。
演示 Holarch 1.27。
您将学到
- 在文档正文中插入实时矩阵并选择其范围
- 查看矩阵突出显示的缺口
- 在模型中弥补缺口,并查看矩阵随之更新
- 说出各标准矩阵的名称以及每种矩阵将什么标记为缺口
将 Bike-Share Dock 规格说明中的空验证表替换为实时需求验证可追溯性矩阵,选择其范围,查看其突出显示的缺口,在模型中弥补一个缺口并观察矩阵更新,然后以同样方式添加需求可追溯性矩阵。
练习
在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。
- 打开您的 EO-1 演示项目,或创建它:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程)。
- 打开 需要与需求 → 文档 → EO-1 System Requirements Specification,单击章节 2 Attitude Determination and Control 的描述进行编辑。
- 在富文本工具栏中打开 + 并选择 矩阵…。选择 需求分配矩阵,范围保持为此文档,单击 插入,然后按 ⌘ / Ctrl↵ 保存。
- 查看标题说明和带底纹的行。2.5 Safe Mode Recovery 是一个缺口:没有任何条目满足它。
- 选择 2.5,在其 追溯 部分的 satisfied by 下关联 F10 Enter Safe Mode。回到章节 2,再次查看矩阵。
当分配矩阵的 2.5 行列出 F10 Enter Safe Mode 且不再带底纹时,即完成练习。
自测
- 实时矩阵与手动输入的表格有何不同?
- 为什么要在模型中而不是在矩阵中弥补缺口?
- 矩阵可以覆盖哪些范围?
显示答案
实时矩阵与手动输入的表格有何不同?
该块只存储要显示的矩阵和范围。每次显示或导出文档时,Holarch 都会根据模型重建各行,因此它永远不会过时。
为什么要在模型中而不是在矩阵中弥补缺口?
实时矩阵不能逐个单元格编辑。缺口是模型中缺少的关联或属性,在模型中修复后,显示它的每个矩阵和视图都会更新。
矩阵可以覆盖哪些范围?
一个文档的条目、汇编的所有部分或整个项目。接口矩阵和 N² 矩阵还可以覆盖某个 Asset 或 Action 的子项。
延伸阅读
文字稿
显示文字稿 (旁白和屏幕内容)
Introduction
Chapter two: live matrices in documents. Reviewers ask for traceability and verification matrices. In Holarch you don't fill them in by hand: a matrix in a document is rebuilt from the model whenever it is shown or exported.
You will insert a verification matrix into a specification, choose its scope, read the gaps it highlights, close a gap in the model, and add a traceability matrix.
Insert a matrix
Open the Bike-Share Dock system requirements. Its template ends with a verification approach, and section 11.1, Verification Matrix, holds an empty table to fill in by hand.
On screen: Documents → the SRS → Outline → 11.1 Verification Matrix.
Replace it with a live matrix. Click the section's text to edit it, select the empty table, and delete it.
On screen: Edit 11.1 → select → delete.
Open the plus menu, and choose Matrix. Pick the Requirements Verification Traceability Matrix. The scope starts on this document, which holds three of the project's six requirements. Choose Whole project, to cover them all.
On screen: + → Matrix… → RVTM → Scope: Whole project.
The preview lists each requirement with its verification method, its level, the test cases that verify it, and its status. Click Insert, then press Command Return to save the text.
On screen: Insert → Save.
Read the gaps
The matrix sits in the document with a dashed outline. Two rows are shaded as gaps. Show Available Bikes has a method but no test case yet. Anchored Without Digging has no verification method at all.
On screen: The live RVTM in 11.1, two gaps.
Close a gap
Close one gap in the model. Go to section 10, and select 10.2, Anchored Without Digging. In the inspector, click + Label and choose Inspection. The verification method is both a label and an attribute, so either one sets it.
On screen: Outline → 10.2 → inspector + Label → Inspection.
Go back to the matrix. The row for 10.2 now shows Inspection, without touching the matrix. It is still shaded, because no test case verifies it yet: the matrix shows the model as it is.
On screen: Outline → 11.1: the 10.2 row now shows Inspection.
Add an RTM
Add a traceability matrix the same way. Go to section 12, Traceability, edit its text, and insert the Requirements Traceability Matrix for the whole project: each requirement with its parent, the needs it traces from, what it traces to, and what satisfies it.
On screen: 12 Traceability → + → Matrix… → RTM → Whole project → Insert → Save.
Recap
The verification cross-reference matrix, with one column per method, works the same way. Let's recap. You inserted live matrices, chose their scope, read the gaps, and closed one in the model.
Next, you turn the document and its matrices into Word and Excel files.