The process of building the A380 would be a great example to demonstrate divide-and-conquer principle as follows:
1. Divide the given problem instance into subproblems
2. Conquer the subproblems by solving them recursively
3.combine the solutions to the subproblems to a solution for the original problem
There was no way it could create a manufacturing facility large enough to build the entire plane in one place. Various parts are built all over Europe:
- Wings – Broughton, Wales
- Fuselage parts – Hamburg, Germany
- Tiffin – Stade, Germany
- Rudder – Puerto Real, Spain
- Nose – Saint Nazaire, France
- Fuselage and cockpit sub-assemblies – Méaulte, France
- Horizontal tailplane – Getafe, Spain
- Final assembly – Toulouse, France
- Cabin installation and painting – Hamburg, Germany
- Other parts are made around the world, including some in the United States. Most of the largest parts are transported by barge.
The principles of service orientation provide a way to support this theory while achieving a basic paradigm on which many contemporary SOA characteristics can be constructed.
A service is a self-contained unit of software that performs a specific task. It has three components: an interface, a contract, and implementation. The interface defines how a service provider will perform requests from a service consumer, the contract defines how the service provider and the service consumer should interact, and the implementation is the actual service code itself. Because the interface of a service is separate from its implementation, a service provider can execute a request without the service consumer knowing how it does so; the service consumer only worries about consuming services.
Services can be derived as follows
A services are autonomous — The logic governed by a service resides within an explicit boundary. The service has control within this boundary, and is not dependent on other services for it to execute its governance.
Services share a formal contract — In order for services to interact, they need not share anything but a collection of published metadata that describes each service and defines the terms of information exchange.
A services are loosely coupled — Dependencies between the underlying logic of a service and its consumers are limited to the conformance of the service contract.
Services abstract underlying logic — Underlying logic, beyond what is expressed in the service contract metadata, is invisible to the outside world.
A services are comparable — Services may compose others, allowing logic to be represented at different levels of granularity. This promotes reusability and the creation of service abstraction layers.
A services are reusable — Regardless of whether immediate reuse opportunities exist, services are designed to support potential reuse.
A services are stateless — Services should be designed to maximize statelessness even if that means deferring state management elsewhere.
A services are discoverable — Services should allow their descriptions to be discovered and understood by humans and service requests that may be able to make use of their logic.
Finally, service transition, operation services and the improvement of services focusing on processes to provide service on the market, ensure its operational performance and ongoing development of this service to provide optimally.
How the Airbus A380 works http://science.howstuffworks.com/transport/flight/modern/a3804.htm
Core principles for service-oriented architectures http://www.looselycoupled.com/opinion/2005/erl-core-infr0815.html
IBM offers 7 steps to SOA success http://www.idevnews.com/stories/3552/IBM-Offers-7-Steps-to-SOA-Success
SOA and business processes: you are, the process! http://www.oracle.com/technetwork/articles/soa/ind-soa-bpm-2133403.html
Using ITIL for SOA governance http://soa-eda.blogspot.co.nz/2007/12/using-itil-for-soa-governance.html