View TRAK:Minimum Allowed Architecture View Sets

TRAK_logo_60.jpg
The following list shows the views that have to be produced if you elect to produce the view shown first. This is a result of dependencies created by the concept of a Master Architecture View in TRAK.

Enterprise Perspective

Starting with a view from the TRAK Enterprise Perspective:

                                                                                                     
    Minimum Allowed View sets When Creating Any TRAK Enterprise Perspective View  
IDView to be Created Views Needed
VS1EV-01 Enterprise Goals—> MV-02 + EV-01
VS2EV-02 Capability Hierarchy—>MV-02 + EV-02 + EV-01
VS3 EV-03 Capability Phasing (Planned Capability)—>MV-02 + EV-03 + EV-01 + EV-02
VS4EV-03 Capability Phasing (Realised Capability)—> MV-02 + EV-03 + EV-01 + EV-02 + PrV-02 + PrV-01 + SV-01

Concept Perspective

Starting with a view from the TRAK Concept Perspective:

                                                                                                                                             
    Minimum Allowed View sets When Creating Any TRAK Concept Perspective View  
IDView to be Created Views Needed
VS5CV-01 Concept Need—>MV-02 + CV-01
VS7CV-03 Concept Item Exchange—>MV-02 + CV-03 + CV-01
VS8CV-04 Concept Activity to Capability Mapping—>MV-02 + CV-04 + CV-05 + CV-01 + EV-02 + EV-01
VS9CV-05 Concept Activity—>MV-02 + CV-05 + CV-01
VS10CV-06 Concept Sequence—>MV-02 + CV-06 + CV-01 + CV-05 + CV-03
VS11OV-07 Operational Constraints [deleted] replaced byMV-03

•

Procurement Perspective

Starting with a view from the TRAK Procurement Perspective:

                                                                                 
    Minimum Allowed View sets When Creating Any TRAK Procurement Perspective View  
IDView to be Created Views Needed
VS12PrV-01 Procurement Structure—>MV-02 + PrV-01
VS13PrV-02 Procurement Timeline—>MV-02 + PrV-02 + PrV-01
VS14PrV-03 Procurement Responsibility—>MV-02 + PrV-03 + PrV-02 + PrV-01 + SV-01

Solution Perspective

Starting with a view from the TRAK Solution Perspective:

                                                                                                                                                                                                         
    Minimum Allowed View sets When Creating Any TRAK Solution Perspective View  
IDView to be Created Views Needed
VS15Solution Structure  • —> MV-02 + SV-01
VS16SV-02 Solution Resource Interaction —>MV-02 + SV-02 + SV-01
VS17 SV-03 Solution Resource Interaction to Function Mapping —>MV-02 + SV-03 + SV-02 + SV-01 + SV-04
VS18SV-04 Solution Function —> MV-02 + SV-04 + SV-01
VS19• SV-05 Solution Function to Concept Activity Mapping —> MV-02 + SV-05 + SV-04 + SV-01 + CV-05 + CV-01
VS20SV-06 Solution Competence —>MV-02 + SV-06 + SV-04 + SV-01   •
VS21SV-07 Solution Sequence (functional form)—>MV-02 + SV-07 + SV-04 + ] + SV-03 +SV-02 + SV-01
VS22SV-10 Solution Constraints [deleted]replaced by MV-03
VS26SV-07 (Resource Interaction form)—>MV-02 + SV-07 + SV-03 + SV-02 + SV-01

Management Perspective

Starting with a view from the TRAK Management Perspective:

                                                                                 
    Minimum Allowed View sets When Creating Any TRAK Management Perspective View  
IDView to be Created Views Needed
VS23MV-01 Architecture Description Dictionary—>MV-01 + MV-02 + any other views
VS24 MV-02 Architecture Description Design Record Viewpoint—>MV-02 + any other view
VS25MV-03 Requirements & Standards—>MV-03 + any other views


Covered by TRAK IPR and licenses

Category:Framework -> Specification
Category:Framework -> View
Category:Framework -> Viewpoint
Category:TRAK -> Rules

Categories:

  • TRAK
  •  

    © 2010 Eclectica Systems Ltd.