View TRAK:PrVp-01 Procurement Structure Viewpoint
Title
PrVp-01 - Procurement Structure Viewpoint
Version
7
Date
8th December 2017
Overview
The PrVp-01 - Procurement Structure Viewpoint is part of the TRAK Procurement Perspective and one of the 24 TRAK Architecture Viewpoints.
The PrVp-01 describes project structure. It is the perspective equivalent to the CVp-01 Concept Need Viewpoint and SVp-01 Solution Structure viewpoints.
The PrVp-02 describes project structure and its relationship to the organisation that owns it.
Stakeholders Addressed
- Acquirer of Solution
- Owner of Enterprise
- Builder of Enterprise
Concerns Addressed
What is the project structure? How is it governed?
Covered by TRAK IPR and licenses
Description
Describes the structural organisation for procurement of the solution(s).
Covered by TRAK IPR and licenses
Declared Tuples
- Project has part Project
- Organisation governs Project
Covered by TRAK IPR and licenses
Optional Tuples
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 PrV-01 view shall contain:
- at least one Project (the subject of the view)
- any project parts are connected together using ‘Project has part Project’
If it is known what organisation (or part of an organisation) is in control of the project then:
- every Project must be connected to an Organisation using ‘Organisation governs Project’
Note: Where there is a project hierarchy structure it is assumed that the same organisation governs every project in the hierarchy below the point at which the relationship is made unless an additional explicit relationship is shown. This removes the need to connect every project in the hierarchy.
Presentation
- block diagram Project, Organisation = block, TRAK relationship = line with direction indicator)
Hierarchical:
Nested:
Covered by TRAK IPR and licenses
Examples
Views Needed to Construct
- SV-01 (if Organisation governs Project) - master architecture view for Resource
Covered by TRAK IPR and licenses
Consistency Rules
If Organisation owns Project is made in the PrV-01:The Organisation that governs the Project cannot itself be part of the Solution since the former is part of the model of the business and the latter will be part of the model of the thing delivered or developed. The governing organisation might well provide the resource to deliver the project but it is a different organisation to that in the solution - it is important to keep these 2 models distinct.
- { organisation in Organisation governs Project}
NOT EQUAL
- { organisation IN
{
- (same) Project undertakes Project Activity delivers / removes (System is configured with Organisation)
OR
- (System is configured with Organisation) is necessary for Project Activity AND (same) Project undertakes Project Activity
OR
- (same) Project owns Milestone marks introduction of /marks removal of (System is configured with Organisation)
}
This also comes into play if System is configured with Organisation is made in the SV-01
Further rules are applied through the TRAK Bye Laws
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
The PrV-01 is the master architecture view for Project.
It does for Project what the SV-01 does for Resource in the solution perspective.
Covered by TRAK IPR and licenses
Other Frameworks
References
Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Procurement
Category:Acquisition