--- In [email protected], "Steve Jones" <[EMAIL PROTECTED]> wrote: > > My jury just returned. > > Using "business data" as the primary modelling view is fraught with > problems, not least the view of what the model is. What is customer? > What does it mean to whom? Does everyone need to know everything? > > I'll take a business service view from a functional/organisation/data > combined perspective and then worry about the "single" data views > later as a post transactional reporting element. >
I agree, with a service oriented approach, you lead with the functional/organizational views at the top. But I believe the business data needs to be rationalized into the SOA as well, and entity services is a good way to do that. Data chaos is still a huge problem in many enterprises, and addressing the functional at the high level pushes the problem down, but doesn't solve it in my opinion. The data problems will be solved only with deliberate design and engineering, and the SO approach to solving them involves entity services. Steve, what is your opinion of Colin K's policy refund example? How would you partition services in that example? I think entity services are an important part of an SO approach here, and its not just post-transactional data. -Kirstan
