Explore BrainMass

Database Modeling and ER Diagram

Community library: You recently get a job offer from a local community library. The manager asks you to develop a database system to track customers and the books they check out.

Task 1:
Your initial assignment is to create a table for customers. The manager tells you that this table needs to track the following information: all customers' social security numbers, first and last name, address, city, state and zip code, email, phone number, birth date, and date of applying for a library card. Your task is to first "sketch" a customer table (basically what data items or columns should be included in the table) using the Customer_information table at background section as an example. (See attachment) Your table should contain the following:

- Column headings to include all the attributes that need to be in this table.
- Populate the table with five records of data.

Task 2:
Your next task is to design one more table: A customer checkout table to track the books and CD's that the customer has checked out from the library. The "Customers" and "Customer Checkout" table are related to one another. The Customer table contains the basic data on each customer and the primary key is customer number. There is one row for each customer. The Customer Checkout table contains the data for each book. The primary key consists of two pieces of data: Checkout number and customer number. One customer can check out 1 or more books/CD's at a time, but only one customer on a check out order.

Use the templates below to design the two tables: "Templates" for Table Design and Customer Table. (See attachment)

As well, draw an ER diagram of your complete design for the community library. You can use Visio, or the Microsoft word feature to draw the chart, or write down the table schemata and describe the relationships among them. Include a half page report about your experience with this assignment.

© BrainMass Inc. brainmass.com July 20, 2018, 10:47 am ad1c9bdddf


Solution Summary

This solution demonstrates database modelling techniques and the various steps in normalizing entities into 1st normal form, 2nd normal form, and 3rd normal form.