Designing a Human Resources Paper. You are a freelance database designer who has just been contacted by a small software development company named Altair Software. The president of the company has asked you to create a database that will house employee information. The company currently has eight employees and comprises one president, two vice presidents, three programmers, and two sales representatives. The company wants you to create a scalable database that will grow as the company grows. They want to store the following information within the database: Information Required Maximum Value Employee ID 6 integers Employee Last Name 30 characters Employee First Name 30 characters Street Address 60 characters City 30 characters State 2 characters ZIP Code 5 integers Department 30 characters Manager 60 characters Position 30 characters Salary 8 integers The president of the company has given you a document that contains all of the above information for each employee. Tasks: You need to create and submit spreadsheets in Microsoft Excel that accomplish the following: Display a database table in first normal form that will store all of the information listed above. Identify a field or fields to act as the primary key by bolding that field name. Enter all of the provided information into the table in the spreadsheet. Save your spreadsheet as M3_A2_Lastname_Firstname_FirstNormalForm.xls. Decompose the table you created in Step 1 to second normal form. Place each table in its own sheet within the spreadsheet. Identify a field or fields to act as the primary key in each table by bolding that field name. You may insert a new field to act as the primary key if you feel it is warranted. Enter all of the provided information into the appropriate table in the spreadsheet. Save your spreadsheet as M3_A2_Lastname_Firstname_SecondNormalForm.xls. Decompose the table or tables you created in Step 2 to third normal form. Place each table in its own sheet within the spreadsheet. Identify a field or fields to act as the primary key in each table by bolding that field name. You may insert a new field to act as the primary key if you feel it is warranted. Enter all of the provided information into the appropriate table in the spreadsheet. Save your spreadsheet as M3_A2_Lastname_Firstname_ThirdNormalForm.xls. In addition, in a 2- to 3-page Microsoft Word document, you need to: Share your planning strategy to complete the database. Create an entity-relationship diagram from the tables that you designed above using crow’s foot notation. Be sure to note the cardinality and modality for each relationship. Explain why you selected the links between each of the database tables. Save your document as M3_A2_Lastname_Firstname_EntityRelationshipDiagram.doc.
Database Boards and Existence Interdependence Diagram
The axiomsbase conciliate imply of seven boards as shown in the existence interdependence diagram aloft. Each board is carefully alert to assemble whole the required axioms and as well-behaved-behaved secure that the axiomsbase is scaltelling to encounter exoteric and restraintthcoming demands. Each board is explained adown.
Board Employees
As undivided susceptibility divine, the employee board is legal restraint storing basic axioms of our employees such as the employee ID sum, call, harangue, and zip rather than local employee axioms such as interpretationrnames and passwords. The Employee_ID conciliate obey as the pristine clew that conciliate automatically be generated from the board. The pristine clew is essential in facilitating dissipated pursuit through the axiomsbase. The board conciliate be unsteady and scaltelling abundance to stock knowledge encircling the exoteric employees and any sum of employees that susceptibility combine the assemblage in the restraintthcoming. Here, a undivided-to-numerous interdependence where is customary betwixt employee and remuneration where at last an employee has a stint of undivided remuneration past an employee can bear multiple salaries at divergent spells or abetting. Similarly, a undivided-to-numerous interdependence is customary betwixt employee and positions past an employee can restrain undivided or over positions at divergent spells or abetting. Similarly, the interdependence betwixt employee and directors is a undivided to numerous past an employee can bear divergent directors at divergent spells.
Board “departments”
The axiomsbase conciliate to-boot stock branchal knowledge. Here, the clewword dept_no is built on a unique-value shaft and to-boot essential in facilitating dissipated pursuit and in generating of reports encircling branch employees. The clew dept_no is to-boot built automatically from the board and the renunciation is built on the dept_call unique_value shaft (Coronel & Morris., 2016). The axiomsbase is optimized restraint vindication. Similarly, the board is scaltelling in that it can stock the exoteric knowledge encircling the branchs and to-boot to compose restraintthcoming assemblage expansions. A undivided-to-numerous interdependence is customary betwixt the branch and employees and directors past the branch can bear numerous employees and directors at the identical spell.
Board “dept_emp”
This board is a coalition board that is telling to deeptenance a numerous-to-numerous interdependence betwixt dept_emp and the branchs. The deep rationale is that a branch is implyd of at last undivided to numerous employees. Further, an employee can be in divergent branchs at divergent spells and at spells they can suit to divergent branchs abetting. The board implys of span pristine clews which embrace the employee_ID and the dept_no. Similar to antecedent boards, the board can compose as abundantly knowledge as feasible restraint exoteric and restraintthcoming interpretation.
Board “managers”
Just as the antecedent boards, the directors board is built to deeptenance a numerous-to-numerous interdependence betwixt departments and employees. The board has the identical texture as the dept_emp board where it’s implyd of span pristine clews. Additionally, a director is segregate of the assemblage employees’ and thus has to bear an employee ID sum. Further, the director can be legal restraint managing a unfailing branch and the employees among that branch. Further, the board is to-boot scaltelling to compose restraintthcoming changes.
Board “positions”
The positions board creates a undivided-to-numerous interdependence betwixt employees and positions. An employee can bear numerous positions at divergent spells or abetting. Here, a positions archives refers to a one employee through the pristine clew Employee_ID.
Board “salaries”
Identical to the Positions board, the salaries board has a undivided-to-numerous interdependence with the employees board. The deep infer aback this enhancement is that an employee can bear divergent payments with spell as they stir in their ranks or as their business assort changes.
Conclusively, the development supposing to-boot offers the turn restraint restraintthcoming advancement on the axiomsbase development. Restraint development, the boards can be adjusted to compose employee knowledge such as employee phundivided sums, their gregarious safety sums, and abundantly over. Further, functionalities such as Add, Delete, and Update becomes easier to complete when the axiomsbase is regular is this legislation (Elmasri & Navathe, 2010).
References
Coronel, C., & Morris., S. (2016). Database systems: intent, implementation, & address. Cengage Learning.
Elmasri, R., & Navathe, S. (2010). Fundamentals of axiomsbase systems. Addison-Wesley Publishing Assemblage.