SysFEAT - Systemic Framework for Enterprise Architecture & Transformation

CLASS OF CLASS OF INDIVIDUAL - Deployable Software System

Description

Abstract Concept
Deployable Software System is the super-type of all concepts used to describe the deployment of Business Software Systems.

Functional Domain: Application Deployment Architecture

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

Super Types

Concrete Software System (from partition: Operational Role of Concrete Software System)

Dictionary

Dictionary of SysFEAT 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
Specialized Deployable Software	[*..0]	Deployable Software System	Deployable Software System
Deployable Software System	[1..1]	Business Software System	Deployable Software System
Software Physical Channel	[*..0]	Physical Software Interface	Deployable Software System	A Software Physical Channel represents a technical connection between Deployable Software Member through input to output communication ports. The output technical port of a technical area or architecture asks the input technical port of the other technical architecture or area to open the communication line.
Deployable Software Member	[*..0]	Deployable Software System	Deployable Software System
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
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 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.
Realized Business Operating Asset	[*..0]	Resource Operating Asset	Resource Operating Asset
Resource Rule Enforcement	[*..0]	Resource Rule	Resource Operating Asset
Categorization	[*..0]	Category	Class of Bounded Individual	Categorization is a Classification of a Class of Bounded Individual by a Family of Class called Category.
Temporal Sequencing Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual
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: d5e6d8015c464b40.rdf

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

INTERNAL STRUCTURE

../images/d5e6d8015c464b40_624e6c925ed97717_i.png

CONNECTORS

Connector	Source	Target	Connector Type	Description
Software Physical Channel	Deployable Software Member. Physical Client Point	Deployable Software Member. Physical Service Point	Physical Software Interface	A Software Physical Channel represents a technical connection between Deployable Software Member through input to output communication ports. The output technical port of a technical area or architecture asks the input technical port of the other technical architecture or area to open the communication line.