課程章節
培訓 · 第 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.