TRAK-Community

Title

CVp-05 - Concept Activity Viewpoint

Version

5

Date

20th Jan 2011

Overview

The CVp-05 Concept Activity Viewpoint is part of the TRAK Concept Perspective and one of the 21 TRAK Architecture Viewpoints.

The CVp-05 identifies the activities conducted by concept nodes as part of an implementation-free description of the overall concept.

The CVp-05 viewpoint is the specification for the CV-05 Concept Activity View.

Stakeholders Addressed

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

Concerns Addressed

What does each concept node need to do?

Covered by TRAK IPR and licenses

Description

Describes what the concept node does

Covered by TRAK IPR and licenses

Mandatory

The following tuples are mandatory:

• Node conducts Concept Activity
• Concept Activity has part Concept Activity
• Concept Activity precedes Concept Activity
• Concept Activity is quantified by Metric

Covered by TRAK IPR and licenses

Optional

The following tuples may be shown on a OV-05:

• Concept Activity triggers Item
• Item has part Item
• Function realises Concept Activity
• Concept Activity supports Capability
• Concern about Node
• Concern about Concept Activity
• Concern about Item
• Concept Activity traces to Document
• Node has part Node
• Node traces to Document
• Item traces to Document
• Node traces to Requirement
• Concept Activity traces to Requirement
• Item traces to Requirement
• Standard governs Node
• Standard governs Concept Activity
• Standard governs Item

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

Well-Formedness

A CV-05 view shall contain:

• at least one Node (the subject of the view)
• the subject Node must have at least one Concept Activity

Covered by TRAK IPR and licenses

Presentation

• block diagram (hierarchical form). (Node, Concept Activity, Item = block, TRAK relationship = line with direction indicator)
• Activity Diagram (activity form)

The CV-05 can be shown as a form of functional hierarchy or in the form of a UML activity diagram to indicate an order (although a sequence diagram has to be used to properly define sequence) - i.e. CV-06.

Hierarchical form:

Activity form:

Covered by TRAK IPR and licenses

Examples

Views Needed to Construct

• CV-01 Concept Need (specified by CVp-01 Concept Need Viewpoint) - master architecture view for Node

See Minimum Allowed View Sets

Covered by TRAK IPR and licenses

Consistency Rules

• Node must appear in CV-01
• IF {Function realises Concept Activity} THEN {Resource (that performs same Function) realises Node must be made on the SV-01 }

Covered by TRAK IPR and licenses

Configuration History

The TRAK Viewpoints project on Sourceforge (trakviewpoints.sourceforge.net) maintains a version-controlled repository. The change record is at http://trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log

Comments

The CV-05 is the master architecture view for Concept Activity.

Covered by TRAK IPR and licenses

Other Frameworks

See also:

• DNDAF::OV-5a Functional Model Subview and DNDAF::OV-5b Operational Process Model Subview
• DODAF::OV-5a Operational Activity Decomposition Tree Model and DODAF::OV-5b Operational Activity Model
• MODAF::OV-5 -Operational Activity Model View
• NAF::NOV-5 Operational Activity Model Subview

Category:Framework -> Viewpoint

 

Categories:

• Framework
  • Viewpoint