> Object orientation describes the world as it is.  Service
> orientation describe the world as it is to be.  Functional
> orientation describes the world as mathematics. Assembly language is
> machine orientation and describes the world as it is computers.  So
> SOA is software architecture in the same sense as any architecture
> of preceding technologies.

I am sorry. I find this useless.

Object-oriented software design has a set of engineering principles. A
really good set that I have used for years...

PDF:
http://www.objectmentor.com/resources/articles/Principles_and_Patterns.PDF

These principles can be used to design new systems that meet the
needs of the business, are maintainable, etc. They can be used to
design distributed, integrated, evolvable systems.

There is nothing remotely like this in utility that I know of for "SOA".

Instead we get these sayings like, "OO describes the world as it
is. SOA describes the world as it is to be."

I find no value in such a statement. How does an engineer or an
business analyst use this kind of statement?

-Patrick









SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to