3.4.3 Specification of a Binary Collaboration

The next step is to build a Binary Collaboration from the defined Business Transactions. Again, the Binary Collaboration is the realisation of a Business Process and a Business Process can combine several Business Transactions. The class diagram from figure 6 shows, that in fact a Business Collaboration is realised by different states. Each Business Transaction Activity is a state. Further the Binary Collaboration has several authorised roles and each Business Activity (business state) comes from one authorised role and goes to an authorised role. As mentioned earlier a Business Activity can be another Binary Collaboration.

Figure 6: UML Diagram of a Binary Collaboration (Adapted from the Business Process Specification Schema document)

The example XML code shows the Binary Collaboration with the name ``Firm Order''. The Binary Collaboration has one Business Transaction Activity with the name ``Create Order'' and two authorised roles, namely ``buyer'' and ``seller''. The Business Transaction Activity references a Business Transaction ``Create Order'' defined earlier or somewhere else.

<BinaryCollaboration name=''Firm Order'' timeToPerform=''P2D''>
        <Documentation>	
                timeToPerform = Period: 2 days from start of transaction
        </Documentation>
        <InitiatingRole name=''buyer''/>
        <RespondingRole name=''seller''/>
        <BusinessTransactionActivity name=''Create Order''
                businessTransaction=''Create Order''
                fromAuthorizedRole=''buyer''
                toAuthorizedRole=''seller''/>
</BinaryCollaboration>