课程章节
1.1 Holarch 工作区 5:34
熟悉一个完整模型的各个部分。
演示 Holarch 2.21。
您将学到
- 从“管理项目”创建 CubeSat EO-1 演示项目
- 浏览侧栏的生命周期分组,并从分组的概览页面打开页面
- 在属性面板、数据库和条目视图中查看条目的属性和追溯
- 使用 ⌘K / Ctrl+K 按名称查找条目、页面或命令
- 打开当前页面的帮助和“需要处理”列表
基于 CubeSat EO-1 演示项目浏览 Holarch 工作区:管理项目、主页、侧栏及其生命周期分组、概览页面、文档和属性面板、数据库、条目视图和编辑器标签页、使用 Command K 搜索、问题列表、保存和撤销,以及每个页面上的帮助。
练习
在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。
- 创建 EO-1 演示项目:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程)。
- 在 主页 上阅读 需要处理 卡片,然后单击侧栏中的 验证,并从其概览页面打开 测试中心。
- 单击侧栏底部的 数据库,单击 + 筛选 并选择类 Test Case。选择 TC-04 Pointing Accuracy Test,在属性面板中查看其 追溯:它验证哪条需求。
- 双击 TC-04 行,在 条目视图 中打开它,然后按 ⌘K / Ctrl+K,输入
battery,并在 1.3.2 Battery Pack 上按 Enter。在两个编辑器标签页之间切换。 - 单击顶栏中的“需要处理”标志,打开 失败的测试 条目。在该页面上,单击顶栏中的 ? 并阅读帮助面板。
- 如需带检查的分步演练,请运行教程 1“快速上手”(帮助 → 教程)。
当 TC-04 和 1.3.2 Battery Pack 在各自的编辑器标签页中打开,且您能说出 TC-04 验证的需求时,即完成练习。
自测
- 您在数据库中更改了一条需求的描述。系统需求规格说明是否仍显示旧文本?
- 什么情况下应使用 ⌘K / Ctrl+K 而不是侧栏?
- 为什么没有“保存”按钮?
显示答案
您在数据库中更改了一条需求的描述。系统需求规格说明是否仍显示旧文本?
不会。每个条目只有一份;文档、数据库、图和属性面板都显示同一个条目,因此编辑会出现在所有地方。
什么情况下应使用 ⌘K / Ctrl+K 而不是侧栏?
当您知道所需内容的名称或编号时。⌘K / Ctrl+K 按名称查找条目、页面、文档、图和命令;侧栏用于按生命周期阶段浏览。
为什么没有“保存”按钮?
Holarch 在您每次更改时立即保存,并在顶栏中显示保存状态。每次更改都是一个撤销步骤,因此 ⌘Z / Ctrl+Z 可以将其撤回。
延伸阅读
文字稿
显示文字稿 (旁白和屏幕内容)
Introduction
Welcome to Holarch Training. This first chapter is a tour of the workspace: where things are, how to move around, and how to read what each part of the window tells you. All you need is a browser.
By the end of it, you will know the parts of the window that every later chapter uses: the rail, the top bar, the editor tabs, the inspector, and the Help.
Manage Projects and the demo
After you sign in, Holarch opens Manage Projects. It lists the projects you own and the projects others have shared with you. A project holds one model of one system: its requirements, functions, parts, tests and documents.
On screen: Manage Projects.
To learn the workspace, start with the demo project. Click Project Files, then New Demo Project, and choose the CubeSat. Holarch builds a complete model of a small earth observation satellite, the CubeSat EO-1.
On screen: Project Files ▾ → New Demo Project ▸ CubeSat.
Home
The project opens on its Home page. Needs attention, at the top, counts the open problems: links to review, overdue to-be-determined items, failing tests, measures over their limits, high risks and model check findings.
On screen: Home: Needs attention.
Below it, the Lifecycle cards give the main number of each stage, such as how many requirements are approved and how many are verified. Next actions lists the most urgent work.
On screen: Home: Lifecycle, Next actions.
The rail and overview pages
On the left is the rail. Its groups follow the systems engineering lifecycle from top to bottom: needs and requirements, behavior, architecture, interfaces, verification, risk and decisions, and plan and deliver.
On screen: The rail's lifecycle groups.
Below the groups are the tools that work across the whole project: the Database, Diagrams, the Trash, Settings with the project's Schema, Help, and Manage Projects to switch projects.
On screen: The rail tools.
Click a group to open its overview page. Needs and Requirements shows live numbers for the stage, a card for each of its pages, and its recent diagrams. The group's pages also appear under it in the rail.
On screen: Needs & Requirements overview.
Documents and the inspector
Click Documents, and open the system requirements specification.
On screen: Documents → the SRS.
The document opens in an editor tab under the top bar. The outline on the left lists its sections, and the full text is in the middle, numbered and nested.
On screen: The document editor and its outline.
Click a requirement's number in the text. The inspector on the right shows the selected item in one panel: the item itself, its attributes, its trace to the rest of the model, its discussion and its details.
On screen: Select 3.1 Orbit Average Power; the inspector.
Click Trace at the top of the inspector. This requirement is satisfied by part of the power system and has a test case that verifies it. These links are what make the model more than a document.
On screen: Inspector → Trace.
The Database and the Item View
Now click Database at the bottom of the rail. It lists every item of the model in one table, whichever page it was created on.
On screen: Database.
Filters narrow the table. Click Filter, and choose the class Requirement. The table shows only requirements: the same ones you just saw in the document.
On screen: + Filter → Class → Requirement.
Select a row, and the same inspector opens. There is only one copy of each requirement, so an edit here also changes the document.
On screen: Select a row; the inspector.
Double-click a row to open the item in the Item View. It shows everything about one item on one page: its attributes, relationships, comments and history.
On screen: Double-click → Item View.
Each document, diagram or item you open gets an editor tab. Tabs stay open while you work, and after a reload. Click the document's tab to go back to it.
On screen: Editor tabs → back to the SRS.
Search, problems and Help
To jump to anything by name, press Command K, or click Search in the top bar. Type deploy.
On screen: Search → deploy.
Results include pages, items, documents and diagrams. Press Enter to open the function Deploy Solar Arrays in the Item View, in another tab.
On screen: Enter → Deploy Solar Arrays.
The warning icon in the top bar counts the open problems. Click it for the list. Each entry opens the page that holds the data, so you can fix it there.
On screen: Problems list.
Holarch saves every change as you make it, and the top bar shows the save status. There is no Save button. Every change is one undo step, with Command Z or the Undo button.
On screen: Save status, Undo and Redo.
Your account menu is at the top right. It holds your account settings, preferences, AI settings, Send Feedback, and Sign Out.
On screen: Account menu.
When you are not sure what a page does, click the question mark in the top bar. It opens the Help for the page you are on in a side panel, with steps and examples.
On screen: ? → Help side panel.
Help in the rail opens the Help Center, the keyboard shortcuts, a primer on the modeling language, and guided tutorials. The Help Center also holds the videos, including this course.
On screen: Help in the rail.
Recap
Let's recap. You opened the demo project, moved through the lifecycle with the rail, read items in the inspector, used the Database and the Item View, searched with Command K, and found Help for every page.
In the next chapter, you create your own project and its first items. See you there.