Used and New from Other Sellers
Used and New from Other Sellers
from $2.04
Usually ships in 1-2 business days
(Save 95%)
Other sellers (Paperback)
-
All (9)
from
$2.04
-
New (5)
from
$28.0
-
Used (4)
from
$2.04
Note: Marketplace items are not eligible for any BN.com coupons and promotions
$28.00
Seller since Tue Jan 01 01:01:01 EST 2008
0201721635 BRAND NEW NEVER USED IN STOCK 125,000+ HAPPY CUSTOMERS SHIP EVERY DAY WITH FREE TRACKING NUMBER
Ships from: fallbrook, CA
Usually ships in 1-2 business days
- •Standard, 48 States
- •Standard (AK, HI)
$35.41
Seller since Tue Jan 01 01:01:01 EST 2008
Brand New, Perfect Condition, Please allow 4-14 business days for delivery. 100% Money Back Guarantee, Over 1,000,000 customers served.
Ships from: Westminster, MD
Usually ships in 1-2 business days
- •Canadian
- •International
- •Standard, 48 States
- •Standard (AK, HI)
$35.42
Seller since Mon Jan 01 01:01:01 EST 2007
BRAND NEW
Ships from: Avenel, NJ
Usually ships in 1-2 business days
- •Canadian
- •International
- •Standard, 48 States
- •Standard (AK, HI)
$61.76
Seller since Tue Aug 05 04:42:11 EDT 2014
New
Ships from: Idyllwild, CA
Usually ships in 1-2 business days
- •Canadian
- •International
- •Standard, 48 States
- •Standard (AK, HI)
- •Express, 48 States
- •Express (AK, HI)
$63.00
Seller since Fri Jan 01 01:01:01 EST 2010
7-24-01 other 1 BRAND NEW! ONLY Expedited orders are shipped with tracking number! *WE DO NOT SHIP TO PO BOX* Please allow up to 14 days delivery for order with standard
...
shipping. SHIPPED FROM MULTIPLE LOCATIONS.
Read more
Show Less
Ships from: San Jose, CA
Usually ships in 1-2 business days
- •Canadian
- •Standard, 48 States
- •Standard (AK, HI)
- •Express, 48 States
- •Express (AK, HI)
More About This Textbook
Overview
The Unified Modeling Language (UML), the standard graphical notation for modeling business and software application needs, has emerged as an effective modeling tool for database design. When used as a common modeling language for the many facets of system development, the UML can serve as a unifying framework that facilitates the integration of database models with the rest of a system design.
This pragmatic guide introduces you to the UML and leads you through the process of UML-based database modeling and design. The book presents the different types of UML diagrams, explaining how they apply to the database world, and shows how data modeling with the UML can be tied into the Rational Unified Process.
UML for Database Design is structured around the database design process: business use case modeling, business object modeling, database requirements definition, analysis and preliminary design, and, finally, detailed design and deployment. For each phase of development the book describes the overall objectives and workflow of that phase, the status of the case study, the relevant UML constructs, and the nuts and bolts of database modeling and design with the UML. Drawing on their extensive industry experience, the authors reveal the trials and tribulations of database development teams, lessons learned, and pointers for success.
Topics covered include:
A case study runs throughout the book to illustrate key concepts and techniques, and appendixes containing the actual UML models from this case study are used to catalog the type and extent of models that would be developed for such a system.
Practical, concrete, and based on real-life experience, UML for Database Design brings you exactly the information you need to begin working with the UML and take full advantage of the technology for high-quality database modeling and design.
0201721635B06292001
Product Details
Related Subjects
Meet the Author
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
Read an Excerpt
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 ApproachWe 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 gurus@UMLforDatabaseDesign.com, or visit our website http://www.UMLforDatabaseDesign.com.
Table of Contents
Foreword.
Preface.
The Approach.
Chapter Summaries.
Acknowledgments.
1. Introduction.
Why Read This Book?
Who Should Read This Book?
How To Read This Book?
2. Database Design From Requirements to Implementation.
Database Modeling vs. Database Design.
Data Modeling Today.
UML Diagrams for Database Design.
UML Differs From Traditional Database Modeling.
The Case Study.
3. Business Modeling for Database Design.
The Workflow.
The Case Study Status.
The Concepts.
The Approach.
The Design.
4. Requirements Definition.
The Workflow.
The Case Study Status.
The Concepts.
The Approach.
The Design.
5. Analysis and Preliminary Design.
The Workflow.
The Case Study Status.
The Concepts.
The Approach.
The Design.
6. Preparing For Transformation to the Database Design Model.
The Workflow.
The Case Study Status.
The Concepts.
The Approach.
The Design.
7. Database Design Models-UML Profile for Database Design.
The Workflow.
The Case Study Status.
The Concepts.
The Approach.
The Design.
8. Implementing the Physical Aspects of the Database.
The Workflow.
The Case Study Status.
The Concepts.
The Approach.
The Design.
9. Summary of Using the UML for Database Design.
The Workflow.
The Case Study Status.
The Approach.
The Design.
Glossary.
Appendix A: The Models.
Organization.
The Business Use Case Models.
The Business Object Models.
The Traditional Conceptual Data Models.
The System Use Case Models.
The Design Models.
The Database Design Models.
Appendix B: The Use Case Descriptions.
Index.
Preface
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:
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 gurus@UMLforDatabaseDesign.com, or visit our website http://www.UMLforDatabaseDesign.com.
0201721635P06272001