課程章節
培訓 · 第 7 單元:遵循流程 · 第 7.2 章,共 4 章
7.2 即時檢查及其指出的工作 2:21
讓模型告訴您哪些已完成、接下來要做什麼。
展示 Holarch 2.41。
您將學到
- 閱讀檢查的狀態(已完成、部分完成、尚未開始)及其詳細資訊
- 沿著檢查的「開啟」連結前往進行工作的頁面
- 完成檢查所需的工作,並觀察檢查與階段更新
- 勾選手動檢查,並說明 Holarch 會隨之記錄什麼
完成 Kossiakoff 指南的需要分析階段:Holarch 從模型讀取的檢查及其狀態與詳細資訊、前往進行工作之頁面的「開啟」連結、從範本建立而讓其檢查變為已完成的運作概念文件,以及手動勾選並記錄勾選者與時間的檢查。
練習
在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。
- 開啟您的 EO-1 示範專案(如果沒有,請建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。開啟計畫 → SE 流程,並選擇 Kossiakoff SE 方法(在流程中選擇,或選取它後按一下使用此流程)。
- 在需要分析中,閱讀哪些檢查已完成,以及其詳細資訊所計算的內容,例如需要 N1–N3。
- 在 Needs Analysis 文件檢查旁,按一下開啟。按一下 + 新增文件,輸入
EO-1 Needs Analysis,在範本適用於下選擇需要分析文件,挑選範本卡片,然後按一下建立。 - 回到 SE 流程,確認文件檢查已完成,且該階段的百分比已上升。
- 勾選關於調查既有系統與技術的手動檢查,閱讀是誰在何時勾選的,然後按 ⌘Z / Ctrl+Z,再重新勾選一次。
當 Needs Analysis 文件檢查已完成,且調查檢查顯示您的名稱與時間時,即完成。
自我檢查
- 帶有標記的檢查與帶有核取方塊的檢查有什麼不同?
- EO-1 以 Statement 記錄其需要。為什麼這些算作需要,而其章節標題卻不算?
- 「開啟」會帶您到哪裡?
顯示答案
帶有標記的檢查與帶有核取方塊的檢查有什麼不同?
標記(✓、◐ 或 ○)是從模型讀取的,會隨模型變更而改變。核取方塊則用於模型無法顯示的判斷,例如可行性;勾選它會記錄是誰在何時勾選。
EO-1 以 Statement 記錄其需要。為什麼這些算作需要,而其章節標題卻不算?
需要檢查會計算已追溯到需求的 Statement。文件中的章節 Statement 只有在經過追溯後才算作需要。以 Requirement 記錄的需要不算作需要。
「開啟」會帶您到哪裡?
前往進行該檢查工作的頁面,例如文件、品質、可追溯性矩陣或功能分析。回到 SE 流程即可看到檢查更新。
延伸閱讀
文字稿
顯示文字稿 (旁白與畫面內容)
Introduction
Chapter two: live checks. Most checks in a process guide are read from the model, so they change as the model changes. The rest are checks only people can make.
We continue on the Bike-Share Dock, in the needs analysis phase of the Kossiakoff guide.
Reading a check
Open Plan and Deliver, then SE Process. Each check has a mark in front of it: a tick when it is done, a half circle when it is partly done, and an empty circle when there is nothing yet.
On screen: Plan & Deliver → SE Process; the step cards.
Under each check, a short detail says what Holarch found. Record the stakeholder needs is done: the project already has its needs as statements. The project also has top-level functions and assets, so those checks are done too.
On screen: Done checks and their details.
From a check to the work
Describe how the system will be used is not done yet. Its detail says there is no concept of operations document. Click Open next to it.
On screen: Concept of Operations check → Open.
Open goes to the page where the work happens, here Documents. Click New Document, choose the type Concept of Operations Document, name it Bike-Share Dock Concept of Operations, and click Next.
On screen: Documents → + New Document → type, name, number → Next.
Choose the outline template, and click Finish. The new document has the usual sections of a concept of operations, ready to write.
On screen: Template: Concept of Operations (Outline) → Finish.
Go back to SE Process. The check is done now, and its detail counts the document. The needs analysis phase in the life cycle shows the higher percentage.
On screen: SE Process: the check is done; the phase percentage.
Checks people make
Some checks cannot be read from the model, such as whether meeting the needs is feasible. These have a checkbox instead of a mark. When your team has made the check, tick it.
On screen: Manual check: feasibility → tick.
Holarch records who ticked it, and when. Clear the box to take it back, and like every change, a tick is one undo step.
On screen: Checked by … on ….
Recap
Let's recap. Each check shows its state and what Holarch found. Open leads to the page where the work happens, the check follows the model as you work, and the checks only people can make are ticked by hand, with who and when.
Next, you move between phases and prepare a gate review.