Holarch
课程章节

培训 · 课程 1. 入门 · 第 1.4 章,共 8 章

1.4 您的第一张图 4:00

绘制模型,在图上添加内容,并在每个视图中看到同一个模型。

演示 Holarch 1.27。

您将学到

  • 通过 + 新建图 创建系统的 Asset 图
  • 在图上显示每个部件执行的功能
  • 在图上添加部件和 Conduit,并在数据库中找到它们
  • 切换图的类型,以层次结构查看相同的条目
  • 构建一张显示某条需求周围追溯关系的 Spider 图

从现有的系统条目创建 Bike-Share Dock 的 Asset 图:Holarch 根据关系绘制其部件及其功能。添加外部后台系统和一条 Conduit、一个新部件和一根电源线,在图上重命名一个部件并在数据库中看到该更改,然后以层次结构查看相同的条目,并用 Spider 图追溯一条需求。

项目文件

  • 起始项目 (.holarch.json;管理项目 → 项目文件 ▾ → 导入项目 (.json)…)
  • 完成项目 (.holarch.json;管理项目 → 项目文件 ▾ → 导入项目 (.json)…)

视频从 holarch.app 播放;参见隐私政策。

练习

在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。

  1. 打开您的 EO-1 演示项目(或创建它:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程))。
  2. 单击侧栏底部的 图,然后单击 + 新建图。选择 Asset 图,在 图的对象 中输入 EPS,选择 1.3 EPS,然后单击 创建。打开 执行的 Action,查看每个部件执行哪个功能。
  3. 选择 + Asset ▾ → 新建子 Asset…,创建 Battery Heater。单击图工具栏中的 ⋯(更多操作),然后单击 + Conduit:从 Battery Pack 到 Battery Heater,命名为 Heater Power Line。然后选择 排列 ▾ → 整理布局。
  4. 打开 数据库,找到作为新行出现的 Battery Heater 和 Heater Power Line。
  5. 回到图的标签页,使用类型选择器将类型切换为 层次结构图。
  6. 创建 3.2 Battery Capacity 的 Spider 图,层级保持为 2。

当 3.2 的 Spider 图显示满足它的 Battery Pack 和验证它的 TC-07 Battery Capacity Test 时,即完成练习。

自测

  1. 您没有删除任何内容,只是在图上重命名了一个部件。新名称还会出现在哪里?
  2. 为什么新建的 1.3 EPS 的 Asset 图已经显示了三个部件?
  3. 什么情况下 Spider 图比 Asset 图更有用?
显示答案
  1. 您没有删除任何内容,只是在图上重命名了一个部件。新名称还会出现在哪里?

    出现在该条目出现的所有地方:数据库、文档、其他图和属性面板。图是模型的视图,而不是单独的绘图。

  2. 为什么新建的 1.3 EPS 的 Asset 图已经显示了三个部件?

    该图读取模型中已有的 decomposed by 关系,因此无需手动放置就能绘制出各部件。

  3. 什么情况下 Spider 图比 Asset 图更有用?

    当您想查看某个条目周围跨关系类型的追溯时:需要、功能、部件和测试,例如用于判断变更的影响。

延伸阅读

文字稿

显示文字稿 (旁白和屏幕内容)

Introduction

Chapter four: your first diagram. In Holarch a diagram is a view of the model. It draws items and relationships that already exist, and whatever you add on a diagram goes into the model.

We continue with the Bike-Share Dock, whose parts and functions we related in the last chapter.

Create a diagram

Open Diagrams at the bottom of the rail. It lists every diagram in the project. None is saved yet, but Holarch already offers derived views of the dock, because the dock has parts.

On screen: Diagrams page: derived views only.

Click New Diagram, and pick the type. An Asset Diagram shows a system and its parts.

On screen: + New Diagram → Asset Diagram.

Then choose the root, the item the diagram is about. Type the first letters of Bike-Share Dock, pick it, and click Create.

On screen: Root: S.0 Bike-Share Dock → Create.

Holarch draws the dock with the three parts you related in the last chapter. Nothing was drawn by hand: the diagram reads the decomposed by relationships.

On screen: The asset diagram.

Check Performed Actions, and each part lists the functions it performs. That is the allocation from the last chapter, now on the picture.

On screen: Performed Actions.

Add to the model on the diagram

The back office service is outside the dock, but the kiosk talks to it. Click Asset, choose Existing Asset Outside the Root, and pick Back Office Service. It appears outside the dock's border.

On screen: + Asset ▾ → Existing Asset Outside the Root… → S.4.

A conduit is a physical or data link between assets. Click Conduit, connect the kiosk to the back office service, name the link Cellular Data Link, and click Create.

On screen: + Conduit → Kiosk → Back Office Service → Cellular Data Link.

The Arrange menu tidies the picture. Click Arrange, then Tidy Layout.

On screen: Arrange ▾ → Tidy Layout.

New parts can be added on the diagram too. Click Asset, choose New Child Asset, and create the dock's power supply.

On screen: + Asset ▾ → New Child Asset… → S.5 Power Supply.

Connect it to the charging unit with a second conduit, the Power Cable, and lay the diagram out again.

On screen: + Conduit → Power Supply → Charging Unit → Power Cable; Tidy Layout.

One model, many views

Now select the kiosk. The inspector shows the same item you created in the Database. Rename it Rental Kiosk.

On screen: Select Kiosk → inspector → Rental Kiosk.

Open the Database. The kiosk is renamed there too, and the power supply and both conduits are new rows. There is only one model, and the diagram is one view of it.

On screen: Database: Rental Kiosk, Power Supply, conduits.

The same items can be drawn in other ways. Go back to the diagram's tab, and switch its type at the top to Hierarchy Diagram: the dock's breakdown as a tree.

On screen: Back to the diagram → type: Hierarchy Diagram.

A spider diagram follows the links outward from one item. On the Diagrams page, click New Diagram, choose Spider Diagram, and make the requirement Unlock a Bike its root.

On screen: Diagrams → + New Diagram → Spider → root 1.1.

Set the level to two. It shows the requirement, the need it traces to, the function that satisfies it, and the part that performs that function: the traceability you built, on one page.

On screen: Level 2.

Every diagram can be exported with Export: as a picture, a Word document, a web page or a print, for a report or a review.

On screen: Export… dialog.

Recap

Let's recap. You created an asset diagram from the dock, saw its parts and functions drawn from the model, added an external system, a part and two conduits, renamed a part on the diagram, and viewed the same items as a hierarchy and a spider diagram.

Next, you write a requirements document whose requirements are items of this same model.