Holarch
課程章節

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

2.4 基準線與待審查的關聯 2:40

將規格書凍結在基準線中、變更一個需求,並審查該變更影響到什麼。

展示 Holarch 2.13。

您將學到

  • 儲存附有核准紀錄的文件基準線
  • 說明變更已核准的需求會對其狀態與關聯造成什麼影響
  • 以「差異」審查被標記的關聯,並附上備註將其標記為已審查
  • 將基準線與目前版本比較,並匯出變更

將 Bike-Share Dock 規格書連同核准凍結在基準線中,變更一個已核准的需求,看它回到審查狀態且其關聯被標記為待審查,審查該關聯並附上備註標記為已審查,然後列出自基準線以來的所有變更。

專案檔案

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

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

練習

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

  1. 開啟您的 EO-1 示範專案(或建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。
  2. 開啟 EO-1 System Requirements Specification,按一下標題欄中的版本 ▾,然後選擇儲存基準線…。將它命名為 PDR Baseline,以您的姓名與角色填寫一列核准者,然後按一下建立。
  3. 在 3.3 Depth of Discharge 的描述中將 30% 改為 25%,並閱讀快顯通知:該需求回到 In Review,且其關聯需要審查。
  4. 開啟需要與需求 → 待檢查的連結。在 3.3 的某一列上按一下差異,接著按標記為已審查…,寫下您檢查的內容,然後按一下標記為已審查。
  5. 在文件中選擇版本 ▾ → 比較版本…,將從設為 PDR Baseline、到設為目前版本,然後按一下變更 (Excel)。
  6. 開啟控制與審查 → 基準線和版本,在 SRR Baseline 旁找到 PDR Baseline。若要凍結整個模型而不只是一份文件,請使用此頁頁首的 + 儲存基準線…。

當 PDR Baseline 的變更報告列出 3.3 的編輯,且您審查過的關聯不再出現在「待檢查的連結」中時,即完成。

自我檢查

  1. 為什麼變更需求會標記依賴它的關聯,而不只是標記該需求本身?
  2. 文件基準線與專案基準線有什麼不同?
  3. 將關聯標記為已審查時,為什麼要寫備註?
顯示答案
  1. 為什麼變更需求會標記依賴它的關聯,而不只是標記該需求本身?

    另一端的項目,例如滿足它的功能或驗證它的測試,都是依照舊文字檢查的。每個關聯都必須重新檢查,看它是否仍然成立。

  2. 文件基準線與專案基準線有什麼不同?

    文件基準線凍結一份文件及其核准(版本 ▾ → 儲存基準線…)。專案基準線凍結每個項目與關係(基準線和版本 → + 儲存基準線…)。

  3. 將關聯標記為已審查時,為什麼要寫備註?

    備註記錄檢查了什麼,以及關聯為何仍然成立。它會加入關聯項目的留言中,讓審查者日後能追蹤這項決定。

延伸閱讀

文字稿

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

Introduction

Chapter four: baselines and links to review. Once a specification is agreed, changes need control: everyone should know what changed, and what the change might break.

We baseline the Bike-Share Dock specification, then change one of its requirements.

Change control

A baseline is a read-only snapshot of a document, with its approvals. After it, every change is visible, and a change to a requirement marks the links that depend on it for review, until someone checks them.

On screen: Card: baselines and links to review.

First, give Show Available Bikes a link to depend on. In the Database, select it, and in its Trace section link it with satisfied by to the rental kiosk, which shows the numbers.

On screen: 4.1.1 → Trace → satisfied by + → Link existing… → Rental Kiosk.

Baseline

Open the specification, and the version menu in its title block. Choose Save Baseline, name it SRR Baseline for the requirements review, add your role, and click Create.

On screen: SRS → Current version ▾ → Save Baseline… → SRR Baseline → Create.

A change

Now a change. The team wants the kiosk to show the charge level of each e-bike too. Select Show Available Bikes, and update its statement in the inspector.

On screen: 4.1.1 → Item → new description.

The message says what happened, in the same undo step as the edit: the approved requirement went back to In Review, and its link to the rental kiosk now needs review.

On screen: The toast and the status.

Links to review

Open Needs and Requirements, then Links to Review. Each row is a link to check. Diff shows exactly how the text changed.

On screen: Links to Review → Diff.

The rental kiosk can show charge levels too, so the link still holds. Click Mark Reviewed, write what you checked, and click Mark Reviewed. The link no longer needs review.

On screen: Mark Reviewed… → note → Mark Reviewed.

Changes since the baseline

To see everything that changed since the review, open the specification's version menu again, and choose Compare Versions: from SRR Baseline to the current version.

On screen: SRS → version ▾ → Compare Versions… → SRR Baseline → Current.

The report lists each addition, removal and edit, ready to export to Excel or as a Word redline for a change board.

On screen: The change report.

Recap

Let's recap. You baselined the specification with an approval, changed an approved requirement, saw it return to review with its link flagged, marked the link reviewed with a note, and listed the changes since the baseline.

Next, you plan and run the tests that verify the requirements.