hi i have project about data base design and i need to make designing a complete database management system to address a practical database need and implementing a relational database based on tha

CIS305 Project 1

Project Description

The project is designing a complete database management system to address a practical database need and implementing a relational database based on that design. Your database system should be designed to perform general information management tasks such as systematic collection, update, and retrieval of information for a small organization.

The objective of Project #1 is to develop a normalized relational data model describing the primary business processes of Pine Valley Furniture Company (PVF). PVF is in the business of wholesale distribution, whereby they purchase most of their products directly from various manufacturers, and then they sell these products to their customers. PVF can actually fabricate some of the products they sell, in addition to purchasing them from the manufacturers.

The initial entities for your model are CUSTOMER, ORDER, and PRODUCT. In addition to these initial entities, you are provided with several business rules.

You should treat this project as a business assignment in which your instructor is your customer. You are to deliver the results of this project in a very professional and accurate format. The quality of your project submission is a reflection of your attention to detail, and it is an important factor that influences how your customers will think of you and how quickly they will pay you. Your instructor (customer) will deduct points for incorrect formatting, as well as, inaccurate or incomplete work. Your grade represents your pay.

Initial Entities.

CUSTOMER ( CustomerID, CustomerName, CustomerAddress, CreditLimit)

ORDER (OrderID, CustomerID, CustomerPoNumber, OrderDate, DueDate, ShipDate)

PRODUCT( ProductID, ProductDescription, UnitPrice, StockQuentity)

Deliverable 1

Begin with the initial entities for CUSTOMER, ORDER, and PRODUCT provided above, transform them into relations, and normalize your model to 3rd Normal Form. This is your deliverable #1. Realize that the three entities (or the three converted relations) are not in 3rd Normal Form. This is obvious by the many-to-many relationship that would need to exist between ORDER and PRODUCT. You are to do the steps necessary to obtain 3rd Normal Form. You do not have to show how you got there, but you are to provide a document that shows the final relations you come with (and their relationships) once you have achieved 3rd Normal Form. Hint: You answer will be within the Word document you submit as your Project 1 Assignment response along with the other deliverables for this assignment. Be sure to format this showing the logical schema (Rectangle boxes for relations in alphabetical order and lines between the relations to indicate the relationships). This format is NOT an ERD. Make sure it includes proper formatting and capitalization, as well as the appropriate relationships.

Deliverable 2

In Deliverable 2 you will start with a copy of your Deliverable 1, and build upon it by adding the necessary functionality to support the following business rules:

Business Rules:

Each customer may place multiple orders, and each order may consist of multiple products

Each Customer is serviced by a Sales Representative that is an employee of PSC. A Sales Rep may service multiple customers.

Employees that are Sales Reps are paid commission on their sales based on a commission rate for the Sales Representative. Different Sales Reps may have different commission rates.

All products are purchased from suppliers, and multiple suppliers can provide each product; however, some products can also be fabricated by PSC. Different suppliers charge different amounts for the products. Fabricated products consist of a Bill of Materials that describes the components (parts) of each product. Component parts are products too.

Each employee is required to complete a series of PSC courses. It is essential to document the courses employees complete, as these skills are used to evaluate promotion eligibility.

In Deliverable 2, You will add the additional relations and relationships t the relational schema you created in Deliverable 1. You must maintain 3rd Normal Form in this enhanced model. Be sure to list your relations in alphabetical order, and be sure to include the relationships between the relations (all of these lines may look a little messy). Also, keep in mind that all of the relations must be shown flush left against the left margin of the page and in alphabetical order. Be sure to use the correct capitalization formatting with RELATION names being singular and in ALL CAPS while attributes are presented using ProperCamel notation. Remember that this logical schema is a listing of the relations and relationships, and it is not in the same format as an ERD.

Deliverable 3

Contains the same information as Deliverable 2, except in a different format. Deliverable 3 is an Entity Relationship Diagram (ERD) that you develop in ERwin. All of the functionality indicated in the business rules must be present. Also, this exercise is an excellent opportunity to show your understanding of Enhanced Entity Relationship Diagrams (EERD), as you will have the opportunity to demonstrate Supertype/Subtypes. A helpful hint here is to take a screenshot of your Erwin ERD instead of printing it. Erwin places a big watermark description across the page when you print using the free Community Edition of the software; however, if you simply take a screenshot, then the watermark does not appear. All entities, attributes, and relationships must be properly labeled. Although they are presented in different visual formats, the information contained on this Deliverable 3 Erwin logical data model (ERD) must exactly correspond to the information contained on Logical Schema of deliverable #2

Deliverable tips:

Within a Word document, submit all three deliverables in the exact order specified.

Deliverable 1 with consist of the logical schema showing the relations and relationships

Deliverable 2 will be in the same formation as Deliverable 1, but it will contain many more relations and relationships

Deliverable 3 will contain the same information as Deliverable 2 but it will be in a different format. Deliverable 3 will be in the format of an ERD, and you will develop your ERD in ERwin. You must also attach a copy of your erwin file.

Include a table of contents.

Data Profile

Follow the instructions provided within the course syllabus regarding submitting projects

The first two deliverables must show relations and relationships

The third deliverable mush show entities, relationships, attributes, cardinalities and keys.

You must name your files using the syntax of LastnameFirstInitialLab1. So, be sure to name your .docx and your .erwin files using our last name, first initial, and “Lab1” as the file names.

Use VISIO to present the Diagrams

Logical Database Design and the Relational Model

Project Submission Requirements:

Be sure to read and follow the project submission instructions located on the course syllabus.

You must submit your Word document with your Project and a copy of your Erwin file.

The starting point of your project is to identify a database need of a real client, and explore questions such as:

What is the purpose of the database? Why is it needed? What should it do?

Who is the client/user?

What is the problem/challenge in general?

How can the problem be solved?

Why is the project important?

Who are the users and what are their information needs?