TRAK Architecture ViewpointsPrVp-01 Procurement Structure
This page reproduces part of the PrVp-01 Procurement Structure architecture viewpoint definition from the specification - TRAK00001. TRAK. Architecture Framework. Viewpoints. The page content is therefore subject to the same GNU Free Documentation License terms and conditions - see https://www.gnu.org/licenses/fdl-1.3.html
Most of the content is produced from a model of TRAK produced using a different set of architecture viewpoints!
Version
The TRAK PrVp-01 Procurement Structure architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 2024_07_10.
| Perspective | Viewpoint | View ID | Version | Modified |
| Procurement | PrVp-01 | PrV-01 | 7 | 2017-12-08 |
Summary
The TRAK PrVp-01 Procurement Structure architecture viewpoint defines the requirements for the TRAK PrV-01 Procurement Structure architecture view. This involves allowed content and minimum acceptable content ('well-formedness' criteria). The TRAK00001. TRAK. Architecture Framework. Viewpoints specification also defines consistency rules that apply to a set of architecture views (an Architecture Description).
The TRAK PrVp-01 Procurement Structure architecture viewpoint content is summarised under the following sections:
- stakeholder concerns
- description
- allowed content
- well-formedness criteria
- presentation methods
- comments
The TRAK Architecture Viewpoints specification provides are complete definition not only of the PrVp-01 Procurement Structure architecture viewpoint but considerations for the architecture description formed from a set of architecture views.
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns.
Stakeholder Concerns
Stakeholder Concerns Addressed by the PrVp-01 Procurement Structure Architecture Viewpoint
The TRAK PrVp-01 Procurement Structure architecture viewpoint addresses the following concerns:
- How is the project governed?
- What is the project structure?
Description
Describes the structural organisation for procurement of the solution(s).
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Project has part Project' that form short statements about the thing(s) being described.
'Project has part Project' is a Statement or Assertion in a PrV-01 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the PrV-01 Procurement Structure architecture view. Specifically these statements address the concerns for this PrVp-01 Procurement Structure architecture viewpoint. These form the basis for the well-formedness section of the PrVp-01 Procurement Structure architecture viewpoint.
There are 2 possible subject statements in total which include 2 metamodel elements ( Organisation and Project ).
Return to the top of the Procurement Structure page.
- Organisation governs Project
- Project has part Project
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
Optional Statements (Triples)
These optional statements (triples) for the PrV-01 Procurement Structure architecture view provide useful context with respect to a subject or universally allowed statements involving the subject or object (start or finish) elements in the Subject Statements (triples).
Universal statements may be added to any TRAK architecture view and describe typical concepts such as compliance or traceability:
- ... traces to Argument, Contract, Requirement, Document or Standard
- ... satisfies Contract, Requirement, Document or Standard
- Concern or Claim about ...
- Contract, Requirement, Document or Standard governs ...
'Contract governs Project' - an optional statement or assertion for the PrV-01 Architecture View
These statements address the concerns of their respective architecture viewpoint and will have been created first on these other architecture views.
There are 26 possible statements which may be used to augment the PrV-01 Procurement Structure architecture view, split into 5 groups:
- Universal - Applicable Requirements
- Universal - Assurance
- Universal - Concern Identified
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Procurement Structure page.
Universal - Applicable Requirements
6 additional context statements:
- Contract governs Organisation
- Contract governs Project
- Requirement governs Organisation
- Requirement governs Project
- Standard governs Organisation
- Standard governs Project
Return to the top of the PrV-01 optional statements (triples).
Universal - Assurance
4 additional context statements:
- Claim about Organisation
- Claim about Project
- Organisation traces to Argument
- Project traces to Argument
Return to the top of the PrV-01 optional statements (triples).
Universal - Concern Identified
2 additional context statements:
- Concern about Organisation
- Concern about Project
Return to the top of the PrV-01 optional statements (triples).
Universal - Requirement Compliance
6 additional context statements:
- Organisation satisfies Contract
- Organisation satisfies Requirement
- Organisation satisfies Standard
- Project satisfies Contract
- Project satisfies Requirement
- Project satisfies Standard
Return to the top of the PrV-01 optional statements (triples).
Universal - Traceability or Reference
8 additional context statements:
- Organisation traces to Contract
- Organisation traces to Document
- Organisation traces to Requirement
- Organisation traces to Standard
- Project traces to Contract
- Project traces to Document
- Project traces to Requirement
- Project traces to Standard
Return to the top of the PrV-01 optional statements (triples).
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
Well-Formedness Criteria
Well-formedness criteria define the minimum acceptable view content based on the subject statements (triples). These criteria are not yet represented within the model of TRAK. Please refer to the PrVp-01 Procurement Structure definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The PrV-01 Procurement Structure architecture view may use any of following means to the statements (triples):
- block diagram (Project, Organisation = block, TRAK relationship = line with direction indicator)
Note that a textual presentation is acceptable for any TRAK architecture view.
Comments
The PrV-01 Procurement Structure architecture view is the master source (origin) on which you first create the following elements or statements:
It does for Project what the SV-01 does for Resource in the solution perspective.
Neighbouring Architecture Views
The PrV-01 Procurement Structure architecture view content may overlap that of the following neighbouring architecture views:
- MV-01 Architecture Description Dictionary
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
- PrV-02 Procurement Timeline
- PrV-03 Procurement Responsibility
Navigation & Website Tracker
Spotted an error or want to suggest something - create a ticket
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
The TRAK architecture viewpoints are subject to the terms of open source license: GNU Free Documentation License (Version 1.3, November 2008) at https://www.gnu.org/licenses/fdl-1.3.html.