课程章节
培训 · 课程 6. 迁移到 Holarch · 第 6.1 章,共 5 章
6.1 规划迁移 3:00
在导入之前确定每种数据在模型中的去向。
演示 Holarch 2.21。
您将学到
- 将每种源数据映射到类、标签、属性或关系
- 检查项目架构中是否有导入所需的属性和标签
- 为架构中没有对应位置的源字段添加属性
- 找到“导入和导出”页面并说出其四个步骤
规划迁移到 Holarch:示例 Plant Inspection Drone 及其团队带来的文件、数据如何映射到 LML 的类、标签、属性和关系、项目架构在何处显示可用内容,以及每次导入都会做什么。
练习
在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。
- 打开您的 EO-1 演示项目(如果没有,请创建:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程))。
- 在侧栏中打开 设置 → 架构,单击 类 下的 Requirement,列出需求电子表格可以填写的属性(例如 Priority、Owner、Verification Method)。
- 打开架构的 标签 页面,找到 Performance Requirement 等种类保存在何处。
- 假设供应商的跟踪表中有一列
Supplier Ref没有对应的位置:在 Requirement 上单击 + 属性,将其命名为Supplier Ref,选择文本类型,然后单击 添加属性。 - 打开 需要与需求 → 导入和导出,了解拖放区接受哪些格式,以及 导出 卡片提供哪些功能。
当 Supplier Ref 位于 Requirement 属性列表的最后,且您能说出典型跟踪表中每一列应放在哪里时,即完成练习。
自测
- 为什么要在导入之前确定每种数据的去向?
- 某一列没有匹配的属性。您有哪些选择?
- 一次导入出了问题。如何撤回?
- 什么情况下应使用 管理项目 → 导入项目 (.json)… 而不是“导入”页面?
显示答案
为什么要在导入之前确定每种数据的去向?
落入正确的类、标签、属性和关系中的数据,可以立即用于追溯、质量检查和报告。导入后再修正则意味着要手动编辑许多条目。
某一列没有匹配的属性。您有哪些选择?
在导入之前于 设置 → 架构 中添加该属性,或在映射步骤中将该列映射到“新属性(已添加到架构)”。
一次导入出了问题。如何撤回?
按一次 ⌘Z / Ctrl+Z:从“导入”页面进行的导入是一个撤销步骤。
什么情况下应使用 管理项目 → 导入项目 (.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.