Introduction to database database management information technology

1. Concepts of Database Management, Fifth Edition 1-1
Chapter 1
Introduction to Database Management
At a Glance
Table of Contents
 Overview
 Objectives
 Teaching Tips
 Instructor Notes
 Quick Quizzes
 Classroom Activities
 Discussion Questions
 Key Terms
 Applying Database Concepts
Lecture Notes
Overview
In this chapter, students examine the requirements of Premiere Products, a company that will be used in many
examples in this chapter and in the rest of the text. Students learn how Premiere Products initially stored its data,
what problems employees encountered with this storage method, and why management decided to use a database
management system. Students then study the basic terminology and concepts of databases and database
management systems. They also learn the advantages and disadvantages of database processing. Finally, students
examine the database requirements for Henry Books, the company featured in the case that is used throughout the
text.

2. Concepts of Database Management, Fifth Edition 1-2
Chapter Objectives
 Introduce Premiere Products, the company that is used as the basis for many of the examples throughout the
text.
 Introduce database terminology.
 Describe database management systems.
 Explain the advantages and disadvantages of database processing.
 Introduce Henry Books, the company that is used in the case that runs throughout the text.
Teaching Tips
 Encourage students to use the embedded questions and answers included throughout the chapter to test their
understanding of the concepts as well as the design of the two databases. It is critical that students understand
the entities, attributes, and relationships for both the Premiere Products database and the Henry Books
database. Students will use these databases in exercises and assignments throughout the text.
 Make sure students understand how to navigate the tables in both the Premiere Products and Henry Books
databases. Encourage them to use the embedded questions and answers to test their understanding of the
tables.
 Use Appendix B for a group assignment. Appendix B includes an additional case problem, Alexamara Marina
Group with exercises for Chapters 1 through 6.
Instructor Notes
Premiere Products Background
Premiere Products, a distributor of appliances, housewares, and sporting goods is a fictitious company that will be
used throughout the text. Since its inception, the company has used spreadsheet software to maintain company
data. Use Figure 1.1 to illustrate the problems associated with using spreadsheets to maintain this data.
Problems
 Redundancy.
 Difficulty accessing related data.
 Limited security features.
 Multiple updates.
 Size limitations.
Define redundancy. Redundancy wastes spaces, makes changes more cumbersome and time-consuming, and can
lead to inconsistencies. Review the embedded question and answer on page 3. Use Figure 1.2 to introduce the type
of data that Premiere Products must be able to store and retrieve. Premiere Products must maintain information
about sales reps, customers, and parts inventory as well as store information about orders. The company needs to
maintain data on more than one category (customers, sales reps, orders, parts) and is interested in the relationships
between the categories. Point out that the amounts in the Total column are not stored in the database but are
calculated.

3. Concepts of Database Management, Fifth Edition 1-3
Database Background
Define and discuss the database terms: entity, attribute, and relationship. An entity is a person, place, object,
event, or idea for which you want to store and process data. An attribute is a characteristic or property of an entity.
The terms column and field are used as synonyms in many database systems. A relationship is an association
between entities. Use Figure 1.3 to point out the Rep and Customer entity and the attributes for each entity. The
one-to-many relationship that exists between sales reps and customers in the Premiere Products database is
illustrated in Figure 1.4. In a database system, a one-to-many relationship is handled by using common columns in
the two tables.
Define database. A database is a structure that can store information about multiple types of entities, the attributes
of those entities, and the relationships among the entities. A data file (a file used to store data) is not the same as a
database. Figure 1.5 lists the five tables that make up the Premiere Products database. Each table represents an
entity. The data in the tables are related through common fields. It is these relationships that allow the user to
access data from more than one table and produce reports, queries, and forms. Because the same part can be found
on many orders and one order can include many parts, there is a many to many relationship between the Part and
the Orders table. The OrderLine table relates the Part and Orders table by including both the OrderNum field and
the PartNum field. The OrderNum field is the common field between the Orders and the OrderLine tables. The
PartNum field is the common field between the Part and OrderLine tables. Point out the problems with storing data
in the table structure shown in Figure 1.6. Students will learn how to solve these problems in later chapters.
Review the embedded questions and answers on page 11. Students should be able to navigate through the tables to
find the answers.
Define entity-relationship diagram (E-R). An entity-relationship (E-R) diagram is a visual way to represent a
database. Rectangles represent entities and lines represent relationships between entities. Use the E-R diagram in
Figure 1.7 to review the entities, attributes, and relationships in the Premiere Products database. Students learn
how to create E-R diagrams in Chapter 6.
Quick Quizzes
1. A(n) _____ is a characteristic or property of an entity.
Answer: attribute
2. A(n) _____ is a person, place, object, event, or idea for which you want to store and process data.
Answer: entity
3. A(n) _____ is a structure that can store information about multiple types of entities, the attributes of those
entities, and the relationships among the entities.
Answer: database
Database Management Systems
Define Database Management System (DBMS). A Database Management System (DBMS) is a program, or
collection of programs, through which users interact with a database. Popular DBMSs include Access, Oracle,
DB2, MySQL and SQL Server. Access currently is the most popular DBMS for use with personal computers.
There are versions of Oracle, DB2, MySQL and SQL Server that run under Windows, Unix, and Linux as well as
mainframe operating systems. Figure 1.8 illustrates using a DBMS directly and Figure 1.9 describes using a
DBMS through another program.
Database design is the process of determining the structure of a database. Students learn database design principles
in later chapters. Figures 1.10 and 1.11 illustrate forms created for Premiere Products. Forms are screen objects
used to maintain, view, and print data from a database. A DBMS also must be able to generate reports such as the
one shown in Figure 1.12. A DBMS such as Access has the ability to create switchboard systems – a set of special
forms used to provide controlled access to the data, forms, reports, and other objects in a database. Use Figures
1.13 and 1.14 to show part of the switchboard system for the Premiere Products database.

4. Concepts of Database Management, Fifth Edition 1-4
Advantages of Database Processing
Discuss the advantages of database processing.
1. Getting more information from
the same amount of data
In a nondatabase, file-oriented environment, data often is partitioned
into several disjointed systems. Getting data from multiple systems can
be difficult and in some cases, impossible. When data is stored in a
single database, access is quick and easy.
2. Sharing data Several users can have access to the same data and still use it in a
variety of ways.
3. Balancing conflicting
requirements
A database administrator (DBA) is a person or group in charge of the
database. The DBA is responsible for keeping the overall needs of the
organization in mind and ensuring that the database benefits the entire
organization and not just one group.
4. Controlling redundancy In a nondatabase, file-oriented system, multiple copies of the same data
usually exist. With a database approach, data is stored only once, thus
eliminating redundancy.
5. Facilitating consistency When the same data is stored more than once, the potential for
inconsistency exists. This means that the same piece of data can be
stored correctly in one location and incorrectly in another location.
Because the potential for inconsistency is a direct result of redundancy,
and because the database approach reduces redundancy, there is much
less potential for the occurrence of this sort of inconsistency.
6. Improving integrity An integrity constraint is a rule that must be followed by data in the
database. A database has integrity if the data in it satisfies all
established integrity constraints. A good DBMS should provide an
opportunity to incorporate integrity constraints in the database design.
7. Expanding security Security is the prevention of access to the database by unauthorized
users. A DBMS has features, for example, passwords, encryption, and
group permissions that help ensure the security of the data.
8. Increasing productivity A good DBMS reduces the need for individual programs to manipulate
data.
9. Providing data independence Data independence is a property that allows changes to the structure of
the database without changes to the programs that access the database.
Disadvantages of Database Processing
Discuss the disadvantages of database processing.
1. Larger file size A DBMS is a large program that occupies a great amount of disk space as well a
substantial amount of internal memory. Also, because the data is stored in one
file, the database file requires a large amount of both disk space and internal
memory.
2. Increased complexity A DBMS is a complex product. To take full advantage of the system requires a
significant amount of learning. A sound database design is critical to the
successful use of a DBMS.
3. Greater impact of
failure
In a nondatabase, file-oriented system, a failure of one system does not
necessarily affect users of any other systems. In a database approach, a failure on
the part of one user that damages the database can affect other users.
4. More difficult recovery If a database is damaged in some way, the process of recovering the database
requires several steps that restore the database first to its last known correct
status and then re-apply any database updates.

5. Concepts of Database Management, Fifth Edition 1-5
Introduction to Henry Books Database Case
Describe Henry Books. Ray Henry, the owner of a bookstore chain, must maintain information about bookstore
branches, publishers, authors, and books. Ray has decided to store his data in a database. The type of data that
Henry needs to maintain is described in Figures 1.17 through 1.20. The E-R diagram for the database appears in
Figure 1.21. The diagram shows six entities: Publisher, Author, Wrote, Branch, Book, and Inventory. There is a
one-to-many relationship (one publisher can publish many books) between the Publisher table and the Book table.
The common field between the two tables is Publisher Code. Because one author can write many books and one
book can be written by many authors, there is a many-to-many relationship between books and authors. The Wrote
table relates books and authors by including the BookCode field and the AuthorNum field. The BookCode field is
the common field between the Wrote and Book tables. The AuthorNum field is the common field between the
Wrote and Author tables. Because the same book can be found at many bookstore branches and one bookstore
branch has many books, there is a many-to-many relationship between the Branch and Book table. The BookCode
field is the common field between the Inventory and Book tables. The BranchNum field is the common field
between the Inventory and Branch tables. Review the embedded questions and answers in this section with
students to make sure they understand the Henry Books database.
Classroom Activities
Ask students for examples of entities, attributes, and relationships that would be appropriate for a database of
names, grades, and related information for this course to make sure they understand these important key terms.
Ask each student to list one place (for example, doctor’s office, dentist’s office, employer, school) where data
about them is stored. Write the list on the board. Ask students what happens when data that is stored about them is
incorrect. Students quickly see the advantages of minimizing data redundancy and improving integrity.
Pick up any object in the classroom, such as a coffee mug, a book, a pen, and ask students to list the attributes to
describe the object as an entity.
Discussion Questions
Now that you have an understanding of what a database is, have you interacted with any databases in the previous
24 hours? What were they and how did you interact with them?
When a database approach is used, a failure on the part of one user that damages the database can affect other
users. What are some specific examples of database failures? If you were one of the users, how would you be
affected?

6. Concepts of Database Management, Fifth Edition 1-6
Key Terms
All key terms are defined in the Glossary section of the textbook.
Attribute
Column
Data file
Data independence
Database
Database administration (dba)
Database administrator
Database design
Database management system (dbms)
Entity
Entity-relationship (e-r) diagram
Field
Forms
Integrity
Integrity constraint
One-to-many relationship
Redundancy
Relationship
Security
Switchboard
Applying Database Concepts
Note: Each of the textbooks listed below has its own Instructor’s Manual that provides lecture notes, teaching tips,
and solutions. The integration tips are designed to help you integrate and reinforce material in the Concepts book
with the specific DBMS application text. The suggested exercises complement and enhance the exercises in the
Concepts book. You also will want to assign exercises that cover the material presented in the specific application
text.
Access 2003 New Perspectives (Brief, Introductory, Comprehensive)
Integration Tips
Tutorial 1 introduces students to Microsoft Access. Session 1.1 identifies the same database concepts that are
discussed in Chapter 1 of the Concepts book. Session 2.1 in Tutorial 2 presents basic guidelines for designing
databases.
 Introduce Northeast Seasonal Jobs International and make sure students understand the purpose of the
database and the type of data needed by Elsa Jensen. (AC 3)
 Use the database shown in Figures 1-1 and 1-2 to point out the entities (records), attributes (fields), and
relationships. Identify the common field (EmployerId) between the Employer table and the Position table.
(AC 4 and AC 5)
 Ask students what type of relationship exists between the Employer table and the Position table (one to
many). (AC 5)
 Use Quick Check questions 1 through 4 as review. (AC 13)
 Point out the guidelines for designing databases in Session 2.1 (AC 36). Use Figure 2.3 to show inconsistent
data and data redundancy. (AC 37).
Suggested Exercises
 Assign the Databases Lab Assignment in Tutorial 1 This assignment demonstrates the essential concepts of
file and database management systems. (AC 34)
 Use Case Problem 4, Mountain River Adventures to ask students about other entities and attributes (in
addition to the client entity) to include in the database. Obtain some trip brochures (or use the WWW to find
information on adventure tours) and ask students to determine the design of the database. This can be an
individual or a group exercise. It can be a homework assignment or an in-class assignment. (AC 32)
 Assign Tutorial Discussion Question 2 in Tutorial 1. Tutorial Discussion Questions are in the Instructor’s
Manual.

7. Concepts of Database Management, Fifth Edition 1-7
Access 2003 Shelly Cashman (Introductory, Complete, Comprehensive)
Integration Tips
Project 1 introduces students to Microsoft Access and identifies the same database concepts that are discussed in
Chapter 1 of the Concepts book. Data redundancy also is discussed.
 Introduce Ashton James College and make sure students understand the purpose of the database and the type
of data needed by the administration. (AC 3)
 Use the database shown in Figure 1-1 to point out the entities, attributes, and relationships. Identify the
common field (Trainer Number) between the Client table and the Trainer table. (AC 5)
 Ask students what type of relationship exists between the Trainer table and the Client table (one to many).
(AC 5)
 Discuss Designing a Database. Use Figure 1-83 to review the problems associated with redundancy. (AC 50)
Suggested Exercises
 Use the Begon Pest Control database in Apply Your Knowledge 1 as a homework assignment. Ask students to
list the entities (Customer and Technician), the common field (Technician Number), and the type of
relationship that exists between the tables (one Technician is related to many Customers.) Ask them to
identify an additional attribute that could be added to the Technician table (telephone number or year-to-date
salary are two choices.) (AC 55)
 Use Cases and Places 3 to ask students about the entities and attributes to include in the database. The
database design can have either two entities (Book, Publisher) or three entities (Book, Publisher, Author.) Ask
students for additional attributes that could be included in the Publisher table (publisher address and telephone
number are two choice.) This can be an individual or a group exercise. It can be a homework assignment or an
in-class assignment. (AC 63)
A Guide to SQL, Sixth Edition
Integration Tips
Chapter 1 describes both the Premiere Products database and the Henry Books database.
 Point out that the Premiere Products and Henry Books databases used in this book have the same database
design. The actual data also is the same except for the dates in the Orders table. (2)
 Use the Henry Books database to point out the entities, attributes, and relationships. (8)
 Identify the common field (Publisher Code) between the Publisher table and the Book table. (9, 11)
 Ask students what type of relationship exists between the Publisher table and the Book table (one to many).
(9, 11)
Suggested Exercises
 Assign Premiere Products exercises 4, 5, 6, and 9 as complements to the exercises in the Concepts book. (15)
 Assign Henry Books exercises 2, 6, 7, 8, 10, and 11 as complements to the exercises in the Concepts book.
(16)