SysFEAT - Systemic Framework for Enterprise Architecture & Transformationk

BUILDING BLOCK - Concrete Software System

Description	Abstract Concept A Concrete Software System is a Software System that is the concrete implementation of an Business Software System. Operational Role of Concrete Software System: a Concrete Software System is either a Deployable Software System or a Software Technology System
Super Types	Software System (from partition: Conceptualization Levels of Software System)
Functional Domain	EA Pattern - Physical Software Operating Pattern The EA Pattern - Physical Software Operating Pattern domain provides abstractions shared by all physical software artifacts.
Dictionary	Dictionary of SysFEAT concepts

RELATIONSHIPS

Simple Graph Graph & Inheritance Table

Simple Graph

Composition: ➝ Classification: ➝ Specialization: ➝ Enumerated definition: ➝ Syntax: ➝

Graph & Hierarchy

Composition: ➝ Classification: ➝ Specialization: ➝ Enumerated definition: ➝ Syntax: ➝

Relationship Table

Relationship	Cardinality	Target Entity	Source Entity	Description
Realized Software System	[1..1]	Business Software System	Concrete Software System
Fulfilled Technology Capability	[*..0]	Software Technology Capability	Concrete Software System
Physical Service Point	[1..1]	Physical Software Interface	Concrete Software System	A Physical Service Point is a connection point allowing opening a communication to a technical architecture or an application technical area that complies with a specified communication protocol (SMTP, HTTP, etc.).
Physical Client Point	[1..1]	Physical Software Interface	Concrete Software System	A technical output port is a point that allows asking to open a communication line from a technical architecture or an application technical area and that complies with a specified communication protocol (SMTP, HTTP, etc.).
Specialized Business Operating Agent	[*..0]	Resource Agent	Resource Agent
Provided Resource Interface	[*..0]	Resource Service Interface	Resource Agent
Consumed Resource Interface	[*..0]	Resource Service Interface	Resource Agent
Resource Connection	[*..0]	Resource Service Interface	Resource Agent
Resource Agent Part	[*..0]	Resource Agent	Resource Agent
Performed Resource Scenario	[*..0]	Resource Interaction Process	Resource Agent	A Performed Resource Scenario is a Resource Interaction Process operated by a Resource Agent.
Performed Resource Process	[*..0]	Resource Action Process	Resource Agent	A Performed Resource Process is a Resource Action Process operated by a Resource Agent.
Resource Store	[*..0]	Information Domain	Resource Agent
Realized Business Operating Asset	[*..0]	Resource Operating Asset	Resource Operating Asset
Resource Rule Enforcement	[*..0]	Resource Rule	Resource Operating Asset
Realized Agent	[*..0]	Agent	Agent
Life Start	[*..0]	Agent Life Cycle Event	Agent	A Life Start is a Start Type that denotes the type of event that signifies the beginning of an Agents existence.
Life End	[*..0]	Agent Life Cycle Event	Agent	A Life End is an End Type that denotes the type of event that signifies the end of an Agents existence.
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.

TEXTUAL SYNTAX

SEMANTIC TAXONOMY

Sub-Types Super-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
Physical Client Point	Technology System::Technology Request Point	Physical Software Interface	A technical output port is a point that allows asking to open a communication line from a technical architecture or an application technical area and that complies with a specified communication protocol (SMTP, HTTP, etc.).
Physical Service Point	Technology System::Technology Service Point	Physical Software Interface	A Physical Service Point is a connection point allowing opening a communication to a technical architecture or an application technical area that complies with a specified communication protocol (SMTP, HTTP, etc.).