S7 — Service Interface Parameters

Purpose & Usage

The S7 Viewpoint is concerned with the identification and specification of all the parameters used in service operations/ functions for the interface in

Scope

• scope.
• Detailed Service design.
• Service compatibility analysis.
• Service- oriented architecture governance.
• Service interoperability. Scope
• Shall contain parameters of Service Operations or parameters of Service Functions relevant for the entity of interest.
• Shall contain Passive Resources involved in Services Functions or Service Operation Parameters.
• May show Services that are enabled by the Service Functions.
• May show Service Interfaces that specify the Service Operation, and the Services that specify the Service Interface.

Representation

• Tabular.
• Diagram.

Cut-out (Meta-model)

flowchart TB
    LPR["Logical Passive Resource"]:::activity
    PPR["Physical Passive Resource"]:::config
    ServiceFunctionParameter["Service Function Parameter"]:::service
    ServiceOperationParameter["Service Operation Parameter"]:::service
    ServiceFunction["Service Function"]:::service
    ServiceOperation["Service Operation"]:::service
    Service:::service
    ServiceInterface["Service Interface"]:::service
    ServiceFunctionParameter -->|"involves"| LPR
    ServiceOperationParameter -->|"involves"| PPR
    ServiceFunction -->|"has"| ServiceFunctionParameter
    ServiceOperation -->|"has"| ServiceOperationParameter
    ServiceFunction -->|"enables"| Service
    Service -->|"specifies"| ServiceInterface
    ServiceInterface -->|"specifies"| ServiceOperation
    classDef service fill:#E5C1E5,stroke:#7B4F7B,color:#000
    classDef activity fill:#9DC3E6,stroke:#1F4E79,color:#000
    classDef config fill:#F4B084,stroke:#833C0C,color:#000

Notes on the Cut-out

S7 distinguishes Service Function Parameters (logical) from Service Operation Parameters (physical realization). Parameters are linked to Data Models transitively through Passive Resources.

NAFv4 Compliant Example

flowchart TB
    SIC["«Service» Situation Information Consolidation"]:::service
    SitPic["«Service Interface» Situation Picture"]:::service
    SubmitLoc["«Service Operation» submit Location Of Resource"]:::service
    SetAOI["«Service Operation» set Area Of Interest"]:::service
    DR["«Service Function» Data Receiving"]:::service
    DS["«Service Function» Data Storing"]:::service
    GeoLoc["«Service Operation Parameter» Geographic Location"]:::service
    Track["«Service Operation Parameter» Track"]:::service
    ResParam["«Service Operation Parameter» Resource"]:::service
    IncomingData["«Service Function Parameter» Incoming data"]:::service
    DataPayload["«Service Function Parameter» Data Payload"]:::service
    SitReport["«Information Product» Situational Report"]:::activity
    ConsSitPic["«Information Product» Consolidated Situational Picture"]:::activity
    PosRpt["«Data Product Type» Position Report"]:::config
    TgtRec["«Data Product Type» Target Track Record"]:::config
    SIC -->|"specifies"| SitPic
    SitPic -->|"specifies"| SubmitLoc
    SitPic -->|"specifies"| SetAOI
    SubmitLoc -->|"has"| GeoLoc
    SetAOI -->|"has"| GeoLoc
    SubmitLoc -->|"has"| Track
    SubmitLoc -->|"has"| ResParam
    GeoLoc -->|"involves"| PosRpt
    Track -->|"involves"| TgtRec
    DR -->|"enables"| SIC
    DS -->|"enables"| SIC
    DR -->|"has"| IncomingData
    DS -->|"has"| DataPayload
    IncomingData -->|"involves"| SitReport
    DataPayload -->|"involves"| ConsSitPic
    classDef service fill:#E5C1E5,stroke:#7B4F7B,color:#000
    classDef activity fill:#9DC3E6,stroke:#1F4E79,color:#000
    classDef config fill:#F4B084,stroke:#833C0C,color:#000