THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Let's think in SOA. Leave the IT things such as hardware, software and networks on side and think from the business perspectives. First, we need to identify the business functions and model them as service components. And then define the relationship between business functions. For example, Order Processing needs to deal with Inventory and Shipment. These dependencies are captured as references and services.
Business Functions | Service Services Provided | Service Services Consumed |
Order Processing | Process ordersOrders | Check Inventory, Collect Payment, Arrange Shipments |
Inventory | Check Inventory | Warehouse |
Payment | Collect payment | Credit Card Authorization, PayPal |
Shipment | Ship the order | Shippers such as UPS, USPS or Fedex |
Map into SCA terms
Business Functions | Components |
Services Provided | Services |
Service Services Consumed | References |
How to customize the business logic? | Properties |
How is the business function logic implemented | Implementation |
How is are the service provided depending services resolved? | Wire |
How are components communicated? | Binding |
QoS | Intent/Policy |
...