Bounded Aggregate

DEFINITION RELATIONSHIPS TAXONOMY BORDERS INTERNAL STRUCTURE LOGICAL FORMULATION CONTENT MANAGEMENT

ENTITY - Bounded Aggregate

Description

Abstract Concept

A Bounded Aggregate is an Aggregate Entity Block which hides its internal structure to the outside world by means of formal Borders.

The only way to access a Bounded Aggregate is through its formal Borders, which ensures the aggregate's internal consistency.

The Borders of a Bounded Aggregate is determined by the Ordering Connections it can participate to.

Within a Bounded Aggregate structure, Bounded Members can be linked together through Ordering Connectors.

The nature of Ordering Connectors is given by their associated Ordering Connection.

Examples:

- Action Process Typees are bounded by their start and end events (see Behavioral Event).

- Applications are bounded by their APIs borders (API Service Point and API Request Point).

Functional Domain: Compositionality

The purpose of the Compositionality family of concepts is to provide syntactic mechanisms that support the construction of composite Building Blocks.

External references

OMG - KerML - Classifier

OMG - UML - EncapsulatedClassifier

SysFEAT - Modularity.pdf

Super Types

Aggregate Entity Block

Dictionary

SysFEAT Upper Ontology

Lexical Scope

Block Lexical Scope

Container

Framework Mapping

Meta-Model Legend : Aggregate - Internal Structure

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
Border	[*..0]	Ordering Connection	Bounded Aggregate	Abstract Relationship
Exit Border	[*..0]	Ordering Connection	Bounded Aggregate	Abstract Relationship An Exit Border is a Border of a Bounded Aggregate that serves as a connection point allowing Bounded Members to connect to external Bounded Aggregates.Examples: an Exit Border can be physical (such as a door or gateway), functional (such as requested API endpoint in software or the End Event of a process).
Entry Border	[*..0]	Ordering Connection	Bounded Aggregate	Abstract Relationship An Entry Border is a Border of a Bounded Aggregate that serves as a connection point allowing external Aggregate Blocks to access Aggregate Members within the Bounded Aggregate.Examples: an Entry Border can be physical (such as a door or gateway), functional (such as an API endpoint in software or the Start Event of a process).
Bounded Member	[*..0]	Bounded Aggregate	Bounded Aggregate	Abstract Relationship A Bounded Member is an Aggregate Member that aggregates a Bounded Aggregate.Bounded Members can be related by means of Ordering Connectors which connect an Exit Border of a source Bounded Member to a corresponding Entry Border of a target Bounded Member.
Ordering Connector	[*..0]	Ordering Connection	Bounded Aggregate	Abstract Relationship A Ordering Connector is Block Member that connects a source Bounded Member to a target Bounded Member through their Entry Border and Exit Border.The semantic of Connector is given by their associated Ordering Connection.Examples:. Event that manifests a transition between two states.. Sequences between the end of a process step and the start of another process step.. Interface connection between a service consumer agent and a service provider agent.
Unbounded Member	[*..0]	Building Block	Aggregate Entity Block	Abstract Relationship An Unbounded Member is an Aggregate Member of an Aggregate Entity Block that aggregates a Building Block that is not a Bounded Aggregate.Unbounded Members cannot be related by Ordering Connections (see Bounded Aggregate).
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).
Typology	[*..0]	Class of Entity	Entity	Abstract Relationship A Typology is a Relation between an Entity and its categorical nature - the intrinsic properties or criteria that determine the Entity membership within a Class of Entity. Typology governs two distinct categorization mechanisms:- instance of Entity: assigning a Ordered Entity to a predefined Class of Entity based on shared characteristics (e.g., grouping by common traits).- SubTypeOfEntity: refining a Class of Entity into a subclass with narrower criteria (e.g., inheritance hierarchies or subtype relationships).While instance of Entity focuses on grouping Ordered Entitys into Class of Entitys, SubTypeOfEntity emphasizes hierarchical refinement of Class of Entityes themselves. Both mechanisms operate under the umbrella of typology, which formalizes how Ordered Entitys are systematically categorized.
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 Dependency	[1..1]	Entity	Entity	Abstract Relationship An Existential Dependency relationship is a Relation where the source Entitys existence depends on the existence of the target Entity.The cardinality of the set of targetted Entity is [1..1].
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: 8cfa941b6852781f.agda

File: 8cfa941b6852781f.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	Description
Border	Aggregate Block::Aggregate Member	Ordering Connection
Entry Border	Bounded Aggregate::Border	Ordering Connection	An Entry Border is a Border of a Bounded Aggregate that serves as a connection point allowing external Aggregate Blocks to access Aggregate Members within the Bounded Aggregate. Examples: an Entry Border can be physical (such as a door or gateway), functional (such as an API endpoint in software or the Start Event of a process).
Exit Border	Bounded Aggregate::Border	Ordering Connection	An Exit Border is a Border of a Bounded Aggregate that serves as a connection point allowing Bounded Members to connect to external Bounded Aggregates. Examples: an Exit Border can be physical (such as a door or gateway), functional (such as requested API endpoint in software or the End Event of a process).

INTERNAL STRUCTURE

../images/8cfa941b6852781f_8cfabb0a6852840f_i.png

CONNECTORS

Connector	Source	Target	Connector Type	Description
Ordering Connector	Bounded Member. Border. Exit Border	Bounded Member. Entry Border	Ordering Connection	Abstract Connection A Ordering Connector is Block Member that connects a source Bounded Member to a target Bounded Member through their Entry Border and Exit Border. The semantic of Connector is given by their associated Ordering Connection. Examples: . Event that manifests a transition between two states. . Sequences between the end of a process step and the start of another process step. . Interface connection between a service consumer agent and a service provider agent. References: OMG - KerML - BinaryLink