課程章節
培訓 · 第 6 單元:移轉到 Holarch · 第 6.3 章,共 5 章
6.3 從 Word 與 ReqIF 匯入需求 2:22
將 Word 規格書匯入為文件,並匯入供應商的 ReqIF 檔案及其階層與關聯。
展示 Holarch 2.21。
您將學到
- 說明 Word 檔案的哪些部分會成為章節、哪些會成為需求
- 將 Word 規格書匯入為編號的需求文件
- 匯入 ReqIF 檔案及其階層、屬性與關係
- 在「追溯」區段中檢查匯入的關係
從 Word 匯入 Plant Inspection Drone 的酬載規格書,其中標題成為章節、shall 句子成為需求;並從 ReqIF 匯入電池供應商的需求,包括其階層、屬性與一個 refines 關係。
練習
在 Holarch 中於 CubeSat EO-1 示範專案上親自操作。
- 開啟您的 EO-1 示範專案(如果還沒有,請建立:管理專案 → 專案檔案 ▾ → 新增示範專案 → CubeSat(引導式系統工程))。開啟文件 → EO-1 System Requirements Specification,然後按一下交付 ▾ → 規格書 (Word)。
- 在同一份文件中,按一下交付 ▾ → 需求 (ReqIF)…,然後按一下匯出。
- 在管理專案中按一下 + 新增專案,將它命名為
EO-1 Import Practice,然後按一下建立專案。開啟需要與需求 → 匯入和匯出,拖放 .docx,按兩次繼續,然後匯入。 - 將新文件與 SRS 比較:留意哪些標題成為 Statement、哪些 shall 句子成為 Requirement,以及它們如何命名。
- 將 .reqif 檔案匯入同一個專案,然後開啟它所建立的文件,選取 1.6 Revisit Time 檢查其子項目與標籤。
當專案包含兩份文件,一份來自 Word、一份來自 ReqIF,且您能說出哪一份保留了原始名稱與編號時,即完成。
自我檢查
- Word 匯入會將什麼讀作章節,又將什麼讀作需求?
- 供應商可以傳送 Word 或 ReqIF。為什麼要求 ReqIF?
- ReqIF 關係的名稱是 Holarch 不認得的。會發生什麼事?
顯示答案
Word 匯入會將什麼讀作章節,又將什麼讀作需求?
使用 Word 標題樣式的段落會成為 Statement(章節)。含有 shall、must、will 或 should 的段落會成為 Requirement,並以動詞後的前幾個字命名。以一般粗體文字輸入的標題會被當作普通文字。
供應商可以傳送 Word 或 ReqIF。為什麼要求 ReqIF?
ReqIF 帶有每個需求的識別碼、階層、屬性與關係。當供應商傳送較新的檔案時,匯入它會更新相同的項目,而不是新增副本。
ReqIF 關係的名稱是 Holarch 不認得的。會發生什麼事?
它會以 traced to 匯入。如果結構描述不允許這兩個類別之間有 traced to,該關係會被略過並顯示警告。
延伸閱讀
文字稿
顯示文字稿 (旁白與畫面內容)
Introduction
Chapter three: requirements from Word and ReqIF. Many specifications live in Word, and many suppliers exchange requirements as ReqIF files. Both come in through the same Import and Export page.
We import the payload specification and the battery supplier's requirements into the Plant Inspection Drone project.
Word
The Word file uses heading styles for its sections, and plain sentences with shall for its requirements. That is what the Word import reads. Heading styles or Word's list numbering matter: headings typed as ordinary bold text are read as ordinary text.
On screen: Card: what Holarch reads in Word.
Open Import and Export, and drop the file. Holarch detects Word from the file and analyzes it.
On screen: Import and Export → drop the .docx → Word detected.
Click Continue. The numbering pattern stays automatic, which uses numbered headings and shall sentences. Click Continue for the review: Holarch creates a requirements document with the name of the file, and lists the sections and the requirements under them.
On screen: Continue → Map: numbering → Continue → Review.
Click Import. The document opens, numbered from the Word headings, with each shall sentence as a requirement you can now trace and check.
On screen: Import → the document.
ReqIF
Now the supplier's file. ReqIF is the standard exchange format between requirements tools. Open Import and Export again, and drop the file.
On screen: Import and Export → drop the .reqif → ReqIF detected.
Click Continue. Each requirement in the file is a row. Its ReqIF identifier and its parent rebuild the hierarchy, its type becomes the class, and its attributes map by name: the chapter name to the number, the name, and the text to the description.
On screen: Continue → Map.
Click Continue, check the review, and click Import.
On screen: Continue → Review → Import.
Check the result
The supplier's relations come in as relationships. Select Charge Time, and open Trace: it refines Pack Capacity, just as the file says.
On screen: Select B.4 Charge Time → Trace.
Recap
Let's recap. You imported a Word specification, where headings became sections and shall sentences requirements, and a supplier's ReqIF file, with its hierarchy, attributes and relations.
Next, a whole model from another tool.