Using Data Modeler

More documents

Recommendations

Info

Contacting Rational Technical PublicationsTo send feedback about documentation for Rational products, please send e-mail toour technical publications department at techpubs@rational.com.Contacting Rational Technical SupportIf you have questions about installing, using, or maintaining this product, contactRational Technical Support as follows:Your Location Telephone Facsimile E-mailNorth America (800) 433-5444(toll free)(408) 863-4000Cupertino, CA(781) 676-2460Lexington, MAsupport@rational.comEurope, MiddleEast, Africa+31 (0) 20-4546-200Netherlands+31 (0) 20-4545-201Netherlandssupport@europe.rational.comAsia Pacific +61-2-9419-0111Australia+61-2-9419-0123Australiasupport@apac.rational.comNote: When you contact Rational Technical Support, please be prepared to supply thefollowing information:■■■■■Your name, telephone number, and company nameYour computer’s make and modelYour operating system and version numberProduct release number and serial numberYour case ID number (if you are following up on a previously-reported problem)xiiPreface
Introduction: Unifying theTeam1What truly makes a team is a group of people working together to accomplish acommon overall goal. Sometimes the team consists of only two people, other times itconsists of hundreds, but regardless of the number, the team must be unified in itsefforts. A development team is a specialized team in which the various members holddifferent responsibilities in the development life cycle. In solving business problems,there are three distinct roles in a development team—the business analyst, theapplication designer, and the database designer.Team RolesFor the scope of this book, the role of business analyst is performed bybusiness-process analysts, systems analysts, and those who capture and reviewrequirements for a business process. The role of application designer is performed byapplication developers, software engineers, and those who design and reviewapplication designs. The role of database designer is performed by data developers,database administrators (DBAs), data analysts, and those who design and reviewrelational databases.Business Analyst RoleIn the development process, the business analyst’s responsibility is to interview theend-user or client to understand the overall business problem, analyze the business asit currently is, identify the defects in the current processes that are causing the overallbusiness problem, and model the business as it could be. The business analystcaptures the end-users requirements and the process improvements in businessmodels. Business models divide the process into components of events, people orthings, and order the process using use-case, sequence, and activity models.Application Designer RoleThe responsibility of the application designer is to generate code and build anapplication based on the business analyst’s business models. The application designeruses object-oriented conceptual models and creates classes from the use cases,organizing the classes into an object model structure using class models. Then the1
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: PrefaceRational Rose ® , hereafter
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 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

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

Delete template?

Save as template?