SWIM-SERV-015 Technical constraint

Last updated: JUNE 13th, 2019


Requirement

Title

Technical constraint

Identifier

SWIM-SERV-015

Requirement

If technical constraints are known, a service description shall include information about the technical constraints that would guide the consumer in their client development.

Rationale

Knowing and satisfying the pre-requisite constraints of a service facilitate good use of the service, such as benefiting from the indicated quality of service statements.

This requirement supports decision making in terms of assessing the implication, costs and feasibility, of using the service.

Verification

Completeness: Not Applicable.

Consistency: If provided, verify that the information corresponds to the described service.

Correctness: Not Applicable.

Examples/Notes

Example technical constraints: firewall, minimum bandwidth or server resources, interface language, integration pattern, protocol and communication ports.

Example: For a publication service where the subscription mechanism is not based on a capability of the service itself, stakeholders need to understand how they can subscribe (e.g. using electronic form, email, etc).

Level of Implementation

Mandatory Conditional

Guidance

Examples

See the Technical Constraint section within the Donlon TOBT Setting Service Description.