TRAK Architecture Viewpoints

• SourceForge Project Summary

trakviewpoints project

• Introduction
• What is an Architecture Viewpoint?
• Architecture Viewpoints & Views
  • Architecture Viewpoint Concerns
  • Enterprise Perspective
  • Concept Perspective
  • Procurement Perspective
  • Solution Perspective
  • Management Perspective
• Why Use Triples?
• Modelling TRAK Viewpoints
• Open Source
• Download
• Get Support / Join
• Discussion Forums
• Report Bug
• Support Request
• Keep Informed

TRAK SourceForge Projects

Definition

• TRAK
• TRAK Metamodel
• TRAK Viewpoints

Implementation

• Implementations of TRAK
• UML Profile for TRAK
• Rail Symbols
• MDG Technology for TRAK (Sparx Enterprise Architect)
• TRAK MooD 2010 Template
• TRAK OmniGraffle Stencil
• TRAK Visio Template

TRAK Information

• TRAK - Important Ideas
• TRAK FAQs (SF - trak project)
• Projects Using TRAK
• Demo Model
• Supporting Links
• Blog - "The Residual World"
• TRAK Community Wiki
• Community Discussion Forums

 

 

 

 

 

 

 

 

 

 

 

CVp-04 Concept Activity to Capability Mapping

This page reproduces part of the CVp-04 Concept Activity to Capability Mapping 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 CVp-04 Concept Activity to Capability Mapping architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 10 July 2024.

Summary

The TRAK CVp-04 Concept Activity to Capability Mapping architecture viewpoint defines the requirements for the TRAK CV-04 Concept Activity to Capability Mapping 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 CVp-04 Concept Activity to Capability Mapping architecture viewpoint content is summarised under the following sections:

• stakeholder concerns
• description
• allowed content
• well-formedness criteria
• presentation methods
• examples
• views needed to construct
• consistency rules
• comments

The TRAK Architecture Viewpoints specification provides are complete definition not only of the CVp-04 Concept Activity to Capability Mapping 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.

Description

Describes how the concept activities relate to the enterprise capabilities needed. This enables the following problems to be identified:

• capabilities required by an enterprise that aren't supported by any concept activity. This might lead to nothing being developed to deliver the capability.
• concept activities that aren't needed.

Allowed Content

TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Concept Activity supports Capability' that form short statements about the thing(s) being described.

'Concept Activity supports Capability' is a Statement or Assertion in a CV-04 Architecture View

The rationale and theory for the allowed content of an architecture view is explained separately.

Subject Statements (Triples)

These are statements (triples) that describe the subject of the CV-04 Concept Activity to Capability Mapping architecture view. Specifically these statements address the concerns for this CVp-04 Concept Activity to Capability Mapping architecture viewpoint. These form the basis for the well-formedness section of the CVp-04 Concept Activity to Capability Mapping architecture viewpoint.

There are 5 possible subject statements in total which include 4 metamodel elements ( Capability , Concept Activity , Enterprise and Node ).

Return to the top of the Concept Activity to Capability Mapping page.

Optional Statements (Triples)

These optional statements (triples) for the CV-04 Concept Activity to Capability Mapping 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 traces to Contract' - an optional statement or assertion for the CV-04 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 54 possible statements which may be used to augment the CV-04 Concept Activity to Capability Mapping 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 Concept Activity to Capability Mapping page.

Well-Formedness Criteria

This web site is a partial representation of the TRAK Architecture Viewpoints Specification

Well-formedness criteria define the minimum acceptable view content based on the subject statements (triples). These criteria are not included in this web page.

Please refer to the Well Formedness section within the CVp-04 Concept Activity to Capability Mapping architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (10 July 2024).

Presentation Methods

The CV-04 Concept Activity to Capability Mapping architecture view may use any of following means to the statements (triples):

• Table or Matrix (row/column headings = Node, Concept Activity, Capability, Enterprise, Description)
• Block diagram (Node, Concept Activity, Enterprise, Capability = block, TRAK relationship = line with direction indicator)

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

Examples

Example CV-04 Concept Activity to Capability Mappping Architecture View - PassengerFocus - Advocate and Campaign Capabilities

A UML example of a TRAK CV-04 Concept Activity to Capability Mappping architecture view. Describes the mapping from the advocate and campaign capabilities of PassengerFocus.

Produced using (Sparx Systems Enterprise Architect UML modelling tool in conjunction with the MDG for TRAK plugin (https://sf.net/p/mdgfortrak.)

Views Needed to Construct

This web site is a partial representation of the TRAK Architecture Viewpoints Specification

Since a triple originates in a particular architecture view if there is a subsequent architecture view that uses the same triple it need not be created. Similarly you might wish to create a triple but in order to do so the node element has first to be created in its originating architecture view.

For example, you cannot describe the functionality of an element without first defining the element having that functionality. A Concept Activity described using a CV-05 architecture view needs a Node described in a CV-01 architecture view. These dependencies between architecture views create a natural sequence or order in which architecture views are created by virtue of their content. These criteria are not yet included in this web page.

Please refer to the Views Needed in Order to Construct section within the CVp-04 Concept Activity to Capability Mapping architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (10 July 2024).

Consistency Rules

This web site is a partial representation of the TRAK Architecture Viewpoints Specification

Consistency rules define rules applied to keep the collection of architecture views consistent and also to keep the logic formed by the statements using triples consistent. These criteria are not included in this web page.

Please refer to the Consistency Rules section within the CVp-04 Concept Activity to Capability Mapping architecture viewpoint definition in the TRAK00001. TRAK. Architecture Framework. Viewpoints specification (10 July 2024).

Comments

The CV-04 is not the origin for any node elements. The CV-04 is the origin for 'Concept Activity supports Capability' tuple. The originating architecture views needed to construct the CV-04 are the EV-02 ('Enterprise requires Capability') and the CV-05 ('Node conducts Concept Activity').

Any unmapped Capability or Concept Activity elements should be identified as a concern using 'Concern about Capability' or 'Concern about Concept Activity' respectively.

Neighbouring Architecture Views

The CV-04 Concept Activity to Capability Mapping architecture view content may overlap that of the following neighbouring architecture views:

• CV-05 Concept Activity
• EV-01 Enterprise Goal
• EV-02 Capability Hierarchy
• MV-02 Architecture Description Design Record
• MV-03 Requirements and Standards
• MV-04 Assurance
• SV-05 Solution Function to Concept Activity Mapping

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.