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.