SysFEAT - Systemic Framework for Enterprise Architecture & Transformation

CLASS OF CLASS OF INDIVIDUAL - 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.

Functional Domain: Application Deployment Architecture

The Application Deployment Architecture domain defines concepts used to organize Applications in Deployable Packages.

Super Types

Software Deployment Architecture

Application

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: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝

Graph & Hierarchy

Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> 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 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.).
Realized Logical System	[*..0]	Logical Software System	Business Software System
Realized Agent	[*..0]	Agent Type	Agent Type
Life Start	[*..0]	Agent Life Cycle Event	Agent Type	A Life Start is a Start Type that denotes the type of event that signifies the beginning of an Agent Types existence.
Life End	[*..0]	Agent Life Cycle Event	Agent Type	A Life End is an End Type that denotes the type of event that signifies the end of an Agent Types 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.

SERIALIZATION FORMAT

TEXTUAL SYNTAX RDF

File: d5e6d7c65c464ae3.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
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.).

INTERNAL STRUCTURE

../images/d5e6d7c65c464ae3_624e69f05ed9709f_i.png

CLASS OF CLASS OF INDIVIDUAL - Application Deployment Architecture

RELATIONSHIPS

Simple Graph

Graph & Hierarchy

Relationship Table

SERIALIZATION FORMAT

SEMANTIC TAXONOMY

SUB-TYPES

SUPER-TYPES

BORDERS

INTERNAL STRUCTURE

CHARTER

Missing Content

Governance

Provide Feedback