View TRAK:CVp-03 Concept Item Exchange Viewpoint

TRAK_logo_60.jpg

Title

CVp-03 - Concept Item Exchange Viewpoint

Version

8

Date

8th December 2017

Overview

The CVp-03 - Concept Item Exchange Viewpoint is part of the Concept Perspective and one of the 24 TRAK Architecture Viewpoints.

The CV-03 Concept Item Exchange view describes exchange of energy, data, materiel in high level terms that are the response(s) to the needs established between parts of the concept in the corresponding CV-01 Concept Need view.

The CVp-03 viewpoint is the specification for the TRAK::CV-03 Concept Item Exchange architecture view.

Stakeholders Addressed

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

Covered by TRAK IPR and licenses

Concerns Addressed

Have the items exchanged by concept nodes been identified? What is required to satisfy the concept needs?

Covered by TRAK IPR and licenses

Description

Describes what is exchanged to meet the needs identified.

Covered by TRAK IPR and licenses

Declared Tuples

To establish the existence of the exchange:

EITHER

(

)

OR

(

)

To characterise the exchange:

Covered by TRAK IPR and licenses

Optional Tuples

Context - Concept Structure:

Universal:

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

Pre-requisites:

  • at least 1 Node-pair (2 Nodes related to each other by ‘Node has Need for Node’ or ‘Node needs Node’) (the subject of the view) must exist on a CV-01

A CV-03 view shall contain:

  • at least 1 Node-pair (the subject of the view – using ‘Node has Need for Node’ or ‘Node needs Node’)
  • every Node-pair must have at least 1 Item Exchange (using ‘Item Exchange from / to Node’)
  • every Item Exchange must be characterised by at least 1 Item being exchanged ( using ‘Item Exchange carries Item’)
  • every Item Exchange and Item must be typed (allowed values = Unknown, Data, Energy or Resource - see TRAK Metamodel document). Default= Unknown - a possible concern in the architecture description.
  • every Item Exchange between a node pair has a direction (from/to) which is opposite to the direction of the Need for the same node pair
  • every Node must be uniquely identified

Covered by TRAK IPR and licenses

Presentation

  • block diagram (Node = block, Item Exchange = line with direction indicator, Item = text label, Need = line with direction indicator)
  • Matrix
  • N-squared diagram (Nodes on diagonal, intersections marked with Item(s) to represent direction of Item Exchanges and Items being exchanged )

Block diagram form:

CVp-03_examplePresentation_block.gif

Note:The item exchanges are typed = IE1=Energy, IE2=Data. If this cannot be attached to the resource interaction(s) an accompanying list of typed item exchanges would be needed.

Matrix form:

                                                 
  CV-03 Concept Item Exchange View - Table or Matrix Form  
Item Exchange IdentifierSource NodeDestination NodeItem(s)Requiring NeedDescription
#IE1BAItem 1 (Energy)#N1cc bsms
#IE2BCItem 2 (Data)#N2nsn,m oe

N-squared diagram form:

                               
  CV-03 Concept Item Exchange View - N-Squared Diagram Form  
Node A  
#IE1 Item 1 (from B to A)(Energy)Node B#IE2 Item 2 (from B to C)(Data)
  Node C

Covered by TRAK IPR and licenses

Examples

Views Needed to Construct

See Minimum Allowed View Sets

Covered by TRAK IPR and licenses

Consistency Rules

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-03 is the master architecture view for Item and Item Exchange.

Note that the direction in which the item exchange occurs is in the opposite direction to the need described in CV-01 because the exchanges are only required because they satisfy the need(s) previously identified. There is therefore a mapping between a need and 1 or more item exchanges.

Other Frameworks

See also:

but note that the despite the misleading name at 1.2.004 the MODAF OV-3 can now also be used to describe materiel, energy and human resource flows.

References

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

Categories:

  • Operational
  •  

    © 2010 Eclectica Systems Ltd.