QPR Installation Instructions

Model Lifecycle Management Improvements (305115, 305124, 305201, 305249)

Model Lifecycle Management Improvements (305115, 305124, 305201, 305249)

Previous topic Next topic  

Model Lifecycle Management Improvements (305115, 305124, 305201, 305249)

Previous topic Next topic JavaScript is required for the print function  

QPR Modeling Client now has a range of features for managing model lifecycle.

 

The Navigator view can now be configured to show base model element usage in child models. This includes showing the child model instances of base model elements as sub-nodes of the element in question in the base model. Another possibility is to show the child models as sub-nodes of the base model element if the base model element is used in the child models. This makes it more easy, for example, to see unused base model elements, to replace some instances with some other element, or to see where some particular information items are used in the child models.

 

Procedures can be defined for automatically importing elements from a source model to the currently open model. This can be used to maintain information consistency between different models. For example certain types of artifacts can be imported into a corresponding library models, and an approved set of those artifacts can then be imported back to the business models via a base model.

 

Importing of data between models is supported by new QPR API functions "ImportElements", "ImportElementType" and "ImportTypes", which can be used to import elements, element types, custom attribute types, and custom hierarchies from a source model to the currently open model.

 

When moving elements between models, you may end up having duplicates of the same element. The new Duplicate Element Management hierarchy settings in the Navigator view can be used to show which elements are duplicated and to replace the duplicates.