Multiple approaches can be taken to institutionalize SOA life-cycle management. For example, a top-down approach could follow a set of steps similar to those shown below.
A bottoms-up approach could follow a set of steps that focuses on how to provide a standardized information transport mechanism (e.g., machine-to-machine messaging) between existing applications and products. This is very similar to an Enterprise Application Integration (EAI) approach, and it could typically start by instituting an Enterprise Service Bus (ESB) implementation that hosts the appropriate protocol/application adaptors needed to place information on the information transport mechanism. However, this approach can quickly fall into a product-focused solution that fails to deliver any real business value through the use of shared, reusable services and metadata schemas/tagging. Therefore, an organization will rather quickly find itself performing the early steps described in the top-down approach.
Seros realizes that a wide spectrum of SOA implementation maturity exists across today’s organizations. Therefore, Seros has postured itself to support multiple approaches to instituting SOA life cycle management whether it be top-down, bottoms-up, middle-out, etc. Seros has accomplished this via the inherent flexibility offered by our design pattern based approach. That is, we can help to preserve existing product investments through an incremental SOA architecture migration strategy. Regardless of the approach taken to instituting SOA life cycle management, Seros provides low risk and affordable options to move to the required SOA implementation as quickly as possible while also minimizing the complexity of the migration.