PDE V-Modell XT Editor - Editing the V-Modell

After staring the V-Modell Editor you can open an existing model or create a new one as described above. After opening a model, the editor shows its elements (hierarchy) in the so called Model Tree (see figure below on the left side).


Model Tree

The model tree allows you to create new child elements via the Add submenu of the context menu. The editor filters element types in the Add submenu that can not be added based on the selected element and the already existing child elements. Additionally, the Model Tree’s context menu can be used for copy, paste or cut operations as well as to move elements up and down. Moving elements up or down affects the serialization order of those elements.  For project types and project type variants the option to open the tailoring view (see below for description) is also provided in the context menu.

Use_VMX_2      Use_VMX_3

Property Grid

The property grid provides editors to modify property values of the selected element. The provided editors are specifically designed to for each property type, e.g.: text values are modified in a text editor, references in a unary or multiple role editor and html in a html editor (see the figures below).


The html editor has two different modeling views:

  • The design view displays and edits parsed html code and provides a design menu to format text or to add images, lists or simple tables.
  • The source view allows to modify the html source code.


After the modification of the html in the design view, validation methods (that are called during the conversion of the parsed html code) provide information on whether the html code was accepted or not (and why not). This is particularly useful as the V-Modell XT only supports a partial subset of html. Therefore, the validation methods can return information on unsupported html tags and remove them from the actual html code during the parsing process.

Diagram Surface (Creating procedure modules)

The diagram surface in the V-Modell XT Editor can be used to create procedure modules graphically. Every element of a procedure module has a specific graphical visualization on the diagram surface, which can help process engineers understand what the procedure modules was build for and extend or correct it.


  1. Adding new elements to the diagram surface:
    1. Context Menu: After selecting an element, you can use the context menu to create child elements or to delete the element itself (see figure above).
    2. Dynamic menu on the diagram surface Ribbon Menu: Whenever an element is selected, the Ribbon Menu for the diagram surface is updated to reflect the addable child elements for the selected element. You can then use this menu to add new child elements (see figure below).

  2. Removing elements from the diagram surface: If removing a procedure module from the diagram surface, you can choose whether to delete it from the model or to delete it from the diagram surface. In the first case, the visualization information as well as the procedure module itself will be removed from the model. In the second case, the visualization information will be removed from the diagram surface and a layout for the procedure module will be saved in the model, so that the procedure module can be displayed the exact same way later on.
  3. Displaying existing procedure modules on the diagram surface: To display existing procedure modules you can drag and drop them onto the diagram surface from the model tree. If there is a layout already defined for this specific procedure module, it will be displayed according to the layout.

Adding new relationships: The process of adding new relationships in the diagram designer is as follows (also see the figure below)

  1. Select a source element for the relationship, mouse over a triangle (each side of the element) and press and hold the left mouse button down
  2. Move the mouse over the target element of the relationship and release the left mouse button
  3. The relationship is created automatically


Tailoring View

The Tailoring View is a specific view to configure project types (Projekttypen) and project type variants (Projekttypvarianten). Both project types and variants consist of multiple different elements, that are not easy to maintain in the model tree.  The main reason for that can be seen in the structural composition of the project types and variants. E.g.: a project type can have an unlimited number of BedingteProjektmerkmale, with each BedingtesProjektmerkmal referencing a ProjektMerkmal. For the process engineer, only the references to the ProjektMerkmal are of importance as the BedingteProjektmerkmale and the BedingtesProjektmerkmal are structural components to model such references. Therefore, the Tailoring View hides those structural components and allows to create and maintain project type and variants much easier and faster. To create a new reference to a ProjektMerkmal, you only have to drag and drop a ProjektMerkmal in the area marked as “Bedingte Projektmerkmale” and all the underlying structures as well as the reference itself will be created automatically.

Tailoring View features:

  • Drag&Drop modeling of project types and variants
  • Structural components are hidden and only the important references are displayed
  • Structural components are created automatically whenever a new element is added

The figures below show the Tailoring View for project types and project type variants respectively.


Last edited Dec 6, 2010 at 4:40 PM by evgenij84, version 1


No comments yet.