Database Modeling and Normalization



Database Modeling and Normalization

Entity - Relationship Diagram

The below is the Entity relationship diagram that can be used by the human resource department in order to manage their system effectively. Boyce - Codd normal form is utilized for the purpose of normalizing the database (PATTON, 2009, pp. 12-35).

Fig 1: HR database ER diagram

Database Design

Fig 2: Table Description

Fig2: Table Description (continued)

Fig 3: Table Description (continued)

Fig 4: Table Description (continued)

Fig 5 Table Description (continued)



Data Flow Diagrams

The below is the data flow diagram that clarifies and shows information movement in the system. The preliminary examination of the system leads to the subsequent situation level flow diagram data (BRUZA, 1989, pp. 107-115).

Fig6 Level 0 DFD

Further analysis led to the following level -1 data flow diagram fragments.

Fig7 Level 1 DFD fragments

Fig8 Level 1 DFD fragments

Fig 9: Level 1 DFD

The level 1 DFD can be further refined to the following level 2 DFDs



Fig 10 Level 2 DFD



Fig 11 Level 2 DFD

The subsequent picture shows the scenario of the “Admin” module. The module of Admin allows the management in order to perform the main functions as it is defined by the Requirements Analysis (ALLEN, 2004, pp. 58-86):

Entrance into information of Logs to verify the data of usage.

Managing Users Account.

Carry out searching.

Complaints of the Service users.

Fig 12 Use Case diagram for the “Admin” moduleThe “Admin” module Use - Cases have control flows as depicted

Fig 13 Activity Diagram for “Manage access rights”

Fig 14 Activity diagram for complaint servicing

System and Program Listing

The coding for the “Admin” module for the HR Intranet Portal has been based on the following logical Approach :- Four main use-cases have been designed by which the administrator can manage the user access to the portal (PATTON, 2009, pp. 12-35) :-

Create Employee Roles - User roles are created according to the categories the employees have in the organization.

Create Modules Framework - A hierarchical structure is created for storing the HR main-modules and sub-modules.

Assign Applications to Roles - Administrator assigns the various application modules accessible to respective roles.

Assign Employees to Roles -- The Employees are assigned to the respective roles to which they belong.

Use Case 1 :- Create Employee Roles

Primary Actors :- Administrator

Stake Holders & Interests :

Organization :- Needs specific access to be given for the portal to each employee group.

Administrator :- Creates specific roles for employee's access to the portal.

Preconditions :- Administrator is authorized and identified.

Success Guarantee :-

The roles have been created for the system access.

Roles are deleted if required.

Basic Flow :-

Administrator adds new role to the system.

The role is saved in the database.

Administrator logs out.

Exceptions :-

1.a) Administrator deletes a role from the system

1) Administrator selects the role to be deleted.

2) System checks for sub roles and denies deletion if any exist.

3) System deletes the role, updates the changes in database and informs administrator.

1.b) Administrator views the existing roles

1) System fetches and displays the roles from database along with the applications assigned to the role.

Use Case 2 :- Create Modules Framework

Primary Actors ...