Автор работы: Пользователь скрыл имя, 29 Декабря 2011 в 05:34, контрольная работа
UML has become increasingly popular in the last few years. UML is without doubt a very useful object-oriented application component design and development environment, and the growing object-oriented developer community has taken to it with justifiable enthusiasm.
It is not only project managers and database administrators who are guilty of breaking the link between data modeling and database implementation. On too many occasions we have seen data modelers deliver models that are incomplete or unworkable. Often this can be traced to a lack of understanding of database structures and a limited view of data modeling as “describing the real world,” without adequate recognition that the description has to serve as a database specification. Such modelers may be only too pleased to have someone else take responsibility for the result.
Ernest Hemingway once suggested that screenwriters would do well to throw their manuscripts across the California state line and “get the hell out of there.” This may or may not be good advice for screenwriters, but data modelers have a responsibility to see that their models are both implementable and implemented. As such, the project plan must allow for data modeler involvement in performance design and tuning of the physical data
model.