课程章节
培训 · 课程 3. 行为和架构 · 第 3.4 章,共 6 章
3.4 接口 2:31
为每个接口指定状态、负责人和容量,通过它承载条目,并导出 ICD。
演示 Holarch 1.27。
您将学到
- 查看接口登记册并按接口状态筛选
- 在属性面板中设置接口的状态、负责人、介质和容量
- 为所传输的条目指定数据速率并查看容量检查
- 将接口的 ICD 导出到 Word,并打开系统的 I² 图
在接口登记册中管理 Bike-Share Dock 的接口:为蜂窝数据链路设置状态、负责人和容量,为其承载的条目指定数据速率,查看容量检查,导出接口控制文档,并在 I² 图中查看租车站的接口。
练习
在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。
- 打开您的 EO-1 演示项目,或创建它:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程)。
- 打开 接口 → 接口登记册,单击 Proposed 卡片。单击 IF-14.1 Customer Portal 这一行。
- 在属性面板中,将 Interface Status 设为 Agreed,Owner 设为
Ground Segment Lead,Medium 设为HTTPS。保留其 Capacity 1000 Mbps。 - 打开 接口 → 条目与输入/输出,选择 Image Product(门户传输的条目),将 Data Rate 设为
50,Data Rate Units 设为Mbps。回到登记册,将指针指向 IF-14.1 的 Capacity 列并查看检查结果。单击其所在行的 ICD 导出接口控制文档。 - 在数据库中选择 1 EO-1 Spacecraft,然后选择 打开方式 ▾ → I2 图。找到包含 IF-01 Payload Power Line 的单元格。
- 如需带检查的分步演练,请运行教程 7“接口”(帮助 → 教程)。
当 IF-14.1 为 Agreed 并设置了 Owner 和 Medium、其容量检查显示 OK,并且您已获得 ICD Word 文件时,即完成练习。
自测
- Holarch 如何判断一个 Conduit 能否承载其条目?
- 为什么数据速率属于条目,而不属于 Conduit?
- Proposed 或 Agreed 这样的接口状态向读者说明了什么?
- I² 图的单元格包含什么?
显示答案
Holarch 如何判断一个 Conduit 能否承载其条目?
它将该 Conduit 所传输的每个条目的 Data Rate(或 Size)相加,将每个值换算为该 Conduit 的单位,并将总和与 Capacity 比较。结果为 OK、Over capacity、Unit mismatch 或 No capacity。
为什么数据速率属于条目,而不属于 Conduit?
速率描述的是被承载的内容,同一条目可以经过多个 Conduit 传输。每个 Conduit 的检查会将其承载的条目相加,并与自身的容量比较。
Proposed 或 Agreed 这样的接口状态向读者说明了什么?
两端团队的进展程度:Draft 和 Proposed 表示已写下但尚未被双方接受,Agreed 表示双方均已接受,Baselined 是最终阶段。登记册的卡片按状态计数。
I² 图的单元格包含什么?
其所在行和列对应的两个子资产之间的 Conduit:行为起点端,列为另一端。
延伸阅读
文字稿
显示文字稿 (旁白和屏幕内容)
Introduction
Welcome back. The dock's parts connect through interfaces: a power cable, a data link. This chapter manages them.
You will work in the Interface Register, the list of every interface in the project.
The register
Open Interfaces, then Interface Register. Each conduit from Getting Started is a row: the cellular data link between the kiosk and the back office, and the power cable from the power supply to the charging unit. Neither has a status yet.
On screen: Interfaces → Interface Register.
Status, owner and capacity
Select the cellular data link. In the inspector, set its interface status to Proposed: the kiosk team has written it down, and the back office team has not agreed to it yet. Its owner is the back office team.
On screen: Cellular Data Link → Interface Status: Proposed; Owner.
Give it a capacity: sixty-four kilobits per second, and set its medium to cellular LTE.
On screen: Capacity 64, Units kbit/s, Medium.
Items it carries
Now say what the link carries. The unlock code from Rent a Bike travels from the back office to the kiosk over this link. In its Trace section, show all relations, and under transfers, link Unlock Code.
On screen: Trace → Show all relations → transfers + → Link existing… → Unlock Code.
For the capacity check, the item needs a data rate. Select Unlock Code in the Database and set its data rate: two kilobits per second.
On screen: Database → Unlock Code → Data Rate 2 kbit/s.
The capacity check
Back in the register, the row counts the item it carries, and the capacity check says OK: two kilobits per second on a link of sixty-four. If the items ever carried more than the link can, the check would turn red.
On screen: Register → capacity check.
ICD and I²
The interface control document is one click away. ICD exports this interface as a Word document for the other team, generated from the model, so it agrees with the design.
On screen: ICD → Word export.
For the whole dock, open the I squared diagram. Select the Bike-Share Dock in the Database, choose Open in, then I2 Diagram. The parts sit on the diagonal, and each cell between two parts holds the interfaces that join them.
On screen: Database → S.0 → Open in ▾ → I2 Diagram.
Recap
Let's recap. You read the register, gave an interface a status, an owner and a capacity, related the item it carries, let the capacity check compare them, exported the ICD, and opened the I squared diagram.
Next, you put numbers on Rent a Bike, and simulate it.