--- In [email protected], "Kirstan Vandersluis" <[EMAIL PROTECTED]> wrote: > > I would say that you cannot have a successful SOA without MDM, since > the vocabulary of the business should be managed as part of MDM (the > master data dictionary). The vocabulary is a critical point of > alignment of business with IT. It seems MDM is part of SOA. > > But companies have been trying to implement MDM (or at least major > pieces of MDM) for a long time (probably with similar level of success > that Anne Manes finds with SOA), and the MDM initiative is often > independent of SOA. MDM has benefits even if a company is not service > oriented. So now it seems MDM is NOT a part of SOA. > > In the end, all you can say is that MDM is a required activity if you > are service oriented. >
I tend of think of MDM as forming a common entity vocabulary between IT's rather than between business and IT. Having a common vocabulary used by IT does greatly ease discussions between IT and business in large system with many different applications, but in a small system with only few applications, I don't think it is should be a requirement. What's troubling me is how much business people think actually think how the master data is organized when doing business. In the grid or in Javaspace, doesn't users more think about the model in the space rather then the physical model used behind these technologies? H.Ozawa
