1. Database Design
Chapter 7

2. Chapter 7: Database Design
Introduction
An Overview of Databases
Steps in Developing a Database Using Resources, Events and Agents Approach
Normalization

3. Introduction Uses of a modern AIS Systematically record data
Provide convenient and useful formats
Easy access to information

4. What is a Database? Collection of organized data
Used by many different computer applications
Manipulated by database management systems (DBMS)

5. Significance of a Database
Critical information
Volume
Distribution
Privacy
Irreplaceable data
Need for accuracy

6. Significance of a Database
Internet uses
Big Data
Storing Data in Databases
Data Hierarchy

7. Storing Data in Databases
Data must be stored and organized systematically
Three important concepts: Three important concepts
Data hierarchy
Record structures
Database keys

8. Data Hierarchy Data organization in ascending order: Data field Record
File
Database

9. Record Structures Example
Data fields in each record of a database table
Structure is usually fixed
Example

10. Database Keys Primary Key Foreign Keys Unique to each record
Enable referencing of one or more records
Matches primary key of related table

11. Records Combined Into Report

12. Additional Database Issues
Administration
Database Administrator
Documentation
Includes a variety of descriptions
Structures, Contents, Security Features
Data Dictionary
Metadata

13. Data Dictionary Example

14. Additional Database Issues
Data Integrity
Data Integrity controls
Designed by database developers
Processing Accuracy and Completeness
Transaction controls
Ensures accurate transaction processing

15. Additional Database Issues
Concurrency
Concurrency controls
Prevent multi-user access at same time
Backup and Security
Ability to recreate data
Prevent unauthorized access
View controls

16. Study Break #1
The part of the data hierarchy that represents one instance of an entity is a:
Field
Record
File
Database

17. Study Break #2
Within the context of databases, the term “concurrency” refers to the possibility that:
A customer of one store might also be a customer of another store
Two database users might want to access the same record at the same time
A credit entry for a customer requires a debit entry for a matching account
None of these

18. REA Model Resources Organization’s assets Events
Activities associated with a business process
Agents
People associated with business activities

19. Steps in Developing Databases with REA
Identify Business and Economic Events
Identify Entities
Identify Relationships Among Entities

20. Steps in Developing Databases with REA
Create Entity-Relationship Diagrams
Identify Attributes of Entities
Convert E-R Diagrams into Database Tables

21. Identify Events and Entities
Types of Events
Economic
Business
Types of Database Entities
Entities
Agents
Resources

22. Entity Examples

23. Identify Relationships Among Entities
Types of Relationships
Direct relationship
Indirect relationship
Cardinalities
Nature of relationships among entities

24. Cardinality Relationships
Notations
One-to-one (1:1)
One-to-many (1:N)
Many-to-many (N:N)
Purpose
Occurrence of one entity
Associated with occurrence of one event of another entity

25. Cardinality Relationships

26. Entity-Relationship Diagram
Purpose
Diagram entities
Relationships among entities
Structure
Rectangles represent entities
Connecting lines represent relationships

27. E-R Diagram Example

28. Relationship Tables Provide greater flexibility
Need for Relationship Tables
Linking tables with foreign keys
Many-to-many relationships

29. Relationship Tables

30. Schematic of Database Tables

31. Study Break #3 In the REA model, the “A” stands for: Agents Additions
Accounts
Associations

32. Study Break #4
Which of these is not a cardinality between two database entries?
One-to-one
None-to-none
One-to-many
Many-to-many

33. Normalization Normalization
Methodology ensuring attributes are stored in most appropriate tables
Design promotes accuracy
Avoids redundancy of data storage
Levels
First normal form
Second normal form
Third normal form

34. Unnormalized Data

35. First Normal Form In First Normal Form (1 NF) when:
All data fields are singular
Each attribute has one value
Problems
Data redundancy
Insertion anomaly
Deletion anomaly

36. First Normal Form Example

37. Second Normal Form In Second Normal Form (2 NF) when: It is in 1 NF
All data items depend on primary record key
Benefits
More efficient design
Eliminates data redundancy

38. Second Normal Form Example

39. Third Normal Form In Third Normal Form (3 NF) when: It is in 2 NF
Does not contain transitive dependencies
Data field A does not determine data field B
Ultimate Goal
Create database in 3 NF

40. Third Normal Form Example

41. Study Break #5
A database is in third normal form (3 NF) if it is second normal form and:
All the data attributes in a record are well-defined
All the data attributes in a record depend on the record key
The data contains no transitive dependencies
The data can be stored in two or more separate tables