View Source

{section}
{column}
{info:title=Mission Statement}A complete *end-to-end SOA strategy* to ensure that customers get return on investment (ROI). The result is a *no-nonsense SOA* with clear directions that:
* puts *IT and business* on the same path
* ensures the *evolvability* of services
* ensures continuous *creation of business value*

This workspace is committed to improving this strategy.{info}
{column}
{column}

{note:title=Yes we know..}
..that you are probably bored to death by SOA talks. But there is much to learn to be able to successfully apply a service oriented architecture, and somebody need to speak up and show the way... :)
{note}

{column}
{column}

{tip:title=Terms and definitions}
[SOA|SOA] [Real SOA|Real SOA], [Governance|Governance], [Policy], [Enterprise Architecture (EA)], [PAB], [ESE|Evolving Service Endpoint Pattern], [EDR|Enterprise Domain Repository Pattern]
[Service Manifest], [Service Categories], [H2A], [A2A], [ACS], [CS],
[Software Design], [Architecture], [Architecture Principles and Axioms], [Patterns|SOA Patterns], [IdM | Identity Management (IdM)], [AM |Access Manager (AM)], [MDM|Master Data Management Notes]
{tip}

{column}
{section}

h3. How it all fits together

| [!EA.jpg!|Enterprise Architecture (EA)] | [!fromEAtoSOA.jpg!|From EA to SOA (and back)] | [!SOA.jpg!|SOA] | [!SOApatterns.jpg!|SOA Patterns] | [!Code.jpg!|Source Code] |


{section}
{column}
!ServiceManifestSmall.jpg!

{column}
{column}

h3. Key takeaways

* Business driven
* The big fight is to teach developers and architects how to build *distributed systems* and to care about *data* and real *business value*
* Some things does not change (too much). Let us make sure that we avoid spaghetti in our Business Objects across our SOA and systems. We can limit the spaghetti to the process services of the edge of our SOA.
* Start small
* Middleware/ESB is not key (or necessary) for a SOA
* [The Laws of SOA]
* [Design-Time Governance - SOA Design Rules]

-----

{column}
{section}