課程章節
培訓 · 第 6 單元:移轉到 Holarch · 第 6.2 章,共 5 章
6.2 從 Excel 與 CSV 匯入需求 2:32
將需求試算表匯入為文件,並保留其階層、標籤與屬性。
展示 Holarch 2.21。
您將學到
- 準備一份具有標題列、大綱編號與 Class 欄的試算表
- 匯入試算表,並在「對應」步驟中檢查每一欄的 Holarch 欄位
- 從匯入的列建立需求文件
- 確認階層、標籤與狀態都已從檔案匯入
從 Excel 匯入 Plant Inspection Drone 的需求追蹤表:準備工作表、將匯入設定為需求文件、檢查每一欄如何對應到欄位、屬性或標籤、預覽、儲存,並在模型中查看編號的階層、標籤與狀態。
練習
在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。
- 開啟您的 EO-1 示範專案(如果還沒有,請建立:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。在資料庫中搜尋
class:Requirement,按一下匯出…,選擇表格 (CSV),勾選狀態與優先順序(保持勾選標籤),然後按一下匯出。 - 在試算表應用程式中開啟該檔案。保留標題列與第 1、2 節的列,然後在最上方新增兩列:
1、Mission Imaging、ClassStatement,以及2、Attitude Determination and Control、ClassStatement。將它儲存為 .xlsx 或 .csv。 - 在管理專案中按一下 + 新增專案,將它命名為
EO-1 Import Practice,然後按一下建立專案。 - 開啟需要與需求 → 匯入和匯出,拖放檔案,按一下繼續,並檢查每一欄的 Holarch 欄位(將不需要的欄設為略過)。
- 按一下繼續,保持勾選從這 N 個項目建立文件,然後按一下匯入 N 個項目。
- 在新文件中,確認 1.6.1 與 1.6.2 位於 1.6 之下,並選取 1.5 查看其標籤與狀態。
當新文件顯示第 1 與第 2 節,其需求依編號巢狀排列,且標籤與狀態完整保留時,即完成。
自我檢查
- Holarch 如何重建試算表各列的階層?
- 有些列匯入後的類別不對。為什麼?
- 您想從試算表更新 50 個現有需求的負責人,而不是建立副本。要怎麼做?
顯示答案
Holarch 如何重建試算表各列的階層?
如果有對應 Parent Row ID 或 Parent Number 欄,就依據該欄,否則依據大綱編號:1.2 放在 1 之下。如果缺少父項,則使用最近的現有上層項目。
有些列匯入後的類別不對。為什麼?
Class 欄中若有結構描述不認得的名稱,會退回使用「無類別的列所用的類別」,並顯示警告。請使用結構描述編輯器中的類別名稱。
您想從試算表更新 50 個現有需求的負責人,而不是建立副本。要怎麼做?
連同 ID 欄一起匯出,編輯檔案,然後在匯入時將 ID 欄對應到「全域 ID」,並將「現有實體的比對依據」設為「全域 ID」。「審查」接著會將它們列在「已更新的項目」下。
延伸閱讀
文字稿
顯示文字稿 (旁白與畫面內容)
Introduction
Chapter two: requirements from Excel and CSV. Spreadsheets are where most requirements live before a model exists, and they come in with their hierarchy and their columns intact.
We import the Plant Inspection Drone's requirements tracker into the project from the last chapter.
Prepare the spreadsheet
Here is the tracker. It has a header row, and outline numbers that give the hierarchy: 1, then 1.1 and 1.2 under it. A Class column says which rows are section headings and which are requirements, and further columns hold labels, priority and status.
On screen: The spreadsheet.
Choose the file
Open Needs and Requirements, then Import and Export. One page takes every format: Excel, CSV, Word, ReqIF and more. Holarch detects the format from the file.
On screen: Needs & Requirements → Import and Export: one page for every format.
Drop the file on the drop zone. Holarch reads it, and reports how many rows and columns it found.
On screen: Drop the file → Analyzed.
Map the columns
Click Continue. Map lists each column, its sample values, and the Holarch field it goes to. Columns whose titles match a field or an attribute are mapped already: Number, Name and Description, Class, Labels, and the Priority and Status attributes.
On screen: Continue → Map.
Check every column before you go on. A column you do not want is set to Skip, and a field with no home in the schema can become a new attribute.
On screen: The mapping table.
Review and import
Click Continue to review. Holarch offers to make the rows a requirements document, and lists each new item before anything is created.
On screen: Continue → Review.
Click Import. The whole import is one undo step, so if something looks wrong, Command Z takes it all back.
On screen: Import 12 items → the new document opens.
With no warnings, the new document opens at once. The outline has the three sections from the sheet, and the requirements are numbered under them, just as they were in the tracker.
On screen: The imported document.
Check the result
Select a requirement. Its labels and its status came in from the sheet's columns, so the model already knows which requirements are in review and which are performance requirements.
On screen: Select 1.1 → inspector: Labels, then Workflow (Status).
Recap
Let's recap. You prepared the spreadsheet, imported it as a requirements document, checked the column mapping, reviewed and imported it, and found its hierarchy, labels and statuses in the model.
Next, a Word specification and a supplier's ReqIF file.