Holarch
课程章节

培训 · 课程 6. 迁移到 Holarch · 第 6.5 章,共 5 章

6.5 导入后的清理 2:40

查找重复和薄弱的需求并加以修正,运行模型检查,并将分别导入的内容连接起来。

演示 Holarch 2.13。

您将学到

  • 对导入的文档运行质量检查并阅读其发现项
  • 删除重复的需求并改写含糊的需求
  • 运行模型检查,查找整个模型中的遗漏之处
  • 将导入的需求连接到满足它们的资产

在导入之后清理 Plant Inspection Drone 模型:运行需求质量检查以找到一条重复需求和一条薄弱需求,删除前者并改写后者,运行模型检查,并将导入的需求追溯到满足它们的已导入部件。

项目文件

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

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

练习

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

  1. 打开您在前几章中创建的 EO-1 Import Practice 项目(或按第 2 章的方法导入 EO-1 需求的 CSV)。
  2. 打开 需要与需求 → 质量,在范围栏中选择一个导入的文档,然后单击 检查质量。
  3. 如果您两次导入了相同的需求(Word 和 ReqIF),请在 数据库 中勾选重复项所在的行,并使用批量操作栏中的 删除条目… 将其删除。改写 2.5 Safe Mode Recovery 使其可测量,然后再次检查质量。
  4. 打开 验证 → 模型检查,打开规则 Requirement.8“没有设计实体满足的叶需求”。
  5. 如果您也导入了资产(第 4 章),请选择 2.1 Pointing Accuracy,在 追溯 中通过 + → 关联现有… 添加到 ADCS 的 satisfied by。再次运行模型检查。

当 2.5 的得分高于之前,且 Requirement.8 不再列出 2.1 时,即完成练习。

自测

  1. 质量检查看的是什么?模型检查看的又是什么?
  2. 为什么自动质量评分永远不会超过 78%?
  3. 为什么要在迁移后立即连接需求和部件?
显示答案
  1. 质量检查看的是什么?模型检查看的又是什么?

    质量检查根据良好需求的各项品质为每条需求的措辞评分。模型检查在整个模型中查找缺口,例如没有任何内容满足的需求、孤立的条目或无人执行的动作。

  2. 为什么自动质量评分永远不会超过 78%?

    Correct 和 Feasible 需要人工判断,因此检查永远不会将其标为已满足。您在审查需求后自行标记。

  3. 为什么要在迁移后立即连接需求和部件?

    它们来自不同的文件,彼此之间没有关联。从此以后,每条 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.