TRAK-Community

Date

15th February 2010

Definition

Part of the TRAK Management Perspective.

A normative document. It is a formal document that establishes criteria, processes, practices or defines protocols.

It represents a collective set of requirements rather than an atomic one for which the stereotype Requirement is used instead.

Covered by TRAK IPR and licenses

 

Tests For

• takes form of a document
• normative
• law
• requirement document
• normative plan document

Covered by TRAK IPR and licenses

Tests Against

• an atomic requirement - would then be a Requirement

Covered by TRAK IPR and licenses

Comments

Note that a Standard can be connected to an atomic requirement using has part if you need to draw attention to a specific individual requirement within it.

Attributes

• issue (string)
• issue date (date)
• number (string)
• part (string)
• withdrawal date (date)

Inherited Attributes

+ from Document

Covered by TRAK IPR and licenses

Relationships

Standard participates in the following relationships:
• Standard governs Architecture Description Element
• Standard has part Standard
• Standard is equivalent to Standard
• Standard enacts Standard
• Standard supercedes Standard
• Standard depends on Standard
• Contract applies Standard
• Standard is a Document
• Standard has part Requirement

from Architecture Description Element

• Concern about Standard
• Standard traces to Requirement
• Standard traces to Document
• Standard governs Standard

Covered by TRAK IPR and licenses

 

Master Architecture View

Any Standard 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 Standard.

Covered by TRAK IPR and licenses

Other Frameworks

• MODAF::Standard
• NAF::Standard

References

 

Category:Metamodel -> Stereotype
Category:Management

Categories:

• Management