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 準則仍未完成。它要求什麼?

    以 traced to 建立的、從需要(Statement)到回應它們之需求的關聯。這是建模工作,而不是勾選方框。

延伸閱讀

文字稿

顯示文字稿 (旁白與畫面內容)

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.