TRAK Architecture ViewpointsEVp-01 Enterprise Goal
This page reproduces part of the EVp-01 Enterprise Goal 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 EVp-01 Enterprise Goal 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 |
| Enterprise | EVp-01 | EV-01 | 8 | 2024-07-10 |
Summary
The TRAK EVp-01 Enterprise Goal architecture viewpoint defines the requirements for the TRAK EV-01 Enterprise Goal 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 EVp-01 Enterprise Goal 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 EVp-01 Enterprise Goal 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 EVp-01 Enterprise Goal Architecture Viewpoint
The TRAK EVp-01 Enterprise Goal architecture viewpoint addresses the following concerns:
- What is the Enterprise and what goals does it set out to achieve?
Description
Describes the enterprise and any constituent parts (including by time) together with the goals that the Enterprise Aspires to.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Enterprise aspires to Enterprise Goal' that form short statements about the thing(s) being described.
'Enterprise aspires to Enterprise Goal' is a Statement or Assertion in a EV-01 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the EV-01 Enterprise Goal architecture view. Specifically these statements address the concerns for this EVp-01 Enterprise Goal architecture viewpoint. These form the basis for the well-formedness section of the EVp-01 Enterprise Goal architecture viewpoint.
There are 4 possible subject statements in total which include 3 metamodel elements ( Enterprise , Enterprise Goal and Metric ).
Return to the top of the Enterprise Goal page.
- Enterprise Goal has part Enterprise Goal
- Enterprise Goal is quantified by Metric
- Enterprise aspires to Enterprise Goal
- Enterprise has part Enterprise
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..
Optional Statements (Triples)
These optional statements (triples) for the EV-01 Enterprise Goal 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 ...
'Enterprise Goal traces to Argument' - an optional statement or assertion for the EV-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 40 possible statements which may be used to augment the EV-01 Enterprise Goal architecture view, split into 6 groups:
- Context
- Universal - Applicable Requirements
- Universal - Assurance
- Universal - Concern Identified
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Enterprise Goal page.
Context
1 additional context statements:
- Organisation realises Enterprise
Return to the top of the EV-01 optional statements (triples).
Universal - Applicable Requirements
9 additional context statements:
- Contract governs Enterprise
- Contract governs Enterprise Goal
- Contract governs Metric
- Requirement governs Enterprise
- Requirement governs Enterprise Goal
- Requirement governs Metric
- Standard governs Enterprise
- Standard governs Enterprise Goal
- Standard governs Metric
Return to the top of the EV-01 optional statements (triples).
Universal - Assurance
6 additional context statements:
- Claim about Enterprise
- Claim about Enterprise Goal
- Claim about Metric
- Enterprise Goal traces to Argument
- Enterprise traces to Argument
- Metric traces to Argument
Return to the top of the EV-01 optional statements (triples).
Universal - Concern Identified
3 additional context statements:
- Concern about Enterprise
- Concern about Enterprise Goal
- Concern about Metric
Return to the top of the EV-01 optional statements (triples).
Universal - Requirement Compliance
9 additional context statements:
- Enterprise Goal satisfies Contract
- Enterprise Goal satisfies Requirement
- Enterprise Goal satisfies Standard
- Enterprise satisfies Contract
- Enterprise satisfies Requirement
- Enterprise satisfies Standard
- Metric satisfies Contract
- Metric satisfies Requirement
- Metric satisfies Standard
Return to the top of the EV-01 optional statements (triples).
Universal - Traceability or Reference
12 additional context statements:
- Enterprise Goal traces to Contract
- Enterprise Goal traces to Document
- Enterprise Goal traces to Requirement
- Enterprise Goal traces to Standard
- Enterprise traces to Contract
- Enterprise traces to Document
- Enterprise traces to Requirement
- Enterprise traces to Standard
- Metric traces to Contract
- Metric traces to Document
- Metric traces to Requirement
- Metric traces to Standard
Return to the top of the EV-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 EVp-01 Enterprise Goal definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The EV-01 Enterprise Goal architecture view may use any of following means to the statements (triples):
- block diagram (blocks to represent Enterprise, Enterprise Goal and Metric)
Note that a textual presentation is acceptable for any TRAK architecture view.
Comments
The EV-01 Enterprise Goal architecture view is the master source (origin) on which you first create the following elements or statements:
- Enterprise
- Enterprise Goal
- Enterprise Goal is quantified by Metric
Neighbouring Architecture Views
The EV-01 Enterprise Goal architecture view content may overlap that of the following neighbouring architecture views:
- CV-04 Concept Activity to Capability Mapping
- EV-02 Capability Hierarchy
- EV-03 Capability Phasing
- MV-01 Architecture Description Dictionary
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
- SV-01 Solution Structure
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.