[REQUIRED, one]

Technical Definition:

How the behaviours, requests, algorithms, resources, state representations, etc., are combined to provide the functionality. What are the constraints in sequencing behaviours and requests (both of this Service Expression itself and the interactions of this Service Expression with other service expression)? What are the use patterns? The pre- and post-conditions and specification of side effects and state changes are sufficient to deduce this information for a single Service Expression; this separate entry combines the disparate and disconnected behaviours into a more comprehensive presentation needed to understand how to use the Service Expression either alone, or in combination with other Service Expressions.

Note: This is a precise technical description; it details conforming and non-conforming interactions that span multiple requests.

Commentary:

A precise, technical explanation of how the Requests & Behaviours combine to produce the desired functions, including any constraints on the sequencing of Requests and Behaviours that govern how the Service Expression can be used either by itself or in combination with other Service Expressions.