On 11/6/06, Michael Poulin <[EMAIL PROTECTED]> wrote:
> Shashank,
> I have not got what you have meant in:
> "But their is a diagram for how SOA RM relates to
> other work?? Wherein in SOA implementation (not spec nor RM) seems to
> be the biggest block.
> Service oriented Architecture implementation is the biggest block??
> Reference model just guides or just a small part of Architecture work??"
I meant, as mentioned in other mail, that in the paper published as RM
for SOA bby OASIS, there is no architecture diagram for SOA? There is
only one diagram that shows "Relation of SOA with others.."!!!
> However, I do agree with you in "How can you define the artifacts of the
> systems without having identified artifacts and their relations with each
> other?" This is why I tried to define the artifacts of the business system
> via Business Services and Business Processes ( that I posted in a discussion
> of this group several days ago).
>
My point was around RM for soa by OASIS. They have not researched much
or made relation explicit between soa and bp, bs etc.
> Having such definitions, my next step is to orient development of services
> in IT to these two types of artifacts rather than toward just-that-moment
> "business requirements" related to a fraction of "business" operations, ie.
> implementation of the Business Services and Business Processes. The
> operations are secondary to the business and may be changed without impact
> on the real business function in the enterprise business model. In other
> words, I see purpose of SOA in addressing core business functions (yes, a
> lot of supporting services are also needed), and SOA RM gives me enough
> "room for maneure" for my task.
>
This may be correct. But I was looking more from the ideas being
standardized. The closest to the thoughts discussed here, I found in
the RM by CBDI forum. They have made Zachman kind of framework with
columns (who, when, where why etc.) and then rows concept, logical and
physical. This RM is closest to what I have learned from discussion
here.
Still we need better architecture diagram to make more explicit
relation. but at least the ideas around soa i find more closer to what
we are discussing here.
regards,
shashank
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
