Currently, my favourite ones are: - Service-Oriented Architecture: It is said that the architecture of an Information System is Service-Oriented when it supports the Service-Orientation paradigm.
- Service Orientation: It is a way to structure an information system so that the implementation of the whole functionalities offered by it is distributed across discrete units called services, which can be used through a programmatic interface. - Service: A service is an element of an information system which offers a precise set of functionalities through a number of well-defined automatic interfaces. They can be expanded but these are short enough. Honestly, I think these are compatible with the OASIS SOA RM ones, seen from the technology side. However, the ones from the RM are too abstract for my linking. I won't try to explain them to my mother. She is not interested in SOA, and indeed should not be. Neither should be a business director. As you can imagine, I see SOA only as a technical artifact. Regards --Javier --- In [email protected], "Gervas Douglas" <[EMAIL PROTECTED]> wrote: > > No one anywhere in the known universe has yet come up with a > definition of SOA which commands widespread acceptance. Perhaps it is > time we had another crack at it. > > Over to you ladies and gents... > > Gervas >
