課程章節
培訓 · 第 1 單元:入門 · 第 1.1 章,共 8 章
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(引導式系統工程)。
- 在首頁上,閱讀需要處理卡片,然後按一下導覽列中的驗證,並從其概覽頁面開啟測試中心。
- 按一下導覽列底部的資料庫,按一下 + 篩選並選擇類別 測試案例。選取 TC-04 Pointing Accuracy Test,並在屬性面板中閱讀其追溯:它驗證哪項需求。
- 按兩下 TC-04 列以在項目檢視中開啟它,然後按 ⌘K / Ctrl+K,輸入
battery,並在 1.3.2 Battery Pack 上按 Enter。在兩個編輯器分頁之間切換。 - 按一下頂端列中的「需要處理」旗標,並開啟失敗的測試項目。在該頁面上,按一下頂端列中的 ?,並閱讀說明面板。
- 若要進行有檢查的逐步練習,請執行教學課程 1 Getting Around(說明 → 教學課程)。
當 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.