Description
Imagine that you work for a consulting firm that offers information technology and database services. Part of its core services is to optimize and offer streamline solutions for efficiency. In this scenario, your firm has been awarded a contract to implement a new personnel system for a government agency. This government agency has requested an optimized data repository for its system which will enable the management staff to perform essential human resources (HR) duties along with the capability to produce ad hoc reporting features for various departments. They look forward to holding data that will allow them to perform HR core functions such as hiring, promotions, policy enforcement, benefits management, and training.
Using this scenario, write a three to four (3-4) page paper in which you:
- Determine the steps in the development of an effective Entity Relationship Model (ERM) Diagram and determine the possible iterative steps / factors that one must consider in this process with consideration of the HR core functions and responsibilities of the client.
- Analyze the risks that can occur if any of the developmental or iterative steps of creating an ERM Diagram are not performed.
- Select and rank at least five (5) entities that would be required for the development of the data repositories.
- Specify the components that would be required to hold time-variant data for policy enforcement and training management.
- Diagram a possible 1:M solution that will hold salary history data, job history, and training history for each employee through the use of graphical tools. Note: The graphically depicted solution is not included in the required page length.
- Plan each step of the normalization process to ensure the 3NF level of normalization using the selected five (5) entities of the personnel database solution. Document each step of the process and justify your assumptions in the process.
- Diagram at least five (5) possible entities that will be required to sustain a personnel solution. The diagram should include the following:
- Dependency diagrams
- Multivalued dependencies
Note: The graphically depicted solution is not included in the required page length.
Your assignment must follow these formatting requirements:
- Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.
- Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.
- Include charts or diagrams created in a drawing tool with which you are familiar. The completed diagrams / charts must be imported into the Word document before the paper is submitted.
The specific course learning outcomes associated with this assignment are:
- Recognize the historical development of database management systems and logical data models.
- Explain the fundamentals of how data is physically stored and accessed.
- Compose conceptual data modeling techniques that capture information requirements.
- Use technology and information resources to research issues in the strategic implications and management of database systems.
- Write clearly and concisely about topics related to the strategic planning for database systems using proper writing mechanics and technical style conventions
| Points: 120 |
Assignment 4: Database Modeling and Normalization |
|||
|
Criteria |
Unacceptable Below 70% F |
Fair 70-79% C |
Proficient 80-89% B |
Exemplary 90-100% A |
| 1. Determine the steps in the development of an effective Entity Relationship Model (ERM) Diagram and determine the possible iterative steps / factors that one must consider in this process with consideration of the HR core functions and responsibilities of the client.
Weight: 15% |
Did not submit or incompletely determined the steps in the development of an effective Entity Relationship Model (ERM) Diagram. Did not submit or incompletely determined the possible iterative steps / factors that one must consider in this process with consideration of the HR core functions and responsibilities of the client. | Partially determined the steps in the development of an effective Entity Relationship Model (ERM) Diagram. Partially determined the possible iterative steps / factors that one must consider in this process with consideration of the HR core functions and responsibilities of the client. | Satisfactorily determined the steps in the development of an effective Entity Relationship Model (ERM) Diagram. Satisfactorily determined the possible iterative steps / factors that one must consider in this process with consideration of the HR core functions and responsibilities of the client. | Thoroughly determined the steps in the development of an effective Entity Relationship Model (ERM) Diagram. Thoroughly determined the possible iterative steps / factors that one must consider in this process with consideration of the HR core functions and responsibilities of the client. |
| 2. Analyze the risks that can occur if any of the developmental or iterative steps of creating an ERM Diagram are not performed.
Weight: 10% |
Did not submit or incompletely analyzed the risks that can occur if any of the developmental or iterative steps of creating an ERM Diagram are not performed. | Partially analyzed the risks that can occur if any of the developmental or iterative steps of creating an ERM Diagram are not performed. | Satisfactorily analyzed the risks that can occur if any of the developmental or iterative steps of creating an ERM Diagram are not performed. | Thoroughly analyzed the risks that can occur if any of the developmental or iterative steps of creating an ERM Diagram are not performed. |
| 3. Select and rank at least five (5) entities that would be required for the development of the data repositories.
Weight: 10% |
Did not submit or incompletely selected and ranked at least five (5) entities that would be required for the development of the data repositories. | Partially selected and ranked at least five (5) entities that would be required for the development of the data repositories. | Satisfactorily selected and ranked at least five (5) entities that would be required for the development of the data repositories. | Thoroughly selected and ranked at least five (5) entities that would be required for the development of the data repositories. |
| 4. Specify the components that would be required to hold time-variant data for policy enforcement and training management.
Weight: 10% |
Did not submit or incompletely specified the components that would be required to hold time-variant data for policy enforcement and training management. | Partially specified the components that would be required to hold time-variant data for policy enforcement and training management. | Satisfactorily specified the components that would be required to hold time-variant data for policy enforcement and training management. | Thoroughly specified the components that would be required to hold time-variant data for policy enforcement and training management. |
| 5. Diagram a possible 1:M solution that will hold salary history data, job history, and training history for each employee through the use of graphical tools.
Weight: 15% |
Did not submit or incompletely diagramed a possible 1:M solution that will hold salary history, data, job history and training history for each employee through the use of graphical tools. | Partially diagramed a possible 1:M solution that will hold salary history data, job history and training history, for each employee through the use of graphical tools. | Satisfactorily diagramed a possible 1:M solution that will hold salary history data, job history, and training history for each employee through the use of graphical tools. | Thoroughly diagramed a possible 1:M solution that will hold salary history data, job history, and training history for each employee through the use of graphical tools. |
| 6. Plan each step of the normalization process to ensure the 3NF level of normalization using the selected five (5) entities of the personnel database solution. Document each step of the process and justify your assumptions in the process.
Weight: 20% |
Did not submit or incompletely planned each step of the normalization process to ensure the 3NF level of normalization using the selected five (5) entities of the personnel database solution. Did not submit or incompletely documented each step of the process and did not submit or incompletely justified your assumptions in the process. | Partially planned each step of the normalization process to ensure the 3NF level of normalization using the selected five (5) entities of the personnel database solution. Partially documented each step of the process and partially justified your assumptions in the process. | Satisfactorily planned each step of the normalization process to ensure the 3NF level of normalization using the selected five (5) entities of the personnel database solution. Satisfactorily documented each step of the process and satisfactorily justified your assumptions in the process. | Thoroughly planned each step of the normalization process to ensure the 3NF level of normalization using the selected five (5) entities of the personnel database solution. Thoroughly documented each step of the process and thoroughly justified your assumptions in the process. |
| 7a. Diagram at least five (5) possible entities that will be required to sustain a personnel solution. Include the dependency diagrams in your diagram.
Weight: 5% |
Did not submit or incompletely diagramed at least five (5) possible entities that will be required to sustain a personnel solution. Did not submit or incompletely included the dependency diagrams in your diagram. | Partially diagramed at least five (5) possible entities that will be required to sustain a personnel solution. Partially included the dependency diagrams in your diagram. | Satisfactorily diagramed at least five (5) possible entities that will be required to sustain a personnel solution. Satisfactorily included the dependency diagrams in your diagram. | Thoroughly diagramed at least five (5) possible entities that will be required to sustain a personnel solution. Thoroughly included the dependency diagrams in your diagram. |
| 7b. Diagram at least five (5) possible entities that will be required to sustain a personnel solution. Include multivalued dependencies in your diagram.
Weight: 5% |
Did not submit or incompletely diagramed at least five (5) possible entities that will be required to sustain a personnel solution. Did not submit or incompletely included multivalued dependencies in your diagram. | Partially diagramed at least five (5) possible entities that will be required to sustain a personnel solution. Partially included multivalued dependencies in your diagram. | Satisfactorily diagramed at least five (5) possible entities that will be required to sustain a personnel solution. Satisfactorily included multivalued dependencies in your diagram. | Thoroughly diagramed at least five (5) possible entities that will be required to sustain a personnel solution. Thoroughly included multivalued dependencies in your diagram. |
| 8. Clarity, writing mechanics, and formatting requirements
Weight: 10% |
More than 6 errors present | 5-6 errors present | 3-4 errors present | 0-2 errors present |
