I agree with your view expressed earlier --start SOA is the architecture at the level of service modeling. The implementation of Services maybe using OO that needs another architecture at different level of abstraction. In other words, we need different architectures at different levels of abstraction.
So we need a BMP architecture as much as we need a architecture at service level abstraction. Architectures at different levels of abstractionare ontologicially and sementically distinct and are not overlapping in representation of reality. --end Your this view slightly contradicts the scope of SOA as mentioned in this message. If BMP architecture decides to meet IT architecture (based on SOA) I will definitely qualify that as one way of doing Enterprise Architecture (EA). Certainly not SOA. I agree with Steve when he says ---start Which to me is the dust, because we've been there, done that and failed a whole load of times. CICS was the same, MVS (IIRC) was the same, CORBA was the same, EAI was the same, DCOM was the same and now we have WS. For SOA to actually matter it must change the way people think, and neither BPM nor SOA 4 IT is capable of achieving that. ----end But if we want to achieve what he and we all want, that enterprise must have seamless integration between BP and IT infrastructure we need to change our approach, towards enterprise as a whole and organize all the activities and process within an organization within a common framework, which according to some is SOA, but I think that is EA. regards, Shashank D. Jha On 5/10/07, Jerry Zhu <[EMAIL PROTECTED]> wrote:
I correct what I said below as ... reusable by BP.(not IT) It is interesting to diferentiate IT capability from business capability. Business capabilities are the driving factor and requirements of IT capabilities. So when we say SOA, we mean both SOA business and IT capabilities. In SOA, services are defined as IT assets that encapsulate business capabilities (of certain business granularity) accessbile over network and can be assembled and reassembled to form business processes (larger business granularity than service). SOA is IT strategy that make services standard based, interoperable and reusable. This IT strategy is made possible only when we model business processes in SOA way. So SOA is also a business strategy in business process modelings. So I agree what you say below. Jerry --- "Shashank D. Jha" <[EMAIL PROTECTED] <shashank.dj%40gmail.com>> wrote: > Can I say that SOA is IT capability which will be/is > used by BP? > > regards, > Shashank D. Jha > > So SOA is not just dust but business capabilities > > enabled by IT and made accessible and reusable by > IT. > > > > Jerry > > > > --- Steve Jones <[EMAIL PROTECTED] <jones.steveg%40gmail.com> > <jones.steveg%40gmail.com>> wrote: > > > > > I have to disagree here Jerry, Business Process > is > > > a long way away from being the only way that > value > > is _generated_ within a business. When people > > > interact with businesses they tend to interact > at > > > specific points, these tend to be marked, and > indeed > > referred to as the "market facing services" of > > > the organisation. > > > > > > Viewing SOA as just about the dust at the edges > > > misses the real point of SOA > > > which is that by using services to model > _business_ > > > you can understand what > > > different approaches are required in different > area. > > > BPM and SOA, if driven > > > from a technical perspective, will fail to > deliver > > > any real benefits to > > > organisations. Technology is a secondary > concern, > > > the main goal is changing > > > the way people think about IT. If SOA just aims > to > > > be the dust while BPM is > > > the business then it will be just as successful > as > > > BPM was _before_ SOA and > > > as EAI was in controlling that dust. > > > > > > > > > > > http://service-architecture.blogspot.com/2007/05/soa-isnt-about-technology.html > > > I tried to sum up what I mean in two pictures. > > > > > > Steve > > > > > > > > > On 07/05/07, Jerry Zhu <[EMAIL PROTECTED] <jerryyz%40yahoo.com> > <jerryyz%40yahoo.com>> wrote: > > > > > > > > I see some conceptual confusion here. Business > > > > process outcomes in the form of > produce/service > > > > delivered is not the same as SOA services. Now > > > here > > > > product/service refers to customer value > created > > > and > > > > delivered. This value has nothing to do with > > > > procedures or activties but is measured by the > > > > external customer that varies from customer to > > > > customer. Customer (external) value is > created, by > > > > definition, only by business processes not by > > > smaller > > > > granualities such as subprocesses, procedures > or > > > > activities. > > > > > > > > These smaller units can be captulated into SOA > > > > services to be assembled and reassembled to > form > > > new > > > > business processes. Therefore in this context, > SOA > > > > service is a function not a intangible value. > > > > > > > > I think this distinction is not only > politically > > > > correct but also convenient both in business > and > > > > technical sense. > > > > > > > > Jerry > > > > > > > > > > > > --- "Shashank D. Jha" <[EMAIL PROTECTED]<shashank.dj%40gmail.com> > <shashank.dj%40gmail.com> > > > <shashank.dj%40gmail.com>> > > > > wrote: > > > > > > > > > Thanks for a insightful article. > > > > > > > > > > But still it fails to convince me that --- > > > > > Quoting from your article..start > > > > > Thus, SOA may be viewed as a technical > > > architecture > > > > > built around an > > > > > enterprise business model, not around > isolated > > > > > business procedures or > > > > > just-this-moment operational needs. SOA is > > > supposed > > > > > to address current and > > > > > upcoming business requirements, diversity, > which > > > is > > > > > limited by a particular > > > > > business model. If the business model is > unclear > > > in > > > > > the organization, > > > > > Services and Processes, SOA won't help but > > > rather > > > > > will confuse the company a > > > > > lot.--end > > > > > > > > > > It makes a great statements but fails to > > > emphasize > > > > > the need to business > > > > > people or Analysts to adopt SOA to model or > > > develop > > > > > business processes. > > > > > > > > > > All the examples and contents attempts to > prove > > > that > > > > > SOA is IT initiative > > > > > and IT solution to allow business agility. > > > > > > > > > > Overall this article again demonstrate that > SOA > > > is > > > > > to make IT systems to > > > > > adapt o business requirements. > > > > > > > > > > As iterated by me earlier sometimes back in > the > > > same > > > > > forum that SOA-RM by > > > > > OASIS is too Raw and Abstract and to be > useful > > > to an > > > > > BA. > > > > > > > > > > I still of my view that SOA is about making > > > > > flexible, easy to change, > > > > > manage, controlling granularity of software > > > service > > > > > etc. based on input from > > > > > business initiative/ process. > > > > > > > > > > Business needs business process modeling and > > > changes > > > > > in the same must be > > > > > able to execute over underlying > infrastructure > > > with > > > > > as much ease as possible > > > > > and this is where SOA comes into picture. > > > > > > > > > > regards, > > > > > Shashank D. Jha > > > > > > > > > > On 5/6/07, Michael Poulin > <[EMAIL PROTECTED] <m3poulin%40yahoo.com> <m3poulin%40yahoo.com> > > > <m3poulin%40yahoo.com>> > > > > > wrote: > > > > > > > > > > > > Shashank, > > > > > > I have tried to put Steve's words in a > form of > > > > > article, actually, related > > > > > > to the SOA RM standard. I think, it will > help > > > you > > > > > to decouple your > > > > > > understanding from the exclusive IT > > > perspectives. > > > > > > (http://java.sys-con.com/read/314124.htm) > > > > > > > > > > > > - Michael > > > > > > > > > > > > > > > > > > *Steve Jones <[EMAIL PROTECTED]<jones.steveg%40gmail.com> > <jones.steveg%40gmail.com> > > > <jones.steveg%40gmail.com>>* > > > > wrote: > > > > > > > > > > > > On 05/05/07, Shashank D. Jha > === message truncated ===
