Need A++ work with low turnitin score

tkilh1

m3_a2_henry_trevor.doc.docx

Home >Information Systems homework help >Need A++ work with low turnitin score

THE PLANNING STRATEGY TO COMPLETE THE DATABASE

The planning strategy to complete the database

Trevor Henry

Argosy University

Professor Alissa Johnson

07/20/2016

As a database designer, I want to structure employees’ data for Altair Software Company in tables that discard unnecessary duplication while providing a quick search path to all needed information. The task involves refining tables, columns, keys, and relationships in order to come up with an efficient database through a process called normalization. Normalization refers as to the process of eliminating repeating groups, reducing tendency, removing multiple keys for partial dependency and splitting non-key attributes (Byrne, 2013).

Normalization has many benefits in the company’s database management system that makes it better when it comes to the programming of the database (Coronel, 2016). This task is dealing with the attributes and entities of the employees’ information for the company. For Altair Software’s system to understand the logic presented in the spreadsheet table without any confusion, there should be no similar entities and attributes, or tables and columns. As the company continues to grow, the increasing data will raise the chances of redundant and repetitions as well as dependent data. As a result, it will not be convenient and easy for them to get the best result for most of their database commands and queries. To avoid such problem and ensure better performance and maintenance when they will be handling a large database, it better for them to reduce the dependencies and duplicates records from their database as soon as possible (Jiang, 2014).

My strategy is to use normalization to complete the database where am going to arrange it in such a way that they can easily find out the necessary employees records or data without any delay or confusions. I will do this by normalizing their database up to the third normal form to ensure that they get better results. In this process, I will decompose the large first norm table into smaller ones to minimize the dependency and duplicity among the attributes within the table. Holding non-normalized data in their system can lead them to a big problem in their database. Therefore, it is good to reduce the number of similar types of attributes in another table without any transitive or partial dependency from the table one after the other (Coronel, 2016).

The process starts with displaying a database table in the first normal form or 1NF. By not violating 1NF, the company will be creating more space that is unused by reducing the number of records in the table, which ultimately eliminate the wastage of the useful memory. Besides, violations of 1NF will result in the unused and complex queries that can lead to repeated values of records with a lot of dependencies (Byrne, 2013).

The second normalization for is useful in making each column dependent on its primary key. However, the second normal form or 2NF will lead the company to the redundant data in their records, creating complicated modifications and overhead. By getting the lead of 2NF, I will obtain 3NF that is more beneficial to the software company by ensuring the best result from their relative database management system (RDBMS).

Altair Software will indeed find the third normalization form more useful that the other dorm of normalization because each column is directly dependent on the primary key (Jiang, 2014). This will reduce the redundancies in their database as well as the complexity and problems in updating their records.

DEV

Programmer II

Vice President

SALES

Positions

Sales Rep

Programmer I

Street Address

ZIP

City

First Name

Last Name

Departments

EXEC

MGMT

Employees

Divided

Has a

Assigned

President

State

Figure 1: An entity-relationship diagram

Key (Thalheim, 2013)

Rectangles represent entities

Ovals represent attributes

Diamond shape represents actions or relationships

One to one

One to many

Many

One or more

One and only one

Zero or one

Zero or many

From figure 1, every employee has one ID, and one and only one name for either first or last name. On the other hand, several workers can possess similar names. One or many employees can share the same ZIP code, but a given ZIP code number may be associated with many workers from the company or none. Different cities, streets, and states can have a distinctive or shared ZIP while the ZIP of each of them is unique. Every employee is assigned to one and only one department while a department may have one or several of them. Furthermore, each of the workers can only hold one position while at least one of them should serve in a given position.

Also, there can be one or more position for sale rep, programmer 1, programmer 2, and vice president, whether occupied or vacant. On the other hand, each of these occupants can be missing, for example, when programmer one is sucked leaving the post empty, or they can have many occupants. Besides, companies usually have one position for president with only one president, but the job can sometimes be vacant for several reasons. Every department can also be divided into one or more position, but every position belongs to one and only one department. Finally, each of the EXEC, MGMT, DEV, and SALES belong to one department.

References

Byrne, B., & Shahzad Qureshi, Y. (2013). The Use of UML Class Diagrams to Teach Database Modelling and Database Design. In Procs of the 11th Int Workshop on the Teaching, Learning and Assessment of Databases (TLAD). The Higher Education Academy.

Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management. Cengage Learning.

Jiang, T. (2014). U.S. Patent No. 8,914,395. Washington, DC: U.S. Patent and Trademark Office.

Thalheim, B. (2013). Entity-relationship modeling: foundations of database technology. Springer Science & Business Media.