TRAK-Community

Version & Date

2nd October 2017

Configuration History

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

Definition

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

From the TRAK Metamodel:

An individual architecture description object that is used to describe or represent an item of real-world architecture. An architecture description element can appear in an architecture description.

Covered by TRAK IPR and licenses

Tests For

Not applicable - not itself used in any TRAK architecture views.

Tests Against

Not applicable - not itself used in any TRAK architecture views.

Attributes

• name
• description
• element URI
• AD exchange element external reference
• AD exchange element owning ID
• AD exchange element owning organisation
• AD exchange element recipient element name
• AD exchange element recipent element ID
• AD exchange element recipient organisation
• AD exchange element reference URL
• pm codeword
• pm descriptor (enumerated = None/Budget/ Commercial / In Confidence/ Investigation / Management /Medical / Personal /Personal Data/ Policy & Strategy)
• pm marking (enumerated = Not Protectively Marked /Protect / Restricted/Confidential / Secret /Top Secret)
• pm marking owner (organisation)
• pm national caveat
• reference URL

Covered by TRAK IPR and licenses

These attributes are intended to capture the information that might be needed for an exchange of an AD between 2 different organisations and therefore between 2 different tools.

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

Architecture Description Element participates in the following relationships:

Architecture Description Tuples that may appear in any TRAK View:

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

Tuples within the TRAK Metamodel used for the description or management of TRAK, for example to show conformance to the ISO/IEC/IEEE 42010 standard:

• Architecture Description Tuple has part Architecture Description Element
• Architecture Description Element is member of Architecture Perspective
• Architecture View presents Architecture Description Element

The following elements within the TRAK Metamodel are Architecture Description Elements within TRAK.

• Architecture Description Elements represented as Nodes
  • Architecture Description
  • Architecture Task
  • Architecture View
  • Argument
  • Capability
  • Claim
  • Competence
  • Concept Activity
  • Concern
  • Contract
  • Document
  • Enterprise
  • Enterprise Goal
  • Event
  • Evidence
  • Function
  • Interaction Element
  • Item
  • Job
  • Metric
  • Milestone
  • Mitigation
  • Node
  • Organisation
  • Physical
  • Port
  • Project
  • Project Activity
  • Protocol
  • Requirement
  • Risk
  • Role
  • Software
  • Standard
  • System
  • Threat
  • Vulnerability

• Architecture Description Elements represented as Connectors

  • about
  • addresses
  • allows
  • AND
  • applies
  • aspires to
  • can lead to exposure to
  • carries
  • caused by
  • conducts
  • contains
  • contributes to
  • delivers
  • depends on
  • derived from
  • disproves
  • enacts
  • equivalent to
  • exchanges
  • exploits
  • exposed to
  • exposes
  • extends to
  • from
  • governs
  • has
  • has part
  • hosted on
  • impacts on
  • implements
  • is a
  • is attached to
  • is configured with
  • is managed by
  • is member of
  • is necessary for
  • is quantified by
  • issued by
  • Item Exchange
  • makes
  • marked by
  • marks introduction of
  • marks removal of
  • Need
  • NOT
  • opposes
  • OR
  • owns
  • performs
  • physically depends on
  • physically supports
  • plays
  • Port Connection
  • poses
  • precedes
  • proves
  • realises
  • removes
  • requires
  • Resource Interaction
  • results in
  • satisfies
  • supersedes
  • supports
  • to
  • to conduct
  • traces to
  • triggers
  • undertakes
  • uses

 

Configuration History

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

Master Architecture View

Not Applicable since Architecture Description cannot itself appear in any architecture view - it is an abstract parent type or class.

Comments

The parent of all TRAK element types used in ADs. The intent of the attributes is to capture identification and ownership to allow bi-directional exchange of ADs between 2 organisations.

Covered by TRAK IPR and licenses

Element URI

The idea or thought is that someday it will be possible for models to be distributed and the URI is the attribute that holds the address of the element.

AD Exchange

Attributes beginning with ‘model exchange’ are designed to try and preserve information such that a 2-way round trip exchange of elements is possible between 2 organisations and therefore possibly tools. In this situation we need to try and preserve each organisation’s unique IDs etc.

Protective Markings

For the security-conscious it is now possible to declare national security classifications without the document becoming Restricted in doing so.  In the UK the Security Policy Framework replaces the older Manual of Protective Security (MPS). See https://www.cabinetoffice.gov.uk/spf/faqs.aspx on the Cabinet Office website.

The protective or protective markings are taken from the UK but should suffice in most situations, including commercial.

pm Descriptor

A qualifier used with the protective marking to denote the type of information, sensitivity or need to protect e.g. Personal. Commercial. i.e. combination might be PROTECT - PERSONAL

• None
• Budget - Proposed or actual measures for the Budget before their announcement
• Commercial - relating to a commercial establishments processes or affairs
• Indicates information received under an air of confidence, the disclosure of which might be an actionable breach in law
• Investigation - Investigations into disciplinary or criminal matters
• Management - policy and planning affecting the interest of groups of staff
• Medical - medical reports, records and material relating to staff
• Personal - Information that contains personal information of an individual. Material intended for the person to whom it may be addressed
• Personal Data - Any biographic data relating to an individual (e.g. name, address, D.O.B.) or Sensitive personal data as defined by s2 of the Data protection Act, including records relating to the criminal justice system, finances or group membership
• Policy / Strategy - information that forms part of a council policy or strategy or procedure that isassociated with internal use only

These have been taken from the following but the suspicion is that there is a Home Office or Cabinet scheme. Although UK in origin they do offer a general method for marking privacy even in non national security environments.

• Security Policy No.2: Protective Marking and Asset Control https://www.cabinetoffice.gov.uk/spf/sp2_pmac.aspx
• Handling of Protectively Marked Materiel - A Guide for Police Personnel (October 2001). https://www.ncalt.com/documents/modelsforlearning/Protective Marking.pdf
• Guidance for the Classification Marking of NHS Information https://www.connectingforhealth.nhs.uk/systemsandservices/infogov/security/risk/infoclassifications.doc
• The Use of Protective Markings in the Department of Work and Pensions. https://www.whatdotheyknow.com/request/14130/response/38437/attach/6/The Use of Protective Markings in DWP.doc
• Scottish National Infrastructure - Protective Marking Guideline https://www.improvementservice.org.uk/library/download-document/2342-scottish-national-infrastructure-guideline-for-protectively-marking-information/

pm Marking Owner

The owner of the protective marking who has the authority to sanction release or lower the protective marking classification. It is used in conjunction with the protective marking, usually as the prefix e.g. NHS PROTECT, TFL CONFIDENTIAL, or as a national authority - UK RESTRICTED.

pm Codeword

A codeword is another mechanism to limit distribution - only those with the need to know and the codeword have access to the element

pm National Caveat

A restriction of the audience who can see the element by nationality e.g. UK EYES ONLY would restrict the potential audience to UK nationals. This is not the same as the protective marking owner i.e. UK PROTECT does not restrict the audience and therefore the combination would be for example UK EYES ONLY, UK PROTECT

Note that a restriction on who can see the element through pm Codeword or pm National Caveat is separate to the marking itself. Similarly the release authority or owner is separate i.e. UK Protect means that the change of classification is with the UK authorities. This is not to be confused with UK Eyes Only which is a limitation on who can see the element.

Other Frameworks

References

• Architecture Description Tuple
• TRAK Enterprise Architecture Framework Metamodel. https://sf.net/p/trakmetamodel
• TRAK. Implementation. Architecture Description Elements https://sf.net/projects/trak/files/Implement TRAK/

Category:Metamodel -> Stereotype

Categories:

• Metamodel
  • Stereotype