TRAK-Community

Title

CVp-01 - Concept Need Viewpoint

Version

8

Date

3rd February 2011

Overview

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

The CVp-01 describes the logical connections between Nodes in terms of Needs.

The CVp-03 Concept Item Exchange builds on this by providing a high level description of the items that are exchange to satisfy these needs.

The CVp-01 viewpoint is the specification for the TRAK::CV-01 Concept Need architecture view.

Stakeholders Addressed

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

Full size:File:cvp01StakeholderConcern.pdf

Covered by TRAK IPR and licenses

Concerns Addressed

What are the concept needs?

Covered by TRAK IPR and licenses

Description

Describes the concept in terms of the set of abstract things or stuff (nodes) and how they depend on each other by way of conceptual structure and need. The CV-01 provides a way to describe that A needs B at a high level that is free from any idea of solution.

The response to a need is an exchange of one or more items which is defined by the CV-03.

Covered by TRAK IPR and licenses

Mandatory Metamodel Tuples

• Node has Need
• Node has part Node

Covered by TRAK IPR and licenses

Optional Metamodel Tuples

Context - Realisation by Solution:

• Resource realises Node

where Resource = System, Physical, Software, Organisation, Job or Role

Universal:

• Concern about Architecture Description Element
• Document traces to Architecture Description Element
• Requirement traces to Architecture Description Element
• Standard governs Architecture Description Element

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-01 view shall contain:

• at least two Nodes (including the subject of the view)
• every Node must be connected to at least one Need
• each Need (line or intersection in a matrix) must be uniquely identified, have a direction and a description

Covered by TRAK IPR and licenses

Presentation

• matrix (if only showing need relationships)
• N-squared diagram (Nodes on diagonal, intersections marked to represent direction of Need)
• block diagram (Node = block, Need = line with text label and direction indicator)

Block diagram form:

Covered by TRAK IPR and licenses

Matrix form:

                                           

  CV-01 Concept Need View - Table or Matrix Form  

Need Identifier	Source Node	Needed Node	Need(s)	Description
#N1	A	B	Need 1	nnn mmm
#N2	C	B	Need 2	mmm sss jj

N-squared diagram form:

                             

  CV-01 Concept Need View - N-Squared Diagram Form  

Node A	#N1 Need 1 (A needs B)
	Node B
	#N2 Need 2 (C needs B)	Node C

Examples

Views Needed to Construct

• None - CV-01 - master architecture view for Node and Need.

See Minimum Allowed View Sets

Covered by TRAK IPR and licenses

Consistency Rules

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

A Node (see TRAK Metamodel document) is a solution-free thing and provides a way of very coarsely describing a concept. Although solution-free if there are real world restrictions or givens that the concept has to work with these may be represented as a single thing. No detail or technology!

Covered by TRAK IPR and licenses

Other Frameworks

Other frameworks show need in both the OV-01 and OV-02 views:

• DNDAF::OV-1 High-Level Operational Concept Graphic Subview and DNDAF::OV-2 Operational Node Connectivity Description Subview
• DODAF::OV-1 High-Level Operational Concept Graphic Model and DODAF::OV-2 Operational Resource Flow Description Model
• MODAF::OV-1a High-Level Operational Concept Graphic View, MODAF::OV-1b Operational Concept Description View,  MODAF::OV-1c Operational Performance Attributes View and MODAF::OV-2 Operational Node Relationship Description View
• NAF::NOV-1 High-Level Operational Concept Description Subview and NAF::NOV-2 Operational Node Connectivity Description Subview

References

• TRAK Enterprise Architecture Framework Viewpoints http://trakviewpoints.sourceforge.net

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

Categories:

• Framework
  • Specification
• Viewpoint

Operational