Holarch
課程章節

培訓 · 第 2 單元:需求與驗證 · 第 2.3 章,共 6 章

2.3 待決事項與核准 2:31

追蹤仍待決定的數值,並讓需求經過審查與核准。

展示 Holarch 2.13。

您將學到

  • 將尚未定案的數值標記為 TBD 或 TBR,並指定負責人與到期日
  • 在 TBD/TBR 登錄表上追蹤待決事項,並在定案時關閉
  • 將需求狀態設為 In Review,送交審查
  • 從核准頁面核准一個需求,並附理由拒絕另一個需求

將需求數值標記為待審查並指定負責人與到期日,在 TBD/TBR 登錄表上追蹤並關閉它,然後將需求從 Draft 推進到 In Review,並在核准頁面上核准或拒絕,同時記錄決定。

專案檔案

  • 起始專案 (.holarch.json;管理專案 → 專案檔案 ▾ → 匯入專案 (.json)…)
  • 完成的專案 (.holarch.json;管理專案 → 專案檔案 ▾ → 匯入專案 (.json)…)

影片從 holarch.app 播放;請參閱隱私權政策。

練習

在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。

  1. 開啟您的 EO-1 示範專案(或建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。
  2. 選取 1.5 Daily Collection Volume。在屬性面板的工作流程群組中,將 TBD/TBR 設為 TBR、TBD Owner 設為 Payload Lead,並設定兩週後的到期日。
  3. 開啟需要與需求 → TBD/TBR。找到逾期的那一列(3.5 Battery Thermal Control),以最終的溫度範圍改寫其陳述,然後按一下該列的關閉。
  4. 選取 6.3 Telemetry Archive(仍為 Draft),並在屬性面板的工作流程群組中將其狀態設為 In Review。
  5. 開啟需要與需求 → 核准。選取 6.3 Telemetry Archive,然後按一下審查列中的核准。如果對話方塊在需要重新審查下列出項目,請查看它們,然後按一下核准確認。
  6. 選取 5.3 Downlink Link Margin,按一下拒絕…,說明理由是鏈路預算尚未重新計算,然後確認。

當登錄表列出 1.5 且不再列出 3.5,而 6.3 顯示 Approved、5.3 顯示 Rejected,且各自附有您的姓名與時間時,即完成。

自我檢查

  1. TBD 與 TBR 有什麼不同?
  2. 為什麼要在陳述中寫入最佳估計值,而不是讓數值留空?
  3. 您編輯了一個 Approved 需求的文字。它的狀態會怎樣?
顯示答案
  1. TBD 與 TBR 有什麼不同?

    TBD 表示數值仍待確定。TBR 表示已有數值,但仍需審查。兩者都需要負責人與到期日。

  2. 為什麼要在陳述中寫入最佳估計值,而不是讓數值留空?

    設計工作可以依照估計值繼續進行,而登錄表確保有人在到期日前把它定案。

  3. 您編輯了一個 Approved 需求的文字。它的狀態會怎樣?

    它會回到 In Review,並附註文字在核准後已變更,讓變更在團隊依其進行開發前先經過審查。

延伸閱讀

文字稿

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

Introduction

Chapter three: open items and approvals. Some values are not settled when a requirement is written, and every requirement needs a review before the team builds to it.

We continue with the Bike-Share Dock specification.

Open items

TBD means a value is still to be determined. TBR means there is a value, but it still has to be reviewed. Either way, write your best estimate, and record who will settle it and by when.

On screen: Card: TBD and TBR.

The 10 seconds in Pay at the Kiosk depends on the payment provider, who has not confirmed it. In the Database, select the requirement, and on the Attributes tab set TBD/TBR to TBR, the owner, and the due date.

On screen: 5.1.1 → TBD/TBR = TBR, owner, due date.

Open Needs and Requirements, then TBD/TBR. The register lists every open item with its owner and due date, and counts the overdue ones and those with no owner. Export sends it to the owners as a spreadsheet.

On screen: Needs & Requirements → TBD/TBR.

When the provider confirms the value, edit the requirement if needed, and click Close on its row. The item leaves the register.

On screen: Close.

Approvals

Requirements move through a review: Draft while they are written, In Review when they are ready, then Approved or Rejected. Approved requirements are the ones the team builds to.

On screen: Card: the review workflow.

Send two requirements for review. In the Database, set the status of Show Available Bikes and of Operate in Cold and Heat to In Review.

On screen: Status → In Review, twice.

The reviewer opens Needs and Requirements, then Approvals. It lists every requirement in review. Select Show Available Bikes; the inspector shows the approval box. Click Approve.

On screen: Approvals → Show Available Bikes → Approve.

Select Operate in Cold and Heat. The city has not confirmed the temperature range, so click Reject, give the reason, and click OK. The decision is recorded with the reviewer's name and the time.

On screen: Operate in Cold and Heat → Reject… → reason → OK.

Recap

Let's recap. You marked a value to be reviewed, followed it on the TBD/TBR register and closed it, sent requirements for review, and approved one and rejected another with a reason.

Next, you freeze the specification in a baseline, and see what a change does to the links.