When you make an EA package ‘managed’, you associate it with a single Reference Model.
As you do this, you can also provide additional rules, which apply to the way just your package uses this Reference Model.
In this way, different packages can use the same Reference Model in slightly different ways. We call this the Reference Model Context.
You can specify:
Whether the Reference Model rules are applied strictly.
Where – in your EA model – a modeler must find elements of a particular type
Whether they are allowed to create new elements of that type, or must use only existing ones.
These rules can be applied for each element type which is described in your Reference Model.
Why do I need a ‘Reference Model Context’?
Using Reference Model Contexts allows you to use the same Reference Model for different packages in slightly different ways.
Re-using existing elements
So, in the example above, when the modellers using Model Package A, they can be made to get all their ‘Element A’ instances from a specified package. This might be a list of approve Stakeholders, Components or SysML blocks. But those rules don’t apply to Model Package B.
Strict or Relaxed modelling
Your Reference Models have lots of rules about what can be added to diagrams. To enforce those rules, giving no opportunity for deviation – or to relax them, to allow modellers to experiment, check the relevant box.
Note that if you choose ‘Relaxed’ then modellers can add any elements or connectors to their diagrams, but they will get a warning if those elements do not comply with your chosen Reference Model.
Project Browser > Select the package you want to manage > Specialize > Model Expert > Manage Package
Note If you select a package that is already ‘managed’ then your final menu option changes from ‘Manage Package’ to ‘Package properties’.