Holarch
課程章節

培訓 · 第 6 單元:移轉到 Holarch · 第 6.1 章,共 5 章

6.1 規劃移轉 3:00

在匯入之前,決定每種資料在模型中的去處。

展示 Holarch 2.21。

您將學到

  • 將每種來源資料對應到類別、標籤、屬性或關係
  • 檢查專案的結構描述中是否有匯入所需的屬性與標籤
  • 為結構描述中沒有對應位置的來源欄位新增屬性
  • 找到匯入和匯出頁面,並說出其四個步驟

規劃移轉到 Holarch:範例 Plant Inspection Drone 及其團隊帶來的檔案、資料如何對應到 LML 類別、標籤、屬性與關係、專案的結構描述在哪裡顯示可用的內容,以及每次匯入會做什麼。

專案檔案

  • 完成的專案 (.holarch.json;管理專案 → 專案檔案 ▾ → 匯入專案 (.json)…)

影片從 holarch.app 播放;請參閱隱私權政策。

練習

在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。

  1. 開啟您的 EO-1 示範專案(如果還沒有,請建立:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。
  2. 在側欄中開啟設定 → 結構描述,按一下類別下的 需求,並列出需求試算表可以填入的屬性(例如 Priority、Owner、Verification Method)。
  3. 開啟結構描述的標籤頁面,找出 Performance Requirement 這類種類存放的位置。
  4. 假設供應商的追蹤表有一欄 Supplier Ref 找不到對應位置:在 需求 上按一下 + 屬性,將它命名為 Supplier Ref,選擇文字類型,然後按一下新增屬性。
  5. 開啟需要與需求 → 匯入和匯出,看看拖放區接受哪些格式,以及匯出卡片提供哪些選項。

當 Supplier Ref 位於 Requirement 屬性清單的最後,且您能說出典型追蹤表的每一欄應放在哪裡時,即完成。

自我檢查

  1. 為什麼要在匯入前決定每種資料的去處?
  2. 某一欄沒有相符的屬性。您有哪些選擇?
  3. 匯入出錯了。要如何撤回?
  4. 什麼時候要使用「管理專案 → 匯入專案 (.json)…」而不是匯入頁面?
顯示答案
  1. 為什麼要在匯入前決定每種資料的去處?

    進入正確類別、標籤、屬性與關係的資料,可立即用於追溯、品質檢查與報告。在匯入後才修正,就得手動編輯許多項目。

  2. 某一欄沒有相符的屬性。您有哪些選擇?

    在匯入前於「設定 → 結構描述」中新增屬性,或在「對應」步驟中將該欄對應到「新屬性(已新增到結構描述)」。

  3. 匯入出錯了。要如何撤回?

    按一次 ⌘Z / Ctrl+Z:從匯入頁面進行的匯入是單一復原步驟。

  4. 什麼時候要使用「管理專案 → 匯入專案 (.json)…」而不是匯入頁面?

    用於將整個專案還原為一個新的獨立專案。匯入頁面則會將檔案中的項目合併到目前開啟的專案。

延伸閱讀

文字稿

顯示文字稿 (旁白與畫面內容)

Introduction

Welcome to Migrating to Holarch. Most teams arrive with their data in other places: requirements in spreadsheets and Word documents, specifications from suppliers, and models in other tools. This track shows how each one comes in, and what to check afterwards.

This first chapter is about planning. A little thought about where each kind of data belongs saves a lot of clean-up later.

The example

Our example is the Plant Inspection Drone, a drone system that inspects tanks and pipe racks inside a process plant. Its team brings four files.

On screen: The example card.

Map your data

Before importing, decide where each kind of data goes. Rows of a requirements list become Requirements. Section headings become Statements that hold them. Parts and systems become Assets, and functions become Actions.

On screen: Mapping card: classes.

Types such as functional or performance become labels. Fields such as status or rationale become attributes. And links such as satisfies, verified by or refines become relationships, so they can be traced later.

On screen: Mapping card: labels, attributes, relationships.

Check the schema

Create the project first. In Manage Projects, click New Project, name it Plant Inspection Drone, and click Create Project.

On screen: + New Project → Plant Inspection Drone → Create Project.

The project's schema lists every class with its attributes and labels. Open Settings at the bottom of the rail, then Schema.

On screen: Settings → Schema.

Select Requirement. Its attributes include the status, with the values Draft, In Review, Approved and Rejected. The usual kinds of requirement, such as Functional and Performance, are under Labels. If your data has a field with no home here, an owner can add an attribute or a label before the import.

On screen: Schema → Requirement → its attributes; then Labels.

One import page

All imports start on one page: Needs and Requirements, then Import and Export. Drop any file here: Word, Holarch project files, Excel and CSV, plain text, UML and SysML models, or ReqIF. Holarch detects the format from the file.

On screen: Needs & Requirements → Import and Export: the drop zone.

Each import takes four steps: File, Map, Review and Import. It gives the items new identities in your project, and the whole import is a single undo step, so you can try it and take it back. Content from files is cleaned of anything unsafe on the way in.

On screen: The Import steps.

Recap

Let's recap. You met the Plant Inspection Drone and its files, mapped their data to classes, labels, attributes and relationships, checked the schema, and found the Import and Export page.

Next, the requirements tracker comes in from Excel.