Hi again, I'm sorry for this note too, Michael, but large projects usually create dictionaries to limit what words can be used in the specifications, screens, and database. Otherwise, developers tend to use differents words and makes the documents more difficult to read and systems to interoperate. Large companies often have set of these dictionaries. Also, most projects don't model interfaces parameters nor messages using UML. The cost to model using UML on all the relationships between parameters of all interfaces to achieve flexibility is just too high.
I'm been adding words to my dictionaries and been using them and have to say they work. I'm always open to new ideas and I think most people are also interested in knowing about what actually works. Cheers, H.Ozawa 2009/12/16 Michael Poulin [email protected] > > 4) “Domain specific semantic dictionary” vs. UML. It is well-known (sorry > for this note) that the Domain specific semantic is limited in the scope by > the Domain. You cross the domain – your information looses sense. Since you > so confident in Domain specific over the UML, I start thinking about > cultural specifics of countries where people frequently change the domain > and where they stay with the domain for long time. Am I right? > >
