05 Jul Designing a Database

Part 2: Begin Designing a Database

Module_3 Database Design Sample document shows the parts of the database design for this module.

Please keep your database design simple. Have no more than 10 tables, including associative entities. If you must, narrow the scope of your database design in order to meet this requirement.

Part 2 Requirements

You will design a database. Questions and problems from Chapters 3, 4, 5, and 6 can be used as the concept for the database you create for this project. In this module, you will start by defining the purpose of the database and the information the database is to provide. You will list entities, write the business rules for each relationship between entities and create an ERD. Refer to the Module_3 Database Design Sample document for an example.

Part 2, Section 1: Database Definition

State the purpose of the database.

Define the requirements of the database. Describe who are the users and how the database will be used,

Part 2, Section 2: Database Design

This section of the Assignment must include at least 5 tables and should have no more than 10 tables.

List the entities of your database.

Present the business rules that determine connectivity in your ER model. Do not give rules for links to associative entities; simply give the M:N relationship rules and the name of the associative entity you will use for that relationship. Example: Apartment – Tenant. One apartment may currently be occupied by one or more tenants. (many)One tenant may occupy many apartments (but only one at a time). (many)Apartment M:N Tenant; AE: ApartmentTenant

Draw the ERD; copy the drawing into your Word project document

NB: Below is the problem to use to answer the question. The MODULE 3 SAMPLE attached is just an example of how your work is supposed to look like.

Problem to use to solve the questions.

• A department employs many employees, but each employee is employed by only

one department.

• Some employees, known as “rovers,” are not assigned to any department.

• A division operates many departments, but each department is operated by only

one division.

• An employee may be assigned many projects, and a project may have many

employees assigned to it.

• A project must have at least one employee assigned to it.

• One of the employees manages each department, and each department is

managed by only one employee.

• One of the employees runs each division, and each division is run by only one

employee.