課程章節
培訓 · 第 6 單元:移轉到 Holarch · 第 6.5 章,共 5 章
6.5 匯入後的整理 2:40
找出重複與薄弱的需求並加以修正、執行模型檢查,並連接分別匯入的內容。
展示 Holarch 2.13。
您將學到
- 對匯入的文件執行品質檢查,並閱讀其發現事項
- 移除重複的需求,並改寫含糊的需求
- 執行模型檢查,找出整個模型中的未竟之處
- 將匯入的需求連接到滿足它們的資產
在匯入後整理 Plant Inspection Drone 模型:執行需求品質檢查以找出一個重複需求與一個薄弱需求,刪除前者並改寫後者,執行模型檢查,並將匯入的需求追溯到滿足它們的匯入零件。
練習
在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。
- 開啟您在前面章節中的
EO-1 Import Practice專案(或依第 2 章的做法匯入 EO-1 需求的 CSV)。 - 開啟需要與需求 → 品質,在範圍列中選擇其中一份匯入的文件,然後按一下檢查品質。
- 如果您將相同的需求匯入了兩次(Word 與 ReqIF),請在資料庫中勾選重複項目的列,並以批次列中的刪除項目…將其刪除。改寫 2.5 Safe Mode Recovery 使其可量測,然後再次檢查品質。
- 開啟驗證 → 模型檢查,並開啟規則 Requirement.8「沒有任何設計實體滿足的末端需求」。
- 如果您也匯入了資產(第 4 章),請選取 2.1 Pointing Accuracy,並在追溯中以 + → 關聯現有… 對 ADCS 新增 satisfied by。再次執行模型檢查。
當 2.5 的分數比之前高,且 Requirement.8 不再列出 2.1 時,即完成。
自我檢查
- 品質檢查檢視什麼,而模型檢查又檢視什麼?
- 為什麼自動品質分數永遠不會超過 78%?
- 為什麼要在移轉後立即連接需求與零件?
顯示答案
品質檢查檢視什麼,而模型檢查又檢視什麼?
品質檢查依照良好需求應有的品質,為每個需求的用語評分。模型檢查則檢視整個模型中的缺口,例如沒有任何東西滿足的需求、孤立的項目,或沒有人執行的動作。
為什麼自動品質分數永遠不會超過 78%?
Correct 與 Feasible 需要人的判斷,因此檢查永遠不會將它們標為已達成。您在審查需求後自行標記它們。
為什麼要在移轉後立即連接需求與零件?
它們來自不同的檔案,彼此之間沒有關聯。從那時起,每個 satisfied by 關聯都會提供給可追溯性、涵蓋率與模型檢查。
延伸閱讀
文字稿
顯示文字稿 (旁白與畫面內容)
Introduction
Chapter five: cleaning up after import. Imported data carries its old problems along, and the pieces arrive from different files unconnected. A short clean-up pass fixes both.
This is the last chapter of the migration track.
Quality check
Open Needs and Requirements, then Quality. Choose the imported tracker, and click Check Quality. Every requirement is scored against the qualities of a good requirement, and the findings say what to fix.
On screen: Quality → Document: PID Requirements Tracker → Check Quality.
Two findings stand out. Requirement 2.4 says the same thing as 2.1, in slightly different words: a duplicate from the old tracker. And 3.2 is vague: fast and easy to use cannot be measured, and the and joins two requirements in one.
On screen: Findings for 2.4 and 3.2.
Fix the findings
Remove the duplicate. In the Database, check the row of Crack Imaging, click Delete Entity in the bulk bar, and confirm.
On screen: Database → check 2.4 → Delete Entity… → Delete.
Then rewrite the vague one. Select Easy Operation, click its description, and replace it with something testable.
On screen: Easy Operation → Item → Description.
Run the quality check again. The duplicate is gone, and the rewritten requirement scores better.
On screen: Quality → Check Quality again.
Model checks
The model checks look at the whole model, not just the wording. Open Verification, then Model Checks. They list loose ends, such as requirements nothing satisfies yet, and each finding links to the item.
On screen: Verification → Model Checks.
Connect what came in
The requirements and the parts came from different files, so nothing connects them yet. Connect them. Select Crack Resolution in the Database. In Trace, click the plus on satisfied by, choose Link existing, and pick the camera payload.
On screen: 2.1 → Trace → satisfied by + → Link existing… → Camera Payload.
Wall Thickness is satisfied by the ultrasonic probe, in the same way. Each link you add now feeds traceability, coverage and the model checks from here on.
On screen: 2.2 → Trace → satisfied by + → Link existing… → Ultrasonic Probe.
Recap
Let's recap. You ran the quality check, removed a duplicate, rewrote a weak requirement, ran the model checks, and connected the imported requirements to the imported parts.
That completes Migrating to Holarch. You can now plan a migration, bring in spreadsheets, Word documents, ReqIF files and models from other tools, and clean up what arrives.
On screen: Track complete card, then end card.