Difference between revisions of "SOA Delivery lifecycle"
Jump to navigation
Jump to search
| Line 44: | Line 44: | ||
<tr> | <tr> | ||
<th>Description</th> | <th>Description</th> | ||
<td> | <td>Simple data-centric or logic-centric services</td> | ||
<td>Technology gateways, adapters, façades, and functionality-adding services</td> | |||
<td>Encapsulate process logic</td> | |||
<td>Service shared with other enterprises or partner organizations</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th>Implementation complexity</th> | <th>Implementation complexity</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Revision as of 00:10, 17 June 2007
Following general stages in SOA delivery lifecycle are recognized
- service-oriented analysis
- service-oriented design
- service development
- service testing
- service deployment
- service administration
Top-down approach[edit]
- promotes the formal definition of corporate business models prior to modeling service boundaries
- can result in the highest quality level of SOA
- it also imposes a significant volume of up-front analysis work
Bottom-up approach[edit]
- delivery of application services on an "as needed" basis
- is easy to follow
- does not result in the advancement of service-orientation or process-enabled SOA
Agile approach[edit]
- meet in the middle
- on-going analysis is supported, while still allowing the immediate delivery of services
- as analysis progresses, existing services are revisited and revised as required
Service-oriented design (steps)[edit]
- compose SOA (define service layers,position core standards, choose SOA extensions)
- design entity-centric business services
- design application services
- design task-centric services
- design service-oriented business process
SOA Layers[edit]
An example of possible SOA layers and their characteristics.
| * | Basic services | Intermediary services | Process-centric services | Public (enterprise) services |
|---|---|---|---|---|
| Description | Simple data-centric or logic-centric services | Technology gateways, adapters, façades, and functionality-adding services | Encapsulate process logic | Service shared with other enterprises or partner organizations |
| Implementation complexity | ||||
| State management | Item four | |||
| Reusability | Item four | |||
| Frequency of change | Item four | |||
| Mandatory element of SOA | Item four |