| Description | A Deployable Data Package represents a data part of an Application that must be hosted and accessed by application services (code) to run. Each Deployable Data Package is associated to Required Software Technologys (for data hosting and access) and can host several data structures. Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model). |
|---|---|
| External references |
C4 Model - Level 2 - Container Diagram |
| Super Types |
Deployable Package |
| Functional Domain |
Application Deployment ArchitectureThe Application Deployment Architecture domain defines concepts used to organize Applications in Deployable Packages. |
| Dictionary |
Dictionary of SysFEAT concepts |
| Framework Mapping | C4 Model Mappings : Container Database |
Composition: ➝ Classification: ➝ Specialization: ➝ Enumerated definition: ➝ Syntax: ➝
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.
| 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.). |