Migration von DOORS 9 zu DOORS Next Generation



Migration from DOORS 9 to DOORS Next Generation Details (german) …

Do you know the amount of modules, templates and DXL-plugins in your company? Consider what the migration means when DXL is no longer available! The major questions which need to be answered before you migrate are:

  • What are the differences between DOORS 9 and DOORS Next Generation?
  • Which functions are provided by DOORS Next Generation, which needed DXL-extensions in DOORS 9?
  • How can data as well as processes be migrated (and modernized)?

We propose an iterative and interactive migration procedure

  • Initial migration
    • Import selected modules without transformation in DOORS Next Generation
    • Analyze existing specification landscape and workflows
  • Workshop
    • Interactive analysis of the migrated modules
    • Interactive analysis of workflows
  • Post-processing
    • Joint creation of user stories for data migration
    • Joint creation of user stories for workflow migration
  • Adaptation
    • Realize user stories (DNG-Migrator adjustment)
    • Realize user stories (workflows creation / customization)
  • Data migration
    • Migrate modules using DNG-Migrator
    • Start iteration again with workshop


Automatic migration with ReqIF

We develop the DNG-Migrator, a tool that greatly simplifies the migration from 9 DOORS modules to DOORS Next Generation. The tool is based on ReqIF – the standard exchange format for requirements. It realizes an ETL process to:

  • Extract ReqIF-files from DOORS 9
  • Transform the extracted ReqIFs with the DNG-Migrator
  • Load the transformed ReqIFs into DOORS Next Generation






The DNG-Migrator is highly extensible. Internally, he provides small-scaled transformation rules, which are assembled to migration commands. Thus, individual migration commands can be implemented very quickly. The DNG-Migrator already supports several standard migration commands. The most important are described below.


Harmonize attributes and datatypes

Attributes and data types that appear in several modules in DOORS 9 are duplicated in DOORS Next Generation when importing the ReqIF without treatment. In order to prevent this, for each attribute, and for each data type URIs must be set (URI = same same attributes and same data type). For this purpose, IBM provides a  there is a Video-Tutorial from IBM User Education.

The migration command Harmonize attributes and datatypes performs the steps that are shown in the video tutorial, automatically. Here, inconsistencies (e.g.different enumerations, MinMax-Values, etc.) are detected and can be resolved.


Extract artifact types

DOORS 9 is module-oriented. This means, that all objects of a module have the same artifacts and data types. Individual artifact types often are specified in DOORS 9 in a separate column (e.g. Heading, information, requirement …). DOORS Next Generation is artifact-oriented. The artifacts within a module can have different artifact types. IBM provides a Video-Tutorial from IBM User Education  which shows how the artifact types in DNG be extracted after importing the ReqIF..

The migration command Extract artifact type(s) searches the column in which in DOORS 9 artifact types were maintained and creates the artifact types accordingly. Unneeded attributes can be deleted automatically (for example, the column ‚ASIL level‘ is not needed for the artifact type ‚information‘).


Extract bricks

DOORS 9 is module-oriented. This means, that all specification artifacts were often kept in a single module. For example, in a chapter ‚functions‘ all system’s functions are listed. The description of each function has the same structure. The artifact-orientation in DOORS Next Generation allows you to specify these functions in external modules. When a function is needed in a system’s specification, it is simply linked to the corresponding chapter. The usage of this new DOORS Next Generation feature promotes reuse of specification artifacts as system specifications only are containers for linked artifacts.

The migration command Extract bricks extracts all selected subchapters of a chapter (for example, functions, safety objectives, components …). Each subchapter is stored in a new module (incl. new artifact type for the module) which is linked to the origin location.


Further migration commands

We are currently developing further migration commands. The highly expandable architecture of the DNG-Migrator allows us to implement individual migration commands that fit exactly to your needs.

Highest quality standard

The DNG-Migrator transforms your specification documents in order to achieve an optimal migration outcome. Of course, nothing should go wrong during this process. For this reason, we document and test our DNG-Migrator: Each function and each parameter of the source code is documented. In addition, we always strive for a 100% branch coverage by unit tests. Each migration command also logs the transformations that it performs. Through these measures, we ensure that the DNG-Migrator works the way it should.