"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Update Model Dependencies tool

Related pages

Contents

Description

This tool updates a selected model’s dependencies on another package that has been versioned (or had it's internal model element identifiers (GUIDS) modified for some reason)

The information about which package an external element comes from is not included in the EA internal model, so this must be looked up in a model registry file (SKOS format, as generated by the companion function [[ModelIndexSKOS][Model Index (SKOS) tool] ).

This tool allows a model to be versioned to use a new version of the imported model.

For example, model A (Version 1) has relationships with model B(Version 1).

Package_dependencies.png

Context_Diagram__Class1.png

Context_Diagram__Class_A2.png

One scenario is:

  1. A new version of the base package (B) has been released: B(Version 2)
  2. A new version of model A, A(Version 2) has been created to track the new base model.
  3. The model A(Version 2) will have the original relationships with model B(Version 1).
  4. We update A(Version 2) to use B(Version 2)

Other possible scenarios are:
  • Model A is updated directly - discarding the knowledge about the orignal depency on B in favour of B(Version 2)
  • Model A is imported and its original dependencies are not available, but updated versions are.

In these cases, the procedure is the same except that:
  • The XMI file for model A is manipulated, without need for a version

Tutorial

Assume you have a model A (Version 1). Model A(Version 1) references a external model B(version 1).

You create a new version of model A (Version 2) using “Create A New Version” function. Model A (Version 2) does not have any references to the external model B (Version 1). You need to take the following steps to recreate the relationships between model A(Version 2 ) and model B(Version 1).

Step 1. Use “Model Index(SKOS)” function to generate a model registry for model B(Version 1). We call this file B_v_1.skos.

Step 2. Export model A (Version 2) to an XMI file using EA’s model export function. We call this XMI file A_v_2.xml.

Step 3. Right click on any package in the project browser, select “Update Model Dependencies Tool” in the Solid Ground Add-in.

update_dependencies.JPG

     Specify the “A_v_2.xml” file path in the “XMI File” field

     Specify the “B_v_1.skos” file path in the “SKOS File” field

     Click on “Update” button.

Step 4. A_v_2.xml was updated by the function. Import this newly updated xml file back into EA using EA’s model import function. The new model should have a correct reference to model B (version 1).

 
  • update_dependencies.JPG:

Topic attachments
I Attachment Action Size Date Who Comment
Context_Diagram__Class1.pngpng Context_Diagram__Class1.png manage 2.3 K 04 Jan 2010 - 14:33 RobAtkinson Original Relationship Dependency
Context_Diagram__Class_A2.pngpng Context_Diagram__Class_A2.png manage 3.9 K 04 Jan 2010 - 14:29 RobAtkinson Original attribute datatype usage dependency
Package_dependencies.pngpng Package_dependencies.png manage 3.7 K 04 Jan 2010 - 14:25 RobAtkinson Original Package dependencies
update_dependencies.JPGJPG update_dependencies.JPG manage 13.5 K 24 Dec 2009 - 11:43 RickMeng  
Topic revision: r4 - 15 Oct 2010, UnknownUser
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).