課程章節
培訓 · 第 2 單元:需求與驗證 · 第 2.2 章,共 6 章
2.2 將需要追溯到需求 2:07
將每個需求追溯到其來源的需要或約束,並找出缺口。
展示 Holarch 1.27。
您將學到
- 在屬性面板中將需求追溯到其來源的需要
- 從列查詢與欄查詢建立可追溯性矩陣
- 按一下矩陣中的儲存格來建立追溯關聯
- 以「僅缺口」找出未追溯的需求,並決定如何填補每個缺口
將 Bike-Share Dock 的需求追溯到其來源的利害關係人需要與約束:在屬性面板中建立一個關聯,在由兩個查詢建立的可追溯性矩陣中建立許多關聯,然後處理缺口:沒有來源的需求,它們指出缺少的需要,或是沒有人要求的需求。
練習
在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。
- 開啟您的 EO-1 示範專案(或建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。
- 在資料庫中選取 1.6.2 Off-Nadir Imaging。在追溯中的 traced from 上(如果沒有列出,請勾選顯示所有關係),按一下 + → 關聯現有…,勾選 N2 Twice-Weekly Revisit,然後按一下關聯所選。
- 開啟驗證 → 可追溯性矩陣。將列設為查詢
class:Requirement、欄設為查詢number:N*,並選擇關係 traced from。 - 按一下 N2 Twice-Weekly Revisit 下方 1.5 Daily Collection Volume 的空白儲存格:每日的收集量正是讓重訪得以實現的因素。
- 勾選僅缺口。為 1.7 Mission Lifetime 補上缺少的需要:以下一個可用的 N 編號(例如
N4)建立 StatementTwo Growing Seasons,然後在矩陣中將它關聯到 1.7。 - 若要進行有檢查的逐步練習,請執行教學課程 3 Trace Requirements(說明 → 教學課程)。
當勾選「僅缺口」時不再出現 1.5、1.6.2 與 1.7,即完成。
自我檢查
- 將需要追溯到需求能回答哪三個問題?
- 「僅缺口」顯示一個沒有來源的需求。正確的修正方式一定是將它關聯到最接近的需要嗎?
- 什麼時候用可追溯性矩陣建立關聯比用屬性面板更好?
顯示答案
將需要追溯到需求能回答哪三個問題?
需求為何存在、每個需要是否都有需求涵蓋,以及當需要變更時哪些需求會跟著變更。
「僅缺口」顯示一個沒有來源的需求。正確的修正方式一定是將它關聯到最接近的需要嗎?
不是。要嘛是缺少某個需要而應補上,要嘛是該需求並不需要而應移除。只為了填補缺口而建立的關聯會掩蓋這個問題。
什麼時候用可追溯性矩陣建立關聯比用屬性面板更好?
當您要在兩組項目之間建立許多關聯時:您能看到整個格線、按一下就建立一個關聯,並立即看到缺口。
延伸閱讀
文字稿
顯示文字稿 (旁白與畫面內容)
Introduction
Chapter two: tracing needs to requirements. Every requirement should come from somewhere: a stakeholder need, a constraint, or a higher requirement. Tracing records where.
We trace the Bike-Share Dock's requirements to its needs and constraints.
Why trace
Tracing answers three questions. Why does this requirement exist? Is every need covered by a requirement? And when a need changes, which requirements change with it?
On screen: Card: why trace.
One link
One link at a time works in the inspector. In the Database, select Show Available Bikes. In its Trace section, add a traced from link to the need Find a Bike Nearby.
On screen: 4.1.1 → Trace → traced from + → Link existing… → N.1.
Many links
For many links, use the Traceability Matrix. Open Verification, then Traceability Matrix. Click Rows, and set them from a query: every requirement.
On screen: Verification → Traceability Matrix → Rows → Query → class:Requirement.
Set the columns from a query too: the needs and constraints, whose numbers start with N and C. Then choose the relationship, traced from.
On screen: Columns → Query → number:N.* OR number:C.* → Relationship: traced from.
Each click on an empty cell creates a link. Detect a Returned Bike comes from the operator's need to return bikes without staff. The two design constraints, the footprint and the anchoring, come from the sidewalk constraint.
On screen: Click three cells.
Find the gaps
Now look for gaps. Check Gaps only: the matrix keeps the requirements that are traced to nothing in the columns.
On screen: Gaps only.
Each gap is a question for the team. Either a need is missing, such as the rider's need to pay quickly, or the requirement is not needed. Add the missing need, or delete the requirement, but do not leave it untraced.
On screen: The gaps.
Recap
Let's recap. You traced one requirement in the inspector, built a Traceability Matrix from two queries, created links with a click, and found the requirements that still have no source.
Next, open items and approvals.