"We didn't start the fire ... it was always burning since the world's been turning ..." [Billy Joel 1989]. Is SOA the "Same Old Architecture?" or is it "Simply Over Ambitious?" Let's apply SOA's arsenal:: XML, BPM, Services, SOAP, Web Services - to the real world and find out. Let's put out some fires.

« De-mystifying SOA products selection | Main | The roles of Service Component Architecture (SCA) and Service Data Objects (SDOs) »

Modeling processes and services

Business architecture builds the foundation for accurately modeling IT assets. Regardless of the approach used in creating a solution, be it EA, SOA or BPM, defining accurate and complete business architecture is a must, in case of a top-down approach. Business architecture can be modeled using process modeling and business service modeling

The standards like BPEL are focusing on process modeling. Process usually defines an operation. Now a service can map 1<-> to a process or a service can be composed of more than 1 processes. On the other hand a process can be choreographed using multiple services. A service is more than an opearion, it also has an interface and implentation. Does UML meet the need to model a service? or is there a need to simplify UML and tailor it to Service modeling and call it SML (service modeling language) ?

TrackBack

TrackBack URL for this entry:
http://www.infosysblogs.com/soa-mt/mt-tb.fcgi/26

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)