课程章节
1.2 您的第一个项目 5:43
创建项目,了解什么是类,并添加第一批条目。
演示 Holarch 2.41。
您将学到
- 从“管理项目”创建带名称和描述的项目
- 为需要、约束、需求、功能和部件选择合适的 LML 类
- 使用 + 新建条目 创建条目,并为其指定编号和标签
- 在表格中编辑条目,并撤销和重做该更改
创建本课程其余部分所用的 Bike-Share Dock 项目,了解条目的类的含义,并在数据库中添加第一批利益相关方需要、一个带标签的约束、一条需求、一个功能和系统本身;在表格中编辑并撤销。
练习
在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。
- 打开您的 EO-1 演示项目(或创建它:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程))。
- 单击侧栏底部的 数据库,然后单击 + 新建条目。选择类 Statement,将其命名为
Field Boundary Overlays,编号为N4,描述该需要(农艺师希望在每张植被图上绘制田块边界),然后单击 创建。 - 再创建一个 Statement:
Rideshare Mass Limit,编号C1,说明航天器不得超过分配器的质量限制。在属性面板中单击 + 标签 并选择 Constraint。 - 创建一个 Requirement:
Field Boundary Layer,编号6.6,以 shall 语句编写,并确认其 Status 为 Draft。然后创建一个 Action:Overlay Field Boundaries,编号F12。 - 在表格中双击 N4 的描述,修改一个词并按 Enter。按 ⌘Z / Ctrl+Z 撤销,按 ⇧⌘Z / Ctrl+Shift+Z 重做。
- 单击 + 筛选 并选择类 Statement,同时查看需要和约束。
当 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.