Holarch
課程章節

培訓 · 第 1 單元:入門 · 第 1.3 章,共 8 章

1.3 屬性與關係 3:29

描述項目,並將它們連接成模型。

展示 Holarch 2.41。

您將學到

  • 在屬性面板中編輯項目的屬性,例如需求的理由
  • 以「關聯現有…」關聯項目,並從兩端閱讀每個關聯
  • 將資產分解為零件,並將功能分配給執行它的零件
  • 將功能追溯到它所滿足的需求
  • 在項目檢視中沿著相關項目瀏覽模型

以屬性(描述、理由、狀態)描述 Bike-Share Dock 的項目,並以關係將它們連接起來:將需求追溯到其來源需要,將系統分解為其零件,說明哪個零件執行哪項功能、哪項功能滿足哪項需求,並在屬性面板與項目檢視中從兩端閱讀每個關聯。

專案檔案

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

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

練習

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

  1. 開啟您的 EO-1 示範專案(或建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。
  2. 在資料庫中,選取 2.5 Safe Mode Recovery,並在屬性面板中輸入理由(為什麼太空船必須自行離開安全模式)。
  3. 選取 F10 Enter Safe Mode。在追溯中找到 satisfies(若未列出,請勾選顯示所有關係),按一下 + → 關聯現有…,勾選 2.5 Safe Mode Recovery,然後按一下關聯所選。選取 2.5,並在 satisfied by 下找到同一個關聯。
  4. 選取 1.4 C&DH,勾選顯示所有關係,並以 performs 將其關聯到 OPS.9 Hold Data Onboard,這是唯一一個尚無零件執行的運作步驟。
  5. 選取 2.2 Mission Operations Center。在 decomposed by 上,按一下 + → 新增 Asset…,並建立 Image Processing Server。
  6. 按兩下 F10 Enter Safe Mode 以開啟項目檢視,然後依序按一下相關名稱:從 F10 到 1.4 C&DH,再從那裡到 1 EO-1 Spacecraft。

當 2.5 Safe Mode Recovery 的項目檢視在 satisfied by 下列出 F10,且 OPS.9 在 performed by 下列出 1.4 C&DH 時,即完成。

自我檢查

  1. 您從 F10 以 satisfies 新增了一個關聯。為什麼 2.5 不需任何額外步驟就顯示 satisfied by?
  2. 為什麼「關聯現有…」中的選擇器不會列出專案中的每個項目?
  3. 以 performs 將資產關聯到動作,在系統工程術語中記錄了什麼?
顯示答案
  1. 您從 F10 以 satisfies 新增了一個關聯。為什麼 2.5 不需任何額外步驟就顯示 satisfied by?

    每個關係在每個方向都有一個名稱。它是同一個關聯,從功能讀作 satisfies,從需求讀作 satisfied by。

  2. 為什麼「關聯現有…」中的選擇器不會列出專案中的每個項目?

    它只列出該關係允許此項目使用之類別的項目,因此您無法建立結構描述未定義的關聯。

  3. 以 performs 將資產關聯到動作,在系統工程術語中記錄了什麼?

    將功能分配給執行該功能的實體零件。

延伸閱讀

文字稿

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

Introduction

Chapter three: attributes and relationships. Attributes describe an item. Relationships connect items, and they are what turn a list of items into a model.

We continue with the Bike-Share Dock project from the last chapter.

Attributes

Open the Database, and select the requirement Unlock a Bike. The inspector's Item section holds its number, name and description. Below it, Attributes holds the attributes of its class, such as a rationale and a status.

On screen: Database → 1.1 Unlock a Bike → Attributes.

A rationale says why the requirement exists, which helps when someone later wants to change it. Type it in, and click elsewhere to save.

On screen: Rationale.

Asset and Action have their own attributes, such as a function's duration, which simulation uses later. A project owner can add attributes to any class in the Schema.

On screen: Attributes of an Action.

Relate items

Now the relationships. Select Unlock a Bike again, and click Trace in the inspector. It groups the relations of this class by purpose. Find traced from, click its plus button, and choose Link existing.

On screen: Trace → traced from → + → Link existing…

The picker lists only items that this relation allows. Check Find a Bike Nearby, the need this requirement answers, and click Link Selected.

On screen: Pick N.1 → Link Selected.

Every relationship has a name in each direction. Select the need, and its Trace shows the same link the other way round: Find a Bike Nearby is traced to Unlock a Bike.

On screen: N.1 → traced to 1.1.

Structure and allocation

Next, the system's structure. Select Bike-Share Dock, find decomposed by, and relate its three parts at once: the docking bay, the kiosk and the charging unit. The back office service is an external system, outside the dock, so it is not one of its parts.

On screen: S.0 → decomposed by → S.1–S.3.

Then say which part does what. Select the kiosk. Performs has no links yet, so tick Show all relations, and relate the kiosk with performs to Rent a Bike and Take Payment. In systems engineering terms, you are allocating functions to the physical parts.

On screen: S.2 Kiosk → Show all relations → performs → F.1, F.4.

The docking bay performs Return a Bike, and the charging unit performs Charge Bikes. They are related the same way.

On screen: S.1, S.3 performs (entered off camera).

Finally, link the function to the requirement it meets. Select Rent a Bike, and relate it with satisfies to Unlock a Bike.

On screen: F.1 → satisfies → 1.1.

Reading the links

Trace shows the relations that have links, plus a few kept visible even when empty. Untick Show all relations, and you see just what this function is connected to.

On screen: Trace → Show all relations off.

Double-click the row to open the Entity View. It shows the same sections on a full page, and linking works here too.

On screen: Entity View of Rent a Bike.

Click a related item's name to move to it. From the function, go to the kiosk that performs it, and from there to the dock it belongs to. This is how you walk the model.

On screen: Entity View: → Kiosk → Bike-Share Dock.

Recap

Let's recap. You edited attributes, related items with Link existing, read each link from both ends, decomposed the system, allocated functions to parts, and walked the links in the Entity View.

Next, you draw part of this model as a diagram.