CONNECTION - Physical Software Interface
| Description | An Physical Software Interface is a physical specification of an Application Interface to which it adds the following physical characteristics: 1) The software communication protocol which defines the format of the data, the procedures for error handling, and the protocols for data transfer. Examples of software communication protocols include HTTP, SOAP, gRPC, 2) Potential specific target port number. 3) Optional restrictions on source port number to use . 4) Transport protocol (TCP/UDP). Physical Software Interfaces can also represent lower lever APIs supported by Software Technology Systems such as DHCP, SMTP, IMAP, LDAP. |
|---|---|
| Super Types | 
Service Interface |
| Dictionary | Dictionary of SysFEAT concepts |
| Functional Domain | 
EA Pattern - Physical Software Operating PatternThe EA Pattern - Physical Software Operating Pattern domain provides abstractions shared by all physical software artifacts. |
| Categories | Technical Level |
RELATIONSHIPS
Simple Graph Graph & Inheritance Table
Simple Graph
Composition: ➝ Classification: ➝ Specialization: ➝ Enumerated definition: ➝ Syntax: ➝
TEXTUAL SYNTAX
CONNECTION DIAGRAM
CONNECTION ENDS
| Name | Type | Super Type | Description | |
|---|---|---|---|---|
| Source End | 
Consumed Software Service |
Service Interface::Consumed Service | ||
| Target End | 
Produced Software Service |
Service Interface::Provided Service |
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.