TRAK-Community

Date

23rd July 2015

Definition

One of the elements within the the TRAK metamodel and part of the Concept Perspective.

The Need is the relationship line that shows that A needs B (a dependency) and that there is some associated exchange i.e. it represents the need for A to talk to B.

Covered by TRAK IPR and licenses

 

Tests For

Tests Against

• if routing matters it isn’t a Need

Comments

Note that having identified the needs for Nodes on a CV-01 architecture view / CVp-01 Concept Need Viewpoint that the Item flow to satisfy the Need (CVp-03) is in the opposite direction to that of the Need.

Attributes

• need identifier
• need type (enumeration = Unknown, Data, Energy, Materiel)

Inherited attributes:

+ Architecture Description Element

Covered by TRAK IPR and licenses

Relationships

Need participates in the following relationships:

• Node has Need
• Need for Node
• Need requires Item Exchange
• Resource Interaction realises Need

Inherited relationships:

+ from Architecture Description Element:

• Claim about Need
• Concern about Need
• Contract governs Need
• Requirement governs Need
• Standard governs Need
• Need satisfies Contract
• Need satisfies Requirement
• Need satisfies Standard
• Need traces to Argument
• Need traces to Document
• Need traces to Requirement

Covered by TRAK IPR and licenses

 

Master Architecture View

Any Need used within an architecture description of the system-of-interest must appear on a CV-01 Concept Need View for the architecture description.

The CV-01 is the Master Architecture View for Need.

Covered by TRAK IPR and licenses

Other Frameworks

• MODAF::Needline
• NAF::Needline

References

 

Category:Metamodel -> Stereotype
Category:Framework -> Relationship
Category:Relationship

Categories:

• Framework
  • Relationship
• Metamodel
  • Stereotype
• Relationship