SysFEAT - Systemic Framework for Enterprise Architecture & Transformation

CLASS OF INDIVIDUAL - Operational Transformation

Description

Abstract Concept

An Operational Transformation is an Initiative that creates or transform Operating Asset Types, based on a Capability Map's functional scope.

Its Goal is to deliver new or improved Capabilitys, with measurable qualitative properties, to well identified beneficiary stakholders.

Functional Domain: Initiative and Transformation Pattern

The Initiative and Transformation Pattern domain defines management concepts required for transformation initiatives.

Super Types

Enduring Initiative (from partition: Initiative Kind of Initiative)

Dictionary

SysFEAT System Operating Framework

Lexical Scope

Model Lexical Scope

Model Container

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
Functional Scope	[*..0]	Capability Map	Operational Transformation	Abstract Relationship
Subject Operating Asset	[*..0]	Asset Block	Operational Transformation
Packaged Initiative Resource	[*..0]	Initiative Instrument	Enduring Initiative	Abstract Relationship
Dependent Initiative	[*..0]	Enduring Initiative	Enduring Initiative	Abstract Relationship
Sub-Initiative	[*..0]	Enduring Initiative	Enduring Initiative	Abstract Relationship
Roadmap	[*..0]	Initiative Stage	Enduring Initiative	Abstract Relationship Set of all Initiative Stages of an Enduring Initiative that, along with coordinating Initiative Milestones, forms its roadmap.
Goal	[*..0]	Asset Property	Enduring Initiative	Abstract Relationship A Goal is a statement about an Asset Property of Initiative Subjects of an Enduring Initiative that cannot be obtained within a specified period, but which can be obtained over a longer time period.
Packaged Property Block	[*..0]	Model Property Block	Model Container
Packaged Documentation	[*..0]	Documentation	Model Container
Packaged Tag	[*..0]	Tag	Model Container
Imported Model Container	[*..0]	Model Container	Model Container	Abstract Relationship The Imported Model Container relationship extends the Model Lexical Scope of a Model Container to Model Building Blocks of the imported Model Container.
Qualifying Property	[*..0]	Property	Bounded Individual	Abstract Relationship Qualifying Property is a specialization relationship between a Bounded Individual and its qualifying Property.
Temporal Sequencing	[*..0]	Temporal Bounding	Bounded Individual	Abstract Relationship
Nested Description Note	[*..0]	Description Note	Model Lexical Scope
Existential Dependency	[1..1]	Entity	Entity	Abstract Relationship An Existential Dependency relationship is a Relationship where the source Entitys existence depends on the existence of the target Entity.The cardinality of the set of targetted Entity is [1..1].
Meronymy (Part Of)	[*..0]	Particular Entity	Particular Entity	Abstract Relationship Meronymy (Part Of) is a directional part-to-whole Relationship between Particular Entitys, where the source Particular Entity (the part) is defined has being part of a larger whole Particular Entity.In accordance with principles of Compositionality, Meronymy (Part Of) is not simply the inverse of Holonymy. In some cases, the whole Particular Entity is not inherently defined by some its parts. Location (Located at) and period relationships are such Meronymy (Part Of).Example:- William Shakespeare is born in Stratford-upon-Avon, but the Stratford-upon-Avon geo-location is not inherently defined by William Shakespeare. It is defined by its geophysical containers: Continent-Europe, Landmass-Great Britain.- William Shakespeare is born in 1564, but the year 1564 is not inherently defined by the birth of William Shakespeare. It is defined by its position in the Gregorian calendar and contains countless other global events.
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.

SERIALIZATION FORMAT

TEXTUAL SYNTAX RDF

File: 299e882b68488d2c.rdf

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.

BORDERS

Name	Super type	Border Type
Coordination Milestone	Bounded Individual::Temporal Border	Initiative Milestone
end	Bounded Individual::End	Initiative Milestone
start	Bounded Individual::Start	Initiative Milestone