View TRAK:Role
Version & Date
28th January 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 Solution Perspective.
The duties or status assumed or part played by a person or organisation.
Covered by TRAK IPR and licenses
Tests For
- many roles map to a single job
Covered by TRAK IPR and licenses
Tests Against
Attributes
Inherited Attributes:
- + Architecture Description Element
- + Human Resource which inherits from Resource (and hence also Safety-Monitored Element)
Covered by TRAK IPR and licenses
h3>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
Full size:File:Role.jpg
Role participates in the following:
- Job plays Role
- Organisation plays Role
- Role is a Human Resource
- Role requires Competence
- Role extends to Resource (System, Physical, Software, Human Resource)
- System is configured with Role
+ from Resource
- Role performs Function
- Resource Interaction from Role
- Resource Interaction to Role
- Role realises Node
Configuration History
See change record for the TRAK metamodel at https://trakmetamodel.svn.sourceforge.net/viewvc/trakmetamodel/trunk/?view=log
Comments
Jobs usually have many roles - some will be specific to the job and some will be more generic, for example as an employee. If a single role occupies most of the time of an employee then it is likely that a Job will be created around that role.
Sponsor and Stakeholder are roles that occur frequently and ISO/IEC 42010 / IEEE 1471 uses them in the definition of architecture viewpoints. A method for the use of TRAK:Role in a MV-02 Architecture Design Record is provided in the MVp-02 commentary which allows the scope and concerns of a particular architectural task to be described.
Typical roles include:
- Auditor
- Bidder
- Control Authority
- Design Authority
- Independent Safety Authority
- Prime Contractor
- Regulator
- Subject Matter Expert
- Supplier
- System Authority
Master Architecture View
Any Role used within an architecture description of the system-of-interest must appear on a SV-01 Solution Structure View for the architecture description.
The SV-01 is the Master Architecture View for Role.
Covered by TRAK IPR and licenses
Other Frameworks
References
- TRAK. Implementation. Architecture Description Elements https://sf.net/projects/trak/files/Implement TRAK/
- TRAK Enterprise Architecture Framework Metamodel. https://sf.net/p/trakmetamodel
Category:Metamodel -> Stereotype
Category:Solution
Category:Architecture Framework -> Solution