課程章節
培訓 · 第 1 單元:入門 · 第 1.2 章,共 8 章
1.2 您的第一個專案 5:43
建立專案、了解類別是什麼,並新增第一批項目。
展示 Holarch 2.41。
您將學到
- 從「管理專案」建立具有名稱與描述的專案
- 為需要、約束、需求、功能與零件選擇正確的 LML 類別
- 以「+ 新增項目」建立項目,並為其指定編號與標籤
- 在表格中編輯項目,並復原與重做該變更
建立本課程其餘部分使用的 Bike-Share Dock 專案,了解項目的類別代表什麼,並在資料庫中新增第一批利害關係人需要、一個帶標籤的約束、一個需求、一個功能與系統;在表格中編輯並復原。
練習
在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。
- 開啟您的 EO-1 示範專案(或建立它:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。
- 按一下導覽列底部的資料庫,然後按 + 新增項目。選擇類別 陳述,將其命名為
Field Boundary Overlays、編號N4,描述該需要(農藝師希望在每張植生地圖上繪出田區邊界),然後按一下建立。 - 建立第二個 Statement
Rideshare Mass Limit,編號C1,說明太空船不得超過分離器的質量限制。在屬性面板中,按一下 + 標籤並選擇約束。 - 建立一個 需求
Field Boundary Layer,編號6.6,以 shall 陳述撰寫,並確認其狀態為 Draft。接著建立一個 動作Overlay Field Boundaries,編號F12。 - 在表格中按兩下 N4 的描述,修改一個字,然後按 Enter。按 ⌘Z / Ctrl+Z 復原,再按 ⇧⌘Z / Ctrl+Shift+Z 重做。
- 按一下 + 篩選並選擇類別 陳述,以同時查看需要與約束。
當 Statement 篩選列出 N1 到 N4 與 C1、C1 帶有 Constraint 標籤,且 6.6 Field Boundary Layer 顯示狀態 Draft 時,即完成。
自我檢查
- 為什麼建立項目時類別很重要?
- 一位利害關係人表示,操作人員必須能在家中規劃過境。那是 Statement 還是 Requirement?
- 如果類別已經說明了項目是什麼,標籤的用途是什麼?
顯示答案
為什麼建立項目時類別很重要?
類別決定項目可以有哪些屬性與關係。Holarch 只提供對該項目合理的關聯:資產可以執行動作,風險則不行。
一位利害關係人表示,操作人員必須能在家中規劃過境。那是 Statement 還是 Requirement?
Statement:它是以利害關係人的用語表達的需要。將它正式化的需求稍後才出現,並追溯回它。
如果類別已經說明了項目是什麼,標籤的用途是什麼?
標籤將同一類別的項目分成不同種類,例如標記為 Constraint 的 Statement,讓您不必新增類別就能依種類篩選與產生報告。
延伸閱讀
文字稿
顯示文字稿 (旁白與畫面內容)
Introduction
Chapter two: your first project. You will create a project for a new system, learn what an item's class means, and add the model's first items.
This is the project the rest of the course builds on, so it is worth following along in your own account.
Create the project
In Manage Projects, click New Project. Name the project after the system. Our example for this course is a bike-share dock: a station on the street that holds, locks, charges and rents out bicycles.
On screen: + New Project → Bike-Share Dock.
Add a short description, so others know what the project covers. The folder is optional: it only groups projects in this list. Then click Create Project.
On screen: Description → Create Project.
The new project opens on Home. It is empty for now, so Next actions has one suggestion: write or import the first requirements.
On screen: Home of the new project.
Classes
Everything in a model is an item, which Holarch also calls an entity. Its class says what kind of thing it is. The classes come from the Lifecycle Modeling Language, L M L, and a few of them cover most of the work.
On screen: Concept card: the main classes.
The class decides which attributes and relationships an item can have. A requirement can be satisfied by an asset, and an asset can perform an action, but a risk cannot perform anything. Holarch only offers the links that make sense.
On screen: Concept card.
Create items
Open the Database at the bottom of the rail. In a new project, the table is empty.
On screen: Database (empty).
Click New Entity in the top bar. Choose the class first. Start with a Statement: a good model begins with what people need, before any requirement.
On screen: + New Entity → Statement.
Name it Find a Bike Nearby, number it N.1, and describe the need in the rider's own words. Then click Create.
On screen: Name, number, description → Create.
The new item is selected, and the inspector on the right shows it. Every field can be changed there later.
On screen: The inspector shows N.1.
Add the operator's need the same way: Return Bikes Without Staff, number N.2.
On screen: + New Entity → Statement N.2.
Constraints are statements too. Create one: the dock must fit on a standard sidewalk.
On screen: + New Entity → Statement C.1.
Labels and numbers
Then click Label in the inspector, and choose Constraint. Labels sort the items of one class into kinds, and you can filter and report by them.
On screen: Inspector → + Label → Constraint.
Now the first requirement. Choose the class Requirement, name it Unlock a Bike, number it 1.1, and write it as a shall statement.
On screen: + New Entity → Requirement 1.1.
New requirements start with the status Draft. As the team reviews them, the status moves to In Review and then Approved; a later chapter shows how.
On screen: Inspector → Attributes → Status.
Functions are Actions: what the system does. Create Rent a Bike, number F.1.
On screen: + New Entity → Action F.1.
Parts are Assets. Create the system itself, Bike-Share Dock, number S.0, and give it the label System.
On screen: + New Entity → Asset S.0, label System.
The other parts, functions and requirements are added the same way: the docking bays, the kiosk, the charging unit and the operator's back office; returning a bike, charging and payment; and two more requirements.
On screen: The rest entered off camera; the table fills.
Edit and undo
You can also edit right in the table. Double-click a number or a description, type, and press Enter.
On screen: Double-click the description of Charge Bikes → edit.
Every change is one undo step. Click Undo in the top bar, or press Command Z, and the old text is back. Redo brings the change back again.
On screen: Undo, then Redo.
To see one kind of item at a time, click Filter and choose a class. Here are the assets of the dock.
On screen: + Filter → Asset.
Recap
Let's recap. You created the Bike-Share Dock project, learned what classes are, and added needs, a constraint, a requirement, a function and the system, with numbers and labels, in the Database.
Next, you describe these items with attributes and connect them with relationships.