This is a more complete set of artifacts from a proposed SOA framework project.  The third diagram (WebSphere Stack Components) has been posted here previously.

This is a progression of diagrams created in order to analyze the open or standards compliant nature of components within multiple various vendor software stacks.

In the first diagram, I provide a breakdown of functional classes for further review – a decent representation of components in a system.

SOA Component Classes

Here, the components with an overlay of the proposed SOA framework.

SOA Component Classes by Framework Segment

Here, the same components, with WebSphere specific implementations grouped therein.  Notice here, the legend notes tightly coupled (red) versus loosely coupled (blue) component connections.  This is to signify whether we could easily utilize or replace the component in question with a component from another vendor (or better, from an open source…source).

WebSphere Stack Components

The same WebSphere components with the segment overlay.

WebSphere Stack Component with Framework Segments Overlay

Here, the same generic component classes with BEA software stack specific components and segment overlay.  Again, the legend provides good information concerning vendor neutrality.

BEA Stack Components with Framework Segments Overlay

This is the same component class set with an example Free and Open Source [FOSS] implementation.  Notice that all of the connections between components are vendor neutral, or standardized connections.  Thus, any component may be replaced relatively easily as needed.  This is only one possible implementation using FOSS.  At the time (c. 2007) I attempted to highlight best of breed software, and much of the selection may be updated now.

FOSS Components (example) with Framework Segment Overlay

Posted by john joseph roets of createTank.