Technology Outcome Event

CLASS OF CLASS OF CONNECTION - Technology Outcome Event

Description

Abstract Concept
A Technology Outcome Event is an Outcome Event that indicates the availability of an expected change in the state of some Technology Functional Asset produced by a Technology System .

Functional Domain: EA Pattern - Technology Operating Pattern

The EA Pattern - Technology Operating Pattern is used to describe the common features of Technology Operating Assets.

Super Types

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

Technology Functional Asset (from partition: Structural Partition of Technology Functional Asset)

Dictionary

SysFEAT Enterprise concepts

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
Produced Technology Outcome	[1..1]	Technology Behavior	Technology Outcome Event	Abstract Relationship
Consumed Technology Outcome	[1..1]	Technology Behavior	Technology Outcome Event	Abstract Relationship
Technology Outcome	[*..0]	Technology Functional Asset	Technology Outcome Event	A Technology Outcome represents any tangible or intanglible Technology Functional Asset or state of such Technology Functional Asset, that can be the subject of a technology transaction.As such, a Technology Outcome can be improved or transformed in some way by a producer Technology System resulting in an increase in value (Technology Outcome Event) that benefits (utility) to a userTechnology System or Business System that use this Technology Outcome.Examples:- A new AI system that is the result of the development of a platform team and sales activiies of a software company (producer Agent) for the benefit of a Business System.
Specialized Technology Asset	[*..0]	Technology Functional Asset	Technology Functional Asset
Technology Risk	[*..0]	Technology Risk Type	Technology Functional Asset
Classified by Class of Class of Individual	[1..1]	Class of Class of Individual	Behavioral Event
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.
Asset Type Qualification	[*..0]	Asset Property	Asset Type	Abstract Relationship Qualification of an Asset Type by an Asset Property.
Applicable Condition Type	[*..0]	Condition Property Type	Asset Type	Set of Condition Property Types that can be applied to an Asset Type.
Classified by Bounded Individual MetaClass	[1..1]	Bounded Individual MetaClass	Asset Type
Asset Categorization	[*..0]	Asset Category	Asset Type	Abstract Relationship
Asset Categorization Scheme	[*..0]	Asset Category Family	Asset Type	Abstract Relationship
Connection End	[*..0]	Bounded Aggregate	Ordering Connection	Abstract Relationship
Connection Member	[*..0]	Ordering Connection	Ordering Connection	Abstract Relationship
End Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual	Abstract Relationship
Start Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual	Abstract Relationship
Temporal Ordering Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual	Abstract Relationship
Aggregate Holonymy Type	[*..0]	Class of Bounded Individual	Class of Bounded Individual	Abstract Relationship An Aggregate Holonymy Type is a reified flavor of Poly Class of Holonymy 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)
Class of Holonymy	[*..0]	First Order Class	First Order Class	Class of Holonymy is the powertype of Holonymy Relation.
Class of Meronymy	[*..0]	First Order Class	First Order Class	Class of Meronymy is the powerType of Meronymy Relation.
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 Scoped Building Block).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.Hierarchical Members are the KerML equivalent of composite features.
Block Member	[*..0]	Building Block	Aggregate Block	A Block Member is an Aggregate Member that aggregates its releated Building Block by reference (see Reference Relation).Block Members are used to build network structures of Building Blocks while Hierarchical Members are used to build hierarchical structures of Building Blocks.
Nesting Relation	[*..0]	Entity	Lexical Scope	Abstract Relationship A Nesting Relation is a Relation that references its target Entity by nesting, using a Nesting Adjacency.Nesting is a fundamental concept in complex systems organization where elements are contained within other elements, creating hierarchical or constextual web-like structures. This embedding mechanism intrinsically links the properties, behaviors, and lifecycles of nested entities to their containing entities, forming cohesive units at multiple scales.Nesting facilitates the emergence of complex Aggregate Blocks and properties from simpler entities, enables efficient design of systems across levels, and supports both autonomy and integration within systems (see Compositionality).Nesting also facilitates the creation of modules through packaging of Building Blocks (see Packaging).
Reference Relation	[*..0]	Entity	Entity	Abstract Relationship A Reference Relation is a Relation that points at a target Entity which is not in the Lexical Scope of its source Entity.
Existential Independence	[*..0]	Entity	Entity	Abstract Relationship An Existential Independence relation is a Relation that specifies that the existence of the source Entity doesnt depend on the existence of its target Entity.The cardinality of set of targetted Entity is [0..*].
instance of Entity	[*..0]	Class of Entity	Entity	Abstract Relationship instance of Entity is a Typology relationship that relates an Entity to a Class of Entity, as instance of this Class of Entity.

LOGICAL FORMULATION

LOGIC-AGDA RDF

File: f4be0a955ee1c4f5.agda

File: f4be0a955ee1c4f5.rdf

CONNECTION DIAGRAM

../images/f4be0a955ee1c4f5_f4be0ac15ee1c65c_i.png

CONNECTION ENDS

	Name	Type	Super Type	Description
Source End	Produced Technology Outcome	Technology Behavior	Resource Outcome Event::Resource Outcome Production
Target End	Consumed Technology Outcome	Technology Behavior	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.