Module Fill

What it is and why it exists

After a migration from another tool, a reorganization of a project, or when a document has to be assembled from existing requirements, the artifacts already exist in DOORS Next but the module that should contain them is empty. Placing hundreds of artifacts into a module by hand, in the right order and at the right level, is slow and error-prone.

Module Fill was created for exactly this step. You provide the structure as a simple list of pairs, such as [231,1][3513,1.1][67452,1.1.1], which can be prepared in Excel or exported from the source tool, and the widget builds the module.

Problems it solves

• Empty modules that must be filled with hundreds of existing artifacts in a precise order and hierarchy.
• Migrations where the document structure is known in the source tool but has to be rebuilt in DOORS Next.
• Manual drag and drop with a high risk of wrong order or wrong levels.
• Partly built modules after interrupted manual work.

Benefits

• Minutes instead of days for large document structures.
• Checked before it runs: the list is validated while you type, every ID is looked up, and the planned module is shown as a table.
• All or nothing: the structure is created in one change, so the module is never left half filled.
• Repeatable: the same list can be used again, for example in a test project first.
• Headings recognized automatically from their artifact type.

How to use

1. Open an empty module.
2. Paste the list of [ID,level] pairs in module order. Levels are written as 1, 1.1, 1.1.1 and so on. Errors and warnings appear while you type.
3. Click Find artifacts (N). The widget finds every artifact and lists any IDs that do not exist in the current configuration.
4. Check the planned structure in the table.
5. Click Fill module (N) and confirm. When it is done, reload the module to see the result.

Good to know

• Module Fill works only on empty modules, so it never mixes a new structure with existing content.
• The artifacts must already exist in the project and configuration you work in.
• Which artifact types are added as headings is a setting (by default Heading).