Holarch
课程章节

培训 · 课程 2. 需求和验证 · 第 2.4 章,共 6 章

2.4 基线和待检查的链接 2:40

将规格说明冻结为基线,更改一条需求,并审查该更改所涉及的内容。

演示 Holarch 2.13。

您将学到

  • 保存带审批记录的文档基线
  • 说明更改已批准的需求会对其状态和关联产生什么影响
  • 使用“差异”审查被标记的关联,并附注说明将其标记为已评审
  • 将基线与当前版本比较并导出更改

将 Bike-Share Dock 规格说明连同一项审批冻结为基线,更改一条已批准的需求,观察它回到评审状态且其关联被标记为待检查,审查该关联并附注说明将其标记为已评审,然后列出自基线以来的所有更改。

项目文件

  • 起始项目 (.holarch.json;管理项目 → 项目文件 ▾ → 导入项目 (.json)…)
  • 完成项目 (.holarch.json;管理项目 → 项目文件 ▾ → 导入项目 (.json)…)

视频从 holarch.app 播放;参见隐私政策。

练习

在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。

  1. 打开您的 EO-1 演示项目(或创建它:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程))。
  2. 打开 EO-1 System Requirements Specification,单击标题栏中的 版本 ▾,然后选择 保存基线…。将其命名为 PDR Baseline,在一行审批人中填写您的姓名和角色,然后单击 创建。
  3. 在 3.3 Depth of Discharge 的描述中将 30% 改为 25%,并阅读提示消息:该需求回到 In Review 状态,其关联需要检查。
  4. 打开 需要与需求 → 待检查的链接。在 3.3 的某一行上单击 差异,然后单击 标记为已评审…,写下您检查的内容,再单击 标记为已评审。
  5. 在文档中选择 版本 ▾ → 比较版本…,从 为 PDR Baseline,至 为 当前版本,然后单击 更改 (Excel)。
  6. 打开 控制与评审 → 基线和版本,在 SRR Baseline 旁边找到 PDR Baseline。如果要冻结整个模型而不是一个文档,应使用此页面标题栏中的 + 保存基线…。

当相对于 PDR Baseline 的更改报告列出 3.3 的编辑,且您审查过的关联不再出现在“待检查的链接”中时,即完成练习。

自测

  1. 为什么更改一条需求会标记依赖它的关联,而不仅仅是该需求本身?
  2. 文档基线与项目基线有什么区别?
  3. 将关联标记为已评审时,为什么要写说明?
显示答案
  1. 为什么更改一条需求会标记依赖它的关联,而不仅仅是该需求本身?

    另一端的条目(例如满足它的功能或验证它的测试)是对照旧文本检查的。每条关联都必须重新检查,以确认它是否仍然成立。

  2. 文档基线与项目基线有什么区别?

    文档基线冻结一个文档及其审批(版本 ▾ → 保存基线…)。项目基线冻结所有条目和关系(基线和版本 → + 保存基线…)。

  3. 将关联标记为已评审时,为什么要写说明?

    说明记录了检查的内容以及关联仍然成立的原因。它会添加到所关联条目的评论中,以便评审者日后追溯该决定。

延伸阅读

文字稿

显示文字稿 (旁白和屏幕内容)

Introduction

Chapter four: baselines and links to review. Once a specification is agreed, changes need control: everyone should know what changed, and what the change might break.

We baseline the Bike-Share Dock specification, then change one of its requirements.

Change control

A baseline is a read-only snapshot of a document, with its approvals. After it, every change is visible, and a change to a requirement marks the links that depend on it for review, until someone checks them.

On screen: Card: baselines and links to review.

First, give Show Available Bikes a link to depend on. In the Database, select it, and in its Trace section link it with satisfied by to the rental kiosk, which shows the numbers.

On screen: 4.1.1 → Trace → satisfied by + → Link existing… → Rental Kiosk.

Baseline

Open the specification, and the version menu in its title block. Choose Save Baseline, name it SRR Baseline for the requirements review, add your role, and click Create.

On screen: SRS → Current version ▾ → Save Baseline… → SRR Baseline → Create.

A change

Now a change. The team wants the kiosk to show the charge level of each e-bike too. Select Show Available Bikes, and update its statement in the inspector.

On screen: 4.1.1 → Item → new description.

The message says what happened, in the same undo step as the edit: the approved requirement went back to In Review, and its link to the rental kiosk now needs review.

On screen: The toast and the status.

Links to review

Open Needs and Requirements, then Links to Review. Each row is a link to check. Diff shows exactly how the text changed.

On screen: Links to Review → Diff.

The rental kiosk can show charge levels too, so the link still holds. Click Mark Reviewed, write what you checked, and click Mark Reviewed. The link no longer needs review.

On screen: Mark Reviewed… → note → Mark Reviewed.

Changes since the baseline

To see everything that changed since the review, open the specification's version menu again, and choose Compare Versions: from SRR Baseline to the current version.

On screen: SRS → version ▾ → Compare Versions… → SRR Baseline → Current.

The report lists each addition, removal and edit, ready to export to Excel or as a Word redline for a change board.

On screen: The change report.

Recap

Let's recap. You baselined the specification with an approval, changed an approved requirement, saw it return to review with its link flagged, marked the link reviewed with a note, and listed the changes since the baseline.

Next, you plan and run the tests that verify the requirements.