Using Data Modeler

UML and Data Modeling2ContentsThis chapter is organized as follows:■UML Introduction on page 5■Why UML for Data Modeling? on page 5■Advantages of Rose UML and Data Modeling on page 7UML IntroductionTeams need one tool, one methodology, and one notation. Since its inception, theUnified Modeling Language (UML) has been unifying members of a developmentteam for faster and higher quality applications. But UML allowed only businessanalysts and application designers to communicate with each other, databasedesigners were excluded because they used a different kind of notation. Rose adds aUML profile to accommodate entity/relationship (E/R) notation with the addition ofData Modeler, allowing the database designer to communicate with the businessanalyst and application designer, making the UML a truly unifying language.Why UML for Data Modeling?The UML offers a standard notation very similar to Peter Chen’s E/R notation. LikeChen’s E/R the UML is based on building structures using entities that relate to oneanother. By adding the data modeling profile, UML’s ability to model an entire systemis increased, allowing you to model not only logical models, but physical data modelstoo, mapping your applications and your databases.Data Modeling Profile Added to UMLA UML profile is an Object Management Group (OMG) approved method of addingto UML for a specific subject, without altering the UML metamodel. UML profilesadded to UML use customized stereotypes and tagged values based on their subject’sconcepts and terminology.5