The specification of services corresponds to the definition of all the information needed to further implement them. This includes all the information in the defined Service Contract: interfaces, operations, input and output parameters, and pre and post conditions if needed. Each operation in the interface must specify: a) name of the method, b) required parameters and for each one, its name, type and description, c) return value, indicating name, type and description, d) list of exceptions, e) brief description of the provided functionality, f) pre-conditions for the successful execution, g) post-conditions that have to be valid after execution. The information related to the in and out messages must be specified, indicating the parameters and data to be interchanged between the parties.

Message Type definitions to be used in operations from the Reseller:

The choreography defined by the Service Contract (if any) must also be specified, based on the interaction between participants, interfaces, operations and parameters used.  Service Contract with roles definition and corresponding choreography for the defined service ReceiveOrder of Reseller.  

In order for services to be generated in SoaML from the BPMN business process model with this information, the Architect must provide it in the BPMN business process model for the activities marked as services.