Holarch
課程章節

培訓 · 第 1 單元:入門 · 第 1.6 章,共 8 章

1.6 尋找內容 2:37

搜尋、篩選、儲存檢視、以 Command K 跳轉,並閱讀項目的歷程。

展示 Holarch 1.27。

您將學到

  • 在輸入的同時依名稱、編號或描述搜尋資料庫
  • 以「+ 篩選」依類別與屬性值篩選
  • 將查詢儲存為與專案共用的檢視
  • 使用 ⌘K / Ctrl+K 開啟項目與頁面,並執行命令
  • 閱讀項目的變更歷程

在 Bike-Share Dock 模型中找到任何東西:在輸入的同時搜尋資料庫、依類別與屬性篩選、找出沒有關係的項目、為整個專案儲存檢視、以 Command K 跳到項目、頁面與動作,並閱讀項目的歷程。

專案檔案

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

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

練習

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

  1. 開啟您的 EO-1 示範專案(或建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。
  2. 在資料庫中,於搜尋方塊輸入 downlink,並閱讀結果來自哪些類別。清除搜尋。
  3. 按一下 + 篩選,選擇類別 需求,接著在需求屬性下選擇狀態、= 是、審查中,然後按一下新增篩選條件。
  4. 在檢視窗格中,按一下儲存檢視…,將其命名為 Awaiting decision,勾選與專案共用,然後按一下儲存。
  5. 按 ⌘K / Ctrl+K 並輸入 TC-09 以開啟 Safe Mode Entry Test;再按一次 ⌘K / Ctrl+K,輸入 rvtm 並開啟 RVTM 頁面;然後輸入 new test,並在不建立任何內容的情況下按 Escape。
  6. 在項目檢視中開啟 3.1 Orbit Average Power,然後按一下歷程記錄…。閱讀哪些欄位有變更,以及是誰變更的。

當 Awaiting decision 出現在「檢視」窗格中並帶有共用標記,且只列出「審查中」的需求時,即完成。

自我檢查

  1. 一位同事每週都會詢問哪些需求仍在審查中。提供這份清單最快的方法是什麼?
  2. 「無關係」篩選會找出什麼?為什麼它很有用?
  3. 未勾選「與專案共用」而儲存的檢視,誰能看到?
顯示答案
  1. 一位同事每週都會詢問哪些需求仍在審查中。提供這份清單最快的方法是什麼?

    以「與專案共用」將查詢儲存為檢視。專案中的每個人都會在「檢視」窗格中取得它,而且它永遠反映目前的模型。

  2. 「無關係」篩選會找出什麼?為什麼它很有用?

    完全沒有關聯的項目,例如沒有任何東西追溯到的需要,或沒有任何東西滿足的需求。它們是模型中的未竟之處。

  3. 未勾選「與專案共用」而儲存的檢視,誰能看到?

    只有您自己,在這個瀏覽器中。它保存在瀏覽器裡,並在您於該瀏覽器開啟的每個專案中提供。

延伸閱讀

文字稿

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

Introduction

Chapter six: finding things. A model grows quickly, and a few tools let you find any item in seconds.

We use the Bike-Share Dock project as it stands after the last chapter.

Search and filter

Open the Database, and type in the search box. The table filters as you type, and the search covers names, numbers and descriptions. Searching for bike finds every item that mentions bikes.

On screen: Database → search: bike.

Click Clear. To narrow by kind, click Filter and choose a class, here Requirement. Each filter shows as a chip next to the search.

On screen: Clear → + Filter → Class: Requirement.

With a class chosen, the menu also lists that class's attributes. Choose Status, then is Draft, and click Add Filter. These are the requirements nobody has reviewed yet: all of them, so far.

On screen: Requirement attributes → Status = Draft → Add Filter.

Loose ends and saved views

Click Clear again. Then click Filter, and choose No relationships. It lists items that have no relationships at all: statements no requirement traces to yet, and requirements nothing satisfies. These are the loose ends to work on next.

On screen: Clear → + Filter → No relationships.

A query you will use again can be saved as a view. Click Save View, and name it Loose ends. Tick Share with project, so everyone on the project gets it in the Views pane.

On screen: Save View… → Loose ends → Share with project → Save.

Command K

Command K is the fastest way to anything. Press it, or click Search in the top bar, and type pay. Items are found by name or number.

On screen: Search → pay.

Press Enter, and Take Payment opens in the Entity View.

On screen: Enter → Take Payment.

Command K also finds pages. Type trace, and choose the Traceability Matrix page.

On screen: Search → trace → Traceability Matrix.

And it runs actions. Type new req, and New Requirement is offered. Press Escape to close it without creating anything.

On screen: Search → new req → Escape.

History

Every item keeps its history. Open Rental Kiosk with Command K, and click History. Each change is listed with who made it and when, including the rename from Kiosk in chapter four.

On screen: Search → Rental Kiosk → Enter → History…

Recap

Close the history. Let's recap: you searched as you typed, filtered by class and attribute, found loose ends, saved a view for the project, used Command K for items, pages and actions, and read an item's history.

On screen: Close → Recap card.

Next, you share the project with others and decide what each person may do.