1. By architecturally neutral, we mean that the requirements contract specifies what the solution has to do but not how.

2. We then used that requirements contract to help identify the required services and the potential relationships between them.

3. This service collaboration represents a requirements contract derived from a business process that specifies what the service solution must do.

4. Figure 1 shows the business services requirements contract that our solution must fulfill.

5. We then used this requirements contract to help identify the required services and the potential relationships between them.

6. Recall that this service collaboration represents a requirements contract, which is potentially derived from a business process that represents what our service solution must do.

7. This maintains the link between the service requirements contract, business processes, the business use case, and the business goals and objectives.

8. The next section treats the business process as a Requirements contract and shows how to identify services in an SOA solution for the intended business operational requirements.

9. What this diagram does show, however, is how these services fulfill the Service Collaboration requirements contract.

10. Next, we viewed the business process as a service collaboration that represents a business Service Requirements contract that must be fulfilled by our eventual solution.

11. To do this, we will treat the business process as a Service Requirements contract.

12. These are the services that are capable of playing the roles in this Business Services Requirements contract.

13. Essentially, we are building (buying, reusing,() adapting) services that are capable of playing the roles in this business services requirements contract.

14. It shows, specifically, what parts of the service provider play roles in the service requirements contract and how constraints on the component fulfill business constraints.

15. This is to be expected, because you are defining the specification in a Service Requirements contract for how a service consumer and provider interact.

16. Then we viewed the business process as a service collaboration that represents a Business Services Requirements contract that must be fulfilled by our eventual solution.

17. OrderProcessor is a component that provides a service by connecting other service providers together, which are choreographed according to a requirements contract.

18. Its parts represent order processing participants that will provide or require services (or both) that are necessary to fulfill the Process Purchase Order requirements contract.