OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-ra message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: todos for PR2


"positioning SOA on the cusp between IT and business" is what I write a lot for last few months. So, let me propose a strawman for this text:


1.4.4 Business Value of the Service Oriented Architecture

A Service Oriented Architecture realizes principles of the concept of service orientation in the sphere of architecture. The architecture in the organisation comprises both business architecture and technical architecture of the systems [ref. to TOGAF 9.0]. While SOA-based systems address aspects of the technical architecture, the similarity of the principles of the Value Networks business model and SOA allows us to see SOA as a conceptual bridge between corporate Business and IT.

Noticed similarity opens up new possibilities for Business and IT to construct service-oriented customer-centric convergent solutions for business problems. Service orientation enables operational and technical flexibility, which contributes to business efficiency the great deal. The Service Orientation concept has the potential not only to align IT with Business, but also to align the entire company with the market dynamics.


If the ideas in this writing are acceptable, I will work on the wording.

- Michael Poulin

--------------------------------------------------------------------------------

From: Francis McCabe <fmccabe@gmail.com> 
To: "soa-rm-ra@lists.oasis-open.org RA" <soa-rm-ra@lists.oasis-open.org> 
Date: Thu, 3 Sep 2009 19:24:08 -0700 

--------------------------------------------------------------------------------

1. As Boris alluded to, I think that a paragraph or two in the  
introduction positioning SOA on the cusp between IT and business could  
be very useful. It is also pretty faithful to the RAF!

2. The concept of interaction in the RM referred *everything* involved  
in interacting with services. For the RA we have to unpack that some.  
This is the foundation for the multi-leveled concept of joint action.  
This should go in Section 3.1.

3. I think that Danny's security diagram should be updated and  
incorporated.

4. The trust and willingness stuff should go in.

5. It would be good if we could go through the text bolding defined  
concepts.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]