View TRAK:PrVp-03 Procurement Responsibility Viewpoint



SVp-06 - Solution Competence Viewpoint




8th December 2017


The SVp-06 - Solution Competence is part of the TRAK Solution Perspective and one of the 24 TRAK Architecture Viewpoints.

The SVp-06 Solution Competence Viewpoint provides the means to describe the competence(s) needed by an organisation or job  in the solution that plays a defined role. These competences can be placed in context by making reference to the function(s) for which the competence(s) is required and also the extent to which the competence is needed.

The SVp-06 architecture viewpoint is the specification for the TRAK::SV-06 Solution Competence architecture view.

Stakeholders Addressed

  • Owner of Solution
  • Acquirer of Solution
  • Developer of Solution
  • Builder of Solution
  • Operator of Solution
  • Trainer of Solution
  • Maintainer of Solution
  • User of Solution

Concerns Addressed

The SVp-06 addresses the following concerns:

Does the organisation or job through its role have the necessary competence to conduct the function? Is the competence consistent with the solution?

Covered by TRAK IPR and licenses


Describes the competence needed for a role. Justified by linking to function or the extent of the resource to which the role applies.

Covered by TRAK IPR and licenses

Declared Tuples






Needing competence:

Optional Rationale:

Covered by TRAK IPR and licenses

Optional Tuples

Context - Structural


If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.

Covered by TRAK IPR and licenses


A SV-06 view shall contain:

[to establish the time point/duration]

  • one Milestone or one Project Activity (sets the time at which the responsibility applies)
  • every Milestone or Project Activity must be connected to 1 Project (using ‘Project owns Milestone’ or ‘Project undertakes Project Activity’ respectively)

Note: A PrV-02 is needed first to make the relationships between Project, Project Activity/Milestone and System to set ‘project time’

[responsibility extent]

  • at least 1 Organisation or 1 Job
  • every Job / Organisation must be connected to at least 1 Role  (using ‘Job / Organisation plays Role’)
  • every Role must be connected to at least 1 System (using ‘Role extends to System’)


  • block diagram (Organisation, Job, Role, Competence, Function = block, TRAK relationship = line with text label and direction indicator)
  • table or matrix (row/column title = Job, Role, Competence, Function, Description)




Full size:File:PrVp-03 example presentation nested.gif

Covered by TRAK IPR and licenses


Views Needed to Construct

See Minimum Allowed View Sets

The SV-06 is the master architecture view for Competence.

Covered by TRAK IPR and licenses

Consistency Rules

Covered by TRAK IPR and licenses

Configuration History

The TRAK Viewpoints project on Sourceforge ( maintains a version-controlled repository. The change record is at


Other Frameworks

In other frameworks competence is something that shown together with organisational structure and relationships:


Category:Framework -> Viewpoint
Category:Framework -> Specification


  • Solution

    © 2010 Eclectica Systems Ltd.