SysFEAT - Systemic Framework for Enterprise Architecture & Transformationk

IDENTITY DIAGRAM MAPPING EXTERNAL REFERENCES

IDENTITY - UAF - Operational Views

Description	Describe the requirements, operational behavior, structure, and exchanges required to support (exhibit) capabilities. Defines all operational elements in an implementation/solution independent manner.
References	OMG - UAF - View - Operational Views
Parent Mapping	UAF Mappings

../images/e23f9c55631844ad_e23f9c75631844cb_i.png

MAPPED ENTITIES

Framework Concept	Framework Definition	SysFEAT Concept	SysFEAT Definition
AbitraryConnector
Action Process	An abstract type that represents a behavior or process (i.e. a Function or OperationalActivity) that can be performed by a Performer. References: OMG - UAF - Process	Action Process	An Action Process is a Behavior that describes a typical course of action intended to produce Outcome Events, through the involvement of Agents as Active Participants. During its course of action, a process consumes or produces Functional Assets, including Information Assets. 1) It may memorize or access Information Assets from and to its Process Stores. 2) It may receive Functional Assets at its boundary: Outcome Consumptions. 3) It may signal the production of Functional Assets at its boundary: Outcome Productions. The course of actions of a Action Process is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do. Within SysFEAT, we can examine Action Processes from two distinct perspectives: a) A conceptual standpoint is provided by Value Streams. b) A concrete implementation standpoint is provided by Resource Action Processes. References: ISO 15926 - ClassOfActivity ISO 9000 - 3.4.1 - Process Merriam Webster - Process OMG - BPMN - Process OMG - UAF - Process OMG - UML - Activity OpenGroup - ArchiMate - Process Russell Ackoff - System of Concepts - Process WordNet - Process
ActivityPerformableUnderCondition	The ActualCondition under which an Activity is performed. References: OMG - UAF - ActivityPerformableUnderCondition		ActivityPerformableUnderCondition is not directly represented in SysFEAT. Rational: This relationship is a side effect of UAF supporting the DoDAF2 specification. There is a better way to associate "conditions" to architecture asset such using measurement constraints.
ActualCondition	An individual describing an actual situation with respect to circumstances under which an OperationalActivity, Function or ServiceFunction can be performed. References: OMG - UAF - ActualCondition		ActualCondition is not directly represented in SysFEAT. Rational: Actual conditions are typical characteristics such as terrain type (e.g. muddy, frozen ground, deep snow, etc.), weather conditions, light conditions. There is no need, at the architecture level, to have instances of such characteristics (eg light condition in Paris on September 2020).
ActualEnvironment	An individual that describes the circumstances of an Environment. References: OMG - UAF - ActualEnvironment		ActualEnvironment is not directly represented in SysFEAT. Rational: Actual conditions are typical characteristics such as terrain type (e.g. muddy, frozen ground, deep snow, etc.), weather conditions, light conditions. There is no need, at the architecture level, to have instances of such characteristics (eg light condition in Paris on September 2020).
ActualLocation	An individual that describes a physical location, for example using text to provide an address, Geo-coordinates, etc. References: OMG - UAF - ActualLocation	Location	A Location is a geopolitical location anywhere on the earth. Examples: - France - Paris - Washington DC - Cairo - Buenos-Aires - Asia References: ISO 15926 - SpatialLocation OMG - UAF - ActualLocation
ActualService	An individual Service. References: OMG - UAF - ActualService		ActualService is not directly represented in SysFEAT. Rational: The UAF Service layer is methodologically redundant with the Operational Layer. An issue has been raised to the UAF Group to address this issue.
Asset	References: OMG - UAF - Asset
Capability		Business Capability	A Business Capability is a conceptual Capability that benefits to Customers (internal or external) of the enterprise. It expresses an ability to produce Conceptual Outcome Events. A Business Capability is defined by its intended Enterprise Outcome Events and the conditions (Condition Property) under which the production of the Enterprise Outcome Events shall be proceeded. The actual Condition Scale Values for a given Business Capability at different stages of Enterprise Initiatives is given by their exhibition (Exhibited Capability). References: OMG - BACM - Capability OMG - UAF - Capability OpenGroup - ArchiMate - Capability OpenGroup - TOGAF - Definition - Business Capability
CapabilityConfiguration		System of Systems	A System of Systems is a Macro Capability Configuration that combine several System of Resources to deliver a common high level Business Capability. Examples: - Air traffic control system - Smart city system - Health Care System - Search and Resue system (SAR) - Naval squadron consisting of an aircraft carrier, its escort ships and its C5ISR capabilities. References: OMG - UAF - CapabilityConfiguration
CapableElement		Agent	An Agent is an Operating Asset which is able to participate actively to Behaviors, to produce and react to Outcome Events. 1. Agents participate to Action Processes (Active Participant) and/or conduct Action Processes (Performed Process). 2. Agents participate to Interaction Process (Scenario Participant) describing how they interact with other Agents. These actions and interactions define Agents boundaries described by Service Interfaces. References: Christensen Institute - Modularity ISO 15926 - ClassOfPossibleRoleAndDomain OMG - KerML - Structure OMG - UML - EncapsulatedClassifier OpenGroup - ArchiMate - Internal Active Structure Element OpenGroup - OAA - Modularity OpenGroup - TOGAF - Definition - System Russell Ackoff - System of Concepts - Abstract System WordNet - Agent
ConceptItem
Exhibits		Fulfilled Capability	Capability(ies) fulfilled by an Agent and its Behaviors. References: OMG - UAF - Exhibits
GeopoliticalExtentType	GeopoliticalExtentType is not implemented as a subtype of OperationalExchangeItem. GeopoliticalExtentType was an initial requirement from DoDAF2 which hasn't been adopted by the final DoDAF specification. It is a legacy component of UAF. References: OMG - UAF - GeopoliticalExtentType
HighLevelOperationalConcept
InformationModel	Conceptual - Indicates that the InformationModel associated with the InformationModelKind is a conceptual InformationModel that defines the required high-level data concepts and their relationships. References: OMG - UAFML - InformationModelKind
InteractionMessage	An abstract type that groups several types of messages used in the InteractionScenario. References: OMG - UAF - InteractionMessage	Interaction Flow	References: OMG - UAF - InteractionMessage
InteractionScenario	An abstract type that specifies interactions between Assets, like ResourcePerformers, and Services. References: OMG - UAF - InteractionScenario	Interaction Process	An Interaction Process is a story (Behavior) that describes how the components of an Agent interacts to produce and consume Outcome Events. This includes: 1) A course of events represented by Object Flows depicting the succesion of intermediate Outcome Events towards the production of the final Outcome Events. 2) Interacting Agents who participate to the story. References: OMG - UAF - InteractionScenario
IsCapableToPerform		Performed Value Stream	Relationship between a Conceptual Agent and Conceptual Behaviors that it performs.
KnownResource	Asserts that a known ResourcePerformer constrains the implementation of the OperationalPerformer that plays the role in the OperationalArchitecture. References: OMG - UAF - KnownResource		KnownResource is not directly represented in SysFEAT. Rational: Resource have different kinds of exchange definitions than those used in operational views.
LifeLine	A Lifeline represents an individual participant in the Interaction. While parts and structural features may have multiplicity greater than 1, Lifelines represent only one interacting entity. References: OMG - UML - Lifeline	Scenario Participant	A Scenario Participant is a Behavior Participant engaged in Interaction Flow the context of an Interaction Process.
MapsToCapability
Natural Resource	Type of physical resource that occurs in nature such as oil, water, gas or coal. References: OMG - UAF - NaturalResource	Natural Resource	A Natural Resource is a kind Physical Business Agent that refers to any class of material or substance that occurs naturally in the environment and can be used by humans for various purposes. These resources are derived from the Earth and include a wide range of physical entities such as water, minerals, forests, fossil fuels, soil, and air. References: OMG - UAF - NaturalResource
Operational Agent
OperationalActivity	An Activity that captures a logical process, specified independently of how the process is carried out. References: OMG - UAF - Operational Activity	Value Stream	Value Streams are used to frame the Conceptual Operating Model of the enterprise: they describe how the enterprise shall operate, at the conceptual level, and helps chunking responsibilities between Conceptual Agents (Operating Domain or Business Function) . In the EA context, a Value Stream is a conceptual Action Process that represents an overarching perspective of the organization's processes aiming at producing Conceptual Outcome Events. The focus is on shaping and understanding the functional relationships and roles within the enterprise : its functional division of labor. This is not to be confused with Value Stream Mapping (VSM) which is focused on Lean optimization and is addressed with the concept of Business Process (see the Organization & Processes domain). A Value Stream is performed by Conceptual Agents who produce Conceptual Outcome Events. It is depicted as a sequence of Value Stream Stages, controlled by events and conditions. Value Stream Activitys are carried out by the involvment of Conceptual Agents as participants in the Value Stream. During its course of action, a Value Stream consumes, produces or stores Business Objects. 1) It may read or write Domain Assets in its Business Object Store. 2) It may receive Domain Assets at its boundary: reacted to Business Outcome Events. 3) It may produce Domain Assets at its boundary: produced Business Outcome Events. The course of actions of a Value Stream is constrained by the application of rules ( Conceptual Rule Enforcement) that define what is allowed and not allowed to do. There are traditionnaly two kinds of Value Streams: 1) Development development Value Streams define all of the actions, both value-creating and nonvalue-creating, required to bring a Product from concept to launch. 2) Operational Value Streams define define all of the actions, both value-creating and nonvalue-creating, required from order to delivery. These include actions to process information from the Customer and actions to transform the product on its way to the Customer. References: Lean.org - Value Stream OMG - BACM - ValueStream OMG - BPMN - Process OMG - UAF - Operational Activity OMG - UAF - OperationalActivity OpenGroup - ArchiMate - Value-Stream OpenGroup - TOGAF - Definition - Value Stream SAFe© - Value Stream Wikipedia - Value Stream
OperationalActivityAction		Value Stream Stage	Involvment of a Value Stream as a step of a parent Value Stream. References: OMG - UAF - OperationalActivityAction
OperationalActivityEdge		Value Stream Flow	Flow of resource or information between stages of a Value Stream.
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
OperationalAsset		Conceptual Operating Asset	A Conceptual Operating Asset is an Operating Asset used to describe the Conceptual Operating Model of the enterprise. It includes Value Streams, Operating Domains and Business Functions and the way they contribute to the delivery of Business Outcome Events. References: OMG - UAF - OperationalAsset
OperationalConnector		Conceptual Interaction Channel	An Interaction represents a contract between entities in a specific context inside or outside a company. These entities can be organizational units, activities, or processes. The content of this contract is described in a protocol.
OperationalConstraint		Conceptual Business Rule	A Conceptual Business Rule is a rule that is under business jurisdiction. A rule’s being 'under business jurisdiction' means that it is under the jurisdiction of the semantic community that it governs or guides - that the semantic community can opt to change or discard the rule. Laws of physics may be relevant to a company (or other semantic community); legislation and regulations may be imposed on it; external standards and best Semantics of Business Vocabulary and Business Rules, v1.0 161 practices may be adopted. These things are not business rules from the company’s perspective, since it does not have the authority to change them. The company will decide how to react to laws and regulations, and will create business rules to ensure compliance with them. Similarly, it will create business rules to ensure that standards or best practices are implemented as intended. References: OMG - BMM - Business Rule OMG - UAF - Operational Constraint
OperationalInformation	References: OMG - UAF - OperationalInformation	Domain Asset	A Domain Asset is the representation of any type of tangible or intanglible resource, or its respective state, that is critical for comprehending an enterprise, including its data, resources, and activities. Similar to any Information Asset, a Domain Asset can be classified into three categories: 1) Conceptual Entitys denote entities that can change over time. 2) Event Concepts embody the temporal boundaries associated with Conceptual Entitys. 3) Concept Propertys represent immutable characteristics of Conceptual Entitys. References: OMG - BACM - Business Object OMG - UAF - OperationalInformation Russell Ackoff - Choice & Communication - Concept
OperationalInteractionScenario	A specification of the interactions between OperationalPerformers in an OperationalArchitecture. References: OMG - UAF - OperationalInteractionScenario	Conceptual Interaction Scenario	As part of the Conceptual Operating Model, a Conceptual Interaction Scenario is a story that frames how the components of a Conceptual Agent interacts to achieve Conceptual Outcome Events. This includes: 1) A course of events represented by Business Object Flows depicting the steps towards the delivery of expected Conceptual Outcome Events. 2) Conceptual Agents who participate to the story.
OperationalInterface		Business Service Interface	A Business Service Interface is a communication behavior that describes a typical course of interactions intended to produce Business Outcome Events, through the involvement of Business Agents. References: OMG - UAF - Operational Interface OpenGroup - ArchiMate - Business-Service OpenGroup - IT4IT - Defining Service Reference Architecture
OperationalMessage		Resource Object Flow
OperationalPerformer	A logical entity that IsCapableToPerform OperationalActivities which produce, consume and process Resources. References: OMG - UAF - OperationalPerformer	Business Function	A Business Function is a Mezzo unit within the enterprise's functional division of labor. It is used to shape the enterprise management structure in regard to how it produces, consumes or processes Business Outcome Events: information, energy, materiel. A Business Function specifies Skills and Functionality(ies) required to perform their activities effectively. References: Christensen Institute - Modularity OMG - UAF - OperationalPerformer OpenGroup - TOGAF - Definition - Business Function OpenGroup - TOGAF 9 - Definition - Business Function Russell Ackoff - System of concepts - FunctionalDivisionOfLabor
OperationalPort
OperationalRole	Usage of a OperationalPerformer or OperationalArchitecture in the context of another OperationalPerformer or OperationalArchitecture. Creates a whole-part relationship. References: OMG - UAF - OperationalRole	Conceptual Agent Part
OperationalSignal		Business Outcome Event	A Business Outcome Event is a Business Event that signals the happening of a change in the state of a Business Operating Asset, produced by the Business Behavior of a Business Agent, for the benefits of an internal or external consumer (especially Customers). References: OMG - BACM - Outcome OMG - UAF - Effect OMG - UAF - OperationalSignal OpenGroup - IT4IT - Defining Service Reference Architecture OpenGroup - OAA - Definition - Outcome
Organization		Department Type	A Department Type is a Mezzo Org-Unit which serves as an administrative unit template in both government and business Organizations. Examples: - Sales department; - Finance department; - Logistics department.. References: OMG - UAF - Organization OpenGroup - ArchiMate - Business-Actor OpenGroup - ArchiMate - Business-Collaboration OpenGroup - TOGAF - Enterprise Metamodel - Actor Russell Ackoff - System of concepts - FunctionalDivisionOfLabor Russell Ackoff - System of Concepts - Organizations UCF Glossary - Department
OrganizationalResource	A group of OrganizationalResources (Persons, Posts, Organizations and Responsibilities) associated for a particular purpose. References: 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. References: Christensen Institute - Modularity Humanresourcesedu.org - Human Resource OMG - UAF - OrganizationalResource OpenGroup - ArchiMate - Business Internal Active Structure Element OpenGroup - ArchiMate - Business-Actor Russell Ackoff - System of Concepts - Organizations
PhysicalResource	An abstract type defining physical resources (i.e. OrganizationalResource, ResourceArtifact and NaturalResource). References: OMG - UAF - PhysicalResource
Post	A type of job title or position that a person can fill (e.g. Lawyer, Solution Architect, Machine Operator or Chief Executive Officer). References: OMG - UAF - Post	Organizational Position	An Organizational Position is a type of position held by people when part of a Department Type. Examples: - Sales representative - Developer - Storekeeper - Architect References: OMG - UAF - Post OpenGroup - ArchiMate - Business-Actor OpenGroup - TOGAF - Definition - Role UCF Glossary - Position Description
ProblemDomain		Subject Activity Domain	References: OMG - UAF - ProblemDomain
ProcessEdge		Object Flow	Object Flow is a Sequence Flow that convey from its source References: OMG - KerML - ItemFlow
ProcessUsage	An abstract type that represents a behavior or process (i.e., a Function or OperationalActivity) that can be performed by a Performer. References: OMG - UAF - ProcessUsage	Process Step	A Process Step is a Process Activity invoking another Action Process References: OMG - BPMN - Call Activity OMG - UAF - ProcessUsage OMG - UML - CallBehaviorAction
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
ResourceArtifact		Business System	A Business System is a man made artifact (Concrete Hardware System or Business Software System) which exposes Functionalityies and can produce Business Outcome Events. A Business System performs System Processes and participates to System Processes or to Business Processes. In System Processes, a Business System is always an active participant (System Process Participant). In Business Processes, a Business System is either an active participant (Automated Participant) or an Instrument used by Org-Units. References: DAU Glossary - family-systems OMG - UAF - ResourceArtifact Russell Ackoff - Choice & Communication - Instrument UCF Glossary - Business System WordNet - Artifact
ResourceAsset		Business Operating Asset	Business Operating Assets comprise physical assets which contribute to the production and consumption of Business Outcome Events of the enterprise. This includes Business Agents, their behaviors (Business Behavior: Business Resource Process, Business Resource Interaction Process), References: OMG - UAF - CapableElement OpenGroup - TOGAF - Definition - Solution Building Block OpenGroup - TOGAF - Guide - Solution Building Blocks
ResourcePerformer		Business Agent	A Business Agent is a Resource Agent which produces and reacts to Business Outcome Events of the enterprise. A Business Agent can be a Human Resource (Organizational Position or Department Type), a Business System (Business Software System or Concrete Hardware System) or a Capability Configuration (an assembly of Org-Units and Business Systems. References: OMG - UAF - ResourcePerformer OpenGroup - TOGAF - Definition - Business System
Rule	An abstract type for all types of constraint (i.e. an OperationalConstraint could detail the rules of accountancy best practice). References: OMG - UAF - Rule	Directive	A Directive is an authoritative declaration that indicates how Agents and their Behaviors should be (or should not be) in the enterprise. Specifically, a Directive defines, constrains or liberates some aspects of an Agent and its Behaviors. As such, Directives shall be considered as constraning Asset Propertys. Directives are intended to assert agent structures or to control or influence their Behaviors. Directives are stated in declarative form. References: OMG - BMM - Directive OMG - SBVR - Element of Guidance OMG - UAF - Rule OpenGroup - ArchiMate - Constraint UCF Glossary - Directive
Service	A mechanism to enable access to one or more capabilities, where the access is provided using a prescribed service interface and is exercised consistent with service constraints and policies. References: OMG - UAF - Service		Service is not directly represented in SysFEAT. Rational: The UAF Service layer is methodologically redundant with the Operational Layer. An issue has been raised to the UAF Group to address this issue.
Software	A sub-type of ResourceArtifact that specifies an executable computer program. References: OMG - UAF - Software	Business Software System	A Business Software System is a Business System used by Business Operations, that represents all granularities of software - ranging from MicroServices to enterprise wide Application Systems - used by Business Operations. All Business Software Systems share the following characteristics: 1) They provide Functionalitys. 2) They expose APIs (Application Interfaces) through which they deliver Information Outcome Events. 3) They handle datastores defined by Physical Data Domains. 4) They perform and participate to System Processes. References: OMG - UAF - Software OpenGroup - ArchiMate - Application Internal Active Structure Element OpenGroup - ArchiMate - Layer - Application Layer UCF Glossary - Software Asset
SubjectOfOperationalConstraint		Conceptual Operating Asset	A Conceptual Operating Asset is an Operating Asset used to describe the Conceptual Operating Model of the enterprise. It includes Value Streams, Operating Domains and Business Functions and the way they contribute to the delivery of Business Outcome Events. References: OMG - UAF - OperationalAsset

EXTERNAL REFERENCES

Framework reference	SysFEAT Description
OMG - UAF - ActivityPerformableUnderCondition	The ActualCondition under which an Activity is performed. The ActualCondition under which an Activity is performed. The ActualCondition under which an Activity is performed.
OMG - UAF - ActualCondition	An individual describing an actual situation with respect to circumstances under which an OperationalActivity, Function or ServiceFunction can be performed. An individual describing an actual situation with respect to circumstances under which an OperationalActivity, Function or ServiceFunction can be performed. An individual describing an actual situation with respect to circumstances under which an OperationalActivity, Function or ServiceFunction can be performed.
OMG - UAF - ActualEnvironment	An individual that describes the circumstances of an Environment. An individual that describes the circumstances of an Environment.
OMG - UAF - ActualLocation	An individual that describes a physical location, for example using text to provide an address, Geo-coordinates, etc. An individual that describes a physical location, for example using text to provide an address, Geo-coordinates, etc. Location A Location is a geopolitical location anywhere on the earth. Examples: - France - Paris - Washington DC - Cairo - Buenos-Aires - Asia
OMG - UAF - ActualService	An individual Service. An individual Service.
OMG - UAF - Asset	An abstract element that indicates the types of elements that can be affected by Risk. Asset as applied to Security views is an abstract element that indicates the types of elements that can be considered as a subject for security analysis An abstract element that indicates the types of elements that can be affected by Risk. Asset as applied to Security views is an abstract element that indicates the types of elements that can be considered as a subject for security analysis An abstract element that indicates the types of elements that can be affected by Risk. Asset as applied to Security views is an abstract element that indicates the types of elements that can be considered as a subject for security analysis. An abstract element that indicates the types of elements that can be affected by Risk. Asset as applied to Security views is an abstract element that indicates the types of elements that can be considered as a subject for security analysis. Functional Asset Functional Assets encompasse all Architecture Asset Types used to describe why and how systems operate/function. This includes the Operating Eco-System where system operates to fulfill these purposes (Agents and their Behaviors). Functional Assets include: 1. Blocks defining results of Behaviors of the enterprise or its sub-systems, that benefit to it internal or external customers : Outcome Event, 2. Blocks used to describe information: Information Asset. 3. Blocks used to describe how the enterprise operates: Operating Assets (Agent, Behavior, Service Interface). All Functional Assets are constrained by Policys and are exposed to Risk Types.
OMG - UAF - GeopoliticalExtentType	A type of geospatial extent whose boundaries are defined by declaration or agreement by political parties. GeopoliticalExtentType is not implemented as a subtype of OperationalExchangeItem. GeopoliticalExtentType was an initial requirement from DoDAF2 which hasn't been adopted by the final DoDAF specification. It is a legacy component of UAF. GeopoliticalExtentType is not implemented as a subtype of OperationalExchangeItem. GeopoliticalExtentType was an initial requirement from DoDAF2 which hasn't been adopted by the final DoDAF specification. It is a legacy component of UAF. GeopoliticalExtentType is not implemented as a subtype of OperationalExchangeItem. GeopoliticalExtentType was an initial requirement from DoDAF2 which hasn't been adopted by the final DoDAF specification. It is a legacy component of UAF.
OMG - UAF - InteractionMessage	Interaction Flow An abstract type that groups several types of messages used in the InteractionScenario. An abstract type that groups several types of messages used in the InteractionScenario.
OMG - UAF - InteractionScenario	Interaction Process An Interaction Process is a story (Behavior) that describes how the components of an Agent interacts to produce and consume Outcome Events. This includes: 1) A course of events represented by Object Flows depicting the succesion of intermediate Outcome Events towards the production of the final Outcome Events. 2) Interacting Agents who participate to the story. An abstract type that specifies interactions between Assets, like ResourcePerformers, and Services. An abstract type that specifies interactions between Assets, like ResourcePerformers, and Services.
OMG - UAF - KnownResource	Asserts that a known ResourcePerformer constrains the implementation of the OperationalPerformer that plays the role in the OperationalArchitecture.
OMG - UAF - NaturalResource	Type of physical resource that occurs in nature such as oil, water, gas or coal. Natural Resource A Natural Resource is a kind Physical Business Agent that refers to any class of material or substance that occurs naturally in the environment and can be used by humans for various purposes. These resources are derived from the Earth and include a wide range of physical entities such as water, minerals, forests, fossil fuels, soil, and air. Type of physical resource that occurs in nature such as oil, water, gas or coal. Type of physical resource that occurs in nature such as oil, water, gas or coal.
OMG - UAF - Operational Activity	An Activity that captures a logical process, specified independently of how the process is carried out. Value Stream Value Streams are used to frame the Conceptual Operating Model of the enterprise: they describe how the enterprise shall operate, at the conceptual level, and helps chunking responsibilities between Conceptual Agents (Operating Domain or Business Function) . In the EA context, a Value Stream is a conceptual Action Process that represents an overarching perspective of the organization's processes aiming at producing Conceptual Outcome Events. The focus is on shaping and understanding the functional relationships and roles within the enterprise : its functional division of labor. This is not to be confused with Value Stream Mapping (VSM) which is focused on Lean optimization and is addressed with the concept of Business Process (see the Organization & Processes domain). A Value Stream is performed by Conceptual Agents who produce Conceptual Outcome Events. It is depicted as a sequence of Value Stream Stages, controlled by events and conditions. Value Stream Activitys are carried out by the involvment of Conceptual Agents as participants in the Value Stream. During its course of action, a Value Stream consumes, produces or stores Business Objects. 1) It may read or write Domain Assets in its Business Object Store. 2) It may receive Domain Assets at its boundary: reacted to Business Outcome Events. 3) It may produce Domain Assets at its boundary: produced Business Outcome Events. The course of actions of a Value Stream is constrained by the application of rules ( Conceptual Rule Enforcement) that define what is allowed and not allowed to do. There are traditionnaly two kinds of Value Streams: 1) Development development Value Streams define all of the actions, both value-creating and nonvalue-creating, required to bring a Product from concept to launch. 2) Operational Value Streams define define all of the actions, both value-creating and nonvalue-creating, required from order to delivery. These include actions to process information from the Customer and actions to transform the product on its way to the Customer.
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 - OperationalInformation	Concept A Concept is the representation of any tangible or intanglible entity that is of interest to understand the enterprise, its data, resources and activities. A Concept is defined through its essential characteristics which can be: 1) A Concept Property that represents some an immutable factual characteristic such as "name", "amount". 2) A Concept Relationship that represents relationships to other Concepts. Concept Property A Concept Property is an immutable factual characteristic of a Conceptual Entity. Example: names, amounts, etc. Domain Asset A Domain Asset is the representation of any type of tangible or intanglible resource, or its respective state, that is critical for comprehending an enterprise, including its data, resources, and activities. Similar to any Information Asset, a Domain Asset can be classified into three categories: 1) Conceptual Entitys denote entities that can change over time. 2) Event Concepts embody the temporal boundaries associated with Conceptual Entitys. 3) Concept Propertys represent immutable characteristics of Conceptual Entitys. An item of information that flows between OperationalPerformers and is produced and consumed by the OperationalActivities that the OperationalPerformers are capable to perform (see IsCapableToPerform). An item of information that flows between OperationalPerformers and is produced and consumed by the OperationalActivities that the OperationalPerformers are capable to perform (see IsCapableToPerform).
OMG - UAF - OperationalInteractionScenario	A specification of the interactions between OperationalPerformers in an OperationalArchitecture.
OMG - UAF - OperationalPerformer	Business Function A Business Function is a Mezzo unit within the enterprise's functional division of labor. It is used to shape the enterprise management structure in regard to how it produces, consumes or processes Business Outcome Events: information, energy, materiel. A Business Function specifies Skills and Functionality(ies) required to perform their activities effectively. Operating Domain An Operating Domain is a Macro functional division of labor within an enterprise, acting as a Conceptual Agent. It embodies a collection of interrelated Business Functions which collaboratively provide one or more Business Capability(ies). Operating Domains serve as the highest hierarchical grouping of Business Functions within the enterprise's Conceptual Environment. A logical entity that IsCapableToPerform OperationalActivities which produce, consume and process Resources. A logical entity that IsCapableToPerform OperationalActivities which produce, consume and process Resources. A logical entity that IsCapableToPerform OperationalActivities which produce, consume and process Resources. A logical entity that IsCapableToPerform OperationalActivities which produce, consume and process Resources.
OMG - UAF - OperationalRole	Usage of a OperationalPerformer or OperationalArchitecture in the context of another OperationalPerformer or OperationalArchitecture. Creates a whole-part relationship. Usage of a OperationalPerformer or OperationalArchitecture in the context of another OperationalPerformer or OperationalArchitecture. Creates a whole-part relationship.
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 - PhysicalResource	An abstract type defining physical resources (i.e. OrganizationalResource, ResourceArtifact and NaturalResource).
OMG - UAF - Post	Organizational Position An Organizational Position is a type of position held by people when part of a Department Type. Examples: - Sales representative - Developer - Storekeeper - Architect A type of job title or position that a person can fill (e.g. Lawyer, Solution Architect, Machine Operator or Chief Executive Officer). A type of job title or position that a person can fill (e.g. Lawyer, Solution Architect, Machine Operator or Chief Executive Officer). A type of job title or position that a person can fill (e.g. Lawyer, Solution Architect, Machine Operator or Chief Executive Officer). A type of job title or position that a person can fill (e.g. Lawyer, Solution Architect, Machine Operator or Chief Executive Officer).
OMG - UAF - Process	An abstract type that represents a behavior or process (i.e. a Function or OperationalActivity) that can be performed by a Performer. An abstract type that represents a behavior or process (i.e. a Function or OperationalActivity) that can be performed by a Performer. Action Process An Action Process is a Behavior that describes a typical course of action intended to produce Outcome Events, through the involvement of Agents as Active Participants. During its course of action, a process consumes or produces Functional Assets, including Information Assets. 1) It may memorize or access Information Assets from and to its Process Stores. 2) It may receive Functional Assets at its boundary: Outcome Consumptions. 3) It may signal the production of Functional Assets at its boundary: Outcome Productions. The course of actions of a Action Process is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do. Within SysFEAT, we can examine Action Processes from two distinct perspectives: a) A conceptual standpoint is provided by Value Streams. b) A concrete implementation standpoint is provided by Resource Action Processes. An abstract type that represents a behavior or process (i.e. a Function or OperationalActivity) that can be performed by a Performer.
OMG - UAF - ProcessUsage	Process Step A Process Step is a Process Activity invoking another Action Process An abstract type that represents a behavior or process (i.e., a Function or OperationalActivity) that can be performed by a Performer. An abstract type that represents a behavior or process (i.e., a Function or OperationalActivity) that can be performed by a Performer. An abstract type that represents a behavior or process (i.e., a Function or OperationalActivity) that can be performed by a Performer.
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 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).
OMG - UAF - Rule	Directive A Directive is an authoritative declaration that indicates how Agents and their Behaviors should be (or should not be) in the enterprise. Specifically, a Directive defines, constrains or liberates some aspects of an Agent and its Behaviors. As such, Directives shall be considered as constraning Asset Propertys. Directives are intended to assert agent structures or to control or influence their Behaviors. Directives are stated in declarative form. Policy A Policy is a Directive that is not directly enforceable whose purpose is to govern, guide or constrain the structure and Behavior of Agents in the enterprise. Policies provide the basis for rules and govern Behaviors carried out by Agents. Example of Policys are Regulation Articles, Business Policys or Architecture principles. An abstract type for all types of constraint (i.e. an OperationalConstraint could detail the rules of accountancy best practice). An abstract type for all types of constraint (i.e. an OperationalConstraint could detail the rules of accountancy best practice).
OMG - UAF - Service	A mechanism to enable access to one or more capabilities, where the access is provided using a prescribed service interface and is exercised consistent with service constraints and policies. A mechanism to enable access to one or more capabilities, where the access is provided using a prescribed service interface and is exercised consistent with service constraints and policies. A mechanism to enable access to one or more capabilities, where the access is provided using a prescribed service interface and is exercised consistent with service constraints and policies.
OMG - UAF - Software	Application An Application is a Business Software System that provides a set of Functionality(ies) that End Users see as a single unit. Essentially Applications are architectural constructions resulting from the combinaison of the following four criteria: 1) A group of Functionality that End Users see as a single unit. 2) A managed asset (Managed Application) associated with a budget line in the context of an Application Portfolio. 3) A body of code that is seen by developers as a single unit. 4) A group of deployable software units (Deployable Application Packages) that must be installed together on one or multiple execution nodes (Computing System). Application is a Mezzo enterprise asset that sits between Application System and Application Component in the decomposition of Business Software Systems. Example: " Payroll" is an Application that is part an " HR System" which is an Application System. The "Payroll" Application includes, among other things, the "Salary and Wage Calculation" Application Component. Business Software System A Business Software System is a Business System used by Business Operations, that represents all granularities of software - ranging from MicroServices to enterprise wide Application Systems - used by Business Operations. All Business Software Systems share the following characteristics: 1) They provide Functionalitys. 2) They expose APIs (Application Interfaces) through which they deliver Information Outcome Events. 3) They handle datastores defined by Physical Data Domains. 4) They perform and participate to System Processes. A sub-type of ResourceArtifact that specifies an executable computer program. A sub-type of ResourceArtifact that specifies an executable computer program. A sub-type of ResourceArtifact that specifies an executable computer program. Software Module A Software Module is a Business Software System that is part of an application system. A Software Module is either an Application, Application Component or a MicroService. All share the ability to be composed of sub-Application Components and have dependencies to enabling Software Technology(ies).
OMG - UAFML - InformationModelKind	Logical - Indicates that the InformationModel associated with the InformationModelKind is a logical data model that allows analysis of an architecture’s data definition aspect, without consideration of implementation specific or product specific issues. It details the conceptual data model. Conceptual - Indicates that the InformationModel associated with the InformationModelKind is a conceptual InformationModel that defines the required high-level data concepts and their relationships. Conceptual - Indicates that the InformationModel associated with the InformationModelKind is a conceptual InformationModel that defines the required high-level data concepts and their relationships. Conceptual - Indicates that the InformationModel associated with the InformationModelKind is a conceptual InformationModel that defines the required high-level data concepts and their relationships. Logical - Indicates that the InformationModel associated with the InformationModelKind is a logical data model that allows analysis of an architecture’s data definition aspect, without consideration of implementation specific or product specific issues. It details the conceptual data model/ Physical - Indicates that the InformationModel associated with the InformationModelKind is a physical data model that is an implementable specification of a data structure. A physical data model realizes a logical data model, taking into account implementation restrictions and performance issues while still enforcing the constraints, relationships and typing of the logical data model. Physical - Indicates that the InformationModel associated with the InformationModelKind is a physical data model that is an implementable specification of a data structure. A physical data model realizes a logical data model, taking into account implementation restrictions and performance issues while still enforcing the constraints, relationships and typing of the logical data model.
OMG - UML - Lifeline	A Lifeline represents an individual participant in the Interaction. While parts and structural features may have multiplicity greater than 1, Lifelines represent only one interacting entity.

IDENTITY - UAF - Operational Views

MAPPED ENTITIES

EXTERNAL REFERENCES

CHARTER

Missing Content

Governance

Provide Feedback