Deployable Package

CLASS OF CLASS OF INDIVIDUAL - Deployable Package

Description

Abstract Concept
A Deployable Package is a split of Application code and data according to deployment and runtime purposes.

Functional Domain: Application Deployment Architecture

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

External references

C4 Model - Level 2 - Container Diagram

Super Types

Deployable Software System

Dictionary

SysFEAT Enterprise concepts

Framework Mapping

C4 Model Mappings : Container

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 Package	[*..0]	Deployable Package	Deployable Package
Packaged Application	[1..1]	Application	Deployable Package
Required Software Technology	[*..0]	Software Technology	Deployable Package
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	Abstract Relationship
Fulfilled Technology Capability	[*..0]	Software Technology Capability	Concrete Software System
Realized Software System	[1..1]	Business Software System	Concrete Software System
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.).
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.).
Specialized Business Operating Agent	[*..0]	Resource Agent Type	Resource Agent Type	Abstract Relationship
Consumed Resource Interface	[*..0]	Resource Service Interface	Resource Agent Type
Provided Resource Interface	[*..0]	Resource Service Interface	Resource Agent Type
Resource Connection	[*..0]	Resource Service Interface	Resource Agent Type	Abstract Relationship
Performed Resource Scenario	[*..0]	Resource Interaction Process	Resource Agent Type	Abstract Relationship A Performed Resource Scenario is a Resource Interaction Process operated by a Resource Agent Type.
Performed Resource Process	[*..0]	Resource Action Process	Resource Agent Type	Abstract Relationship A Performed Resource Process is a Resource Action Process operated by a Resource Agent Type.
Resource Store	[*..0]	Information Domain	Resource Agent Type	Abstract Relationship
Realized Agent	[*..0]	Agent Type	Agent Type
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.
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.
Realized Business Operating Asset	[*..0]	Resource Operating Asset Type	Resource Operating Asset Type	Abstract Relationship
Resource Rule Enforcement	[*..0]	Resource Rule	Resource Operating Asset Type	Abstract Relationship
Conceptual Schematization	[1..1]	Systemic Level Family	Operating Asset
Conceptual Schematization	[1..1]	Conceptualization Level	Operating Asset
Operating Asset Category	[*..0]	Operating Asset Category	Operating Asset
Operating Asset Categorization	[*..0]	Operating Asset Categorization	Operating Asset
Risk	[*..0]	Risk Type	Functional Asset	Abstract Relationship A Risk refers to the potential for loss resulting from inadequate structure or behavior of a Functional Asset.
Policy Conformance	[*..0]	Policy	Functional Asset	A Policy Conformance is the conformity requirement that applies a Functional Asset.
Applicable Condition Type	[*..0]	Condition Property Type	Asset Type	Set of Condition Property Types that can be applied to an Asset Type.
Classified by Bounded Individual MetaClass	[1..1]	Bounded Individual MetaClass	Asset Type
Asset Categorization	[*..0]	Asset Category	Asset Type	Abstract Relationship
Asset Categorization Scheme	[*..0]	Asset Category Family	Asset Type	Abstract Relationship
Temporal Ordering Type	[*..0]	Temporal Bounding Type	Class of Bounded Individual	Abstract Relationship
Relation	[*..0]	Entity	Entity	Abstract Relationship A Relation is the reification of a Linkage of the Predication Substrate, as an Element that represents a directed connection between a source Entity and a target Entity.Relations are nested within their source Entity. (principle of locality).
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 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.
Class of Holonymy	[*..0]	First Order Class	First Order Class	Class of Holonymy is the powertype of Holonymy Relation.
Class of Meronymy	[*..0]	First Order Class	First Order Class	Class of Meronymy is the powerType of Meronymy Relation.

LOGICAL FORMULATION

LOGIC-AGDA RDF

File: 4c7883cd5fca4d5b.agda

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