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