課程章節
培訓 · 第 3 單元:行為與架構 · 第 3.3 章,共 6 章
3.3 分配 2:33
決定由停車站的哪個部分執行每項功能,並找出剩下的功能。
展示 Holarch 1.27。
您將學到
- 以 performed by 關係建立動作對資產的可追溯性矩陣
- 在矩陣中按一下,即可將功能分配給執行它的資產
- 使用「僅缺口」找出沒有任何資產執行的動作
- 在項目的「追溯」區段中確認分配
將 Bike-Share Dock 的功能與 Rent a Bike 的步驟分配給執行它們的零件:在以 performed by 關係建立的動作對資產矩陣中進行,然後使用「僅缺口」列出仍沒有執行者的內容。
練習
在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。
- 開啟您的 EO-1 示範專案,或建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程)。
- 開啟驗證 → 可追溯性矩陣。按一下列標籤,將列來自設為根實體下的階層,並選擇 OPS Run Nominal Imaging Pass 作為根,然後按一下完成。
- 按一下欄標籤,將欄來自設為某類別的所有實體,類別為 Asset,並將關係設為 performed by。
- 勾選僅缺口。剩下 OPS.9 Hold Data Onboard,以及由系統整體執行的根 OPS。
- 按一下 OPS.9 Hold Data Onboard 與 1.4 C&DH 交會的儲存格,1.4 C&DH 是在儲存裝置中保存酬載資料的零件。接著在資料庫中選取 OPS.9,並閱讀其追溯區段中的 performed by。
- 若要進行有檢查的逐步練習,請執行教學課程 6 Physical Architecture and Allocation(說明 → 教學課程)。
當「僅缺口」不再列出 OPS.9,且其「追溯」區段顯示 performed by 1.4 C&DH 時,即完成。
自我檢查
- 為什麼要將「關係」設為 performed by,而不是「所有允許的」?
- 分配儲存在哪裡?
- 「僅缺口」顯示了一列。這一定是錯誤嗎?
顯示答案
為什麼要將「關係」設為 performed by,而不是「所有允許的」?
選擇單一類型時,在空白儲存格上按一下會正好建立該關係。若使用所有允許的類型,當有多種類型適用時,Holarch 必須詢問您指的是哪一種。
分配儲存在哪裡?
儲存在項目上:Action 上為 performed by,Asset 上為 performs。矩陣只是這些關聯的檢視,因此任何其他檢視(例如項目的「追溯」區段)都會顯示相同的分配。
「僅缺口」顯示了一列。這一定是錯誤嗎?
不一定。最上層的運作或功能可能由系統整體執行,因此不需要單一執行者。其餘的每個步驟通常需要一個執行者。
延伸閱讀
文字稿
顯示文字稿 (旁白與畫面內容)
Introduction
Welcome back. Functions say what the dock does. Its parts, the assets, say what it is. Allocation joins the two.
In this chapter you allocate every function to the part that performs it.
What allocation is
Each function should be performed by a part of the system. A function nothing performs will not happen, and a part with no function is weight with no job. In the model, allocation is one relationship: performed by.
On screen: Card: allocation.
Set up the matrix
A matrix is the quickest way to allocate many functions at once. Open Verification, then Traceability Matrix.
On screen: Verification → Traceability Matrix.
Click Rows, and choose all entities of the class Action. Set Columns to the class Asset the same way. Then set the relationship to performed by, so a click on a cell creates exactly that.
On screen: Rows → class Action; Columns → class Asset; Relationship: performed by.
Allocate the functions
The top-level functions first. Three were allocated in Getting Started, and the matrix marks them: Rent a Bike by the Rental Kiosk, Return a Bike by the Docking Bay, and Charge Bikes by the Charging Unit.
On screen: Existing marks: F.1, F.2, F.3.
Allocate the other two. Take Payment is performed by the Back Office Service: click the cell where its row and that column meet. Report Dock Status is performed by the kiosk, which talks to the back office.
On screen: F.4 × S.4, F.5 × S.2.
The steps of Rent a Bike from the last chapter need performers too. Identify Rider happens at the kiosk, Check Account in the back office, and Unlock Bay in the docking bay.
On screen: F.1.1 × S.2, F.1.2 × S.4, F.1.3 × S.1.
Find the gaps
Now turn on Gaps only. The matrix keeps only the rows and columns with no link: the steps still to allocate, and the top-level function, which is done by the dock as a whole.
On screen: Gaps only.
The rest follow the same way. Show Bay Number and Start Rental belong to the kiosk and the back office, and Relock Bay to the docking bay.
On screen: F.1.4 × S.2, F.1.6 × S.4, F.1.7 × S.1.
On the item
Allocation is stored on the items, not in the matrix. Select Rent a Bike in the Database, and open its Trace section: performed by lists the Rental Kiosk.
On screen: Database → F.1 → Trace.
Recap
Let's recap. You set up a matrix of actions against assets with performed by, allocated the functions and the steps with one click each, and used Gaps only to find what was left.
Next, you define how the dock's parts connect: interfaces.