View Archive - TRAK:CVp-02 Concept Viewpoint



CVp-02 - Concept Viewpoint




Not applicable - no longer in use: archived.

The change record is at



The Concept Viewpoint describes in abstract or implementation-free terms how and what is required. It can be regarded as a description of the ‘problem’ for which one or more solutions (implementations) are required. It is often textual but is expected to draw upon or make reference to other concept perspective architecture viewpoints.

Stakeholders Addressed

  • Owner of Concept
  • Developer of Concept
  • Operator of Concept
  • Maintainer of Concept
  • Trainer of Concept
  • User of Concept
  • Disposer of Concept

Covered by TRAK IPR and licenses

Concerns Addressed

The architecture viewpoint addresses the following concerns:

Has the concept purpose been identified?

How is it seen as being used?


Covered by TRAK IPR and licenses


Describes the concept scenarios and purpose within the residual world or environment in which the concept has to work.

Covered by TRAK IPR and licenses

Mandatory Metamodel Tuples

Expected to be largely textual and scenario based but with use of other concept perspective architecture views to illustrate, expand, define.

The set of tuples will be those from the mandatory sets of the concept perspective views used against CVp-01, CVp-03, CVp-04, CVp-05 and CVp-06. The selection of concept views used to illustrate the scenarios is left to the architect.

Covered by TRAK IPR and licenses

Optional Metamodel Tuples


If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.

Covered by TRAK IPR and licenses


A CV-02 view shall contain:

  • identification of the key stakeholders (acquirer, owner, developer, builder, maintainer, operator, trainer, user)
  • identification of the concept (the subject of the view)
  • what the concept does
  • what the concept needs in order to operate / meet its purpose
  • what the concept needs from the things it interacts with ( the residual world )
  • any constraints or requirements that the concept must meet e.g. given systems it has to be able to work with

A narrative text description of the concept shall form part of the architecture description.This can be placed into the view description of each architecture view used or it can be placed using Document in a single place. The CV-02 shall as a minimum either provide links to the concept views, or to the Document(s) that define the concept.

Covered by TRAK IPR and licenses


  • Usually text-based
  • Would expect to include other architectural views from the concept perspective.

Covered by TRAK IPR and licenses


Views Needed to Construct

Will usually draw upon the following in addition to any text:

See Minimum Allowed View Sets

Consistency Rules

Configuration History

  • Deleted at 13th April 2012 release of the TRAK Viewpoints specification. Removed because it did not address a unique set of concerns when compared with other viewpoints within the TRAK::Concept Perspective (and therefore not a unique/ distinct set of stereotypes and relationships).

The TRAK Viewpoints project on Sourceforge ( maintains a version-controlled repository. The change record is at


For context in terms of the bigger picture it should also include at the very least the CV-04 to show how the concept realises the enterprise capabilities and goals.

Covered by TRAK IPR and licenses


Other Frameworks

See also:

Category:Framework -> Viewpoint
Category:Framework -> Specification


  • Operational

    © 2010 Eclectica Systems Ltd.