Uml for Database Design

by Naiburg, Eric; Maksimchuk, Robert

• ISBN13: 9780201721638
• ISBN10: 0201721635
• Edition: 1st
• Format: Paperback
• Copyright: 2001-07-24
• Publisher: Addison-Wesley Professional

Summary

For database professionals, this book provides a practical guide to the use of the Unified Modeling Language (UML) for database design. It is intended for those who have to make things happen in the real world; those who have to deliver real systems to meet real business needs. In short, this book is designed for those pragmatic, working database designers who need to get things done.

UML for Database Design addresses the questions most frequently asked of us by database professionals from all over the globe:

• How can I use UML for database design in the real world?
• How can I fit the UML into my current process?
• How should the database design team adopt this approach?
• How can database and application teams work together using the UML?

The Approach

We have endeavored to ensure that this book didn't get lost in theory, buried in formalism, or trivialized by unrealistic, contrived examples. Thus, at times we may run contrary to the purists. That's OK. The approach we take is to introduce the use of UML for database design in a stepwise fashion, for each phase of the system development life cycle. We move from business modeling at the beginning of the life cycle to database design at the end. We show how the UML applies to the process and the value it provides to the database designer in each phase. A robust, realistic case study (described in Chapter 2) helps demonstrate how to use the UML and how to handle challenges that you may encounter during your real-world projects.

Chapter Summaries

Chapter 1--Introduction. This chapter indicates who should read this book and why. It describes the basic structure of subsequent chapters and the overall flow of the book.

Chapter 2--Database Design from Requirements to Implementation.This chapter discusses database modeling versus database design, addresses data modeling as it exists today, describes how using the UML differs from traditional techniques, and introduces the case study used throughout the remainder of the book.

Chapter 3--Business Modeling for Database Design. This chapter introduces business modeling and how it, and the UML, can be used for database design. Here is where the conceptual model is established.

Chapter 4--Requirements Definition.This chapter shows how all the artifacts provided by the previous business modeling are used to establish the system requirements.

Chapter 5--Analysis and Preliminary Design.This chapter moves from the realm of business requirements into the logical design of the system and its database.

Chapter 6--Preparing for Transformation to the Database Design Model. This chapter transitions from the logical analysis model to the database design model. This chapter also addresses the issues that arise during the mapping of object models to data models.

Chapter 7--Database Design Models--the UML Profile for Database Design.This chapter introduces the UML Profile for Database Design developed by Rational Software Corporation.

Chapter 8--Implementing the Physical Aspects of the Database.This chapter focuses on the physical component of database design.

Chapter 9--Summary of Using the UML for Database Design.This chapter performs a "postmortem" on how the UML was used in the case study project.

Appendix A--UML Models for EAB Healthcare, Inc.This appendix contains the UML models from the case study project.

Appendix B--Use Case Descriptions.This appendix contains the use case descriptions from the case study project.

Contacts

We would appreciate your feedback on this book. If you have questions or comments, please feel free to contact us by email at [e-mail], or visit our website http://www.UMLforDatabaseDesign.com.

0201721635P06272001

Author Biography

Eric J. Naiburg is a product manager for Rational Software Corporation, focusing on the Rational Rose product line. His professional focus is on extending the ability of Rational Rose to support database design and object-relational mapping within the Rose visual modeling tool and the UML. He delivers numerous popular seminars on the topic.

Robert A. Maksimchuk is the Data Modeling Evangelist for Rational. He is a frequent speaker at Rational events, various database conferences, and user groups worldwide, and has more than twenty-four years of experience in the software development field.

0201721635AB06272001

Table of Contents

Foreword	xiii
Preface	xv
The Approach	xv
Chapter Summaries	xvi
Acknowledgments	xvii
Contacts	xvii
Introduction	1	(6)
Why Read This Book?	1	(2)
Systems Development Is a Team Sport	1	(1)
The Unified Modeling Language	2	(1)
Who Should Read This Book?	3	(1)
How to Read This Book	3	(4)
Chapter Organization	3	(1)
Database Designer Callout Boxes	4	(1)
Process Flow Overview	5	(1)
Appendixes	5	(2)
Database Design from Requirements to Implementation	7	(10)
Database Modeling versus Database Design	7	(1)
Database Modeling	7	(1)
Database Design	8	(1)
Data Modeling Today	8	(2)
Best-of-Breed Solutions versus Full Life-Cycle Solutions	9	(1)
A Happy Medium	10	(1)
UML Diagrams for Database Design	10	(2)
Why Use the Various UML Diagrams?	11	(1)
The UML Differs from Traditional Database Modeling	12	(2)
The Case Study	14	(3)
The Vision	14	(1)
A Typical Scenario	15	(1)
The Project Goals	15	(1)
Our Focus	16	(1)
Business Modeling for Database Design	17	(36)
The Workflow	17	(7)
Business Modeling	18	(5)
The Business Today	23	(1)
Current Systems	23	(1)
Today's Systems at Work	23	(1)
The Case Study Status	24	(1)
The Concepts	24	(1)
The Approach	25	(3)
Involving the Database Team	25	(2)
Eliciting the Business Needs	27	(1)
The Design	28	(22)
The Business Use Case Model	28	(6)
The Business Object Model	34	(16)
Summary	50	(3)
Requirements Definition	53	(22)
The Workflow	53	(3)
The Use Case Model	54	(2)
The Case Study Status	56	(1)
The Concepts	56	(1)
The Approach	57	(3)
Involving the Database Team	57	(3)
The Design	60	(13)
Moving from the Business Model to the System Model	60	(9)
Inside the System Use Cases	69	(4)
Summary	73	(2)
Analysis and Preliminary Design	75	(30)
The Workflow	75	(3)
The Class Diagram	76	(2)
Supporting Diagrams and Activities	78	(1)
The Case Study Status	78	(1)
The Concepts	78	(1)
The Approach	78	(2)
Involving the Database Team	79	(1)
The Design	80	(24)
You Want to Do What?	80	(4)
Now Back to Our Program	84	(4)
The Establish MDS System Use Case	88	(5)
The Maintain MDS System Use Case	93	(7)
The Transmit MDS System Use Case	100	(4)
Bringing It Together	104	(1)
Summary	104	(1)
Preparing for Transformation to the Database Design Model	105	(14)
The Workflow	105	(5)
Mapping Models	106	(1)
Mapping Classes to Tables	106	(2)
Mapping Attributes to Columns	108	(2)
The Case Study Status	110	(1)
The Concepts	110	(1)
The Approach	111	(2)
The Design	113	(4)
Making Entities Persistent	113	(1)
Transformation of Attributes	114	(3)
Summary	117	(2)
Database Design Models---the UML Profile for Database Design	119	(30)
The Workflow	119	(5)
Working as a Team	120	(1)
UML Packages	121	(1)
UML Diagrams	122	(1)
Database Design	123	(1)
The Case Study Status	124	(1)
The Concepts	124	(9)
The UML Profile for Database Design	124	(1)
Diagram Elements	125	(6)
Table and Column Elements	131	(2)
The Approach	133	(1)
The Design	134	(13)
Creating Tables from Classes	135	(1)
Background Information	135	(1)
Basic Assessment Tracking	136	(1)
Full Assessment Data	136	(5)
Database Views	141	(6)
Summary	147	(2)
Implementing the Physical Aspects of the Database	149	(26)
The Workflow	149	(4)
Using Previously Created Modeling Artifacts	150	(2)
Putting It All Together	152	(1)
The Case Study Status	153	(1)
The Concepts	154	(3)
The UML Profile for Database Design	155	(2)
The Approach	157	(2)
Partitioning the Database Tables	158	(1)
Modeling the Schema	158	(1)
Modeling the Database	158	(1)
The Design	159	(13)
Creating Tablespaces	160	(10)
Determining Schemas and Databases	170	(2)
Designing the Hardware Needed	172	(1)
Summary	172	(3)
Summary of Using the UML for Database Design	175	(10)
The Workflow	175	(3)
Jump-Starting the Database Design Process	176	(2)
The Case Study Status	178	(1)
The Approach	178	(1)
The Design	179	(4)
The Positives	180	(1)
The Negatives	181	(2)
Summary	183	(2)
Appendix A UML Models for EAB Healthcare, Inc.	185	(80)
Organization of This Appendix	185	(4)
The Models and Diagrams	189	(76)
The Business Use Case Models	189	(9)
The Business Object Models	198	(35)
The Traditional Conceptual Data Models	233	(3)
The System Use Case Models	236	(6)
The Design Models	242	(15)
The Database Design Models	257	(8)
Appendix B Use Case Descriptions	265	(16)
Glossary	281	(6)
Bibliography	287	(2)
Index	289

Excerpts

For database professionals, this book provides a practical guide to the use of the Unified Modeling Language (UML) for database design. It is intended for those who have to make things happen in the real world; those who have to deliver real systems to meet real business needs. In short, this book is designed for those pragmatic, working database designers who need to get things done. UML for Database Designaddresses the questions most frequently asked of us by database professionals from all over the globe: How can I use UML for database design in the real world? How can I fit the UML into my current process? How should the database design team adopt this approach? How can database and application teams work together using the UML? The Approach We have endeavored to ensure that this book didn''t get lost in theory, buried in formalism, or trivialized by unrealistic, contrived examples. Thus, at times we may run contrary to the purists. That''s OK. The approach we take is to introduce the use of UML for database design in a stepwise fashion, for each phase of the system development life cycle. We move from business modeling at the beginning of the life cycle to database design at the end. We show how the UML applies to the process and the value it provides to the database designer in each phase. A robust, realistic case study (described in Chapter 2) helps demonstrate how to use the UML and how to handle challenges that you may encounter during your real-world projects. Chapter Summaries Chapter 1--Introduction.This chapter indicates who should read this book and why. It describes the basic structure of subsequent chapters and the overall flow of the book. Chapter 2--Database Design from Requirements to Implementation.This chapter discusses database modeling versus database design, addresses data modeling as it exists today, describes how using the UML differs from traditional techniques, and introduces the case study used throughout the remainder of the book. Chapter 3--Business Modeling for Database Design.This chapter introduces business modeling and how it, and the UML, can be used for database design. Here is where the conceptual model is established. Chapter 4--Requirements Definition.This chapter shows how all the artifacts provided by the previous business modeling are used to establish the system requirements. Chapter 5--Analysis and Preliminary Design.This chapter moves from the realm of business requirements into the logical design of the system and its database. Chapter 6--Preparing for Transformation to the Database Design Model.This chapter transitions from the logical analysis model to the database design model. This chapter also addresses the issues that arise during the mapping of object models to data models. Chapter 7--Database Design Models--the UML Profile for Database Design.This chapter introduces the UML Profile for Database Design developed by Rational Software Corporation. Chapter 8--Implementing the Physical Aspects of the Database.This chapter focuses on the physical component of database design. Chapter 9--Summary of Using the UML for Database Design.This chapter performs a "postmortem" on how the UML was used in the case study project. Appendix A--UML Models for EAB Healthcare, Inc.This appendix contains the UML models from the case study project. Appendix B--Use Case Descriptions.This appendix contains the use case descriptions from the case study project. Contacts We would appreciate your feedback on this book. If you have questions or comments, please feel free to contact us by email [e-mail],or visit our websitehttp://www.UMLforDatabaseDesign.com. 0201721635P06272001