View TRAK:Concern

TRAK_logo_60.jpg

Version & Date

23rd July 2015

Configuration History

See change record for the TRAK metamodel at http://trakmetamodel.svn.sourceforge.net/viewvc/trakmetamodel/trunk/?view=log

Definition

An interest in a subject held by one or more stakeholder Human Resource.

Covered by TRAK IPR and licenses

Tests For

Tests Against

Attributes

  • concern identifier
  • title (string)
  • opened date (date)
  • priority (‘High’, ‘Medium’, ‘Low’, ‘Not Specified’)
  • concern scope (‘Architecture’, ‘Architecture Description’, ‘Architecture Framework’,‘Task’, ‘Not Specified’)
  • concern status (‘Open’, ‘Closed’, ‘Not Specified’)
  • raised by organisation (organisation)
  • closure action
  • closed date (date)

+ inherited from Architecture Description Element

Covered by TRAK IPR and licenses

Implementation of TRAK Attribute Names and Values

The implementation of TRAK attributes in a tool is controlled by ‘TRAK. Implementation. Architecture Description Elements’ with respect to the case, spelling of attributes and format of values. See References section below.

Relationships

Concern.jpg

Concern participates in the following relationships:

from Architecture Description Element:

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

Covered by TRAK IPR and licenses

Configuration History

See change record for the TRAK metamodel at http://trakmetamodel.svn.sourceforge.net/viewvc/trakmetamodel/trunk/?view=log

Master Architecture View

Any Concern used within an architecture description of the system-of-interest must appear on a MV-02 Architecture Design Record View for the architecture description.

The MV-02 is the Master Architecture View for Concern.

Covered by TRAK IPR and licenses

Comments

This is allied to IEEE1471 where generic concerns are addressed through a Viewpoint (specification). Individual Architectural views address specific concerns.The type of concern identified in the scope attribute are:

  • ‘Not Specified’ - default
  • ‘Architecture’ - related to the real-world thing being described
  • ‘Architecture description’ - related to how the real world thing is represented e.g. might relate to patterns, templates, modelling constructs
  • ‘Achitecture Framework’ - a problem with the model due to the TRAK framework construct or definition
  • ‘Task’ - a concern about the task

Covered by TRAK IPR and licenses

Other Frameworks

References

 

Category:Metamodel -> Stereotype

Categories:

 

© 2010 Eclectica Systems Ltd.