Using Data Modeler

More documents

Recommendations

Info

The next step is to assign attributes to these entities to identify them to the system.This is the same step you take when modeling in the class diagram; you assignattributes to the classes.The final step that both the logical data model and the class diagram share is to relatethese entities or classes to other entities or classes using associations.Figure 2A Class Diagram in RoseStandardized NotationAnother advantage is Rose uses the common notation of the UML. As was discussedin Chapter 2, UML and Data Modeling, the UML data modeling profile addedstereotypes to UML elements relating to data modeling terminology. These sameUML elements are used in the class diagram and with these stereotypes you canunderstand the mapping from the logical data model to the physical data model.Mapping CapabilitiesIn Rose data modeling terminology, a class diagram is also known as an object model.Object models serve two purposes. A class diagram or object model can act as alogical data model, but an object model can also act as a model to capture a conceptual12 Chapter 3 - Logical Data Modeling
view of an application. An object model is necessary if you want to map anapplication to a database. It is the object model mapping to the physical data modelthat is the basis for mapping the application to the database.Mapping an Object Model to a Data ModelRose allows you to take a step beyond identifying high-level entities, attributes, andassociations. It allows you to create a robust logical data model that can map moreprecisely to a physical database. Customizing the object model for your databasehelps to manage change, thereby decreasing the impact a change of requirements canhave on the existing model. If the object model maps to the data model, and changesor enhancements are made to the object model, the same changes or enhancementscan be applied to the data model. You can model your object model specifically tomap to a database by modeling your object model elements—with the exception ofcomponents and operations—to map to data model elements.Mapping ComponentsComponents represent the actual application language. In Rose terminology, acomponent represents a software module (source code, binary code, executable, orDDL) with a well-defined interface. According to the UML Data Modeling profile, acomponent maps to a database, but this mapping is only for reference purposes; inactual object model to data model transformation, components are ignored.Although Rose gives you the option of several component languages to assign to yourlogical package, the Data Modeler add-in is compatible with only three of thosecomponent languages—Java, Visual Basic, and Analysis. The classes that you want tomap to tables in the data model must use one of these three component languages tobe transformed to a data model. If you want to use a component language notcompatible with Data Modeler, it is recommended you create a separate object modelusing your desired component language, and map that model to an Analysis objectmodel that is used for transformation purposes.Mapping OperationsAccording to the UML Data Modeling profile, operations map to various constraints;however, just like components, operations are ignored in the transformation process.Operations are the behavior of a class, and can be useful to database designersbecause they can be used as a basis for identifying index items, possible triggers, andother constraints.Mapping an Object Model to a Data Model 13
Page 1 and 2: Rational the e-development companyU
Page 3 and 4: ContentsPreface....................
Page 5 and 6: MappingDomainstoAttributeTypes.....
Page 7: FiguresFigure1 ADataModelDiagraminR
Page 11 and 12: PrefaceRational Rose ® , hereafter
Page 13 and 14: Introduction: Unifying theTeam1What
Page 15: The Data Modeler SolutionRose unifi
Page 18 and 19: The UML data modeling profile allow
Page 20 and 21: Figure 1A Data Model Diagram in Ros
Page 23: Logical Data Modeling3ContentsThis
Page 27 and 28: Figure 4Attributes Map to ColumnsRo
Page 29 and 30: Figure 6Domain ColumnsData TypeData
Page 31 and 32: Figure 8Associations Map to Non-Ide
Page 33 and 34: Figure 10Association Classes Map to
Page 35 and 36: When Data Modeler transforms an inh
Page 37 and 38: Transform Object Model to Data Mode
Page 39: The entire processing time of the t
Page 42 and 43: Building a New Data ModelYou can bu
Page 44 and 45: Figure 15A TableCreate ColumnsA col
Page 46 and 47: Foreign Key ConstraintForeign key c
Page 48 and 49: in the parent table, because such a
Page 50 and 51: Figure 18A RoleThis helps when tryi
Page 52 and 53: Figure 20A Self-Referencing Relatio
Page 54 and 55: Trigger GranularityTrigger granular
Page 56 and 57: language. You can select DB2GNRL fo
Page 59 and 60: Mapping the PhysicalData Model5Cont
Page 61 and 62: Figure 22Tables Map to ClassesMappi
Page 63 and 64: Figure 25Identifying Relationships
Page 65 and 66: Figure 27Intersection Tables Map to
Page 67 and 68: Figure 29Intersection Tables Map to
Page 69 and 70: Figure 30Transform Data Model to Ob
Page 71 and 72: Implementing thePhysical Data Model
Page 73 and 74: stored procedures and triggers do n
Page 75 and 76:
Synchronization WizardThe synchroni
Page 77:
AppendixAUML Data Modeling ProfileT
Page 80 and 81:
Table 3 Analysis Object to Data Mod
Page 82 and 83:
Table 5 Visual Basic Object to Data
Page 84 and 85:
Table 6SQL 92 Data Model to Object
Page 86 and 87:
Table 8Oracle Data to Object Model
Page 88 and 89:
SQL 7.0 only Data to Object Attribu
Page 91 and 92:
AppendixDDatabase ConnectionsThis a
Page 93:
SybaseYou can use NT authentication
Page 96 and 97:
described 63componentsdescribed 13t
Page 98 and 99:
Llogical data modeling 11logical da
Page 100:
synchronizingdata models 62synchron
show all

Using Data Modeler

Create successful ePaper yourself

Delete template?

Save as template?