SysFEAT - Systemic Framework for Enterprise Architecture & Transformation

CLASS OF CLASS OF CONNECTION - Business Outcome Event

Description

Abstract Concept
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 Type, for the benefits of an internal or external consumer (especially Customers).

Resource Agent Nature of Business Outcome Event: a Business Outcome Event is either an Information Outcome Event or a Physical Outcome Event

Functional Domain: SOF - Business Resource Operating Pattern (B-SOF)

The SOF - Business Resource Operating Pattern (B-SOF) domain defines concepts and relationships used to model how physical resources (Business Operating Assets) operates/functions in Business Resource Ecosystems to deliver Business Outcome Events.

External references

OMG - BACM - Outcome

OMG - UAF - Effect

OMG - UAF - OperationalSignal

OpenGroup - IT4IT - Defining Service Reference Architecture

OpenGroup - OAA - Definition - Outcome

Super Types

Business Event

Resource Outcome Event (from partition: Operational Role of Resource Outcome Event)

Dictionary

Dictionary of SysFEAT concepts

Lexical Scope

Block Lexical Scope

Container

Architecture Container

Framework Mapping

SysFEAT Outcome Centric Model : Business Outcome Product & Service
UAF - Strategy : Effect
UAF - Operational Views : OperationalSignal

RELATIONSHIPS

Simple Graph Graph & Inheritance Table

Simple Graph

Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝

Graph & Hierarchy

Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝

Relationship Table

Relationship	Cardinality	Target Entity	Source Entity	Description
Business Outcome Production	[1..1]	Business Behavior	Business Outcome Event	Abstract Relationship
Business Outcome Consumption	[1..1]	Business Behavior	Business Outcome Event	Abstract Relationship
Business Outcome	[*..0]	Business Operating Asset	Business Outcome Event	Abstract Relationship A Business Outcome is a state of any Business Operating Asset (tangible or intanglible) that is the subject of a business transaction.As such, a Resource Functional Asset is created, enhanced or transformed through the Resource Behavior of a producer Resource Agent Type, resulting in an increase in value (Business Outcome) that benefits (value) to the Business Operating Behavior of a consumer Resource Agent Type.Examples:- A new process (Resource Behavior) that is the result of a refactoring activity done by a consulting organization (producer Agent) for the benefit of a business unit (user Agent).- A new application (Resource Agent Type) that is the result of the development and sales activitiies of a software company (producer Agent) for the benefit of an end user (user Agent).
Specialized Functional Asset	[*..0]	Functional Asset	Functional Asset	Abstract Relationship
Realized Functional Asset	[*..0]	Functional Asset	Functional Asset	Abstract Relationship A kind of specialization between an implementing Functional Asset and its abstract Realized Functional Asset.Realization relationships are the foundation to establish the mapping between Functional Assets that belong to different Conceptualization Levels.
Policy Conformance	[*..0]	Policy	Functional Asset	A Policy Conformance is the conformity requirement that applies a Functional Asset.
Connection End	[*..0]	Bounded Aggregate	Ordering Connection	Abstract Relationship
Connection Member	[*..0]	Ordering Connection	Ordering Connection
Composition Type	[*..0]	First Order Class	First Order Class	Abstract Relationship Composition Type is the powertype of Holonymy.
Start Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual	Abstract Relationship
End Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual	Abstract Relationship
Temporal Sequencing Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual	Abstract Relationship
Aggregate Composition Type	[*..0]	Class of Bounded Individual	Class of Bounded Individual	Abstract Relationship An Aggregate Composition Type is a reified flavor of Composition Type whereby the referenced Class of Individual is aggregated in its parent (whole) Class of Bounded Individual.Example:1) A Process Step is the reification of the composition of a child process in a parent process.2)
Hierarchical Member	[*..0]	Building Block	Aggregate Block	A Hierarchical Member is an Aggregate Member that is also a Block Lexical Scope for the Building Block it aggregates: it relates its aggregated block by nesting (see Nesting Relationship).Hierarchical Members are used to build hierarchical structures of Building Blocks, in constrast to Block Members which are used to build network structures of Building Blocks.
Block Member	[*..0]	Building Block	Aggregate Block	A Block Member is an Aggregate Member that aggregates its releated Building Block by reference (see Referencing Relationship).Block Members are used to build network structures of Building Blocks while Hierarchical Members are used to build hierarchical structures of Building Blocks.
Border	[*..0]	Ordering Connection	Bounded Aggregate	Abstract Relationship

SERIALIZATION FORMAT

TEXTUAL SYNTAX RDF

File: 9dcea4535ec76e6c.rdf

CONNECTION DIAGRAM

../images/9dcea4535ec76e6c_be94dd93655c8164_i.png

CONNECTION ENDS

	Name	Type	Super Type	Description
Source End	Business Outcome Production	Business Behavior	Business Event::Previous Business Event Resource Outcome Event::Resource Outcome Production
Target End	Business Outcome Consumption	Business Behavior	Business Event::Next Business Event Resource Outcome Event::Resource Outcome Consumption

SEMANTIC TAXONOMY

Sub-Types Super-Types

SUB-TYPES

Click node rectangle to collapse/expand one level. Click triangle for full recursive collapse/expand. Double-click on a node to open its URL. Hover for description.

CLASS OF CLASS OF CONNECTION - Business Outcome Event

RELATIONSHIPS

Simple Graph

Graph & Hierarchy

Relationship Table

SERIALIZATION FORMAT

CONNECTION DIAGRAM

CONNECTION ENDS

SEMANTIC TAXONOMY

SUB-TYPES

SUPER-TYPES

CHARTER

Missing Content

Governance

Provide Feedback