Difference between revisions of "SOA Delivery lifecycle"
Jump to navigation
Jump to search
Line 51: | Line 51: | ||
<tr> | <tr> | ||
<th>Implementation complexity</th> | <th>Implementation complexity</th> | ||
<td>Low to moderate</td> | |||
<td>Moderate to high</td> | |||
<td>High</td> | |||
<td>Service specific</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th>State management</th> | <th>State management</th> | ||
<td> | <td>Stateless</td> | ||
<td>Stateless</td> | |||
<td>Stateful</td> | |||
<td>Service specific</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th>Reusability</th> | <th>Reusability</th> | ||
<td> | <td>High</td> | ||
<td>Low</td> | |||
<td>Low</td> | |||
<td>High</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th>Frequency of change</th> | <th>Frequency of change</th> | ||
<td> | <td>Low</td> | ||
<td>Moderate to high</td> | |||
<td>High</td> | |||
<td>Low</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th>Mandatory element of SOA</th> | <th>Mandatory element of SOA</th> | ||
<td> | <td>Yes</td> | ||
<td>No</td> | |||
<td>No</td> | |||
<td>No</td> | |||
</tr> | </tr> | ||
</table> | </table> |
Revision as of 00:15, 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 | Low to moderate | Moderate to high | High | Service specific |
State management | Stateless | Stateless | Stateful | Service specific |
Reusability | High | Low | Low | High |
Frequency of change | Low | Moderate to high | High | Low |
Mandatory element of SOA | Yes | No | No | No |