View TRAK:TRAK Repository Organisation Principles

TRAK_logo_60.jpg

Overview

Following on from the general organisation principles the following has been found to work:

  • a ‘public’ and a private top level folder. The purpose of the private one is that deliberate thought is needed before anything from this is exported or published.
  • a library folder. This contains elements that a commonly re-used and taxonomy diagrams showing how these are structured. The taxonomy diagrams are not TRAK views.
  • a set of folders based on the TRAK perspectives. Each perspective in the TRAK metamodel contains a ‘thing’ which has activities and interfaces or exchanges i.e. Enterprise (Enterprise Perspective), Node (Concept Perspective), Project (Procurement Perspective), System (Solution Perspective), Architecture Task (Management Perspective).

It makes sense to organise around the TRAK metamodel stereotypes since these are the only allowed types of modelling object that can exist and they are visible in a catalog in the tool and can be moved allowing physical organisation of the set of models and library objects.

Note that the contents of each model and therefore the repository is impacted by:

  • TRAK Bye Laws. BLV-3 states that unconnected objects (orphans) cannot exist within a model complying to TRAK. BLV-4 states that every object to object pairing must be shown on at least one TRAK view within the model. Where there are exchanges between different systems this will usually require views in the sending and receiving models for both models to be considered complete.
    • If I describe 2 systems - System A and System B and there is an interface between the 2 this would require a TRAK::SV-02 view in each description (one with the focus on System A and its interfaces to everything else and the other with the focus on System B and its interfaces, one of which is to System A)
  • Minimum Allowed TRAK Architecture View Sets. At the absolute minimum this will require a view containing the object after which the containing folder is named.

Enterprise Perspective Folder

The enterprise perspective is concerned with the top level business and is organised by TRAK::Enterprise i.e. folders are named after each Enterprise.

Since any enterprise perspective view has to contain an Enterprise the individal folder has at the very least to contain a EV-01 Enterprise Goal View showing the Enterprise after which the folder is named in order to comply with the TRAK Minimum Allowed Architecture View Sets.

Concept Perspective Folder

The concept perspective is concerned with the logical requirements and organised by TRAK::Node i.e. folders are named after each Node.

Since any concept perspective view has to contain a Node the individal folder has at the very least to contain a CV-01 Concept Need View showing the Node after which the folder is named in order to comply with the TRAK Minimum Allowed Architecture View Sets.

Procurement Perspective Folder

The procurement perspective is concerned with the introduction and removal of systems by projects and organised by TRAK::Project i.e. folders are named after each Project.

Since any Procurement Perspective view has to contain a Project the individal folder has at the very least to contain a PrV-01 Procurement Structure View showing the Project after which the folder is named in order to comply with the TRAK Minimum Allowed Architecture View Sets.

Solution Perspective Folder

The solution perspective is concerned with the solution to the logical problem or requirements and organised by TRAK::System  and by TRAK::Organisation for the organisations that develop the systems i.e. folders are named after either a System or an Organisation.

Since any solution perspective view has to contain a System or Organisation the individal folder has at the very least to contain a SV-01 Solution Structure View showing the System or Organisation after which the folder is named in order to comply with the TRAK Minimum Allowed Architecture View Sets.

Management Perspective Folder

The management perspective is concerned with the architecture description and common views across the architecture description. It is organised by TRAK::Architecture Task i.e. folders are named after each Architecture Task.

As this folder is organised by architecture task, each folder needs to contain architecture views (MV-02) that provide the linkage from the task to the views within the AD for the system-of-interest in the other perspective folders. Each folder must contain at least a MV-02 that shows the Architecture Task after which the folder is named.

 

Category:Repository

Category:Model -> Organisation

Categories:

 

© 2010 Eclectica Systems Ltd.