Holarch
课程章节

培训 · 课程 7. 遵循流程 · 第 7.4 章,共 4 章

7.4 基于模型开展技术评审 2:38

检查评审的进入准则并准备其评审包。

演示 Holarch 2.13。

← 7.3 阶段和关口 · 所有章节

您将学到

  • 在正式生命周期中找到指定的评审并阅读其进入准则
  • 通过“打开”链接满足一条进入准则
  • 添加评审的里程碑和评审包
  • 说明指南显示什么、评审委员会决定什么

使用 NASA 项目生命周期指南准备系统需求评审 (SRR):关键决策点、某一阶段的评审及其从模型读取的进入准则、从准则的“打开”链接运行的质量检查、根据模板创建的系统工程管理计划,以及评审的里程碑和评审包。

项目文件

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

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

练习

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

  1. 打开您的 EO-1 演示项目(如果没有,请创建:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程))。打开 计划 → SE 流程,在 流程 中选择 NASA 项目生命周期(或选中它后单击 使用此流程)。
  2. 单击 Phase B: Preliminary design and technology completion,阅读 PDR 的进入准则:分配到组件、接口、TPM、缓解措施和验证方法。
  3. 在一条未满足的准则旁边单击 打开,完成其中一项工作,例如设置 2.5 Safe Mode Recovery 的 Verification Method。
  4. 返回 SE 流程,查看该准则的计数。
  5. 在 PDR 下单击 添加关口里程碑 和 创建评审包,然后打开评审包,查看它收集了哪些文档。

当 PDR 显示其里程碑和评审包,且您处理过的准则多计入一个条目时,即完成练习。

自测

  1. 某次评审的所有进入准则都已满足。设计是否就绪?
  2. 为什么要在评审之前而不是在评审时阅读进入准则?
  3. 关于将期望追溯到需求的 SRR 准则仍未满足。它要求什么?
显示答案
  1. 某次评审的所有进入准则都已满足。设计是否就绪?

    不一定。指南显示的是模型中的内容;设计是否良好由评审委员会决定。

  2. 为什么要在评审之前而不是在评审时阅读进入准则?

    Holarch 从模型读取这些准则,因此团队能在还有时间完成工作时就看到缺少什么。

  3. 关于将期望追溯到需求的 SRR 准则仍未满足。它要求什么?

    从需要(Statement)到回应这些需要的需求的关联,通过 traced to 建立。这是建模工作,而不是一个打勾的方框。

延伸阅读

文字稿

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

Introduction

Chapter four: running a technical review from the model. Formal life cycles name their reviews, and each review has entry criteria. Holarch reads the criteria from the model, so the team sees before the review what is ready.

We prepare the System Requirements Review of the Bike-Share Dock, using the NASA project life cycle.

Reviews and entry criteria

Open SE Process, and choose NASA project life cycle in the Process list. The phases run from Pre-Phase A, concept studies, to Phase F, closeout. The diamond on each phase names the key decision point that ends it.

On screen: SE Process → Process ▾ → NASA project life cycle.

Click Phase A, concept and technology development. Its reviews are at the bottom: the System Requirements Review, and the Mission or System Definition Review. Each lists its entry criteria.

On screen: Phase A → Reviews and gates.

Read the SRR's criteria. The system requirements are defined. The requirements have not been quality-checked yet, and there is no systems engineering management plan.

On screen: SRR entry criteria.

Meeting the criteria

Click Open next to the quality criterion. On the Quality page, click the run button to check every requirement. Each one gets a score, and the findings explain what to improve.

On screen: Open → Quality → run the check.

Now the management plan. Go back to SE Process, and click Open next to it. Create a new document of the type Systems Engineering Management Plan Document, from its outline.

On screen: SE Process → Open → + New Document: SEMP.

Back on SE Process, both criteria are met. The one still open, expectations traced to requirements, is real work for the team: it asks for links between the needs and the requirements that answer them.

On screen: SE Process → Phase A: criteria met; tracing still open.

Milestone and package

Click Add Gate Milestone and Create Review Package under the SRR. The package collects the requirements specification and the new management plan for the review board.

On screen: SRR: Add Gate Milestone, Create Review Package.

The guide shows what the model holds. It does not judge whether a design is good: that is the review board's decision. When the review has passed, make the phase current and move on.

On screen: Make Current Phase.

Recap

Let's recap. You switched to the NASA life cycle, read a review's entry criteria, met two of them from their Open links, added the review's milestone and package, and moved the project on.

That completes Track 7. More tracks are at holarch.app slash training.