On 25.01.2007, at 17:29, Mark Baker wrote:
> On 1/24/07, Alex Hoffman <[EMAIL PROTECTED]> wrote:
>> An SOA is simply a software architecture based on services.
>> What's a service? A software program that is intended to be used
>> by another program.
>
> Definitions need to be sufficiently precise in order to enable one to
> distinguish what is from what isn't.
Here is a question that could provide a start towards an
architecturally meaningful definition of SOA:
1. In what way does SOA constrain components of a networked system?
(When I design a component, what am I allowed to do and what not)
2. In what way does SOA constrain data elements of a networked system?
(When I design a data element, what am I allowed to do and what
not)
(Of course the answers to this must be testable to be meaningful).
<throwing-the-gauntlet-mode>
My take is that SOA does not have to say anything about 1 or 2
that is testable.
</throwing-the-gauntlet-mode>
Cheers,
Jan
>
> Mark.
>
>
>
> Yahoo! Groups Links
>
>
> [EMAIL PROTECTED]
>
