Ten Tips for Importing Word Requirement Documents into TestTrack RM - Tips 1-5
If you're just getting started with Helix RM, we have 10 tips to help you import your existing requirements documents from Microsoft Word into Helix RM. Here are the first five:
1. Prepare the Microsoft Word Document
Taking the time to prepare the document ensures the resulting requirements in Helix RM match the Word document as closely as possible. You'll want to use formatting compatible with Helix RM, which means you can't use numbered lists, multi-level lists, tables, or hyperlinks. Also be sure to remove comments and tracked changes.
2. Configure TestTrack RM Before Importing
Before you import, create a new Helix RM project for testing purposes and configure the requirement types your organization uses. You will need to use trial and error to figure out the best way to import your Word documents. That's why we suggest using the test project until you have successfully imported the documents.
3. Select an Import Interpretation Method
When you import a Word document, Helix RM divides the document into individual requirements. You can choose to create requirements in Helix RM based on styles used in the document or list items. The method you select in the Microsoft Word Import Wizard depends on the structure of the Word document and the type of requirements the document includes. Style interpretation uses each paragraph as a requirement while outline interpretation creates a new requirement for every list item. The best way to decide which method to use? Preview them in the import wizard and decide which works better for you.
4. Establish a Requirement Hierarchy
Helix RM uses list levels in the Word document to determine the hierarchical level of a requirement. If you choose to use Word styles but do not have the document in outline form you may need to modify styles in order to create the hierarchy. An easy way to do this is to import styles from a Word template in Helix RM. First, open the requirement document in the templates directory (C:Program FilesSeapineTestTracktemplates). Import the Requirement Level 1 through Requirement Level 9 paragraph styles into your Word requirement document. Finally, make sure to base the styles you are using for the requirement summary text on the corresponding requirement level styles. (i.e., heading 1-requirement level 1, heading 2-requirement level 2).
5. Preview the Import
The preview gives you the opportunity to see exactly how the requirements will be imported into Helix RM. You can make adjustments in the preview to ensure requirements are imported correctly before you start the import.
You are now on your way to better requirements management with Helix RM. When you're ready, read the second part of this series for Tips 6—10