Child pages
  • Guideline for tool versioning
Skip to end of metadata
Go to start of metadata

Problem statement

Several standards developing organizations (SDOs) (or standard bodies) agreed to use the same tool to develop and to share information models.

It turned out that the successful sharing of information models depends on the version of the tool used by the involved users. However, different standard bodies, require different versions of the tool, so that versions cannot easily be aligned.

Note: Currently "Eclipse Papyrus" is used as the tool to share information models between SDOs. The content of this page is related to experience made with Papyrus. However, the content of this page is generic for all kinds of tools.

Possible workable approach

In principle, the latest released version of a tool is better than the previous one. It is recommended to stay close to the latest version. However, only upgrade if you need to or when the new version has a feature you are interested in.

Make sure that the effort for the upgrade of the tool and adaptation of existing information models, is less than the benefits for the upgrade. Evaluate the new version adequately before moving to the next version. Please document your evaluation and experience and share it with others. This way it increases the likelihood that others will also switch to a new version so that modeling experts stay close to the latest version and can exchange information models smoothly.

When you need to upgrade information models, concentrate only on the transferred parts.

In case losing a useful feature after the upgrade, please share your concerns. The community may know workarounds or even solutions. Reach out to the developers of the tool. Developers are interested in developing useful tools and need feedback from users. If the tool development goes in a direction that is significantly contrary to our necessary evolution then we will need to consider changing tools.

  • No labels