Alleluia ! Business services assume technical integration on as-needed basis but inside the service. Services are supposed not to integrate but collaborate contributing their individual business functionality and RWE into common 'basket' - business task (I am not arguing that collaboration is a form of integration).
With regard to Ashley's example, it is the business service which has to define the scope and boundaries of the technical integration and, in general, domain design. This is why Domain Service-Oriented Modelling (DOSOM) and design in the way to go in implementation from the business SO model into technical model and actual realisation, I believe. -- Michael ________________________________ From: Ashley at Metamaxim <[email protected]> To: [email protected] Sent: Thursday, January 8, 2009 11:34:04 AM Subject: Re: [service-orientated-architecture] SOA is Dead Steve Jones wrote: > Well my trite answer is "b(u)y my book". My longer one is that for me > these have _always_ been what I've seen as the services and the job of > IT is to deliver as appropriate to that service. So there will be a > requirement for a Booking service for the accommodation, this can be > provided by IT. There needs to be an archival and search service in > Pathology and again IT can deliver that service. Good! It is, though, interesting to note that if you take the view that IT should be aligned to these "business services" it may work against "integration" . For instance, a number of these "business services" will need, in their IT systems, a model of "patient" with information relevant to the provision of their service. If the IT is to be aligned to the services (as it needs to be if disaggregation of service provision is the aim) then the patient model has to be distributed accordingly. Rgds Ashley
