Requirement
Title | Service behaviour |
|---|---|
Identifier | SWIM-DEFN-220 |
Requirement | A service definition shall include or refer to information about the expected typical behaviour of the service. |
Rationale | This requirement facilitates the understanding of the service behaviour to support operational processes. |
Verification | Completeness: Verify that the behaviour information is included. Consistency: Not Applicable. Correctness: Not Applicable. |
Examples/Notes | Note: The requirement covers the typical behaviour under normal conditions. Details on the handling of unexpected behaviour can be included, e.g., error handling. Note: A diagram showing how the operations support the typical behaviour can be provided. This can be made available in the model view (SWIM-DEFN-330). Note: The service behaviour patterns that are detailed in the Message Exchange Patterns: Identification Guidelines [RD 16] can be used to meet this requirement. |
Level of | Mandatory |
Guidance
Verification Support
Examples
Example:
A typical sequence is:
(1) The service consumer requests dataset series based on a number of selection criteria, and receives back a list with zero, one or more dataset series objects.
(2) The service consumer analyses that list to identify the dataset series he is interested in.
(3) The service consumer requests datasets from the selected dataset series, possibly supplying additional selection criteria, and receives back a list of zero, one or more datasets.
(4) The service consumer analyses that list to identify the dataset(s) he is interested in.
(5) For each dataset of interest
(5a) The service consumer requests the file information of the selected dataset, and receives back a list of one or more file objects.
(5b) For each file object, the service consumer retrieves the file, and receives back the file content.