It is brought into consideration during the information gathering phases in Chapters 2 and 3, but is dealt with in detail in Chapter 7. Will Parker rated it liked it Feb 23, Then you can start reading Kindle books on your smartphone, tablet, or computer — no Kindle device required. Kindle Edition Verified Purchase. Description For Introductory Database courses that focus on hands-on experience. Maxi rated it really liked it Apr 05, Rebecca rated it liked it Oct 31, Congers introduces students to the concepts and vocabulary of normalization by discussing the first three Normal Forms.
|Published (Last):||11 September 2019|
|PDF File Size:||7.22 Mb|
|ePub File Size:||4.90 Mb|
|Price:||Free* [*Free Regsitration Required]|
For Introductory Database courses that focus on hands-on experience. Define and develop a database through a scenario approach. Hands-On Database uses a scenario-based approach that shows students how to build a database by providing them with the context of a running case throughout each step of the process. Features Scenario Approach. In order to help give students this kind of context, Conger presents a scenario approach with an emphasis on defining business rules and then testing the database design against those rules.
Running Case Scenario. End-of-chapter Scenarios. At the end of each chapter, after the practices, there are four additional scenarios for students to work through: NEW. Show Times: Local Shows and Acts. This scenario gives students the opportunity to see another type of database, one that deals with schedules and involves the interactions between several disparate stakeholders, specifically between artists, venues for the shows and fans.
The Wild Wood Apartments scenario involves creating a database to manage a chain of apartment buildings. Grandfield College leads students through the process of making a database to track what software the school owns, the licensing for that software, on what machines the software is installed, and what users have access to those machines. The WestLake Research Hospital scenario involves creating a database to track a double-blind drug study for a new antidepressant. The forms for the WestLake Hospital scenario were simplified and clarified.
Traditional Chapter Conventions. Aside from the running case on Sharon, this text also presents several in-chapter support features, specifically designed to help students understand the core concepts: Things You Should Know. These extended sections provide definitions, explanations, and examples that offer a deeper, more comprehensive context to the things Sharon is doing in the narrative. Things to Think About. These sidebars invite students to consider questions about the processes or topics under discussion.
Found in the margins of the text, this feature warns students about potential mistakes or common errors. Found at the end of each chapter, this feature provides a summary of how students would document the activities conducted during the chapter. Things to Look Up. Found at the end of each chapter, this feature guides students to other resources and topics not fully covered in the book. Throughout the text, key words are highlighted in the margins and are repeated in an exercise at the end of each chapter.
Found at the end of each chapter, practices are designed to give students hands-on experience with the materials of the chapter. The Chapter 5 practices have been totally redone to provide a better demonstration of each stage of normalization. Process-driven Model. The material in this text is based on a process-driven model, ensuring that students see the process of developing a database from the beginning through to the final stages.
Congers introduces students to the concepts and vocabulary of normalization by discussing the first three Normal Forms. SQL Coverage. Chapter 7 of this text contains an extensive introduction to SQL. SQL coverage is continued throughout the remainder of the text.
Security Coverage. Security issues are discussed at several points in the book. It is brought into consideration during the information gathering phases in Chapters 2 and 3, but is dealt with in detail in Chapter 7. In Chapter 2, a brief discussion of cloud computing, cloud databases, and cloud data services has been added.
Chapter 8 now includes a brief discussion of Big Data and some of its implications for database. Also in Chapter 2, a note was added about the interview process and the forms for the WestLake Hospital scenario were simplified and clarified. Table of Contents 1. Who Needs a Database 2.
Gathering Information 3. Requirements and Business Rules 4. Database Design 5. Normalization and Design Review 6.
Hands-On Database: An Introduction to Database Design and Development
Data Warehouse f. A collection of various types of business information including databases and documents Stakeholder a. Anyone who has a stake in the process Work Shadowing q. Observing workers handling data on the job Things to Look Up 1. Information Gathering is often presented as a part of a Systems Design and Analysis.
ISBN 13: 9780133024418