IDENTITY - UAF - Summary & Overview
| Description | Stakeholders: Executives, PMs, Enterprise Architects. Concerns: executive-level summary information in a consistent form. Definition: provides executive-level summary information in a consistent form that allows quick reference and comparison between architectural descriptions. Includes assumptions, constraints, and limitations that may affect highlevel decisions relating to an architecture-based work programme. |
|---|---|
| References | OMG - UAF - View - Summary & Overview |
| Parent Mapping | UAF Mappings |
MAPPED ENTITIES
| Framework Concept | Framework Definition | SysFEAT Concept | SysFEAT Definition |
|---|---|---|---|
 ActualEnterprisePhase |
A time period within which a set of Capabilities are deployed. References: OMG - UAF - ActualEnterprisePhase |
Enterprise Initiative |
An Enterprise Initiative is a past, current or future state of the enterprise. Each stage represents an initiative comprising a purposeful set of activities whose primary purpose is focused on achieving a set of clearly defined objectives that may transcend organisational boundaries and consequently require integrated team working under the direction of an Architecture Governance Committee. |
| ActualOrganizationalResource (as Stakeholder) |
Abstract element for an ActualOrganization, ActualPerson or ActualPost. References: OMG - UAF - ActualOrganizationalResource |
Individual Stakeholder |
An Individual Stakeholder is a person with a Stakeholder role in architecting & assurance activities. |
| ActualStrategicPhase |
A phase of an actual enterprise, mission, ValueStream or EnduringTask endeavor. References: OMG - UAF - ActualStrategicPhase |
Management Stage |
A Management Stage is a past, current or future state of a Management System. Each Management Stage represents a Management Initiative comprising a purposeful set of activities whose primary purpose is focused on achieving a set of clearly defined objectives assigned to Functional Assets managed in the Management System. The set of all Management Stages of an Management System defines its Roadmap. |
| Architecture |
An abstract type that represents a generic architecture. Subtypes are OperationalArchitecture, Service Architecture, and ResourceArchitecture. References: OMG - UAF - Architecture |
Operating Eco-System |
An Operating Eco-System is an Operating Context in which an Agent exists or lives for a specific purpose, interacting with partners. For instance, the operating context of an enterprise includes its customers and suppliers. References: OMG - UAF - Architecture OpenGroup - OAA - Ecosystem Russell Ackoff - System of Concepts - Environment of a system |
| ArchitectureDescription |
An Architecture Description is a work product used to express the Architecture of some System Of Interest. It provides executive-level summary information about the architecture description in a consistent form to allow quick reference and comparison between architecture descriptions -- It includes assumptions, constraints, and limitations that may affect high-level decisions relating to an architecture-based work program. References: OMG - UAF - ArchitecturalDescription |
Enterprise Architecting & Management |
The Enterprise Architecting & Management domain provides the concepts and tools required for Agile@Scale transformation Initiatives and associated Management Systems, along with their governing bodies (Governing Team). References: Felipe Castro - The Beginner’s Guide to OKRs SAFe© - Portfolio SAFe |
| ArchitectureMetaData |
Information associated with an ArchitecturalDescription, that supplements the standard set of tags used to summarize the Architecture. It states things like what methodology was used, notation, etc. References: OMG - UAF - ArchitectureMetaData |
||
| Challenge |
An existing or potential difficulty, circumstance, or obstacle which will require effort and determination from an enterprise to overcome in achieving its goals. References: OMG - BMM - Threat OMG - UAF - Challenge |
Driver Assessment |
A Driver Assessment is a kind of Assessment which is motivated by a Stakeholder Driver. References: OMG - UAF - Challenge |
| Concern |
The UAF concept of Concern comes from ISO 42010: ISO 42010 - Concern matter of relevance or importance to a stakeholder (3.17) Note 1 to entry: concerns can be identified with regards to an entity of interest (3.12) or independently, such as with regards to environment, scenario, situation or use case of that entity. Note 2 to entry: In this document, interest in an entity is intended to encompass interest in that entity’s environment (3.13), life cycle, architecture (3.2), requirements, design, implementation and operation. Such interests are captured via aspects (3.9), concerns and stakeholder perspectives (3.18). Note 3 to entry: The identification of a concern is often the result of prior knowledge, experience and praxis in the domain to which the concern applies. Note 4 to entry: See 5.2.3 for more discussion and examples. References: ISO 42010 - Concern OMG - UAF - Concern OpenGroup - TOGAF - Definitions - Concern |
Driver |
A Driver is a factor which can have a significant impact on the activities, and goals of an Enterprise or a Management System. References: ISO 42010 - Concern OMG - BMM - Influencer OMG - UAF - Driver OpenGroup - TOGAF - Definitions - Concern |
| EnterpriseMission |
Mission captures at a high level what you will do to realize your vision. References: OMG - UAF - EnterpriseMission |
EnterpriseMission is not directly represented in SysFEAT. Rational: |
|
| ImpactedBy |
A tuple used to denote that an Opportunity provides the means for achieving an EnterpriseGoal or Objective. A dependency relationship denoting that an Opportunity provides the means for achieving an EnterpriseGoal or Objective. SysFEAT follows the OMG BMM (see BMM Mapping) which asserts that Challenges are the result of an assessment. Thereby, the result of such assessments are not modeled as architectural relationships. Assessments leads to Decisions which then impact Functional Assets. References: OMG - UAF - ImpactedBy |
||
| Implements (Operational) |
A tuple that defines how an element in the upper layer of abstraction is implemented by a semantically equivalent element (for example tracing the Functions to the OperationalActivities) in the lower level of abstraction. References: OMG - UAF - Implements |
||
| Implements (Resource) |
A tuple that defines how an element in the upper layer of abstraction is implemented by a semantically equivalent element (for example tracing the Functions to the OperationalActivities) in the lower level of abstraction. References: OMG - UAF - Implements |
||
| MetaData |
A comment that can be applied to any element in the architecture. The attributes associated with this element details the relationship between the element and its related dublinCoreElement, metaDataScheme, category and name. This allows the element to be referenced using the Semantic Web. References: OMG - UAF - MetaData |
||
| MotivatedBy |
A tuple denoting the reason or reasons one has for acting or behaving in a particular way. References: OMG - UAF - MotivedBy |
Driver Subject |
Asset Block that is the subject of a Driver. |
| OperationalArchitecture |
A type used to denote a model of the Architecture, described from the Operational perspective. References: OMG - UAF - OperationalArchitecture |
Conceptual Environment |
A Conceptual Environment is an operating context which defines the interactions (Business Interaction) of an Operating Domain with its partners (Customers). References: OMG - UAF - OperationalArchitecture |
| Opportunity |
An existing or potential favorable circumstance or combination of circumstances which can be advantageous for addressing enterprise Challenges. References: OMG - BMM - Opportunity OMG - UAF - Opportunity |
Driver Assessment |
A Driver Assessment is a kind of Assessment which is motivated by a Stakeholder Driver. References: OMG - UAF - Challenge Opportunity is not directly represented in SysFEAT. Rational: |
| OrganizationalResource (as Stakeholder) |
A group of OrganizationalResources (Persons, Posts, Organizations and Responsibilities) associated for a particular purpose. References: OMG - UAF - OrganizationalResource |
Governance Committee |
A Governance Committee is a group of Stakeholders that contributes to architecting and assurance activities and governs Enduring Initiatives. |
| PhaseableElement |
An abstract element that indicates the types of elements that can be assigned to a specific ActualStrategicPhase. References: OMG - UAF - PhaseableElement |
||
| ResourceArchitecture |
A type used to denote a model of the Architecture, described from the ResourcePerformer perspective. References: OMG - UAF - ResourceArchitecture |
System of System Environment |
A System of System Environment is an operating context which defines the interactions (Business Service Channel) of a System of Systems with its partners (Partner Resource Architecture). References: OMG - UAF - ResourceArchitecture |
| ServiceArchitecture |
An element used to denote a model of the Architecture, described from the Services perspective. References: ServiceArchitecture |
ServiceArchitecture is not directly represented in SysFEAT. Rational: |
|
| Stakeholder |
An individual organizational resource, or a type of organizational resource (both internal and external to the enterprise) who has an interest in, or is affected by, outcomes or intermediate effects generated or influenced by the enterprise]. References: OMG - UAF - Stakeholder OpenGroup - TOGAF - Definitions - Stakeholder |
Stakeholder |
A Stakeholder is an individual, team, organization, or classes thereof, having an interest in an Initiative. Stakeholders have concerns with respect to the Initiative considered in relation to its environment. References: ISO 42010 - Terms - 3.10 - Stakeholder OMG - UAF - Stakeholder OpenGroup - TOGAF - Definitions - Stakeholder |
| View |
An information item, governed by an architecture viewpoint, comprising part of an architecture description that communicates some aspect of an architecture. References: OMG - UAF - View |
||
| Viewpoint |
Conventions for the creation, interpretation and use of an architecture view to frame one or more concerns that governs the creation of views. References: OMG - UAF - Viewpoint |
||
| WholeLifeEnterprise |
A WholeLifeEnterprise is a purposeful endeavor of any size involving people, organizations and supporting systems. It is made up of TemporalParts and StructuralParts. References: OMG - UAF - WholeLifeEnterprise |
Enterprise |
An Enterprise is a macro Enduring Initiative that delivers added-value Products (goods & services) to its target Customers. It requires a formal organization of groups of people and resources to achieve its purposes. References: OMG - UAF - WholeLifeEnterprise OpenGroup - TOGAF - Definition - Enterprise SAFe© - Enterprise SAFe© - Portfolio SAFe WordNet - Enterprise |
EXTERNAL REFERENCES
| Framework reference | SysFEAT Description |
|---|---|
 ISO 42010 - Concern |
The UAF concept of Concern comes from ISO 42010: ISO 42010 - Concern. matter of relevance or importance to a stakeholder (3.17) Note 1 to entry: concerns can be identified with regards to an entity of interest (3.12) or independently, such as with regards to environment, scenario, situation or use case of that entity. Note 2 to entry: In this document, interest in an entity is intended to encompass interest in that entity’s environment (3.13), life cycle, architecture (3.2), requirements, design, implementation and operation. Such interests are captured via aspects (3.9), concerns and stakeholder perspectives (3.18). Note 3 to entry: The identification of a concern is often the result of prior knowledge, experience and praxis in the domain to which the concern applies. Note 4 to entry: See 5.2.3 for more discussion and examples. In UAF, the Concern concept is not connected to any other concept and is isolated. In SysFEAT, concern is mapped to Driver which provides closer connection with Stakeholders interests. The UAF concept of Concern comes from ISO 42010: ISO 42010 - Concern matter of relevance or importance to a stakeholder (3.17) Note 1 to entry: concerns can be identified with regards to an entity of interest (3.12) or independently, such as with regards to environment, scenario, situation or use case of that entity. Note 2 to entry: In this document, interest in an entity is intended to encompass interest in that entity’s environment (3.13), life cycle, architecture (3.2), requirements, design, implementation and operation. Such interests are captured via aspects (3.9), concerns and stakeholder perspectives (3.18). Note 3 to entry: The identification of a concern is often the result of prior knowledge, experience and praxis in the domain to which the concern applies. Note 4 to entry: See 5.2.3 for more discussion and examples.
DriverA Driver is a factor which can have a significant impact on the activities, and goals of an Enterprise or a Management System. |
| OMG - BMM - Opportunity |
An existing or potential favorable circumstance or combination of circumstances which can be advantageous for addressing enterprise Challenges. An existing or potential favorable circumstance or combination of circumstances which can be advantageous for addressing enterprise Challenges. An existing or potential favorable circumstance or combination of circumstances which can be advantageous for addressing enterprise Challenges. |
| OMG - BMM - Threat |
An existing or potential difficulty, circumstance, or obstacle which will require effort and determination from an enterprise to overcome in achieving its goals. An existing or potential difficulty, circumstance, or obstacle which will require effort and determination from an enterprise to overcome in achieving its goals. |
| OMG - UAF - ActualEnterprisePhase |
A time period within which a set of Capabilities are deployed. A time period within which a set of Capabilities are deployed A time period within which a set of Capabilities are deployed. |
| OMG - UAF - ActualOrganizationalResource |
Abstract element for an ActualOrganization, ActualPerson or ActualPost. Abstract element for an ActualOrganization, ActualPerson or ActualPost. Abstract element for an ActualOrganization, ActualPerson or ActualPost. Abstract element for an ActualOrganization, ActualPerson or ActualPost. |
| OMG - UAF - ActualStrategicPhase |
A phase of an actual enterprise, mission, ValueStream or EnduringTask endeavor. A phase of an actual enterprise, mission, ValueStream or EnduringTask endeavor. A phase of an actual enterprise, mission, ValueStream or EnduringTask endeavor. |
| OMG - UAF - ArchitecturalDescription |
An Architecture Description is a work product used to express the Architecture of some System Of Interest. It provides executive-level summary information about the architecture description in a consistent form to allow quick reference and comparison between architecture descriptions -- It includes assumptions, constraints, and limitations that may affect high-level decisions relating to an architecture-based work program. An Architecture Description is a work product used to express the Architecture of some System Of Interest. It provides executive-level summary information about the architecture description in a consistent form to allow quick reference and comparison between architecture descriptions -- It includes assumptions, constraints, and limitations that may affect high-level decisions relating to an architecture-based work program. |
| OMG - UAF - Architecture |
An abstract type that represents a generic architecture. Subtypes are OperationalArchitecture, Service Architecture, and ResourceArchitecture. An abstract type that represents a generic architecture. Subtypes are OperationalArchitecture, Service Architecture, and ResourceArchitecture. An abstract type that represents a generic architecture. Subtypes are OperationalArchitecture, Service Architecture, and ResourceArchitecture.
Operating Eco-SystemAn Operating Eco-System is an Operating Context in which an Agent exists or lives for a specific purpose, interacting with partners. For instance, the operating context of an enterprise includes its customers and suppliers. |
| OMG - UAF - ArchitectureMetaData |
Information associated with an ArchitecturalDescription, that supplements the standard set of tags used to summarize the Architecture. It states things like what methodology was used, notation, etc. |
| OMG - UAF - Challenge |
An existing or potential difficulty, circumstance, or obstacle which will require effort and determination from an enterprise to overcome in achieving its goals. An existing or potential difficulty, circumstance, or obstacle which will require effort and determination from an enterprise to overcome in achieving its goals.
Driver AssessmentA Driver Assessment is a kind of Assessment which is motivated by a Stakeholder Driver. |
| OMG - UAF - Concern |
The UAF concept of Concern comes from ISO 42010: ISO 42010 - Concern matter of relevance or importance to a stakeholder (3.17) Note 1 to entry: concerns can be identified with regards to an entity of interest (3.12) or independently, such as with regards to environment, scenario, situation or use case of that entity. Note 2 to entry: In this document, interest in an entity is intended to encompass interest in that entity’s environment (3.13), life cycle, architecture (3.2), requirements, design, implementation and operation. Such interests are captured via aspects (3.9), concerns and stakeholder perspectives (3.18). Note 3 to entry: The identification of a concern is often the result of prior knowledge, experience and praxis in the domain to which the concern applies. Note 4 to entry: See 5.2.3 for more discussion and examples. The UAF concept of Concern comes from ISO 42010: ISO 42010 - Concern. matter of relevance or importance to a stakeholder (3.17) Note 1 to entry: concerns can be identified with regards to an entity of interest (3.12) or independently, such as with regards to environment, scenario, situation or use case of that entity. Note 2 to entry: In this document, interest in an entity is intended to encompass interest in that entity’s environment (3.13), life cycle, architecture (3.2), requirements, design, implementation and operation. Such interests are captured via aspects (3.9), concerns and stakeholder perspectives (3.18). Note 3 to entry: The identification of a concern is often the result of prior knowledge, experience and praxis in the domain to which the concern applies. Note 4 to entry: See 5.2.3 for more discussion and examples. In UAF, the Concern concept is not connected to any other concept and is isolated. In SysFEAT, concern is mapped to Driver which provides closer connection with Stakeholders interests. |
| OMG - UAF - EnterpriseMission |
Mission captures at a high level what you will do to realize your vision. The current implementation of "Mission" doesn't capture the need forf Mission and MissionThread modeling support required by the varions MoDs. The UAF team is working on refined implementation of Mission Thread. Thereby, the current Mission concepts of UAF are not implemented in SysFEAT as they do not fit theneeds. Mission captures at a high level what you will do to realize your vision. Mission captures at a high level what you will do to realize your vision. |
| OMG - UAF - ImpactedBy |
A tuple used to denote that an Opportunity provides the means for achieving an EnterpriseGoal or Objective. A dependency relationship denoting that an Opportunity provides the means for achieving an EnterpriseGoal or Objective. SysFEAT follows the OMG BMM (see BMM Mapping) which asserts that Challenges are the result of an assessment. Thereby, the result of such assessments are not modeled as architectural relationships. Assessments leads to Decisions which then impact Functional Assets. A tuple used to denote that an Opportunity provides the means for achieving an EnterpriseGoal or Objective. A dependency relationship denoting that an Opportunity provides the means for achieving an EnterpriseGoal or Objective. |
| OMG - UAF - Implements |
A tuple that defines how an element in the upper layer of abstraction is implemented by a semantically equivalent element (for example tracing the Functions to the OperationalActivities) in the lower level of abstraction. A tuple that defines how an element in the upper layer of abstraction is implemented by a semantically equivalent element (for example tracing the Functions to the OperationalActivities) in the lower level of abstraction. A tuple that defines how an element in the upper layer of abstraction is implemented by a semantically equivalent element (for example tracing the Functions to the OperationalActivities) in the lower level of abstraction. A tuple that defines how an element in the upper layer of abstraction is implemented by a semantically equivalent element (for example tracing the Functions to the OperationalActivities) in the lower level of abstraction. A tuple that defines how an element in the upper layer of abstraction is implemented by a semantically equivalent element (for example tracing the Functions to the OperationalActivities) in the lower level of abstraction. A tuple that defines how an element in the upper layer of abstraction is implemented by a semantically equivalent element (for example tracing the Functions to the OperationalActivities) in the lower level of abstraction. |
| OMG - UAF - MetaData |
A comment that can be applied to any element in the architecture. The attributes associated with this element details the relationship between the element and its related dublinCoreElement, metaDataScheme, category and name. This allows the element to be referenced using the Semantic Web. |
| OMG - UAF - MotivedBy |
A tuple denoting the reason or reasons one has for acting or behaving in a particular way. A tuple denoting the reason or reasons one has for acting or behaving in a particular way. |
| OMG - UAF - OperationalArchitecture |
Conceptual Environment A Conceptual Environment is an operating context which defines the interactions (Business Interaction) of an Operating Domain with its partners (Customers). A type used to denote a model of the Architecture, described from the Operational perspective. A type used to denote a model of the Architecture, described from the Operational perspective. A type used to denote a model of the Architecture, described from the Operational perspective. A type used to denote a model of the Architecture, described from the Operational perspective. |
| OMG - UAF - Opportunity |
An existing or potential favorable circumstance or combination of circumstances which can be advantageous for addressing enterprise Challenges. An existing or potential favorable circumstance or combination of circumstances which can be advantageous for addressing enterprise Challenges. An existing or potential favorable circumstance or combination of circumstances which can be advantageous for addressing enterprise Challenges. |
| OMG - UAF - OrganizationalResource |
Org-Unit An Org-Unit is a type of Human Resource that represent a unit of social groups within an organization, responsible for operating one or more enterprise's Business Functions. An abstract type for Organization, Person, Post and Responsibility. An abstract type for Organization, Person, Post and Responsibility. A group of OrganizationalResources (Persons, Posts, Organizations and Responsibilities) associated for a particular purpose. An abstract type for Organization, Person, Post and Responsibility. A group of OrganizationalResources (Persons, Posts, Organizations and Responsibilities) associated for a particular purpose. A group of OrganizationalResources (Persons, Posts, Organizations and Responsibilities) associated for a particular purpose. |
| OMG - UAF - PhaseableElement |
An abstract element that indicates the types of elements that can be assigned to a specific ActualStrategicPhase. |
| OMG - UAF - ResourceArchitecture |
A type used to denote a model of the Architecture, described from the ResourcePerformer perspective. A type used to denote a model of the Architecture, described from the ResourcePerformer perspective. A type used to denote a model of the Architecture, described from the ResourcePerformer perspective. A type used to denote a model of the Architecture, described from the ResourcePerformer perspective. A type used to denote a model of the Architecture, described from the ResourcePerformer perspective.
System of System EnvironmentA System of System Environment is an operating context which defines the interactions (Business Service Channel) of a System of Systems with its partners (Partner Resource Architecture). |
| OMG - UAF - Stakeholder |
Stakeholder A Stakeholder is an individual, team, organization, or classes thereof, having an interest in an Initiative. Stakeholders have concerns with respect to the Initiative considered in relation to its environment. An individual organizational resource, or a type of organizational resource (both internal and external to the enterprise) who has an interest in, or is affected by, outcomes or intermediate effects generated or influenced by the enterprise]. An individual organizational resource, or a type of organizational resource (both internal and external to the enterprise) who has an interest in, or is affected by, outcomes or intermediate effects generated or influenced by the enterprise]. |
| OMG - UAF - View |
An information item, governed by an architecture viewpoint, comprising part of an architecture description that communicates some aspect of an architecture. An information item, governed by an architecture viewpoint, comprising part of an architecture description that communicates some aspect of an architecture. |
| OMG - UAF - Viewpoint |
Conventions for the creation, interpretation and use of an architecture view to frame one or more concerns that governs the creation of views. Conventions for the creation, interpretation and use of an architecture view to frame one or more concerns that governs the creation of views. |
| OMG - UAF - WholeLifeEnterprise |
Enterprise An Enterprise is a macro Enduring Initiative that delivers added-value Products (goods & services) to its target Customers. It requires a formal organization of groups of people and resources to achieve its purposes. A WholeLifeEnterprise is a purposeful endeavor of any size involving people, organizations and supporting systems. It is made up of TemporalParts and StructuralParts. A WholeLifeEnterprise is a purposeful endeavor of any size involving people, organizations and supporting systems. It is made up of TemporalParts and StructuralParts. |
| OpenGroup - TOGAF - Definitions - Concern |
The UAF concept of Concern comes from ISO 42010: ISO 42010 - Concern. matter of relevance or importance to a stakeholder (3.17) Note 1 to entry: concerns can be identified with regards to an entity of interest (3.12) or independently, such as with regards to environment, scenario, situation or use case of that entity. Note 2 to entry: In this document, interest in an entity is intended to encompass interest in that entity’s environment (3.13), life cycle, architecture (3.2), requirements, design, implementation and operation. Such interests are captured via aspects (3.9), concerns and stakeholder perspectives (3.18). Note 3 to entry: The identification of a concern is often the result of prior knowledge, experience and praxis in the domain to which the concern applies. Note 4 to entry: See 5.2.3 for more discussion and examples. In UAF, the Concern concept is not connected to any other concept and is isolated. In SysFEAT, concern is mapped to Driver which provides closer connection with Stakeholders interests. The UAF concept of Concern comes from ISO 42010: ISO 42010 - Concern matter of relevance or importance to a stakeholder (3.17) Note 1 to entry: concerns can be identified with regards to an entity of interest (3.12) or independently, such as with regards to environment, scenario, situation or use case of that entity. Note 2 to entry: In this document, interest in an entity is intended to encompass interest in that entity’s environment (3.13), life cycle, architecture (3.2), requirements, design, implementation and operation. Such interests are captured via aspects (3.9), concerns and stakeholder perspectives (3.18). Note 3 to entry: The identification of a concern is often the result of prior knowledge, experience and praxis in the domain to which the concern applies. Note 4 to entry: See 5.2.3 for more discussion and examples.
DriverA Driver is a factor which can have a significant impact on the activities, and goals of an Enterprise or a Management System. |
| OpenGroup - TOGAF - Definitions - Stakeholder |
An individual organizational resource, or a type of organizational resource (both internal and external to the enterprise) who has an interest in, or is affected by, outcomes or intermediate effects generated or influenced by the enterprise]. An individual organizational resource, or a type of organizational resource (both internal and external to the enterprise) who has an interest in, or is affected by, outcomes or intermediate effects generated or influenced by the enterprise].
StakeholderA Stakeholder is an individual, team, organization, or classes thereof, having an interest in an Initiative. Stakeholders have concerns with respect to the Initiative considered in relation to its environment. |
| ServiceArchitecture |
An element used to denote a model of the Architecture, described from the Services perspective. The ServiceArchitecture UAF Concept is not implemented in SysFEAT. Rational: the UAF Service layer is redundant methodologically redundant with the Operational Layer. An issue has been raised in the UAF Group to raise this issue. An element used to denote a model of the Architecture, described from the Services perspective. |