HR Synopsis (No DFD)

HUMAN RESOURCE MANAGEMENT SYSTEM
Table of Contents
1. TITLE OF THE PROJECT..............................................................................................1
2. INTRODUCTION AND OBJECTIVES OF THE PROJECT............................................1
2.1 INTRODUCTION.........................................................................................................1
2.2 OBJECTIVES................................................................................................................1
3. PROJECT CATEGORY..................................................................................................2
4. ANALYSIS.........................................................................................................................2
4.1EXISTING SYSTEM.....................................................................................................2
4.2 PROPOSED SYSTEM..................................................................................................3
4.3 DATA FLOW DIAGRAMS..........................................................................................4
4.4 ER DIAGRAM..............................................................................................................6
4.5 STRUCTURE OF THE MODULE.............................................................................7
.............................................................................................................................................7
5. COMPLETE STRUCTURE................................................................................................8
5.1 MODULES AND THEIR DESCRIPTIONS................................................................8
5.2 DATA STRUCTURE OF THE MODULES...............................................................10
5.3 PROCESS LOGIC FOR ALL MODULES.................................................................19
5.4 TESTING PROCESS TO BE USED...........................................................................20
5.5 REPORT GENERATION...........................................................................................21
6. TOOLS/PLATFORM, HARDWARE AND SOFTWARE REQUIREMENT
SPECIFICATION..................................................................................................................22
6.1 TOOLS AND PLATFORM.........................................................................................22
6.2 SOFTWARE REQUIREMENT SPECIFICATIONS.................................................23
7. ARE YOU DOING THIS PROJECT FOR ANY INDUSTRY/CLIENT?.......................26
8. FUTURE SCOPE AND FURTHER ENHANCEMENT OF THE PROJECT.................26
9.BIBLIOGRAPHY...............................................................................................................26
1
IGNOU BCA PROJECT PROPOSAL 2021
1. TITLE OF THE PROJECT

.
2. INTRODUCTION AND OBJECTIVES OF THE PROJECT

2.1 INTRODUCTION
The Project “HUMAN RESOURCE MANAGEMENT SYSTEM” (HRIMS) is based on

the idea of making the HR department Web-enabled. It is necessary to have a system like
HRMS, which processes all the activities of HR department online. The “Human Resource
Management System” is very useful for the company by integrating all the activities under
one umbrella. It mainly concentrates on HR administration, Leave application, Attendance,
Duty scheduling, Mailing system and a host of other forms which are used in the day to day
working of an organization.
2.2 OBJECTIVES
The objectives of the Human Resource Management System by tracking the process of
creation of duties and Jobs, which will be accessible all over the world.
HRIMS has been developed using a number of modules comprising of the following:-
1. Administration
2. Mailing System
3. Attendance Management
4. Leave Processing
5. Scheduling Of Duties
6. Discussion Forum
7. Payroll
2
3. PROJECT CATEGORY
A Relational Database Management System (RDBMS) is a Database Management System

(DBMS) that is based on the relational model as introduced by E. F. Code. Most popular
commercial and open source databases currently in use are based on the relational model.
RDBMS store the data into collection of tables, which might be related by common fields.
RDBMS also provide relational operators to manipulate the data stored into the database
tables. Most RDBMS use SQL as database query language.
4. ANALYSIS
System development is having two major components: System analysis and System design.
System analysis is the process of collecting and interpreting facts, understanding problems
and using the information to suggest improvements on the system. This will help to
understand the existing system and determine how computers make its operation more
effective.
4.1EXISTING SYSTEM
The existing system is manually operated. Administration of a large Organization is a very

tedious and time consuming task. The existing mailing system is not fully efficient, as the
manager has to inform each and every person by using the common notice board. There is
no way to acknowledge the information. Individually informing a particular employee is not
possible, especially in large organization. The existing attendance management was by
keeping a muster roll at the manager’s cabins. The employee has to go to the manager’s
office and has to wait for signing it. The leave processing was done mainly on paper and
individually submitted in the existing system.
Problems with the Existing Manual System.
1) Reports could not be prepared in time.
2) Calculations were sometimes found incorrect, that caused accumulating problems.
3) Use and maintenance of paper files, registers and other written matter was very
difficult.
3
4) Security of the system depends on the persons dealing with it.

5) Searching of information was time consuming.
6) More man power required.
7) Data verification and validation was required.
4.2 PROPOSED SYSTEM
Proposed System
The proposed system is completely online. It is designed to meet all the disadvantage of the
existing system. In order to overcome the drawbacks of the existing system, it was decided
to create better use interface and databases, which are integrated, reliable, consistent,
flexible and secure.
HR administration module is connected with whole administration of the organization. In

the proposed system there will be a module that will be devoted entirely to the
administration side, which will be accessible only to the administrator.
HR mailing module has a mailing facility by which whenever an employee logs in to the
system any mails that he has received will be made available to him or her. The
management has the facility to send the mail to every person at the click of a button.
Attendance module provides the facility for the employees to mark their attendance online
so that they can avoid the affair of going into the manager’s office and waiting to sign the
muster role. The management on the other side has the facility of generating the reports
regarding the attendance of each and every employee at the mere click of a button.
Leave processing module provides the proposed system also has the facility for the
employees to apply for leave online. The leave application will be send to the HR manager.
If the HR manager approves the leave the employee will be notified automatically and
corresponding changes will be made into the attendance database.
Advantages of Proposed System
4
1) The manager or the administrators can view of access the information virtually from
anywhere in the firm.
2) The managers have the flexibility of providing to the employee with all that material
and information that is necessary.
3) The employee can gain on hand information on which he need to get scheduled.
4) The information can be managed in a standardized database, which can always serve
the process of search much easier and faster.
4.3 DATA FLOW DIAGRAMS
5
6
7
8
9
10
11
4.4 ER DIAGRAM
12
4.5 STRUCTURE OF THE MODULE
Administrator Head Employee
Add Employee View Employee Details View & Edit Personal Details
Create Department View Module View Official Details
Create Section View Duty Add Attendance
CreateDesignation Duty Scheduling View Module
Add Head for Department Job Scheduling View Duty
Send Questions
Create Duty Attendance Report
Check mail
Create Module Leave ReportView&
Send messages
View&Edit Discussion Forum View Job
Create Job Create Salary details
Leave Report
Attendance Report Leave Request
View&Edit Discussion Forum
Provide Job
View Salary
View & Send messages View & Send messages
Edit Questions
Check Attendance
View&Edit Discussion Forum
SanctionSalary
13
5. COMPLETE STRUCTURE
5.1 MODULES AND THEIR DESCRIPTIONS
The “Human Resource Management System” is meant as a system which helps the
management of a large organization. This system is meant to help the management in the
administration of an organization which will be accessible to the employees of the
organization.
MODULES OF THE PROGRAM
The system as a whole can be divided into different modules among which the important
ones are:
 Administration
 Mailing System
 Attendance Management
 Leave Processing
 Scheduling of Duties
 Discussion Forum
 Payroll
There Are Mainly Three Types of Users: -
 Administrator
 Head
 Employee
The Administrator part is done by the Administrator. The Head part is done by the Head
and its report is viewed by the Administrator. The Employee part is performed by the
Employee and its reports are viewed by the Head.
MODULES AND DESCRIPTIONS
1.Administration
This module forms the main part of administration of the entire system. This module is
concerned with the whole administration of the organization. The HR manager will be
having many responsibilities like making an employee know about his/her duties, or inform
him/her about my change in the earlier assigned activities. This module is devoted entirely
to the administration side, which will be accessible only to the administrator.
14
2. Mailing System
There may be many notifications that will have to be send to the employees time after time.
It will be very difficult for the management to inform each and every person about the
notification personally. If the notice is displayed on a common notice board changes are
there that some may not see the notice. To overcome this limitation this module deals with a
mailing facility by which whenever an employee logs in into the system any mails to every
one at the click of a button.
3. Attendance Management
The attendance of the employees will have to be carefully monitored. The proposed system
has the facility for the employees to mark their attendance online so that they can avoid the
affair of going into the manager’s office and waiting to sign the muster roll. The
management on the other side will have the facility of generating the reports regarding the
attendance of each and every employee at the mere click of a button.
4. Leave Processing
The proposed system also has the facility for the employees to apply for leave. The leave
application will be send to the HR manager. If the HR manager approves the leave the
employee will be notified automatically and corresponding changes will be made into the
attendance database.
5. Scheduling of Duties
The management may assign many additional duties to any one of the employees has and
when the need arises. This scheduling of duties has to be made known to the employees so
that they may come prepared. In the proposed system there will be a section, which will
help the employees to know about the new scheduling. The management will only have to
post a new schedule to the concerned employee instead of calling and telling him
personally.
6. Discussion Forum
The technical knowhow of a company is open to the public discussion section. Employee
can post any questions on subjects who the company is excelled in the Discussion Forum
and get their query replies either from the Employee or from the Administrator.
15
7. Payroll
The payroll module allows the administrator to perform various functions related to the
salary of employees, such as adding salary details, HRA, PF, LIC, Incentives, Gratuity and
DA on the basis of employee ID for a specified month.
5.2 DATA STRUCTURE OF THE MODULES
1. Official
Constraint Name Type Reference Table (If any) Remark
Emp_id Employee
Desig_id Primary Designation Unique id to this
Dept_id Key Department table
Section_id Section
Column Name Data Type Size Unique Not Null Description
Emp_id Varchar 15 Yes Yes Employee ID
Desig_id Varchar 50 Yes Yes Designation ID
Dept_id Varchar 50 Yes Yes Department ID
Section_id Varchar 30 Yes Yes Section ID
2. Administrator
Admin_id Primary Unique id to this

Key table
Admin_id Int 4 Yes Yes Administrator ID
Login Varchar 50 Yes Yes Login
Password Varchar 50 Yes Yes Password
16
3. Employee_Details
Emp_id Primary Unique id to this

Key table
Emp_name Varchar 50 Yes Yes Employee Name
password Varchar 50 Yes Yes Password
Address Varchar 60 Yes Yes Address
State Varchar 20 Yes Yes State
Country Varchar 20 Yes Yes Country
Pin Numeric 6 Yes Yes Pin code
DOB Datetime 10 Yes Yes Date of Birth
Age Int 2 Yes Yes Age
Sex Varchar 6 Yes Yes Sex
E-Mail Varchar 30 Yes Yes E-Mail
Phone Numeric 15 Yes Yes Phone Number
Mobile Numeric 15 Yes Yes Mobile Number
Martial_stat Varchar 20 Yes Yes Martial status
Edu_qualification Varchar 50 Yes Yes Educational Qualification
Skill Varchar 50 Yes Yes Skills in which subject
Photo Varchar 50 Yes Yes Passport size photo

Joining_date Datetime 10 Yes Yes Date of Joining
Retirement _date Datetime 10 Yes Yes Date of Retirement
Experience Varchar 50 Yes Yes Previous Experience
Prev_employer Varchar 50 Yes Yes Previous employer
Status Varchar 20 Yes Yes Present Status
Desig_id Primary Unique id to this
17
Key table
Desig_name Varchar 50 Yes Yes Designation Name
Basic_Sal Numeric 6 Yes Yes Basic Salary
4. Designation
5. Salary
Salary_id Primary Unique id to this table

Key
Salary_id Varchar 15 Yes Yes Salary ID
Basic_sal Numeric 6 Yes Yes Basic Salary
HRA Numeric 6 Yes Yes Housing Rent Allowance
DA Numeric 6 Yes Yes Dearness Allowance

TA Numeric 6 Yes Yes Travelling Allowance
Incentive Numeric 6 Yes Yes Incentives
Gratuity Numeric 6 Yes Yes Special Allowance
PF Numeric 6 Yes Yes Provident Fund
LIC Numeric 6 Yes Yes Life Insurance
6. Department
Dept_id Primary Unique id to this table

Key
Dept_name Varchar 50 Yes Yes Department Name
Dept_head Varchar 50 Yes Yes Department Head
18
Tot_Emp Int 4 Yes Yes Total No. of Employees
7. Section
Section_id Primary Unique id to this table

Key
Dept_id Foreign Department
Key
Section _id Varchar 30 Yes Yes Section ID
Section _name Varchar 50 Yes Yes Section Name
Section _head Varchar 50 Yes Yes Section Head
Tot_Emp Int 4 Yes Yes Total No. of
Employees
8. Section_Department
Section_id Section Unique id to this table

Dept_id Primary Department
Key
Section_id Varchar 30 Yes Yes Section ID
9. Duty
Duty_id Primary Unique id to this table

Key
Duty_id Varchar 15 Yes Yes Duty ID
Duty_Name Varchar 100 Yes Yes Name of the Duty
19
Tot_modules Int 4 Yes Yes Total No. of Modules

Cdate Datetime 10 Yes Yes Current Date
Start_date Datetime 10 Yes Yes Date at which duty

start
End_date Datetime 10 Yes Yes Date at which duty
ends
Exp_Sdate Datetime 10 Yes Yes Expected start date
Exp_Edate Datetime 10 Yes Yes Expected end date
Duration Int 4 Yes Yes Duration of Duty
Status Varchar 20 Yes Yes Present Status
10. Duty _Department
Duty_id Primary Duty

Unique id to this table
Dept_id Key Department
11. Duty_Schedule
DSchedule_id Primary Unique id to this table

Key
Emp_id Foreign Employee
Key
Duty_id Foreign Duty
Key
DSchedule_id Varchar 15 Yes Yes Duty Schedule ID
Schedule_date Datetime 10 Yes Yes Date of Schedule
20
Start_date Datetime 10 Yes Yes Starting date

End_date Datetime 10 Yes Yes Ending date
Status Varchar 20 Yes Yes Present status
12. Module
Module_id Primary Unique id to this table

Key
Module_id Varchar 15 Yes Yes Module ID
Module_name Varchar 15 Yes Yes Name of the module
Tot_jobs Int 4 Yes Yes Total No. of Jobs
DSt_date Datetime 10 Yes Yes Date at which duty starts
DE_date Datetime 10 Yes Yes Date at which duty ends
13. Duty_Module
Duty_id Primary Duty

Module_id Key Module
14. Job
Job_id Primary Unique id to this table

Key
21
Job_id Varchar 15 Yes Yes Job ID

Job_name Varchar 50 Yes Yes Name of the Job
MSt_date Datetime 10 Yes Yes module starting date
ME_date Datetime 10 Yes Yes module ending date
Jexps_date Datetime 10 Yes Yes Excepted start date of job
Jexpe_date Datetime 10 Yes Yes Excepted end date of job
15. Module_Job
Job_id Primary Job

Module_id Key Module
Job_id Varchar 15 Yes Yes Job ID
16. Leave_Apply
Leave_id Primary Unique id to this table

Key
Leave_id Varchar 15 Yes Yes Leave ID
Leavetype_id Varchar 15 Yes Yes Type of Leave ID
Purpose Varchar 50 Yes Yes Purpose/reason of
leave
From_date Datetime 10 Yes Yes Which date leave start
To_date Datetime 10 Yes Yes Which date leave ends
Tot_Leave_days int 2 Yes Yes Total number of
22
leaves
Sugg_user Varchar 50 Yes Yes The person who takes
over the charge
Cdate Varchar 10 Yes Yes Current Date
17. Leave_Type
Leavetype_id Primary Unique id to this table

Key
Leavetype_id Varchar 15 Yes Yes Type of Leave ID
Halfday_leave Varchar 15 Yes Yes Half day leave
Compensate_leave Varchar 15 Yes Yes Compensate leave
Sick_leave Varchar 15 Yes Yes Sick leave
Casual_leave Varchar 15 Yes Yes Casual leave
Tot_leave Varchar 15 Yes Yes Total leave
Year Varchar 15 Yes Yes Present year
18. Attendance
Username User Name Unique to this table

Cdate Primary Current Date Unique to this table
Key

Username/empid Varchar 50 Yes Yes User Name
Cdate Datetime 10 Yes Yes Current Date
23
Login_time Datetime 10 Yes Yes Login time

Logout_time Datetime 10 Yes Yes Logout time
19. Job_Schedule
Schedule_id Primary Key Unique id to this table

Emp_id Foreign Key Employee
Module_id Foreign Key Module
Section_id Foreign Key Section
Schedule_id Varchar 50 Yes Yes Job Schedule id
Emp_id Varchar 15 Yes Yes Employee id
Module_id Varchar 50 Yes Yes Module id
Section_id Varchar 30 Yes Yes Section id
20.Mail
Mail_id Primary Unique id to this

Key table
Mail_id Varchar 15 Yes Yes Mail ID
Sender Varchar 20 Yes Yes Name of Sender
Receiver Varchar 20 Yes Yes Name of Receiver
Subject Varchar 20 Yes Yes Subject of Message
Message Varchar 10 Yes Yes Content of Message
24
Cdate Datetime 10 Yes Yes Current date
Ctime Datetime 10 Yes Yes Current time
5.3 PROCESS LOGIC FOR ALL MODULES

Login
 Enter Username and password.
 Access denied if invalid username or password.
Administrator
 Appoints head
 Appoints employee
 Creates new department
 Create new designation
 Assigning duty
 Check attendance
 Answer Questions
Mail
 Check username
 Check mail id
 View message
 Compose message
 Access denied if invalid user
Attendance
 Check mail id
 Login
 Logout
 Mark leave
 View attendance reports
Leave
 Apply leave
 Check the leave account
 Nature of leave
25
 Sanctioning/Rejecting of leave
 Charge hand over to another person
 View leave reports
Duty Scheduling
 Assign duty
 Duty divided into module
 Module divided into job
 Assign jobs to different persons
 Check the time scheduling
Discussion Forum
 View Questions
 Analyze different Questions
 Compose the answers
5.4 TESTING PROCESS TO BE USED.
Testing is the process of executing a program with the intent of finding the errors. In each
phase of the development, the process will be specific input and specific output. Once the
project is confirmed to start the phases of the development of project can be divided into the
following phases:
Software requirement phases
Software design
Implementation
Testing
Maintenance
Unit Testing
Unit testing refers to tests that verify the functionality of a specific section of code, usually
at the function level. In an object-oriented environment, this is usually at the class level, and
the minimal unit tests include the constructors and destructors
System Testing
System testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the system's compliance with its specified requirements. System testing
26
falls within the scope of black-box testing, and as such, should require no knowledge of the
inner design of the code or logic. As a rule, system testing takes, as its input, all of the
"integrated" software components that have passed integration testing and also the software
system itself integrated with any applicable hardware systems. The purpose of integration
testing is to detect any inconsistencies between the software units that are integrated
together (called assemblages) or between any of the assemblages and the hardware. System
testing is a more limited type of testing; it seeks to detect defects both within the "inter-
assemblages" and also within the system as a whole.
Integration Testing
Integration testing is performed to test make sure that everything, functions correctly and
runs smoothly when all modules are grouped together. Software is the integrated collection
of all modules. Modules interact with each other by calling each other’s functions using
interfaces. A module can use data generated by another module. A complete action works
only when all the modules integrated together work properly. The purpose of integration
testing is to test the interface compatibility between the various modules in the software.
5.5 REPORT GENERATION

The following are the reports generated in the system.
 Employee details
 Duty details
 Attendance details
 Leave applications
 Leave
6. TOOLS/PLATFORM, HARDWARE AND SOFTWARE

REQUIREMENT SPECIFICATION
6.1 TOOLS AND PLATFORM
27
HRIMS uses .NET platform for design and Microsoft SQL Server as RDBMS.
.NET allows applying common skills across a variety of devices, application types, and
programming tasks. It enables integration with other tools and technologies to build the
right solution with less effort and time. Microsoft SQL Server is a computer application
used to create desktop, enterprise, and web-based database systems. It is used at different
levels and with various goals.
 Windows Operating System
 Front-end: Asp.Net 4.5 with c #
 Back-end: SQL Server 2014
Front-End: Asp.net 4.5 with c #

ASP.NET
ASP.NET is a Web application framework developed and marketed by Microsoft to allow
programmers to build dynamic Web sites, Web applications and Web services. It was first
released in January 2002 with version 1.0 of the .NET Framework, and is the successor to
Microsoft's Active Server Pages (ASP) technology.
Back-End: SQL Server 2014
SQL Server 2014 Express Edition is an powerful and reliable date management system that
delivers a rich set of features, data protection, and performance for embedded application
client, light web applications, and applications, and local data stores.
6.2 SOFTWARE REQUIREMENT SPECIFICATIONS
The Software Requirements Specification is produced at the culmination of the analysis

task. The function and performance allocated to software as part of system engineering are
refined by establishing a complete information description, a detailed functional description,
a representation of system behavior, and indication of performance requirements and design
constrains, appropriate validation criteria and other information pertinent to requirements.
Below are the S/W requirements specification to manage HRIMS.
The software, HRIMS which is designed for administrating & automating all the major
activities that are carried out in the HR department to increase the efficiency of the system
in order to provide better service to customers.
28
2.6.1 INTRODUCTION
Purpose :
The purpose of this project is to develop a secured human resource management system
with the following objectives:
 A lot of manual work which is time consuming and tedious can be reduced.
 Eliminates wrong entries and hence give accurate report.
 Reduce paper work and extra cost.
 Data redundancy can be avoided.
 Data security.
 Information retrieval is faster.
 User friendliness.
 Flexibility.
 The number of registers can be reduced.
 The new system provides data consistency and integrity so that data at any time
represent the current status.
 The system should provide better security and control over data.
Scope:
This document is meant for use by the developers and will be the basic during testing phase.
Any changes made to the requirements in the future will have to go through formal change
approval process.
The developer is responsible for:

Developing the system, this meets the SRS and solving all the requirements of the system.
 Demonstrating the system and installing the system at client's location after
the acceptance testing is successful.
 Submitting the required user manual describing the system interfaces to work
on it and also the documents of the system.
 Conducting any user training that might be needed for using the system.
 Maintaining the system for a period of one year after installation.
Developer Responsibilities Overview:

The developer is responsible for:
29
 Developing the system,which meets the SRS and solving all the requirements
of the system.
 Demonstrating the system and installing the system at client’s location after
the acceptance testing is successful.
 Submiting the required user manual describing the system interfaces to work
on it and also the documents of the system.
 Conducting any user training that might be needed for using the system.
 Maintaining the system for a period of one year after installation.
References:
 IBM sample SRS format.
 IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
Specifications.
2.6.2 GENERAL DESCRIPTION
Product Functions Overview:

The HRMS has a number of customers with each having different duties. The main
objective of the system is to automate the major activities involved in HR department. This
module automates the transaction process between the Employees and Administrators
through a 100% online solution. It also maintains a record of employee’s details, duty
creation, module creation, job creation, job assignment etc.
User Characteristics:
The main users of the system will be Employees. HR department will be familiar with the
computer based system as training is given to them. Admin staff will also be familiar with
computers for basic day to day account maintenance. Employees will be familiar with basic
operation of the computer.
2.6.3 SPECIFIC REQUIREMENTS
Functional Requirements:
Inputs:
The major inputs for HRIMS can be categorized module wise. Basically, all the
information is managed by the software and in order to access the information one has to
30
produce one's identity by entering the username and password. Every user has his/her own
domain of access beyond which the access is dynamically refrained rather denied.
Output:
The major outputs of the system are tables and reports. Tables are created dynamically to
meet the requirements on demand. Reports, as it is obvious, carry the gist of the whole
information that flows across the institution. This application must be able to produce
output at different modules for different inputs.
Performance Requirements:
Performance is measured in terms of reports generated.
2.6.4. HARDWARE SPECIFICATIONS

Processor : Intel i3 core
RAM :4GB
Hard Disk : 500 GB
Keyboard : Standard Keyboard
Mouse : Standard Mouse
2.6.5. SOFTWARE SPECIFICATIONS
OS : Windows 7
Front-End : Asp.net 4.5 with c#
Back-End : SQL Server 2014
Web Server : IIS 10.0
Web Browser : Internet Explorer, Google Chrome
Technical Specifications
Technical specifications are typically written by the developers and coders, and describe
how they will implement the project. The developers work from the functional
specifications, and translate the functions into their actual coding practices and
methodologies.
7.ARE YOU DOING THIS PROJECT FOR ANY

INDUSTRY/CLIENT?
NO
31
8. FUTURE SCOPE AND FURTHER ENHANCEMENT OF

THE PROJECT
One of the main features of the web technology is its extensibility. The Human Resource
Management System is a complete system as per the user requirement. But it is obvious that
the user requirements will change in future as the environment changes.
The word of computers is not always static. It is always subject to change. The software too
has to mold to suit the requirements of the future. The system is open to reasonable changes
and these changes can be brought about very easily. But drastic changes like changes in the
processing flow, changes in system functioning etc may not be able to accommodate in the
existing system. It can be strongly said that the system has a fair scope for future
development that doesn’t affect the process flow severely.
9.BIBLIOGRAPHY
1. Systems Analysis and Design

Galgotia Publications (P) Ltd
 Elias M. Awad
2. Software Engineering – A Practitioner’s Approach
McGraw-Hill International Edition
 Roger S Pressman
32

HR Synopsis (No DFD)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HR Synopsis (No DFD)

Uploaded by

Copyright:

Available Formats

HUMAN RESOURCE MANAGEMENT SYSTEM

1. TITLE OF THE PROJECT

HUMAN RESOURCE MANAGEMENT SYSTEM

2. INTRODUCTION AND OBJECTIVES OF THE PROJECT

The Project “HUMAN RESOURCE MANAGEMENT SYSTEM” (HRIMS) is based on

A Relational Database Management System (RDBMS) is a Database Management System

The existing system is manually operated. Administration of a large Organization is a very

4) Security of the system depends on the persons dealing with it.

4.2 PROPOSED SYSTEM

HR administration module is connected with whole administration of the organization. In

Advantages of Proposed System

4.3 DATA FLOW DIAGRAMS

4.5 STRUCTURE OF THE MODULE

HUMAN RESOURCE MANAGEMENT SYSTEM

Administrator Head Employee

Create Department View Module View Official Details

Create Section View Duty Add Attendance

CreateDesignation Duty Scheduling View Module

Add Head for Department Job Scheduling View Duty

View&Edit Discussion Forum

MODULES AND DESCRIPTIONS

5.2 DATA STRUCTURE OF THE MODULES

Constraint Name Type Reference Table (If any) Remark

Constraint Name Type Reference Table (If any) Remark

Admin_id Primary Unique id to this

Constraint Name Type Reference Table (If any) Remark

Emp_id Primary Unique id to this

Skill Varchar 50 Yes Yes Skills in which subject

Photo Varchar 50 Yes Yes Passport size photo

Constraint Name Type Reference Table (If any) Remark

Desig_id Primary Unique id to this

Constraint Name Type Reference Table (If any) Remark

Salary_id Primary Unique id to this table

DA Numeric 6 Yes Yes Dearness Allowance

Constraint Name Type Reference Table (If any) Remark

Dept_id Primary Unique id to this table

Tot_Emp Int 4 Yes Yes Total No. of Employees

Constraint Name Type Reference Table (If any) Remark

Section_id Primary Unique id to this table

Constraint Name Type Reference Table (If any) Remark

Section_id Section Unique id to this table

Constraint Name Type Reference Table (If any) Remark

Duty_id Primary Unique id to this table

Tot_modules Int 4 Yes Yes Total No. of Modules

Start_date Datetime 10 Yes Yes Date at which duty

Status Varchar 20 Yes Yes Present Status

10. Duty _Department

Constraint Name Type Reference Table (If any) Remark

Duty_id Primary Duty

Constraint Name Type Reference Table (If any) Remark

DSchedule_id Primary Unique id to this table

Start_date Datetime 10 Yes Yes Starting date

Constraint Name Type Reference Table (If any) Remark

Module_id Primary Unique id to this table

DE_date Datetime 10 Yes Yes Date at which duty ends

Status Varchar 20 Yes Yes Present status

Constraint Name Type Reference Table (If any) Remark

Duty_id Primary Duty

Constraint Name Type Reference Table (If any) Remark

Job_id Primary Unique id to this table

Job_id Varchar 15 Yes Yes Job ID

ME_date Datetime 10 Yes Yes module ending date