"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"

Model Management



Registries for Model Management

This is a placeholder for a more detailed discussion required to support the long term governance and exchange of domain models within a distributed multi-domain community.

Managing models with SVN is advantageous, but falls short of an effective paradigm for sharing models across communities.

It is proposed that management of models is undertaken in the context of a more complete registry solution (with SVN protocol access retained of course).

This way, the registry could do things like make key metadata searchable, allow metadata that doesnt fit into the model, or shouldnt (like for example information linking to the current maintainer community for a package - this may change when the package doesnt.)

The registry would potentially allow:
  • allow additional structured metadata to be managed;
  • allow metadata that has a different lifecycle to the model package to be managed - e.g. current maintenance responsibilities and activities, update policies;
  • allow registration of users (subscription) both to inform other users and to support notification and lifecycle management;
  • searching for models by content;
  • discovery of dependency graphs before you download all the models in the dependency graph;
  • finer grained access control than SVN allows;

Note that it it possible in Enterprise Architect to use a common database as a model repository, which would have some value within an organisation. This is not a feasible solution for international communities developing data standards because:
  • it is tied to a particular modelling tool implementation;
  • database connections are unlikely to be made public on internet;
  • performance and reliability of the wide area network may not be suitable for database connectivity;

Use Cases for Model Management

Many organisations are facing the challenges of deciding what, if any, externally developed domain models can be used within their own domain model.

The actual processes and issues by which such decisions are made are not unique, but their is a lack of guidance, and each domain is left dealing with a complex issue that could be broken down into a set of choices.

Accordingly, a set of Use Cases for Model Management is proposed, and these can be used to guide:
  • adoption of model packages, including creating local "stable proxies" where necessary
  • publishing new model packages
  • improving governance of model packages
  • designing registry solutions for model management
  • developing tools and processes to assist in model management

Some preliminary work has been done in the context of disentangling conceptual models from implementation models. This needs further work - possibly to decouple into "generic" model management Use Cases and those associated with refactoring models.

Attached is an XMI file export of a UML package describing Use Cases for Model Management.

This package could be included in the HollowWorld documentation suite once:
  • completion of the model with scope notes
  • publication of supporting theory paper
  • acceptance of the PIMP concept
  • reviewed and accepted by a representative set of users.

Further work in this area may include looking at dependency management tools such as maven to assist maintaining local caches of version controlled objects.

Topic attachments
I Attachment Action Size Date Who Comment
ModelManagement.xmlxml ModelManagement.xml manage 384.0 K 07 Jul 2009 - 11:12 RobAtkinson XMI file for Model Management Use Cases
Topic revision: r2 - 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).