![]() |
|
||
|
|
|||
![]() |
| Report Summary |
| Title: | Service Oriented Architecture Part 2 - The Bridge | ||
| Author: | Oliver Sims | ||
| Publication Date: | 9 April 2003 | ||
| Report Type: | Journal | ||
| Report Class: | Best Practice | ||
| Abstract: | The Enterprise Service-Oriented Architecture provides the essential foundations for flexible applications. The first report in this series showed how a single architecture based on mature CBD can address B2B, B2C, Workflow, Legacy Wrapping, and provide the scalable Enterprise Services needed. However, to be effective, and to truly enable business agility, there must be clear traceability between business requirements and system implementation. Otherwise the services provided may well not be those the business requires and needs. This report, the second in the series, shows how a seamless progression can be made from a business requirements definition to implementation, with little information loss. This is business-oriented system modeling and design (as opposed to system-oriented business modeling)-a development process that ensures that the "business model" maps one-to-one to components in the IT system, so capturing business requirements much more precisely as well as providing much better business-to-code traceability. | ||
| Backgrounder: | 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. |
||
| Report Size: | 9 Pages | ||
| Report Access Type: |
|
||
| Available for separate purchase | Single copies of recent CBDI Journals may be purchased | ||
| Login |
|
| © Everware-CBDI Inc 1999-2008 |