课程章节
培训 · 课程 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(在存储器中保存载荷数据的部件)交叉的单元格。然后在数据库中选择 OPS.9,查看其 追溯 部分中的 performed by。
- 如需带检查的分步演练,请运行教程 6“物理架构和分配”(帮助 → 教程)。
当“仅缺口”不再列出 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.