Working towards the next version of the SWIM Supporting Material
Page History
Table of Contents |
---|
Requirement
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Guidance
No guidance provided.
Guidance
: list one or more validation activities.for
conformance with the service objectives and requirements. Note: the service objectives and requirements are captured in the service overview and the technical specifications. [SWIM-SERV-027]Rationale: User needs to know how the information service was validated in order to have confidence in the service.
Guidance: indicate whether a validation of the service has been performed; and if so, the method used; and the results achieved.
SvcOvw
Note: Missing a value for "not validated yet" (see Code Lists walk-through).
Note: Is mandatory except for the case not validated.
Descr: The validation method used
Name: Consider renaming type to method. (In addition (consider renaming type as well CodeValidationMethodType)
Guidance: Include a brief statement on the validation results, and if/how the potential consumers may obtain the validation evidence.
Example: This information service has undergone extensive testing prior to deployment by the information service provider “LMN”, infrastructure service provider “ABC”, and regulator “XYZ” to ensure that specific QoS standards are met. Operational monitoring by the information service provider is in place and the information service continues to meet all QoS requirements. For more information on this organization’s validation policies please see <URL>. Specific information regarding the validation by the regulator is available in a validation report upon request.
Guidance for JSON service description
Excerpt | ||||||
---|---|---|---|---|---|---|
UNDERWORK
|
Schema
The guidance concerns JSON Schema v0.0.3 (see Schema releases).
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Rules expressed for the cases as defined in Registry URD.
|
Guidance
Within field validation, itself within field serviceGeneralDescription, list one or more validation activities.
Guidance: When such a mechanism is made available to consumers, it is mandatory to describe it.
Case 1 - A mechanism is made available
Rationale: Allow the service consumer to use the available mechanism and monitor the service.
Within field serviceMonitoring, itself within field serviceTechnicalDescription, provide the following attribute
Provide the description so that the mechanism can be used by the consumer.
Case 2 - No mechanism is made available
Nothing needs to be describedindicate whether a validation of the service has been performed; and if so, the method used; and the results achieved.
In case no validation has been performed, indicate so in the field description.
ValidationOfService - Mandatory (one or more)
An activity whereby a service is checked for conformance with the service objectives and requirements.
Rationale: User needs to know how the information service was validated in order to have confidence in the service.
attribute name | description | type | guidance | rule | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
type | The validation method used |
| Select the validation method used for this validation activity. Note: Mandatory when validation activities have been performed. It is of no use other wise. | Conditional Mandatory | |||||||||||||
description | The description of the service validation | string | Guidance: Include a brief statement on the validation results, and if/how the potential consumers may obtain the validation evidence. Example: This information service has undergone extensive testing prior to deployment by the information service provider “LMN”, infrastructure service provider “ABC”, and regulator “XYZ” to ensure that specific QoS standards are met. Operational monitoring by the information service provider is in place and the information service continues to meet all QoS requirements. For more information on this organization’s validation policies please see <URL>. Specific information regarding the validation by the regulator is available in a validation report upon request. Note: in case no validation has been performed, indicate so. | Mandatory |
Validation Report document (Optional)
A document of type SERVICE_VALIDATION_REPORT may optionally be provided. See Guidance on serviceDocument.
Example
Code Block | ||||
---|---|---|---|---|
| ||||
"serviceTechnicalDescriptionserviceGeneralDescription": { "validation": [ { "type": "SELF_VALIDATION", "serviceMonitoring": description": "The service has been subject to intensive Verification and Validation, in alignment with our Quality Management System." }, { "monitoringDescription "type": "COLLABORATIVE_VALIDATION", "description": "The service ishas monitored,been howeversubject thereto istwo novalidation monitoringsessions interfacewith provideda tofew theservice consumers. The validation report is available upon request." } ] } |
Code Block | |||||
---|---|---|---|---|---|
| |||||
"serviceGeneralDescription": { "serviceTechnicalDescriptionvalidation": [ { "description": "The service has not been validated yet." } ] } |
A complete JSON example is available in page JSON example - Donlon TOBT Setting service description.