Provides students with an accessible presentation of technology so they can easily grasp key ideas. Ex.___
Offers students material grounded in reality so they can prepare for their future decision-making positions. Ex.___
Offers students clear advice for how to improve database practices. Ex.___
Prepares students for selecting and using these different types of applications. Ex.___
Provides students with a useful comparison of both technologies. Ex.___
Provides visual reinforcement of material. Ex.___
This easy-to-follow introduction is designed to help professionals better understand how to use database system technology. The author provides a highly accessible introduction to the paradigms, principles, and applications of databases. This book explains strategic issues in a non-technical manner that is accessible to business decision-makers of all levels of experience and will help them avoid damaging mistakes.
I. INTRODUCTION.1. The Business of Software.
Two Scenarios. In This Book.2. Database Applications.
Operational and Analytical Applications. Procuring Applications. Maintenance. Removing Obsolete Applications. Chapter Summary.
II. DATA MANAGEMENT TECHNOLOGY.3. Architecture.
Tiered Architectures. Transaction-Processing Monitors. Web-Based Architecture. Other Architectural Issues. Chapter Summary. Resource Notes. References.4. Data Management Paradigms.
Files. Groupware. Databases. Comparison of Paradigms. Hybrid Approaches. Chapter Summary. Resource Notes. References.5. Database Paradigms.
Contemporary Database Paradigms. New Database Paradigms. Obsolete Database Paradigms. Comparison of Database Paradigms. Hybrid Approaches. Chapter Summary. Resource Notes. References.6. Relational Databases.
Overview. Defining Database Structure. Manipulating Data. Controlling Access. Object-Relational Databases. Chapter Summary. Resource Notes. References.7. Data Processing.
Combining Databases with Programming. Trading Programming for Database Code. Data Security. Improving Performance. Converting Legacy Data. Chapter Summary. Resource Notes. References.
III. DATABASE DESIGN TECHNOLOGY.8. Modeling Principles.
What Is a Model? Why Build Models? Difficulties with Models. Kinds of Models. Structural Models. Naming Conventions. Chapter Summary. Resource Notes. References.9. Modeling Notations.
Entity-Relationship Notations. IDEFIX Notation. Comparison of Modeling Notations. Judging the Quality of Models. Chapter Summary. Resource Notes. References.10. Managing Models.
The Importance of Skilled Staff. Estimating Modeling Effort. Modeling Sessions. Modeling Pitfalls. Chapter Summary. References.11. Operational Applications.
What Is an Operational Application? Designing Structure. Designing Functionality. Chapter Summary. Resource Notes. References.12. Analytical Applications.
What Is an Analytical Application? Modeling a Data Warehouse. The Bus Architecture. Designing a Data Warehouse. Populating a Data Warehouse. Analyzing Data. Chapter Summary. Resource Notes. References.13. Design Summary.
Two Kinds of Applications. Structural Design Rules. Design List. Chapter Summary.
IV. SOFTWARE ENGINEERING TECHNOLOGY.14. Methodology.
What Is a Methodology? Why Use a Methodology? How Software Is Often Build. How Software Should Be Built. Specific Methodologies. Chapter Summary. References.
If you've taken the trouble to open this book, chances are you're involved with some aspect of software development or purchase. You've probably also experienced the software crisissoftware takes too long to build, has uneven quality, and costs too much. A few firms have managed to use software systems to enhance their business and give them a competitive edge. But many more are still coping with inferior systems that end up hobbling or even sabotaging their goals.
Unfortunately, the whole situation is worse than it has to be. There's no shortage of techniques for combatting the software crisis, but many organizations seem unwilling or unable to use them.
I believe "a failure to communicate" is a big part of the reason. Computing technology is complex and has idiosyncratic jargon, which makes it difficult to explain or understand. Managers have an even harder time because they must deal not only with the software but also with human and organizational issues. They have neither the time nor the patience to wade through technobabble and irrelevant details.
This is particularly true for database systems, which are a special kind of software. Databases are critical, because they provide the memory of an organization. With sound databases, you can readily get the information you need to execute business strategies. With flawed databases, you can't find customers, you lose orders, and the organization fails to capitalize on its collective knowledge.
The marketplace is full of books on software development, but the level of detail is crushing. There is little or no attention to strategy and managerial concerns about how applications should be organized and how they fit together. In contrast, this book takes a broad look at technology and focuses on databases. You need databases that are flexible, sound, and efficient for successful applications.What You Will Find
This book covers key aspects of database technology and provides practical tips that managers can use immediately. It has five main parts.
The primary audience is managers. Nevertheless, several kinds of persons can benefit.
This book is intended for both large (Fortune 500) and small firms. I qualify my advice when a firm's size really matters. For the most part, I assume that a firm is building or purchasing software. Nevertheless, a vendor may find this book helpful in understanding their customers' point of view.Acknowledgments
I thank the many reviewers who took the time to read manuscripts and give me their thoughtful comments: Ian Benson, Jim Blaha, Dave Curry, Kathi Davis, Bill Huth, Chris Kelsey, Sham Navathe, Bill Premerlani, Hwa Shen, Steve Sherman, and Rod Sprattling. The comments of Jim Blaha, Chris Kelsey, and Steve Sherman were particularly thorough and incisive.
Thanks also to Nancy Talbert, who edited the final manuscript improving its readability and organization, and to Alan Apt and Toni Holm of Prentice Hall, who facilitated the book's production and distribution.
I took some of the material from Object-Oriented Modeling and Design for Database Applicatdons (1998, Prentice Hall), which I co-authored with Bill Premerlani.
Finally, I thank the many managers who helped me write this book. Some helped me directly by reviewing the book. Others helped me indirectly over the years by bringing me problems, asking me questions, and clarifying my thinking.Contact Information
If you have any questions or comments, please contact me. I would like to hear if this book has helped you and about your experiences. Send e-mail to email@example.com or firstname.lastname@example.org, or visit my Web site at www.omtassociates.com.