课程章节
培训 · 课程 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“追溯需求”(帮助 → 教程)。
当勾选“仅缺口”后不再出现 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.