- Full Description
Beginning Database Design: From Novice to Professional provides short, easy-to-read explanations of how to get database design right the first time. This book offers numerous examples to help you avoid the many pitfalls that entrap new and not-so-new database designers. Through the help of use cases and class diagrams modeled in the UML, youll learn how to discover and represent the details and scope of the problem in question.
Database design is not an exact science, and solid database design principles and examples help demonstrate the consequences of simplifications and pragmatic decisions. The rationale is to try to keep it simple, but allow room for development as situations change or resources permit. The book also features an introduction for implementing the final design in a relational database.
- Source Code/Downloads
If you think that you've found an error in this book, please let us know by emailing to firstname.lastname@example.org . You will find any confirmed erratum below, so you can check if your concern has already been addressed.On page 42:At page 43 is a example 3-2 explaining delivery system goals.
At the beginning it says: "It will maintain
data about orders including the date, the meals requested, and contact information for the customer and the driver assigned to the delivery."
And at the end says: "The system will not maintain any additional information about drivers nor about which drivers were associated with a particular order."
So... is the system will maintain information about drivers assign to a particular order or not?