Components which would be required to hold time

This preview shows page 4 - 7 out of 17 pages.

Components which would be required to hold time-variant data for policy enforcement and training management can be reviewed with multivalued, valued previously and current val- ued categories. The time-variant data has attributes which can change in value. Some examples
Database Monitoring and Normalization Page 5 include email addresses, phone numbers and home addresses to name a few. Other time-variant data would stay the same and will only have one value. Examples include social security number and birthdate. There are two values defined for time-variant data. These include the current entity which allows for the new value attributes and values which include the primary key, previous value data and data history (Nordmark, S., Zingmark, K. and Lindberg, I. 2016, p. 48). Please re- view the example in Appendix F for clarity. The First Normal Form (1NF) can be defined as the collection of all the related columns in the table. There are no repeated groups within the tables as this would run incorrect results. Primary keys must be loaded to their locations and each column is assigned a special value which cannot be null. The Second Normal Form (2NF) is the second step in the normalization process and can be built on the 1NF. 1NF tables can be placed into 2NF form as long as all prime attributes are dependent on the candidate key (Lindell, S. 2008, p. 208). The Third Normal Form (3NF) is the third step in normalization of the database and builds upon 1NF and 2NF. 3NF should only contain foreign key columns and used as reference to other tables. No other columns from the parent table would be allowed in the referenced table (p. 215). Appendix G shows the diagram of five possible entities that are required to sustain a personnel solution. The diagram in- cludes the dependency diagram and the multivalued dependencies. This study has determined the steps in the development of an effective Entity Relation- ship Model (ERM) diagram and has determined the possible iterative steps or factors that one must consider in the building processes. Special consideration was paid to the human resources core functions and responsibilities of the client. Next, an analysis of the risks that would occur if any of the developmental or iterative steps in creating an ERM diagram were not performed. A selection of five entities that was required for the development of the data repositories was in-
Database Monitoring and Normalization Page 6 cluded. This study specified the components that were required to hold time-variant data for pol- icy enforcement and the training of the management team. A 1:M diagram solution was provided that held the following categories for each employee: salary history, data, job history and training history.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture