[Comment: Section 2, Para 1] Re: [ebsoa] Recipes for Success

["Chiusano Joseph" <chiusano_joseph@bah.com>]

I would like to suggest an alternate version of the definition of SOA
that appears in Section 2, Para 1.

Current definition:

"An architecture is called a Service Oriented architecture if it follows
a general model for how components communicate or interact with each
other."

The following proposed alternate definition approaches the definition of
SOA from a business/functional perspective:

"Service-oriented architectures (SOAs) provide flexibility and agility
for organizations through their representation of business functionality
as implementation-neutral, standards-based shared services. They are a
natural progression in the evolution that began with the advent of XML
and the emergence of Web Services."

I would also recommend an alternate Figure 3.1 that depicts an
architecture with multiple functions exposed as services, many of which
utilize shared services (i.e. each other) for their required
functionality.

Thoughts?

Joe

Matthew MacKenzie wrote:
> 
> So, I've officially thrown down a first draft of this specification, based on Duane's introduction, and an extremely perverted transliteration of the Zachman framework into a simple pattern notation that I cooked up. Its basically at the outline phase right now, I more or less see it having the following structure:
> 
> Introduction - Basic Stuff
> Service Oriented Architecture - What it is, why we're doing it, etc.
> Pattern Notation - How we will represent patterns, define a grammar.
> Patterns - The actual patterns, conforming to the pattern notation.
> 
> So, in order to facilitate the progression of this specification, I will make the following proposals for some ground rules.
> 
> 1. Please, don't edit the working draft unless you are part of the editing team.
> 2. Please, review and send comments and suggested content. One comment per email with a subject that sets the context, e.g. s1.1, fix to para 3. If you draft content that is complex, do it in MS Word using ONLY the default text styles with body text at Arial/10pt.
> 3. Please submit comments and content to the mailing list, so that they are archived.
> 4. Please, don't cc people who are known to be on the list when sending to the list.
> 
> Thanks :-)
> ___________________________
> Matthew MacKenzie
> Senior Architect
> IDBU Server Solutions
> Adobe Systems Canada Inc.
> http://www.adobe.com/products/server/
> mattm@adobe.com
> +1 (506) 871.5409

-- 
Kind Regards,
Joseph Chiusano
Associate
Booz | Allen | Hamilton