[REQUIRED, many]

Technical Definition:

A list of all behaviours exposed by the service expression, i.e., all functionality that can be used by applications or service implementations. Each behaviour or request specification SHALL include sufficient technical information to develop a design for a service implementation that implements the service expression, describing what the behaviour does and how it manipulates state. The information SHALL include:

• a name for the behaviour or request
• the classification (e.g., transactional)
• form and format of the message or request (including data models, document descriptions)
• responses (normal and abnormal)
• pre-conditions
• post-conditions
• side effects and state changes (including algorithms)
• post-conditions
• functionality and operations provided

Commentary:

Detailed technical information about the functions and operations of the Service Expression, including what the behaviours do and how they change state. These are the critical items for designing an implementation of the service expression: name of the behaviour or request; classification; function and operation provided; format of message or request; normal and abnormal responses; pre- and post-conditions; algorithms, changes in state and side effects.