Epic

CLASS OF INDIVIDUAL - Epic

Description

Abstract Concept
An Epic is a time-bound Management Initiative.

Functional Domain: 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).

Super Types

Time-bound Initiative

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
Steering Authority	[1..1]	Responsible Human Entity	Initiative	Abstract Relationship
end	[1..1]	Initiative Milestone	Initiative
Coordination Milestone	[*..0]	Initiative Milestone	Initiative
start	[1..1]	Initiative Milestone	Initiative
Course of Action	[*..0]	Individual Resource Behavior	Initiative	Abstract Relationship A plan recognized by an enterprise as being essential to achieving its goals - i.e. a strategic specification of what the enterprise does. In other words, a Course of Action channels efforts towards Desired Results.Business Capabilities might be required by an Enterprise to conduct its Courses of Action.
Initiative Subject	[*..0]	Asset Block	Initiative	Abstract Relationship Set of Asset Blocks that are the subject of changes undertaken by an Initiative.
Temporal Ordering	[*..0]	Temporal Bounding	Bounded Individual	Abstract Relationship
Property of Individual	[*..0]	Property	Individual	Abstract Relationship An instance of Entity from a Bounded Individual to a Property that asserts the Bounded Individual has the Property.
Meronymy Relation	[*..0]	First Order Entity	First Order Entity	Abstract Relationship Meronymy Relation is a directional part-to-whole Meronymy Relation between First Order Entitys, where the source First Order Entity (the part) is defined has being part of a larger whole First Order Entity.In accordance with principles of Compositionality, Meronymy Relation is not simply the inverse of Holonymy Relation. In some cases, the whole First Order Entity is not inherently defined by some its parts. Location (Located at) and period relationships are such Meronymy Relations.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.

LOGICAL FORMULATION

LOGIC-AGDA RDF

File: 84c799c1664d8b2f.agda

File: 84c799c1664d8b2f.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