Using Data Modeler

More documents

Recommendations

Info

Figure 18A RoleThis helps when trying to transform business requirements to modeled elements inthe data model, and communicates to the business analyst that the businessrequirements have been met.Relationship StructuresUsing identifying and non-identifying relationships you can create differentrelationship structures. One of these structures is an intersection table. The otherstructure is a self-referencing structure.Intersection TablesAlthough, an intersection table is by definition a table, the specific relationshipstructure it participates in is what really defines it. An intersection table is arelationship structure in which one child table is related to two parent tables with two1:n identifying relationships. When such a structure is created the child table containsprimary/foreign keys corresponding to the parent tables’ primary keys, therefore anyupdates made to the child table will affect both parent tables. This kind of relationshipstructure can be used for supertype/subtype structures.38 Chapter 4 - Physical Data Modeling
Figure 19An Intersection TableSelf-referencingAnother relationship structure is a self-referencing structure. A self-referencingstructure uses only one table, relating the table to itself with a non-identifyingrelationship. You use a self-referencing structure when you have an instance of a tablethat must be related with another instance of the same table. This kind of relationshipstructure can be used for recursive relationships.Building a New Data Model 39
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 and 24: Logical Data Modeling3ContentsThis
Page 25 and 26: view of an application. An object m
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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?