SOA Shifts



SOA means a lot of things to a lot of people. And, now that the money is flowing to SOA, even more of us are interested. The reality is that SOA is much more than just a buzzword. It is an architectural style which tends to be best realized using Web Service and open standards. It's not the only way to implement SOA, but sure does seem to be the most popular lately.

We're finding that there are some key "shifts" that have to take place in an organization to be successful with SOA. Today, I'll talk about the first of these "SOA Shifts".

  • Shift #1 - SOA requires a combined effort between IT and the Business Unit
IT, BU - Peace be with you

The point of this shift is that we cannot do SOA without a mutual effort between IT and the BU. Gone are the days of throwing the requirements over the fence and hoping it hits. Not only do these two groups have to work together, they have distinct roles and responsibilities. Basically, the BU runs the show and owns the business drivers, use-cases and processes. IT implements the BU requirements and owns the service definitions.  It's unfortunate that we really do have to refer to this as a "shift", because we should be doing this anyway. But, the reality is that IT and BU typical function as disparate groups and rarely work together to have the business use-cases drive the process and service definition. More about this later, but if you get the gist of this shift, I think we can begin the journey to SOA....


Comments:

Hey John...caught your talk at TSSJS, but I haven't seen your slides at the wiki yet. I really found your talk interesting (I even blogged about it) but I can't remember everything you covered (especially the 8 rules). I'd be interested to get a copy. If you could e-mail them to me, that would be great!

Posted by Lou Sacco on mars 13, 2005 at 04:23 MD EST #

Hello John. Actually not a comment but a question. Did you mean that BU staff should be able to think in use-cases and processs terms? Do you think that BU understand UML? If IT prepared a use-case diagram sketches to show them to BU do you consider they should be capable to understand such diagrams?

Posted by Andrew Golikov on prill 11, 2005 at 02:56 PD EDT #

I think the key is not to have the BU staff thinking in use-cases, but to get to a common vocabulary and understanding of business requirements. SOA is driven by business, and should provide the agility to the business, so they can adapt to changes more easily. That is why the A of architecture is so important. since architecture can help to get a common vocabulary and understanding of business and business requirements.

Posted by Loek on gusht 02, 2005 at 12:16 PD EDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

crupi

Search

Categories
Archives
« prill 2014
DieHënMarMërEnjPreSht
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today