课程章节
培训 · 课程 2. 需求和验证 · 第 2.3 章,共 6 章
2.3 未关闭条目和审批 2:31
跟踪仍待确定的数值,并让需求经过评审和审批。
演示 Holarch 2.13。
您将学到
- 将未确定的数值标记为 TBD 或 TBR,并指定负责人和截止日期
- 在 TBD/TBR 登记册上跟踪未关闭条目,并在确定后关闭
- 将需求状态设为 In Review,以提交评审
- 在“审批”页面上批准一条需求,并附理由拒绝另一条
将某个需求值标记为待审查并指定负责人和截止日期,在 TBD/TBR 登记册上跟踪并关闭它,然后将需求从 Draft 推进到 In Review,并在“审批”页面上批准或拒绝,同时记录决定。
练习
在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。
- 打开您的 EO-1 演示项目(或创建它:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程))。
- 选择 1.5 Daily Collection Volume。在属性面板的 工作流 组中,将 TBD/TBR 设为 TBR,TBD Owner 设为
Payload Lead,截止日期设为两周后。 - 打开 需要与需求 → TBD/TBR。找到逾期的行(3.5 Battery Thermal Control),用最终温度范围改写其语句,然后单击该行的 关闭。
- 选择 6.3 Telemetry Archive(仍为 Draft),在属性面板的 工作流 组中将其 Status 设为 In Review。
- 打开 需要与需求 → 审批。选择 6.3 Telemetry Archive,然后在评审条带中单击 批准。如果对话框在 需要重新评审 下列出条目,请查看它们,然后单击 批准 确认。
- 选择 5.3 Downlink Link Margin,单击 拒绝…,给出链路预算尚未重新计算的理由,然后确认。
当登记册列出 1.5 且不再列出 3.5,6.3 显示 Approved、5.3 显示 Rejected,并且两者都带有您的姓名和时间时,即完成练习。
自测
- TBD 和 TBR 有什么区别?
- 为什么要在语句中写入最佳估计值,而不是将值留空?
- 您编辑了一条 Approved 需求的文本。其状态会怎样?
显示答案
TBD 和 TBR 有什么区别?
TBD 表示数值仍待确定。TBR 表示已有数值,但仍需审查。两者都需要负责人和截止日期。
为什么要在语句中写入最佳估计值,而不是将值留空?
设计工作可以基于估计值继续进行,而登记册确保有人在截止日期前将其确定下来。
您编辑了一条 Approved 需求的文本。其状态会怎样?
它回到 In Review 状态,并附有文本在批准后已更改的说明,因此在团队据此开展工作之前,该更改会先经过评审。
延伸阅读
文字稿
显示文字稿 (旁白和屏幕内容)
Introduction
Chapter three: open items and approvals. Some values are not settled when a requirement is written, and every requirement needs a review before the team builds to it.
We continue with the Bike-Share Dock specification.
Open items
TBD means a value is still to be determined. TBR means there is a value, but it still has to be reviewed. Either way, write your best estimate, and record who will settle it and by when.
On screen: Card: TBD and TBR.
The 10 seconds in Pay at the Kiosk depends on the payment provider, who has not confirmed it. In the Database, select the requirement, and on the Attributes tab set TBD/TBR to TBR, the owner, and the due date.
On screen: 5.1.1 → TBD/TBR = TBR, owner, due date.
Open Needs and Requirements, then TBD/TBR. The register lists every open item with its owner and due date, and counts the overdue ones and those with no owner. Export sends it to the owners as a spreadsheet.
On screen: Needs & Requirements → TBD/TBR.
When the provider confirms the value, edit the requirement if needed, and click Close on its row. The item leaves the register.
On screen: Close.
Approvals
Requirements move through a review: Draft while they are written, In Review when they are ready, then Approved or Rejected. Approved requirements are the ones the team builds to.
On screen: Card: the review workflow.
Send two requirements for review. In the Database, set the status of Show Available Bikes and of Operate in Cold and Heat to In Review.
On screen: Status → In Review, twice.
The reviewer opens Needs and Requirements, then Approvals. It lists every requirement in review. Select Show Available Bikes; the inspector shows the approval box. Click Approve.
On screen: Approvals → Show Available Bikes → Approve.
Select Operate in Cold and Heat. The city has not confirmed the temperature range, so click Reject, give the reason, and click OK. The decision is recorded with the reviewer's name and the time.
On screen: Operate in Cold and Heat → Reject… → reason → OK.
Recap
Let's recap. You marked a value to be reviewed, followed it on the TBD/TBR register and closed it, sent requirements for review, and approved one and rejected another with a reason.
Next, you freeze the specification in a baseline, and see what a change does to the links.