SysFEAT - Systemic Framework for Enterprise Architecture & Transformationk

BUILDING BLOCK - Application Deployment Architecture

Description	An Application Deployment Architecture describes one possible deployment configuration of an Application. It contains Deployable Packages to host, prescribed type of hosting and required Software Physical Channels (with communication protocols, port numbers...) to communicate with each other.
Super Types	Software Deployment Architecture Application
Functional Domain	Application Deployment Architecture The Application Deployment Architecture domain defines concepts used to organize Applications in Deployable Packages.
Dictionary	Dictionary of SysFEAT concepts
Framework Mapping	C4 Model Mappings : Level 3 - Component Diagram

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
Data Part	[*..0]	Deployable Data Package	Application Deployment Architecture
Micro Service Part	[*..0]	MicroService	Application Deployment Architecture	Role of a MicroService in an Application Deployment Architecture.
Application Part	[*..0]	Deployable Application Package	Application Deployment Architecture	Role of a Deployable Application Package is an Application Deployment Architecture.
Specialized Application	[*..0]	Application	Application
Micro-Service Part	[*..0]	MicroService	Application	The embbding of MicroService a into an Application.As MicroServices are selft deployable packages, Applications made of MicroServices can be incrementally updated and deployed.
Realized Logical System	[*..0]	Logical Software System	Business Software System
API Service Point	[1..1]	Application Interface	Business Software System
API Request Point	[1..1]	Application Interface	Business Software System
Software Connection	[*..0]	Application Interface	Business Software System	An Interaction represents a contract between entities in a specific context inside or outside a company. These entities can be organizational units, activities, or processes.The content of this contract is described in a protocol.
Physical data store	[*..0]	Physical Data Domain	Business Software System
Realized Software System	[1..1]	Business Software System	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.).

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.).