01CE101 Nehal Adhikary
01CE102 Anuj Agarwal
01CE008 Rishi Bhilawadikar
Submitted in the partial fulfillment of the requirements of PROJECT II
for the award of
Bachelor of Engineering Degree
Under the guidance of
Mr. R.K.Shende (Internal Guide)
Mr.Pankaj Sharma (External Guide)
UNIVERSITY OF MUMBAI
RAMRAO ADIK INSTITUTE OF TECHNOLOGY, NAVI MUMBAI.
Design And Formulation
3.1 Entity – Relationship Diagram
Shown below is the E.R. Diagram for the Intranet HR portal database. The database is normalized to the Boyce - Codd normal form.
Fig 3.1.1: ER diagram for the Intranet HR portal database
3.2 Database Design
Fig 3.2.1: Table Description
Fig: 3.2.2: Table Description (continued)
Fig: 3.2.3: Table Description (continued)
Fig 3.2.4: Table Description (continued)
Fig 3.2.5: Table Description (continued)
3.3 Data Flow Diagrams
The following level 0 and level 1 and level 2 Data flow diagrams clarify the flow of information in the system.
Initial analysis of the system leads to the following context level data flow diagram.
Fig 3.3.1 Level 0 DFD
Further analysis led to the following level –1 data flow diagram fragments.
Fig 3.3.2: Level 1 DFD fragments
Fig 3.3.3 Level 1 DFD fragments
Fig 3.3.4: Level 1 DFD
The level 1 DFD can be further refined to the following level 2 DFDs
Fig 3.3.5 Level 2 DFD
Fig 3.3.6: Level 2 DFD
4.1 Conceptual and Task modeling
The Following Activity Diagram represents the control flow during user registration.
Fig 3.4.1: Activity diagram for user registration
Fig 3.4.2: Activity diagram for the Session Logging
The following Diagram depicts the usage scenario for “Admin” module. The “Admin” module enables the portal administrator in performing the following key administrative functions as defined in the Requirements Analysis:
1. Access Log information to determine usage statistics.
2. Manage User Accounts.
3. Perform Searches on various search strings.
4. Service user complaints.
Fig 3.4.3: Use Case diagram for the “Admin” module
The “Admin” module Use – Cases have control flows as depicted [pic]
Fig 3.4.4: Activity Diagram for “Manage access rights”
Fig 3.4.5: Activity diagram for “search” use-case
Fig: 3.4.6: Activity diagram for complaint servicing
4.1 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 :-
1) Create Employee Roles – User roles are created according to the categories the employees have in the organization. 2) Create Modules Framework – A hierarchical structure is created for storing the HR main-modules and sub-modules. 3) Assign Applications to Roles – Administrator assigns the various application modules accessible to respective roles. 4) 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...