The specification contains a conformity checklist. It sets out whether conformance with the requirement is "mandatory", "recommended", “optional“ or applicable "when the conditions apply". The organisation or person responsible for the service definition is expected to complete the checklist. It is then possible to attach the checklist to the service definition as evidence of conformance.
To conform with a requirement, the entire requirement has to be satisfied. This includes the need to perform verification. Each requirement contains a statement on the type of verification that is expected (i.e. "completeness", "correctness", "consistency"). The checklist below elaborates on these statements e.g. by spelling out the elements when the requirement states "Verify that the 3 elements are included".
The checklist below is a summary of all of the verification details for easy reference. It is possible to use the table within your own processes.
Requirement | Verification type | Check that: | Level of implementation | Notes |
|---|---|---|---|---|
SWIM-DEFN-010 Service definition coverage
| Correctness | Verify that one and only one service is described. | Mandatory | |
Correctness | Verify that the textual descriptions are correct British English. | Mandatory | ||
Completeness | Verify that the elements are included.
| Mandatory | ||
Completeness | Verify that the element is included. the name of the service | Mandatory | ||
Completeness | Verify that the element is included. a short textual description summarising the service | Mandatory | ||
Completeness | Verify that the applicable elements are included.
| Mandatory | ||
Correctness | If provided, verify that the information is correct. expected geographical coverage of the exchanged information service payload. | Optional | ||
Correctness | If provided, verify that the information is correct. the typical service provider type and typical service consumer(s) type | Recommended | ||
Completeness | Verify that a service category is included. service categories to which the service belongs and, if applicable, reference the service categorisation schemes used. | Mandatory | ||
Consistency | If the service adheres to a service standard, verify that the reference to the service standard is included. | Mandatory Conditional | ||
Completeness | Verify that operational environment information is included or referenced.
| Mandatory | ||
Completeness | Completeness: Verify that the elements are included.
| Mandatory | ||
Consistency | Verify that the functions and real-world effects are consistent with the operational needs. | |||
Correctness | : If provided, verify that the information is correct. constraints which are expected to be applied to accessing and using the service | Recommended | ||
Correctness | If provided, verify that the information is correct. information about the security constraints which are expected to apply to accessing and using the service | Recommended | ||
Completeness | Verify that quality statements are included. information about the expected minimum quality of service offered with regards to:
| Mandatory | ||
Completeness | Verify that quality statements are included. information about the expected minimum quality of the data to be provided by the service | Mandatory | ||
Correctness | If provided, verify that the information is correct. the expected types of sources of the information provided | Recommended | ||
Correctness | If provided, verify that the information is correct. information about any service prototyping activities that have taken place | Optional | ||
Completeness | Verify that the information is included. information about the application message exchange pattern(s) expected to be used by the service | Mandatory | ||
Consistency | Verify that the information is consistent with the selected service interface binding. | |||
Completeness | Verify that the behaviour information is included. the expected typical behaviour of the service. | Mandatory | ||
Not Applicable | Optional | |||
Completeness | Verify that the list of interfaces is included; verify that the name, description and indication are included for each interface.
| Mandatory | ||
Completeness | Verify that the reference information is provided. information about the selected SWIM TI Profile and its version for each service interface | Mandatory | ||
Not Applicable | Optional | |||
Consistency | If provided, verify that the protocols and data format are consistent with the service interface binding.
| Optional | ||
Completeness | Verify that all service operations are described. the expected exposed service operations including:
| Mandatory | ||
Consistency | Verify the service operations against the messaging technology needs. | |||
Completeness | Verify that all service messages are described. the expected messages that are exchanged by the service including input, output and error messages. | Mandatory | ||
Completeness | Verify that the service description describes all elements of the exchanged information and that the required details are provided.
| Mandatory | ||
Consistency | Verify that the elements are consistent with each other and with the AIRM concepts used in the semantic correspondence. | |||
Not Applicable | Recommended | |||
Completeness | If filter expressions are expected, verify that the filter encoding is included. | Mandatory Conditional | ||
Completeness | If the service interface binding supports it, verify that the required elements are included. | Recommended Conditional | ||
Consistency | Verify that provided elements are consistent with the selected binding. | |||
Correctness | If provided, check that the model view is correct. | Optional | ||
Completeness | Verify that all used acronyms and abbreviations are defined. | Mandatory | ||
Consistency | Verify that the abbreviations/acronyms and their definitions are used consistently in the service definition. |