Data Management Individual Project – Project Description Student Name: ____Renee Randall_____________________________ Project Name/Title: ______Relation Modeling______________________ Provide a brief description about what type of data model you’re developing, along with a project description. Project description The business system is undergoing radical changes to cope up with technological paradigms and systems of other businesses in the market. In an attempt to improve the managerial ability, computer application in terms of data management is of paramount consideration. This has brought ease in how data is collected, manipulated, updated, stored and retrieved. But even with these vast advancement in computer technology, many businesses have not made databases that can help the manage data in an efficient manner. The idea of this project was motivated by my experience during my internship program where I acted as an assistant data administrator. The aim of this project is to develop of a company data management database using the relation model that will be used by businesses to foster effective data management. A data model is important to any business as it helps manage data efficiently allowing users to handle multiple tasks easily. The data model will help organizes, stores and manages huge volumes of information in a single application. This will as a result increases efficiency in business operations by reducing related costs. Objectives • To ease data collection, manipulation, and management • To improve storage and retrieval of information from the computer systems of the business enterprise • To enhance organization of data and keep in pace with other companies • To reduce the expenses incurred in data management methods like filling. Relational model For this project, I will use the relation model for implementation. The relational model organizes data into tables known as relations with each consisting of rows and columns. Every column contains an attribute of a particular entity in the database, like product name, customer id, or manager address. Together, these attributes in the relation table are known as domain. Every attribute or a group of attributes will have a primary key which will be referred to from other tables as a foreign key. Every row or tuple will include data on a specific instance about the entity such as a specified customer. The relation model will account for all types of relationships involved in the tables, these being one-to-many, many-to-many and one-to-one relationships. The model will be effective as it can allow tables to be normalized within the database or to comply with the rules of normalization and this will make the database more flexible, scalable and adaptable. By normalizing the tables, pieces of data become atomic, or subdivided into the small manageable pieces. The relational data model will be written in MySQL. Data Management Individual Project Outline – Entities, Attributes, and Relationships: Student Name: ___Renee Randall__________________________________________ Project Name/Title:_____ Relation Modeling ________________________________ Entities and Attributes: Entity Name: customer Attribute: customer Name Attribute: customer Id Attribute: customer Address Attribute: customer phone number Attribute: customer sex Attribute: customer purchase number Entity Name: product Attribute: product Name Attribute: product price Attribute: product Id Attribute: product manufacture date Attribute: product batch number Entity Name: Employee Attribute: Employee Name Attribute: Employee id Attribute: Employee Address Attribute: Employee department Attribute: Employee date of birth Attribute: Employee salary Entity Name: manager Attribute: Manager name Attribute: Manager id Attribute: Manager phone number Attribute: Manager Address Attribute: Manager Age Attribute: Manager Salary Entity Name: Department Attribute: Department Name Attribute: Department Id Attribute: Department number Attribute: Department role Attribute: Department Relationship Definitions: Relationship: one employee works for at least one department Relationship: one department holds many employees Relationship: one manager supervises many employees Relationship: one manager heads one or more department Relationship: one customer can buy one or many products Relationship: Many customers can buy a similar type of product Data Management Individual Project Outline – Entities, Attributes, and Relationships: Student Name: ___Renee Randall__________________________________________ Project Name/Title:_____ Relation Modeling ________________________________ Entities and Attributes: Entity Name: customer Attribute: customer Name Attribute: customer Id Attribute: customer Address Attribute: customer phone number Attribute: customer sex Attribute: customer purchase number Entity Name: product Attribute: product Name Attribute: product price Attribute: product Id Attribute: product manufacture date Attribute: product batch number Entity Name: Employee Attribute: Employee Name Attribute: Employee id Attribute: Employee Address Attribute: Employee department Attribute: Employee date of birth Attribute: Employee salary Entity Name: manager Attribute: Manager name Attribute: Manager id Attribute: Manager phone number Attribute: Manager Address Attribute: Manager Age Attribute: Manager Salary Entity Name: Department Attribute: Department Name Attribute: Department Id Attribute: Department number Attribute: Department role Attribute: Department Relationship Definitions: Relationship: one employee works for at least one department Relationship: one department holds many employees Relationship: one manager supervises many employees Relationship: one manager heads one or more department Relationship: one customer can buy one or many products Relationship: Many customers can buy a similar type of product The conceptual model Running Head: Data Dictionary Creating a Data Dictionary Renee Randall Wilmington University 11/9/17 Data Dictionary Customer Entity Attribute name Data Type Description Values CustomerName VARCHAR Stores customer’s name 25 CustomerID INT Stores each customer’s unique identifier CustomerAddress VARCHAR Stores each customer’s address 30 CustomerPhoneNumber VARCHAR Stores each customer’s phone number. 10 CustomerSex VARCHAR Stores each customer’s gender. 1 CustomerPurchaseNumber INT Stores each customers purchase number. Product Entity Attribute name Data Type Description Values ProductName VARCHAR Stores each product’s name. 25 ProductPrice DECIMAL Stores each product price. ProductID INT Stores each’s product unique identifier. ProductManufactureDate DATE Stores the date when each product was manufactured. ProductBatchNumber VARCHAR Stores each product’s batch number. 15 Data Dictionary Employee Entity Attribute name Data Type Description Values EmployeeName VARCHAR Stores each employee’s name. 25 EmployeeID DECIMAL Stores each employee’s unique identifier. EmployeeAddress VARCHAR Stores each’s employee’s address. 30 EmployeeDepartment VARCHAR Stores each employee’s department. 25 EmployeeDOB DATE Stores each employee’s data of birth. EmployeeSalary DECIMAL Stores each employee’s salary amount Attribute name Data Type Description ManagerName VARCHAR Stores each manager’ name. ManagerID INT Manager Entity Values 25 Stores each manager’s unique identifier. ManagerPhoneNumber VARCHAR Stores each’s manager’s phone number. ManagerAge INT Stores each manager’s age. ManagerAddress VARCHAR Stores each manager’s address. 10 30 Data Dictionary DECIMAL Stores each manager’s salary amount Attribute name Data Type Description Values DepartmentName VARCHAR Stores each manager’ name. 25 DepartmentID INT Stores each manager’s unique identifier. DepartmentNumber INT Stores each’s manager’s phone number. DepartmentRole VARCHAR Stores each manager’s age. ManagerSalary Department Entity 200 Running head: Physical Data Model Physical data model Renee Randall Wilmington University 11/15/17 The Final Physical Data Model is as follows
Purchase answer to see full attachment