SOA, that is, Service-oriented Architecture, is a PLAN that people (architects) use to re-design Systems (IT especially) and organizations.
In involves the adoption of the PLAN by each individual involved in the process - if it is not fully accepted or properly implementing, it could result in shattered SOA-dreams!
BUT, if done properly, can transfrom a business into being a leader in it's space!
Key ideas that could help, on this path:
Measure progress and make course corrections as you go;
Motivate participants that are involved in the SOA-adoption process;
Mechanize, that is, automate processes, on an on-going basis;
Although SOA is an architectural method to create a PLAN, there is one basic principle: Start small - one project at a time! Until this becomes part of the organization culture / fabric!
Implementing SOA, implies that everything should "look" as a Service!
A Service is a basic building-block, that quite often is a repeatable business process/ capability.
An SOA service is a capability that is consumed, for example:
- Credit-check for individuals that are applying for a Loan / Credit
--- or maybe
- Changing the address of a Supplier/Customer/Employee
A Service is "invoked", and it presents a well-defined method that allows a person to access it's capability.
"Services" are located remotely, that is, they can be "invoked" from "anywhere". They are semi-transparent because one does not know how it does it's job.
"Services" can be meshed together thereby providing another Service. AND, if assembled in a particular sequence, they can complete a "process".
... more to come.....
