IBM DOORS (NG) Scripts
Softacus provides scripts for selected DOORS and DOORS Next preparation tasks, including merging eligible objects and splitting modules. The applicable script and processing rules depend on your data and migration approach.
About this offering
Prepare modules for migrationScope a targeted transformationInputs and acceptanceScope and prerequisitesCommon questionDiscuss your modules
Prepare modules for migration
Selected scripts can restructure DOORS Classic modules around a migration to DOORS Next. Source-described operations include merging eligible objects, splitting a module by section and separating content into linked modules.
Scope a targeted transformation
Workflow overview based on the documented scope. Configuration and delivery details are agreed for your environment.
- Choose the operation. Identify the source structure and the module layout you need.
- Set eligibility rules. For object merging, confirm non-heading objects without links and other entries at the same hierarchy level.
- Validate a sample. Check resulting content, hierarchy and links before wider use.
Inputs and acceptance
Provide representative modules, object and link types, and the desired result. Agree the transformed data to be delivered, validation checks and who accepts the changes.
Scope and prerequisites
Confirm source and target versions and processing rules for the selected operation. These are preparation tasks; a complete migration needs its own plan. Script adaptation, execution support and commercial terms require agreement.
Common question
Can every object be merged? The source defines eligibility restrictions. Linked objects and headings are outside the described merge operation.
Discuss your modules
Describe the current structure, intended transformation and any content or relationships that must be preserved.
Related options to compare
- Softacus Migrator — Plan the full Classic-to-Next transition around targeted source-preparation tasks.
- DOORS History Tables Migration to DNG — Assess table reconstruction when history tables require a specific migration treatment.
These are editorial suggestions for related scenarios; they do not imply a shared licence or a product integration.
Source: Official documentation.
