Anne
Good stuff Stefan.
I concur that development cant be separated. My declaration that SOA
Lifecycle and SDLC (Software Development Lifecycle) are "completely"
seperate is specious and you are right to point that out.
The reason why I put it strongly is to raise the point that SDLC and
the lifecycle of a service are at different levels of granularity, and
that "Software" mostly is concerned with what's under the interface
and "Service is mostly concerned with what's up top.
I say "mostly" because of the fundamental inseperability of interface
from implementation which I lampoon in the "Pizza Shop Blueprint"
http://www.soacenter.com/?p=33
I really appreciate the distinction you're making, as I see people
making the mistake that SOA Lifecycle = Software Development
Lifecycle, and probably overcorrected by going in the opposite direction.
The truth, as in most cases falls in between, you are right to point
this out.
It gets interesting when you put policies into a lifecycle, but I'll
leave that for another conversation...
Miko
--- In [email protected], Stefan Tilkov
<[EMAIL PROTECTED]> wrote:
>
> I disagree with Miko's argument that the SOA life cycle begins after
> development. To me, identifying the need for a new service is the
> first step in the SOA LC. This then branches off into the software
> development life cycle, iterates a few times, and then possibly puts
> an updated version of the service interface into the repository.
>
> I agree that while the software development life cycle is primarily
> concerned with implementations, the SOA life cycle is concerned with
> interrfaces. Still, those two can't be totally separated and not
> necessarily created and finalized in any particular order.
>
> Stefan
> --
> Stefan Tilkov, http://www.innoq.com/blog/st/
>
__._,_.___![]()
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
__,_._,___
Reply via email to
