The participants in this example are Buyer, Store and Credit Agency. The business analyst will work with the business user to understand the different parties that will be involved in the business process.
Depending upon the level of detail to be expressed in the scenarios, the participants could define software systems, or also people. Where interactions are defined to a party representing a person, these could be implemented using a service that wraps use of a task management system.
This stage can also define the relationship between the participants. In CDL, this can be achieved by defining the participants, roles & relationships. In BPMN2, this may be based on a conversation model.
Repo: When collaboration model defined, it will need to be stored in the repo and circulated for comment/approval. Comments will need to be recorded against the model (document) in the repository, and potentially some mechanism for recording which comments have been acted upon.
Input: List of participants that will be involved in the system, this could come from UML use cases, sequence models or other suitable requirements documents.
Output: Collaboration model
(Collaboration model in this context could mean a BPMN collaboration/conversation model, a WS-CDL participant/role/relationships model, or some other suitable representation to define the cooperation between multiple parties in a business process).