PrVp-03 Procurement Responsibility

This page reproduces part of the PrVp-03 Procurement Responsibility 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-03 Procurement Responsibility architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 2024_07_10.

PrVp-03 Procurement Responsibility Architecture Viewpoint Configuration
Perspective	Viewpoint	View ID	Version	Modified
Procurement	PrVp-03	PrV-03	7	2017-12-08

Summary

The TRAK PrVp-03 Procurement Responsibility architecture viewpoint defines the requirements for the TRAK PrV-03 Procurement Responsibility 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-03 Procurement Responsibility 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-03 Procurement Responsibility architecture viewpoint but considerations for the architecture description formed from a set of architecture views.

Something needs fixing?

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns.

Stakeholder Concerns

The TRAK PrVp-03 Procurement Responsibility architecture viewpoint addresses the following concerns:

Are their boundaries clear?
What responsibilities do organisations or jobs have in relation to a project or time?

held by stakeholders:

Acquirer (of Solution)
Builder (of Project)
Developer (of Solution)
Disposer (of Solution)
Maintainer (of Solution)
Owner (of Project)
Owner (of Solution)
Trainer (of Solution)

Concerns addressed by all the TRAK architecture viewpoints.

Description

Describes the extent of a role at a point in time.

Allowed Content

TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'System is configured with Physical' that form short statements about the thing(s) being described.

Example of a 'System is configured with Physical' subject triple for the PrV-03 Procurement Responsibility Architecture View

'System is configured with Physical' is a Statement or Assertion in a PrV-03 Architecture View

The rationale for this is explained separately.

Subject Statements (Triples)

These are statements (triples) that describe the subject of the PrV-03 Procurement Responsibility architecture view. Specifically these statements address the concerns for this PrVp-03 Procurement Responsibility architecture viewpoint. These form the basis for the well-formedness section of the PrVp-03 Procurement Responsibility architecture viewpoint.

There are 17 possible subject statements in total which include 9 metamodel elements ( Job , Milestone , Organisation , Physical , Project , Project Activity , Role , Software and System ).

Return to the top of the Procurement Responsibility page.

Job plays Role
Milestone marks introduction of System
Milestone marks removal of System
Organisation plays Role
Project Activity delivers System
Project Activity marked by Milestone
Project Activity removes System
Project owns Milestone
Project undertakes Project Activity
Role extends to System
System is configured with Job
System is configured with Organisation
System is configured with Physical
System is configured with Role
System is configured with Software
System is configured with System
System is necessary for Project Activity

Return to the top of the PrV-03 subject statements (triples).

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..

Optional Statements (Triples)

These optional statements (triples) for the PrV-03 Procurement Responsibility 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 ...

Example of a 'Physical traces to Argument' optional triple for the PrV-03 Procurement Responsibility Architecture View

'Physical traces to Argument' - an optional statement or assertion for the PrV-03 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 117 possible statements which may be used to augment the PrV-03 Procurement Responsibility 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 Responsibility page.

Universal - Applicable Requirements

27 additional context statements:

Contract governs Job
Contract governs Milestone
Contract governs Organisation
Contract governs Physical
Contract governs Project
Contract governs Project Activity
Contract governs Role
Contract governs Software
Contract governs System
Requirement governs Job
Requirement governs Milestone
Requirement governs Organisation
Requirement governs Physical
Requirement governs Project
Requirement governs Project Activity
Requirement governs Role
Requirement governs Software
Requirement governs System
Standard governs Job
Standard governs Milestone
Standard governs Organisation
Standard governs Physical
Standard governs Project
Standard governs Project Activity
Standard governs Role
Standard governs Software
Standard governs System

Return to the top of the PrV-03 optional statements (triples).

Universal - Assurance

18 additional context statements:

Claim about Job
Claim about Milestone
Claim about Organisation
Claim about Physical
Claim about Project
Claim about Project Activity
Claim about Role
Claim about Software
Claim about System
Job traces to Argument
Milestone traces to Argument
Organisation traces to Argument
Physical traces to Argument
Project Activity traces to Argument
Project traces to Argument
Role traces to Argument
Software traces to Argument
System traces to Argument

Return to the top of the PrV-03 optional statements (triples).

Universal - Concern Identified

9 additional context statements:

Concern about Job
Concern about Milestone
Concern about Organisation
Concern about Physical
Concern about Project
Concern about Project Activity
Concern about Role
Concern about Software
Concern about System

Return to the top of the PrV-03 optional statements (triples).

Universal - Requirement Compliance

27 additional context statements:

Job satisfies Contract
Job satisfies Requirement
Job satisfies Standard
Milestone satisfies Contract
Milestone satisfies Requirement
Milestone satisfies Standard
Organisation satisfies Contract
Organisation satisfies Requirement
Organisation satisfies Standard
Physical satisfies Contract
Physical satisfies Requirement
Physical satisfies Standard
Project Activity satisfies Contract
Project Activity satisfies Requirement
Project Activity satisfies Standard
Project satisfies Contract
Project satisfies Requirement
Project satisfies Standard
Role satisfies Contract
Role satisfies Requirement
Role satisfies Standard
Software satisfies Contract
Software satisfies Requirement
Software satisfies Standard
System satisfies Contract
System satisfies Requirement
System satisfies Standard

Return to the top of the PrV-03 optional statements (triples).

Universal - Traceability or Reference

36 additional context statements:

Job traces to Contract
Job traces to Document
Job traces to Requirement
Job traces to Standard
Milestone traces to Contract
Milestone traces to Document
Milestone traces to Requirement
Milestone traces to Standard
Organisation traces to Contract
Organisation traces to Document
Organisation traces to Requirement
Organisation traces to Standard
Physical traces to Contract
Physical traces to Document
Physical traces to Requirement
Physical traces to Standard
Project Activity traces to Contract
Project Activity traces to Document
Project Activity traces to Requirement
Project Activity traces to Standard
Project traces to Contract
Project traces to Document
Project traces to Requirement
Project traces to Standard
Role traces to Contract
Role traces to Document
Role traces to Requirement
Role traces to Standard
Software traces to Contract
Software traces to Document
Software traces to Requirement
Software traces to Standard
System traces to Contract
System traces to Document
System traces to Requirement
System traces to Standard

Return to the top of the PrV-03 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-03 Procurement Responsibility definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.

Presentation Methods

The PrV-03 Procurement Responsibility architecture view may use any of following means to the statements (triples):

Block diagram (Project, Project Activity, Milestone, Resource = block, TRAK relationship = line with direction indicator)
Nested form. The nested form is useful because it immediately makes clear that the responsibilities apply at/during a time period formed by the surrounding frame. It is essential that the relationships must be visible (see TRAK Bye Laws in TRAK Enterprise Architecture Framework document).

Note that a textual presentation is acceptable for any TRAK architecture view.

Comments

If you need to show responsibility extent independently of time use the SV-01 with the Organisation or Job plays Role extends to Resource construct.

Neighbouring Architecture Views

The PrV-03 Procurement Responsibility architecture view content may overlap that of the following neighbouring architecture views:

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.