View TRAK:Master Architecture View

In TRAK each metamodel stereotype is associated with one of the TRAK architecture views that is regarded as the master architecture view for that stereotype. What this means is that the stereotype cannot be created on any other view - it must be created on the master view before it can be used on any other view type.

For example, parts of the solution structure of type Resource must appear on the SV-01 Solution Structure before they can be used on other solution perspective views such as the SV-02 Solution Resource Interaction or SV-04 Solution Function.

This helps ensure that the architecture description contains the proper set of architecture views and that appropriate relationships are shown rather than tucked away on views whose immediate subject focus is different.

This results in a set of dependencies between TRAK architecture views.

Category:TRAK -> Rules



© 2010 Eclectica Systems Ltd.