UML and database design Unified modeling language (UML) is a language for specification, visualization, construction and documentation of business models and other programming systems. UML is a combination of a great number of engineering approaches that used to be utilized for modeling of large and difficult systems. In the 70-80s there existed a variety of object-oriented languages that were highly tailored and were used for one-purpose tasks. The majority of users was at a loss and could not choose a language that would meet all their needs. This situation became an impetus for unification of various methods into more whole and universal modeling languages. In 1994 Grady Booch and Jim Rumbaugh from Rational Software Corporation started working on the unification of Boochs method and OMT (Object Modeling Technique).
In 1995 Ivar Jacobson and his company Objectory united with Rational. As a result the unified method was merged with OOSE (Object-Oriented Software Engineering) and in 1996 the UML was created. The UML ideally blends with the modern world conditions, it was created for distributed, parallel and linked environment. The UML is not bound to any platform or programming language and is perfectly suitable for connecting networks of various systems. Its main characteristic is flexibility that allows it to adapt to new possible issues. According to Naiburg and Maksimchuk, the Unified Modeling Language is also an effective modeling tool for database design.
The Essay on Language As A Method Of Manipulation
Language is more than a way of communication between people; language is a tool used for expressing, collaborating, and influencing. Language can make the audience not only learn, but feel. This is the beauty of language, it is more than a group of words. People often use language as a means of expression to convince people. Politicians, specifically, control the power of the language they speak ...
When used as a common modeling language for the many facets of system development, the UML can serve as a unifying framework that facilitates the integration of database models with the rest of a system design. Nearly all applications of the e-business use databases. One of the most difficult problems was coordination of programming languages and databases, because their different ways of declaration of data structure lead to imperceptible discrepancies and difficulties when transferring data between applications and databases. The use of the unified model UML, that is the basis for both a program code and database schemes, allows avoiding many of these problems. The Rational company has developed for UML a profile of database modeling that is supported in various versions of the application Rational Rose. This profile gives a possibility to construct a logical model of the information and a model of tables of the physical database, which is created on the basis of this data. Availability of two models allows the developer to tune and optimize the database structure that is very important while designing databases. As both models are connected, changes in one of them will be reflected in the other, which will let avoid discrepancies.
As Naiburg and Maksimchuk stated in their book UML for Database Design, the Unified Modeling Language has great benefits for database designers. First, it brings teams together, exposes elements directly on the model that normally get hidden behind modeled elements as tagged values, and describes the database design in great detail. Second, by leveraging work already done in both the requirements and the logical design phases, the database design team is able to get a quick start on building tables and columns and on understanding the requirements and business reasons for creating the database elements. Third, the constraints needed and ways the database would be used become quite evident because of the work done up front to uncover the needs of people using the database and to find out how the database would be used. Using the UML is quite valuable to all teams so far, since the database design is based on the logical design. The application developers can work on the application design at the same time based on the same artifacts. When the time comes, it will be more intuitive for the teams to build the object relational mappings and to create the queries of the database.
The Term Paper on Object-Oriented Analysis & Design UML Class Models
Developing Class Models • Class diagrams developed iteratively – Details added over time during lifecycle – Initially: missing names, multiplicities, other details Class Model Perspectives (cont’d) • Specification – Interfaces defined: a set of operations – But, each implementation class can include more than one interface – A given interface can be shared by more than one class – Sometimes known ...
These benefits improve the quality of database design and make the work of database designers much easier. References: 1. Bell, D. (2003) UML basics: An introduction to the Unified Modeling Language. IBM. Retrieved Apr.30, 2004, from http://www-106.ibm.com/developerworks/rational/lib rary/769.html 2. Naiburg, E.
J. and Maksimchuk, R. A.(2001) UML for Database Design. Addison Wesley Longman, Inc., Chapter 7. Retrieved Apr.30, 2004, from http://www-106.ibm.com/developerworks/rational/lib rary/content/03July/1000/1392/1392_naiburg7.pdf UML basics: An introduction to the Unified Modeling Language 3. Object Management Group, Inc. (2004) Introduction to OMG’sUnified Modeling Language (UML) Retrieved Apr. 30, 2004, from http://www.omg.org/gettingstarted/what_is_uml.htm.
