[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Re: Major Historical SOA Milestone Today

  • To: "Michael Kay" <mike@s...>,"bryan rasmussen" <rasmussen.bryan@g...>
  • Subject: RE: Re: Major Historical SOA Milestone Today
  • From: "Bullard, Claude L \(Len\)" <len.bullard@i...>
  • Date: Thu, 11 May 2006 16:22:23 -0500
  • Cc: <xml-dev@l...>
  • Thread-index: AcZ1NSFYBuXASDpHTRGkbeAGEY/mIQAAIQGQAAHBK4AAAB9GkA==
  • Thread-topic: Re: Major Historical SOA Milestone Today

michael kay rfp
I'd say that was what you were trying to implement, not what you were
attempting to specify.  How could you create an object-oriented program
without the implementation?  We could always Booch up our UML, but at
some point, "bytes must change state".  OOP went South every time we
tried to sell that concept to the businessmen.  It was only when we
described the reports that could be generated and the business rules
they could configure that we finally sold a system implemented with
objects over relational DBs.  Viewpoint matters.

Given an SOA, the business guy should be able to specify what they want
without knowing how we did that.  Unfortunately, they try to know both
and that slows us down; hence, the very long and odious RFP to Proposal
to Contracts to Implementation cycles.  If one can specify a Business as
a set of outward and inward facing services, then it is faster and most
of the choices can be made by the customer.  In business environments
where the critical requirement is to enable ever larger groups to
coordinate actions, this is a good approach for well-known reasons.

Weirdly enough, just as I am writing this, I get email about how
"business objects will revolutionize my applications".

I didn't say it was precise.   Just that is isn't meaningless.

len

-----Original Message-----
From: Michael Kay [mailto:mike@s...] 
Sent: Thursday, May 11, 2006 3:54 PM
To: Bullard, Claude L (Len); 'bryan rasmussen'
Cc: xml-dev@l...
Subject: RE:  Re: Major Historical SOA Milestone Today

> The focal point of SOA is when one decomposes a business into requests
> for services by type regardless of implementation.   That is why an
> object oriented architecture is not an SOA. 

Well "decomposing a business into requests for services by type
regardless
of implementation" sounds exactly like what we wre trying to do when I
was
working on IT architectures in the 1980s, and we called it object
oriented
then. But perhaps we were just trying to be fashionable.

Michael Kay
http://www.saxonica.com/


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.