| Title: |
Modeling for SOA |
| Author: |
Richard Veryard |
| Publication Date: |
12 February 2003 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
What modeling approach is required to implement a Service Oriented Architecture? Everyone is talking about Service Oriented Architectures. While SOA is what might be termed a loosely defined concept, it's a reasonable starting point for creating sets of loosely coupled services. So bear with me if I make the sweeping assumption that we are now starting to understand the technology. But surely the really big question is what shall we do with it? At this juncture we need to think about process, methods and modeling. But can we use the same modeling approach that we have always used for monolithic applications or components?
|
| Backgrounder: |
Since component methods have generally focused on the interface, many writers have assumed that these methods will apply equally to service-oriented architectures. A component can be regarded as a bundle of services, hidden behind service interfaces. Whether we are building components or delivering services, we need to produce models that help us to specify and package these interfaces. Whether we are plugging in externally sourced components, or invoking remote services, we need to produce models that help us procure the requisite services.
However, there are several reasons why a service-based approach is materially different to a component-based approach.
|
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home