View TRAK:Contract

TRAK_logo_60.jpg

Version & Date

15th February 2010

Configuration History

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

Definition

One of the TRAK stereotypes within the the TRAK metamodel and part of the Management Perspective.

From the TRAK metamodel:

A written or spoken agreement. between at least 2 parties that is intended to be enforceable by law.

Covered by TRAK IPR and licenses

 

Tests For

Tests Against

 

Attributes

  • finish date (date)
  • party to contract (organisation)
  • start date (date)

Inherited Attributes:

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

Contract.jpg

TRAK::Contract participates in:

+ from Document

  • Contract has part Document
  • Contract traces to Contract
  • Contract traces to Document
  • Evidence issued by Organisation
  • Document has part Contract
  • Document traces to Contract

+ from Architecture Description Element:

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

Covered by TRAK IPR and licenses

 

Master Architecture View

Any Contract used within an architecture description of the system-of-interest must appear on a MV-03 Standards View for the architecture description.

The MV-03 is the Master Architecture View for Contract.

Covered by TRAK IPR and licenses

Comments

Part of the Solution Perspective.

Other Frameworks

  • DODAF - no representation of Contract at 2.02. DODAF does support the notion of parties to an agreement as a tuple with the DM2 Logical data model https://dodcio.defense.gov/Library/DoD-Architecture-Framework/dodaf20_logical_1_1/ but there is no entity that the architect can use that represents a contract.
  • MODAF - no representation of Contract at 1.2.004.
  • NAF - no representation of Contract at NAF 3.0 (3.1 unknown but unlikely if MODAF doesn’t)

References

Category:Metamodel -> Stereotype

Categories:

 

© 2010 Eclectica Systems Ltd.