| Abstract: |
The Service Oriented Architecture provides the essential foundations for flexible applications. We recommend that every organization needs to evolve and upgrade its core systems portfolio in order to easily support internal and external Web Services, as well as have much greater adaptability in basic application upgrade, BPO and other business driven initiatives. In this first part of our series on SOA we provide detailed guidance on where to start. We show how the same architecture can address B2B, B2C, Workflow, Legacy Wrapping, and provide the scalable Enterprise Services needed. An example will be given of a simple SOAP-based web service (B2B), and how it's implemented through service-oriented components. It will be shown how workflow and B2B can very usefully be thought of as components - not the middleware, rather the specifications, which typically are interpreted at run-time.
|
| Backgrounder: |
Introduction to the Series
This series is about the effective specification, design, and delivery of service-oriented applications and business processes in the enterprise environment. It assumes that applications must integrate not only with legacy, but also with each other, in order to avoid creating tomorrow's stovepipe legacy. In particular, we address the major "choke points" from end-to-end of the development lifecycle, and end-to-end from front to back of the distributed enterprise system.
In five parts, the series looks at the following areas, each article building on its predecessor.
Foundation. The Back-End: Enterprise Service-Oriented Architecture (SOA) as an ideal mixture of CBSE and Web Services. CBSE is the best approach to building business systems, and the web service approach can provide a single service definition and invocation technology not only externally but also internally, whether we're talking B2B, B2C, A2A, wrapping legacy, or providing enterprise services to internal users
Service Design. Application Development: Specifying the Services - system-oriented business modeling as the basis for Service design, where the "business model" maps one-to-one to components in the IT system, so capturing far more precise business requirements as well as much better business-to-code traceability.
Federation. Collaborative Service Delivery: In Part I - The Foundation, we showed how Service Oriented Architecture can establish better separation between major enterprise components, and enable inherently more adaptable back end applications. In this report we examine how these same concepts can enable effective collaboration intra and inter enterprises.
The Technology Platform.
Providing a Service-Oriented platform that helps deal with technology complexity and churn, both at the front-end and at the back-end. This describes the "glue" often needed on top of commercial middleware.
The Service Based Business.
If Enterprise SOA is a worthy goal, how does the IT organization get there? This report looks at a process for transitioning to enterprise SOA, so that the business' goals for IT can be better met.
|
Home