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 streamlined 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 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 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 5 entities of the personnel
database solution. Document each step of the process and justify your
assumptions in the process.
Diagram at least 5 possible entities that will be required to
sustain a personnel solution. The diagram should include the following:
Note: The graphically depicted solution is not included in the required page length.