Taylor - Model Management

Model Management

In any real world application you will need to manage the size of your models so that multiple people can work on the project at the same time. This is often referred to as Team support.

Contents [hide] 1 SCM 2 Architecture 3 Tool Support 3.1 Resource Linking 3.2 Diagram Shortcuts 3.3 Controlling Packages

[edit]

SCM

The obvious solution is to use a Source Control Management (SCM) system such as CVS or Subversion. Taylor model files are just XMI files, so they are ready for scm. And Eclipse provides the scm infrastructure needed for checkin, checkout, diff, merge, etc...

But, scm is not enough.

[edit]

Architecture

We are really talking about an architecture problem. Not the architecture of the tool, but the architecture of your project. Is it one big jumble or is it decomposed into reasonable systems and subsystems and components and so forth.

[edit]

Tool Support

Taylor leverages all of the features provided by EMF and GMF.

There are 2 basic options:

• Use multiple models and link them together
  • See Resource Linking and Diagram Shortcuts
• Divide one model into separate files by package
  • See Controlling Packages

You will probably use some combination of both.

[edit]

Resource Linking

• Right click anywhere in the Navigator and select Load Resource...
• Browse the workspace for a model
• Then you should be able to access the elements in the linked model from various property editors

[edit]

Diagram Shortcuts

• Right click in a diagram and select Create Shortcut...
• Browse to an element you want to display in the diagram

[edit]

Controlling Packages

• Right click any package in the Navigator and select Control...
• Select Browse Workspace and select a folder to create the new file
• Name the file similar to the package name and give it a .uml extension
• Then right click on the navigator and select Save to create the new file
• A little green icon decoration will show that the package is controlled