Take a look at the following documents at OASIS - 
 
http://www.oasis-open.org/committees/download.php/19679/soa-rm-cs.pdf 
<http://www.google.com/url?sa=t&ct=res&cd=2&url=http%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F19679%2Fsoa-rm-cs.pdf&ei=tqhOSPqUIo2uoQS6sYA3&usg=AFQjCNHANxUN9auHo3ElI1ir2yOHIaS1dg&sig2=yw5XtsTMJljK4KdbtyRJ7Q>
 
 
http://www.oasis-open.org/committees/download.php/15071/A%20methodology%20for%20Service%20Architectures%201%202%204%20-%20OASIS%20Contribution.pdf
 
Those documents will help answer some of your questions - however the questions 
you are asking are starting at the "How" or implementation, that would be 
better answered if a business  driven or top-down approach drove your SOA 
effort. 
 
- Amit

 
 If you are not the intended recipient of this message (including attachments), 
or if you have received this message in error, immediately notify us and delete 
it and any attachments.  If you no longer wish to receive e-mail from Edward 
Jones, please send this request to [EMAIL PROTECTED]  You must include the 
e-mail address that you wish not to receive e-mail communications.  For 
important additional information related to this e-mail, visit 
www.edwardjones.com/US_email_disclosure
 
________________________________
 


From: service-orientated-architecture@yahoogroups.com [mailto:[EMAIL PROTECTED] 
On Behalf Of Dey, Santanu
Sent: Friday, June 06, 2008 10:07 AM
To: service-orientated-architecture@yahoogroups.com
Subject: Re: [service-orientated-architecture] Re: Definition of SOA



I have struggled to define a "service" in the first place..
What is a service? We all know SOA and WS are not the same... Must a service be 
machine discoverable? Must it follow WS*? How decoupled and atomic should the 
services be? how important are service life cycle management, service 
operations management aspects?
 
Then there are questions specific to quintessential SOA characteristics....
What do you think at the minimum should be followed? Is service registry a 
must? Do you need to define a Common Message Format? Should the architecture 
support the capability to compose and orchestrate services? is a BPM layer 
essential? is a Service Bus needed ? how important is service virtualization? 
Which standards to be followed?
 
without having clear answers to many questions questions such as above we can 
not unambiguously define SOA. 

On Thu, Jun 5, 2008 at 10:41 PM, Rob Eamon <[EMAIL PROTECTED] <mailto:[EMAIL 
PROTECTED]> > wrote:


        +1
        
        -Rob
        
        --- In service-orientated-architecture@yahoogroups.com 
<mailto:service-orientated-architecture%40yahoogroups.com> , Michael Poulin 
        
        <[EMAIL PROTECTED]> wrote:
        >
        > I would disagree with "üA service-oriented architecture is 
        essentially a collection of services"; it is not an architecture.
        > 
        > - Michael
        
        

        

        

        



Reply via email to