View TRAK:PrVp-03 Procurement Responsibility Viewpoint
Title
SVp-06 - Solution Competence Viewpoint
Version
7
Date
8th December 2017
Overview
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
Description
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
Role-player:
{
- Organisation plays Role
OR
}
AND
Needing competence:
- Role requires Competence
Optional Rationale:
- Competence to conduct Function
Covered by TRAK IPR and licenses
Optional Tuples
Context - Structural
- Organisation has part Job
- System is configured with Organisation
- System is configured with Job
- System is configured with Role
Universal
- Architecture Description Element satisfies Contract
- Architecture Description Element satisfies Requirement
- Architecture Description Element satisfies Standard
- Architecture Description Element traces to Argument
- Architecture Description Element traces to Document
- Claim about Architecture Description Element
- Concern about Architecture Description Element
- Contract governs Architecture Description Element
- Document traces to Architecture Description Element
- Requirement traces to Architecture Description Element
- Requirement governs Architecture Description Element
- Standard governs Architecture Description Element
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
Well-Formedness
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’)
Presentation
- 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)
Nested:
Covered by TRAK IPR and licenses
Examples
Views Needed to Construct
- SV-01 Solution Structure (specified by viewpoint SVp-01) - master architecture view for Resource (Job, Organisation, Role)
The SV-06 is the master architecture view for Competence.
Covered by TRAK IPR and licenses
Consistency Rules
- Resource must appear in SV-01
- Function must appear in SV-04
- Role extends to Resource must appear in SV-01
- System is configured with Role requires Competence to conduct must be consistent with System performs Function (in SV-04)
- Role requires Competence to conduct Function must be consistent with Role performs Function (in SV-04)
- If a suitable function is shown in the SV-04 then the Competence to conduct Function tuple must be made in the SV-06 - this is why the an optional tuple is shown in the Mandatory Tuples section. It guarantees coverage of this tuple in the TRAK metamodel.
Covered by TRAK IPR and licenses
Configuration History
The TRAK Viewpoints project on Sourceforge (https://sf.net/p/trakviewpoints) maintains a version-controlled repository. The change record is at https://trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log
Comments
Other Frameworks
In other frameworks competence is something that shown together with organisational structure and relationships:
- DODAF::OV-4 Organizational Relationships Chart Model
- MODAF::OV-4 Organisational Relationships Chart View
- NAF::NOV-4 Organisational Relationship Chart Subview
References
Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Solution