View TRAK:Initial TRAK Baseline vs MODAF - Stereotypes

TRAK_logo_60.jpg
This outlines the major differences between the TRAK stereotypes in initial release of TRAK and the MODAF stereotypes in the MODAF 1.2.

It is a comparison made with respect to the stereotypes present in TRAK rather than to the MODAF. It does not make a full listing of the MODAF stereotypes not used although an outline list of the MODAF stereotypes that are absent is provided elsewhere.

TRAK:: and MODAF:: prefixes are used to identify the namespace in which each stereotype sits in order to separate similarly-named stereotypes.

Architecture Description

Status: Changed

MODAF
MODAF::Architecture Description - ‘A specification of a system of systems at a technical level which also provides the business context for the system of systems.’

TRAK
TRAK::Architecture Description - ‘IEE1471: An architectural description is a model of the architecture; its purpose is to answer all identified stakeholders’ questions about all identified architecture-related concerns for the system of interest;

The collection of architecture products that describes a system of interest.’

Also adds attributes.

Covered by TRAK IPR and licenses

Architecture Element

Status: New

MODAF
In MODAF the MODAF::Architecture Description is defined as comprising MODAF::Architectural Product which is defined as comprising architectural elements.There is no architecture element defined in MODAF.

TRAK
TRAK::Architecture Element - An individual architectural object.
Adds attributes for AD/model exchange.

Covered by TRAK IPR and licenses

Architecture Framework

Status: Changed

MODAF
MODAF::Architecture Framework - A set of connected View specifications which serve to define how an Enterprise may be represented by an Architectural Description.

TRAK
TRAK::Architecture Framework - An Enterprise Architecture Framework (EA Framework) is a framework Enterprise Architecture which specifies the allowed object types and relationships and which specifies how these are presented in architecture views associated with an Enterprise Architecture.


Covered by TRAK IPR and licenses

Architecture Metamodel

Status: New

MODAF
MODAF::Architecture Framework is defined as comprising MODAF::View but there is no metamodel.
The MODAF::MetaData refers to the Dublin Core metadata for the AD.

TRAK
TRAK::Architecture Metamodel - “Metamodeling” is the construction of a collection of “concepts” (things, terms, etc.) within a certain domain.A model is an abstraction of phenomena in the real world; a metamodel is yet another abstraction, highlighting properties of the model itself. A model conforms to its metamodel in the way that a computer program conforms to the grammar of the programming language in which it is written.


Covered by TRAK IPR and licenses

Architecture Perspective

Status: New

MODAF
In MODAF the grouping of a collection of architecture views is the Viewpoint which isn’t represented in the M3.

TRAK
TRAK::Architecture Perspective - IEEE 1471 refers to an Architectural Perspective as ‘Sharing of architectural models also facilitates an aspect-oriented style of architectural description’
i.e. a grouping of related and overlapping architectural views.


Covered by TRAK IPR and licenses

Architecture Product

Status: Changed

MODAF
MODAF::Architectural Product - A connected and coherent set of Architectural Elements which conform to a View.

TRAK
TRAK::Architecture Product - Something with architectural modelling content.
In TRAK it refers to the AD, Architecture Viewpoints, Architecture Views not just the elements connected to a View.


Covered by TRAK IPR and licenses

Architecture Task

Status: New

MODAF
-

TRAK
TRAK::ArchitectureTask - Something that will result in an architecture description.
Central to conformance with ISO 42010 is the premise that an AD is produced in response to a task to address concerns.


Covered by TRAK IPR and licenses

Architecture View

Status: Changed

MODAF
MODAF equates MODAF::View with IEEE 1471 in MODAF, however, views are not specified using Viewpoints (or any stereotype in the M3)

TRAK
TRAK::Architecture View - ISO42010: A representation of a whole system from the perspective of a related set of concerns. Each TRAK::Architecture View is specified by its own TRAK::Architecture Viewpoint.


Covered by TRAK IPR and licenses

Architecture Viewpoint

Status: New

MODAF
MODAF uses viewpoints to organise collections of related MODAF views.The M3 does not represent the viewpoint.

TRAK
See TRAK::Architecture View for difference use of viewpoint.


Covered by TRAK IPR and licenses

Capability

Status: Changed

MODAF
MODAF::Capability - ‘A high level specification of the enterprise’s ability’.

TRAK
TRAK::Capability -‘The ability to undertake a particular kind of action or the extent of someone’s or something’s ability.’


Covered by TRAK IPR and licenses

Competence

Status: Changed

MODAF
-

TRAK
Replaces MODAF::Actual Competence, MODAF::Competence


Covered by TRAK IPR and licenses

Concern

Status: Changed

MODAF
-

TRAK
TRAK::Concern - An interest in a subject held by one or more stakeholder Human Resource. In TRAK Concern is typed by model architecture, modelling style, framework, task.This is broader than the ISO 42010 sense.


Covered by TRAK IPR and licenses

Contract

Status: New

MODAF
-

TRAK
Used to apply standards at contract issue.


Covered by TRAK IPR and licenses

Document

Status: New

MODAF
-

TRAK
TRAK allows a trace to be made to reference or supporting documents.


Covered by TRAK IPR and licenses

Enterprise

Status: Modified

MODAF
Whole Life Enterprise and Enterprise Phase in MODAF. MODAF::Enterprise Phase has ?is structural part? of relationship with MODAFMODAF::Whole Life Enterprise. Enterprise Phase is therefore a temporal part of the Whole Life Enterprise.

TRAK
Replaced in TRAK by a single TRAK::Enterprise stereotype and a has part relationship. Rather than embed any notion of time into the name it is changed to Enterprise and attribute values used to represent the start and finish dates (period).


Covered by TRAK IPR and licenses

Enterprise Goal

Status:Changed

MODAF

TRAK
TRAK::Enterprise Goal subsumes MODAF::Enterprise Vision as well as MODAF::Enterprise Goal since vision and mission statements are a form of goal for the enterprise.


Covered by TRAK IPR and licenses

Function

Status: Changed

MODAF
-

TRAK
TRAK::Function adds Safety Integrity Level and Independent Safety Auditor,


Covered by TRAK IPR and licenses

Note that in TRAK any TRAK::Resource can have (be allocated) a Function whereas in MODAF only Functional Resources (MODAF:Capability Configuration|MODAF::Capability Configuration]], MODAF::Role and MODAF::System) can have Functions.

Human Resource

Status: Changed

MODAF

TRAK
TRAK::Human Resource inherits Safety Integrity Level and Independent Safety Auditor, Location


Covered by TRAK IPR and licenses

Interaction Element

Status: Changed

MODAF
MODAF - Data Element

TRAK
TRAK::Interaction Element typed by Unknown, Data, Energy, Materiel.


Covered by TRAK IPR and licenses

Item

Status: New

MODAF
MODAF:Information Exchange is the only stereotype that describes a logical exchange and it bundles information elements.

TRAK
Since logical exchanges also include resource, materiel as well as information and need to be represented a new stereotype was needed.


Covered by TRAK IPR and licenses

Item Exchange

Status: New

MODAF
MODAF::Information Element is used in MODAF. It can only represent information.

TRAK
Item Exchange can represent resource, materiel of information.


Covered by TRAK IPR and licenses

Job

Status: Changed

MODAF
MODAF - Post

TRAK
Replaces MODAF::ActualPost and MODAF::Post.
Adds Safety Integrity Level and Independent Safety Auditor, Location


Covered by TRAK IPR and licenses

Metric

Status: Changed

MODAF
MODAF::Measurable Property. MODAF also has Capability with Metric.

TRAK
At the present time TRAK::Metric can only be attached to TRAK::Enterprise Goal, TRAK::Capability, TRAK::Concept Activity or TRAK::Function as these are the most likely stereotypes to need to be quantified.


Covered by TRAK IPR and licenses

Milestone

Status: Changed

MODAF
MODAF::Milestone is defined as a type of Project where startTime = endTime

TRAK
TRAK::Milestone - event marking a significant change or stage in development. It has no associated start or finish time.


Covered by TRAK IPR and licenses

Need

Status: Changed

MODAF
Needline? in MODAF.

TRAK
TRAK::Need is typed by Unknown, Data, Energy, Materiel


Covered by TRAK IPR and licenses

Node

Status: Changed

MODAF
In the MODAF metamodel Node has no definition.

TRAK
TRAK::Node - A node is a logical operational entity.


Covered by TRAK IPR and licenses

Operational Activity

Status: Unchanged

MODAF

TRAK
Minor changes to definition.


Covered by TRAK IPR and licenses

Organisation

Status: Changed

MODAF

TRAK
TRAK::Organisation replaces MODAF::Actual Organisation and MODAF::Organisation Type
Adds Safety Integrity Level and Independent Safety Auditor, Location


Covered by TRAK IPR and licenses

Physical

Status: Changed

MODAF
MODAF includes stereotypes such as MODAF::Platform (not present in TRAK.) and MODAF::System as types MODAF::Artefact.

TRAK
Name change.
Additional attributes properties wrt Design Authority Organisation, Manufacturer Organisation, Safety Integrity Level and Independent Safety Auditor


Covered by TRAK IPR and licenses

Port

Status: Changed

MODAF
PortType,System Port

In MODAF only a MODAF::System can have a port and therefore port connection.

TRAK
TRAK::Port replaces MODAF:SystemPort? Adds ID and name.

Covered by TRAK IPR and licenses

In TRAK any TRAK::Resource can have a port.

Port Connection

MODAF
In MODAF this is a Port Connector. Only a MODAF::System can have a port connection.
TRAK


Covered by TRAK IPR and licenses

In TRAK any TRAK::Resource can have a port connection.

Project

Status: Changed

MODAF
MODAF::Project - A time-limited endeavour to create a specific set of products or services.

TRAK
As TRAK can represent the business (system) that delivers a system it is important to note that this is a Project not the organisation that staffs the project. A TRAK::Project can be handed over to another organisation.

TRAK::Project - An individual or collaborative enterprise that is carefully planned and designed to achieve a particular aim.


Covered by TRAK IPR and licenses

Project Activity

Status: New

MODAF
-

TRAK
TRAK allows description of building blocks in a programme. Useful for justification / explanation of context.


Covered by TRAK IPR and licenses

Protocol

Status: Unchanged

MODAF
-

TRAK
-


Covered by TRAK IPR and licenses

Requirement

Status: Changed
MODAF
MODAF – Requirements identified but not part of the MODAF specification.

TRAK
TRAK - an atomic requirement. Adds owning organisation, priority, type, text, title,

Covered by TRAK IPR and licenses

Resource

Status: Changed

MODAF
-

TRAK
TRAK::Resource has additional attributes for identity and location.


Covered by TRAK IPR and licenses

Resource Interaction

Status: Changed

MODAF
MODAF::Resource Interaction is defined around data exchange.

TRAK
TRAK::Resource Interaction is an interaction and is typed by Unknown, Data, Energy, Materiel


Covered by TRAK IPR and licenses

Role

Status: Unchanged?

MODAF
In the MODAF metamodel MODAF::Role has no definition.

TRAK
TRAK::Role - The function assumed or part played by a person or organisation.


Covered by TRAK IPR and licenses

Safety Monitored Resource

Status: New

MODAF

TRAK
Used to apply Safety Integrity Level and Independent Safety Auditor to TRAK::Resource and TRAK::Function.


Covered by TRAK IPR and licenses

Software

Status: Changed

MODAF
-

TRAK
Additional attributes properties wrt Design Authority Organisation, Manufacturer Organisation. Safety Integrity Level and Independent Safety Auditor


Covered by TRAK IPR and licenses

Standard

Status: Changed

MODAF
-

TRAK
Additional attribute to capture part.


Covered by TRAK IPR and licenses

System

Status: Changed

MODAF
MODAF::System MODAF::System is an artefact and part of the physical architecture alongside Platform and cannot have Organisation, Post or Role.

The MODAF System Viewpoint states that artefacts are ‘Physical objects made for a purpose (e.g. system, sub-system, platform, component or any physical item that occupies space and has attributes)’. MODAF also states that ‘ a system cannot contribute [to capability] alone; it must be hosted on a physical asset used by an organisational resource of both’

MODAF::Capability Configuration is also defined as part of the physical architecture.


TRAK
TRAK::System is central to the framework. TRAK defines humans as part of the system of interest.
TRAK::System sits where MODAF::Capability Configuration does - dead centre. There are also rules to prevent architects making shortcuts to bypass system definition.

It can also be used to represent an increment by configuring it with the things that are added. Addition or removal is indicated using a relationship with Milestone.
Additional attributes properties wrt System Authority Organisation, Design Authority Organisation, Manufacturer Organisation


Covered by TRAK IPR and licenses

 

 

© 2010 Eclectica Systems Ltd.