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

 

 

 

 

 

 

 

 

 

 

 

EVp-03 Capability Phasing

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

Summary

The TRAK EVp-03 Capability Phasing architecture viewpoint defines the requirements for the TRAK EV-03 Capability Phasing 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-03 Capability Phasing architecture viewpoint content is summarised under the following sections:

• stakeholder concerns
• description
• allowed content
• well-formedness criteria
• presentation methods
• examples
• comments

The TRAK Architecture Viewpoints specification provides are complete definition not only of the EVp-03 Capability Phasing 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 when Capabilities (planned or actual) are fielded over time. Capabilities are enduring since on their own they have no associated time. An Enterprise has a start and finish date and therefore when a capability is tied to an enterprise this defines a period for which that capability is required. Similarly a system can realise a capability and when delivered or removed by a project activity there is a time period during which the required capability is realised.

The EV-03 view can be used to show the capabilities needed, the capabilities realised (via the solution and procurement perspectives) or contrast the two to determine capability gaps.The EV-03 view also describes dependencies between capabilities.

Allowed Content

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

'Enterprise requires Capability' is a Statement or Assertion in a EV-03 Architecture View

The rationale for this is explained separately.

Subject Statements (Triples)

These are statements (triples) that describe the subject of the EV-03 Capability Phasing architecture view. Specifically these statements address the concerns for this EVp-03 Capability Phasing architecture viewpoint. These form the basis for the well-formedness section of the EVp-03 Capability Phasing architecture viewpoint.

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

The subject statements are split into 2 groups:

• Capabilities Needed - Phasing
• Capabilities Realised

Return to the top of the Capability Phasing page.

Optional Statements (Triples)

These optional statements (triples) for the EV-03 Capability Phasing 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 ...

'System traces to Requirement' - an optional statement or assertion for the EV-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 65 possible statements which may be used to augment the EV-03 Capability Phasing 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 Capability Phasing page.

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-03 Capability Phasing definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.

Presentation Methods

The EV-03 Capability Phasing architecture view may use any of following means to the statements (triples):

• Table or matrix ([capabilities needed] Capability vs time taken from start and finish dates for each Enterprise; i.e. Capability vs Enterprise [capabilities realised] Capability vs time taken from start and finish dates for each Project Activity that delivers/removes the Capability - i.e. Capability vs System; or contrast the two). The important feature is to be able to see how capability changes with time.
• Block diagram (connected blocks to represent Enterprise, Capability, Project Activity and System)

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

Examples

EV-03 Highlighting a Capability Gap

This example illustrates the use of the EV-03 to highlight a capability gap caused by a system realsing a capability being withdrawn before a new system realising the same capability is delivered into service.

Comments

The time period for the capabilities needed is determined using the start and finish dates for the Enterprise that requires these capabilities. The time period during which a capability is realised is marked using start and finish date(s) of the Project Activity(ies) which delivers the System(s) that realise the particular capability. If more than one system realises the capability then the period for which the capability is realised is determined by the earliest start date and latest finish date for the project activities involved.

Neighbouring Architecture Views

The EV-03 Capability Phasing architecture view content may overlap that of the following neighbouring architecture views:

• EV-01 Enterprise Goal
• EV-02 Capability Hierarchy
• MV-02 Architecture Description Design Record
• MV-03 Requirements and Standards
• MV-04 Assurance
• PrV-02 Procurement Timeline

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..