0% found this document useful (0 votes)
113 views30 pages

Smart HR

This document provides an overview and outline of a project to develop a smart employee management system called SMART HR. It acknowledges contributions from guides and partners. It includes sections that will cover the existing system, objectives of the new system, core components, advantages and limitations, requirements gathering, users, and development approach including use cases, data dictionary, and Agile methodology.

Uploaded by

Aditya Raghvani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
113 views30 pages

Smart HR

This document provides an overview and outline of a project to develop a smart employee management system called SMART HR. It acknowledges contributions from guides and partners. It includes sections that will cover the existing system, objectives of the new system, core components, advantages and limitations, requirements gathering, users, and development approach including use cases, data dictionary, and Agile methodology.

Uploaded by

Aditya Raghvani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 30

SMART HR

A EMPLOYEE MANAGEMENT SYSTEM

Course Name : Software Project -2

Semester : MCA-4

Internal Guide : Dr. Urja Mankad


Group Number : 81
HIMALAY SAGPARIYA
2021004401110067 | B - 49
KINAARI PATEL
2021004401110055 | B - 23
ACKNOWLEDGEMENT

 It is our great pleasure to acknowledge the contribution and


assistance of a few individuals to this effort. We
acknowledge here our debt to those who have contributed
significantly to this project

 We are also indebted to our faculty members, guide Dr.


Urja Mankad and Mr. Dhaval Patoliya (Founder &
CEO of seven Infosystem) for motivating us and fostering
a feeling of belonging towards our abilities. Their helpful
solutions and comments were enriched by their experience
for the betterment of the project. We sincerely acknowledge
that without his support this project would not have been
feasible (possible).

 Special thanks to SEVEN INFOSYSTEM who gave us


this golden opportunity. Finally, we would like to thank
everyone who directly or indirectly helped us with the
project.
TABLE OF CONTENTS
1) Existing system
2) Need for the new system
3) Objective of the New System
4) Problem definition
5) Core Components
6) Project Profile
7) Assumptions and constraints
8) Advantages and Limitations of the Proposed System
9) Requirement Determination
10) Requirement Specification
11) Targeted user
12) Use Case Diagram
13) Data Dictionary
14) Coding Standards
15) Screenshots
16) Agile Project Charter
17) Agile roadmap/schedule
18) Agile project plan
19) Agile user story
20) Agile release plan
21) Agile sprint backlog
22) Agile test plan
23) Earned-value and burn charts
24) Proposed Enhancements
25) Conclusion
26) Bibliography
1) Existing system

 Exiting systems associated with only few businesses.

 They providing their services on very high payable amount.

 User experience – It has very old user experience.

 They don’t have payslip management.

2) Need for the new system

 Some businesses are still working with old management module where

all information of employee’s maintain on paper.

 In large scale it become more complex, to overcome it SMART HR can

provide digital portal(platform) to manage all record with less

manpower.

3) Objective of the New System

 The main objective of this system is to provide facilitate management of

business. SMART HR provide data security of employee. It can overcome

communication gap between employee to higher authorities so

productivity can be increase.


4) Problem definition

 In large scale business it could be complex to maintain employee data

like attendance, leave, employee counting, working days and salary slip.

Additionally, paper work also can be less secure and hectic for

management team.

5) Core Components

 Manage Client:
Super admin(seven infosystem) can manage their client all
information and modules(Admin, HR, Employee).
 Manage HR:
Company higher authorities(CEO,FOUNDER) can manage their HR
employee.
 Manage Employee:
Company higher authorities and HR can manage their all
employee details like, attendance, leave, employee counting,
working days and salary slip.
 Manage Attendance:
Admin(CEO) and HR can manage their employee leave and
working days. Moreover, depend on attendance they also can
manage payable salary and cut off.
6) Project Profile

PROJECT TITLE Employee Management System


COMPONENTS/MODULES Super Admin(Seven Infosystem)
Admin(Company Higher Authority)
HR
Employee
INTERNAL GUIDE Dr. Urja Mankad
EXTERNAL GUIDE Mr. Dhaval Patoliya
PLATFORM Web Portal
INSTITUTE NAME L.J. Institute of Computer Application
COMPANY NAME Seven Infosystem
DEVELOPMENT KIT CodeIgniter
DEVELOPED BY Himalay Sagpariya, Kinnari Patel and team of
Seven Infosystem.

7) Assumptions and Constraints

 Constraints:
 Factors that limit the team’s options:
- Project must be completed in 18 months.
- Existing system must not be interrupted from 9:00 am to 10 pm.

 Assumptions:
 Things that are assumed to be true, but may not be true.
- A dedicated person from marketing will support the team.
- Bugfix effort for each screen will not exceed 20% of the development
effort for the same screen.

8) Advantages and Limitations of the Proposed System

 Advantages:

- SMART HR portal saves record managing time and physical

manpower.

- A modern approach to business management.

- Facilitate maintaining history and records.

- Higher authorities can be accessing all updated information remotely.

 Limitations:

- In the case of existing system interruption companies has to maintain

their data backup for some business days.

9) Requirement Determination
There are plethora of ways to requirement gathering like,

 Similar applications/Websites study


- greyhr

 Questionaries and Survey of business.

10) Requirement Specification

 FUNCTIONAL REQUIREMENTS:

 Super Admin(Seven Infosystem):


 Login
Login with super admin credential.

 Manage Client
Can update/delete/add business assets information from
portal.
 Admin(Founder & CEO):
 Login
Login with admin credential which are given by super
admin.

 Manage HR & Employee


Higher authorities can manage all records of their
employee.
 HR:
 Login
Login with specific HR credential which are given by
admin(System generated ID and password).

 Manage Employee Information


HR can manage all record and information of all employee
like attendance, leave, working days, working hour and
payable salary.

 Employee:
 Login
Login with specific employee credential which are given by
HR(System generated ID and password).

 Apply For Leave

Employee can apply for leave to HR and also can get


reaction from HR or Admin(Higher authority).

 Watch Attendance
Employee can watch his/her working days, working hours
and also can watch leave which are posted by official
committee.
 NON-FUNCTIONAL REQUIREMENTS:

 PERFORMANCE REQUIREMENTS:

- The system must be able to perform smoothly without any


interruptions.
- There should be a minimum interruption in connectivity.

 SECURITY REQUIREMENTS:

- All records of the database should have a backup in case of


data loss.

 HARDWARE REQUIREMENTS:

- Laptop / Personal Computer / Workable Computer System

11) Targeted user

 Small scale business/company

 Large scale business/company


12) Use Case Diagram
13) Data Dictionary
attendance
Field Name Datatype NULL Default
id int(11) No
company_id int(11) Yes NULL
employee_id int(11) Yes NULL
dmy date Yes NULL
start_time datetime Yes NULL
end_time datetime Yes NULL
lunch_break_start datetime Yes NULL
lunch_break_end datetime Yes NULL
worked_hours varchar(30) Yes NULL
left_hours varchar(30) Yes NULL
total_break_time varchar(30) Yes NULL
hours_added int(11) Yes NULL
hours_added_by int(11) Yes NULL
leave_type int(11) Yes NULL
warning varchar(100) Yes NULL
warning_message varchar(300) Yes NULL
hr_notification varchar(300) Yes NULL
created_at timestamp No current_timestamp()
updated_at timestamp Yes NULL

client_admins
Field Name Datatype NULL Default
id int(11) No
name varchar(100) No
email varchar(300) No
contact varchar(10) Yes NULL
password varchar(100) No
role varchar(15) Yes NULL
status tinyint(1) No 0
is_deleted tinyint(1) No 0
created_at datetime Yes current_timestamp()
updated_at datetime Yes NULL

sub_request
Field Name Datatype NULL Default
id int(11) No
company_id int(11) Yes NULL
current_plan_id int(11) Yes NULL
new_plan_id int(11) Yes NULL
payment_type varchar(100) Yes NULL
payment varchar(100) Yes NULL
enum('request',
status No request
'accepted', 'rejected')
created_at datetime No current_timestamp()
updated_at datetime Yes NULL
company_id int(11) Yes NULL
updated_at datetime Yes NULL

companies
Field Name Datatype NULL Default
id int(11) No
name varchar(100) No
contact_person varchar(100) No
country_code varchar(11) Yes NULL
contact varchar(20) No
email varchar(200) Yes NULL
password varchar(100) Yes NULL
uid varchar(100) Yes NULL
avatar varchar(200) No default.png
address varchar(300) Yes NULL
approval tinyint(1) No 0
mail_status varchar(10) Yes NULL
approved_at datetime Yes NULL
status tinyint(1) No 0
is_deleted tinyint(1) No 0
hr_limit int(11) Yes NULL
emp_limit int(11) Yes NULL
hr_created int(11) Yes NULL
emp_created int(11) Yes NULL
sms_ntf tinyint(1) No 0
mail_ntf tinyint(1) No 0
web_ntf tinyint(1) No 0
salary_module tinyint(1) No 0
created_at datetime Yes current_timestamp()
updated_at datetime Yes NULL

employees
Field Name Datatype NULL Default
id int(11) No
name varchar(100) No
username varchar(100) No
email varchar(300) No
country_code varchar(100) Yes NULL
contact varchar(20) Yes NULL
password varchar(100) No
company varchar(300) Yes NULL
added_by varchar(100) No
company_id int(11) Yes NULL
pin varchar(20) Yes NULL
shift_id int(11) Yes NULL
status tinyint(1) No 0
is_deleted tinyint(1) No 0
created_at datetime Yes current_timestamp()
updated_at datetime Yes NULL

event_types
Field Name Datatype NULL Default
id int(11) No
title varchar(300) No
created_at timestamp No current_timestamp()
updated_at timestamp Yes NULL

holidays
Field Name Datatype NULL Default
id int(11) No
title varchar(200) Yes NULL
day_type varchar(200) No
single date Yes NULL
from_date date Yes NULL
to_date date Yes NULL
company_id varchar(11) Yes NULL
added_by_role varchar(100) Yes NULL
role_id int(11) Yes NULL
is_deleted tinyint(1) No 0
active tinyint(1) No 0
created_at timestamp No current_timestamp()
updated_at timestamp Yes NULL

migrations
Field Name Datatype NULL Default
id bigint(20) No
version varchar(255) No
class varchar(255) No
group varchar(255) No
namespace varchar(255) No
time int(11) No
batch int(11) No

hr_admins
Field Name Datatype NULL Default
id int(11) No
name varchar(100) No
username varchar(200) Yes NULL
pin varchar(20) Yes NULL
email varchar(300) No
country_code varchar(100) Yes NULL
contact varchar(20) Yes NULL
password varchar(100) No
role varchar(100) Yes NULL
company_id int(11) Yes NULL
status tinyint(1) No 0
is_deleted tinyint(1) No 0
created_at datetime Yes current_timestamp()
updated_at datetime Yes NULL

plans
Field Name Datatype NULL Default
id int(11) No
name varchar(300) Yes NULL
type varchar(200) Yes NULL
price int(11) Yes NULL
discount int(10) Yes NULL
validity int(10) Yes NULL
benefits varchar(300) Yes NULL
status tinyint(1) No 0
created_at datetime Yes NULL
updated_at datetime Yes NULL

leaves
Field Name Datatype NULL Default
id int(11) No
reason varchar(300) Yes NULL
emp_id int(11) Yes NULL
company_id int(11) No
day_type enum('single', Yes NULL
'week_days')
single_day date Yes NULL
from_day date Yes NULL
to_day date Yes NULL
enum('pending',
approval No pending
'yes', 'no')
by_id int(11) Yes NULL
is_deleted tinyint(4) No 0
active tinyint(4) No 0
created_at timestamp No current_timestamp()
updated_at timestamp Yes NULL

notification_list
Field Name Datatype NULL Default
id int(11) No
company_id int(11) No
from_id int(11) No
to_id int(11) Yes NULL
from_role varchar(30) No
to_role varchar(30) No
message varchar(300) No
is_deleted tinyint(1) No 0
status tinyint(1) No 0
read_status tinyint(1) No 0
created_at timestamp No current_timestamp()
updated_at timestamp Yes NULL

shifts
Field Name Datatype NULL Default
id int(11) No
title varchar(300) Yes NULL
day_start time No
day_end time No
break_start time Yes NULL
break_end time Yes NULL
company_id int(11) Yes NULL
is_deleted tinyint(1) No 0
status tinyint(1) No 0
created_at timestamp No current_timestamp()
updated_at timestamp Yes NULL

salary
Field Name Datatype NULL Default
id int(11) No
company_id int(11) Yes NULL
emp_id int(11) Yes NULL
month_year varchar(100) Yes NULL
total_attendance int(11) Yes NULL
total_absent int(11) Yes NULL
total_halfdays int(11) Yes NULL
remain_leaves int(11) Yes NULL
total_deduction int(11) Yes NULL
final_paid varchar(30) Yes NULL
paid_time datetime Yes NULL
created_at timestamp No current_timestamp()
updated_at timestamp Yes NULL

Subscriptions_log
Field Name Datatype NULL Default
id int(11) No
company_id int(11) Yes NULL
plan_id int(11) Yes NULL
start_date datetime Yes NULL
end_date datetime Yes NULL
transaction_id varchar(20) Yes NULL
time datetime Yes NULL
payment_status varchar(20) Yes NULL
from_bank varchar(20) Yes NULL
account_number varchar(20) Yes NULL
created_at datetime Yes NULL
updated_at datetime Yes NULL

Subscriptions_log
Field Name Datatype NULL Default
id int(11) No
company_id int(11) Yes NULL
plan_id int(11) Yes NULL
start_date datetime Yes NULL
end_date datetime Yes NULL
hr_limit int(11) Yes NULL
emp_limit int(11) Yes NULL
payment_terms varchar(300) Yes NULL
payment_id int(11) Yes NULL
transaction_time datetime Yes NULL
status tinyint(4) No 0
sub_status tinyint(4) No 0
created_at datetime Yes NULL
updated_at datetime Yes NULL

contacts
Field Name Datatype NULL Default
id int(11) No
name varchar(200) No
email varchar(200) No
phone varchar(13) No
subject varchar(299) Yes NULL
message text Yes NULL
is_deleted tinyint(1) No 0
created_at timestamp No current_timestamp()
updated_at timestamp Yes NULL

tbl_country
Field Name Datatype NULL Default
id int(11) No
name varchar(150) No
nationality varchar(64) No
sortname varchar(3) No
calling_code varchar(6) No
currency_code varchar(6) No
currency_name varchar(32) No
currency_symbol varchar(8) No
enum('Active',
is_active No
'Inactive')
insertdate datetime No current_timestamp()
14) Coding Standards

 Class and method names should always be in a proper format

 Method arguments and Local variables should always be in Camel case.

 Avoid the use of underscore while naming identifiers.

 Use proper alignment for coding.

15) Screenshots
Client Admin – Login

Client Admin - Company List

Client Admin – Company Details


Client Admin – Company Dashboard

Client Admin – Company Hr Admins


Client Admin – Employees

Client Admin – Shifts


16) Agile Project Charter

PROJECT TITLE Employee Management System


PROJECT SCOPE The project main aims to manage all details
of employees.
PROJECT INTERNAL GUIDE Dr. Urja Mankad
PROJECT EXTERNAL GUIDE Mr. Dhaval Patoliya
PROJECT OF Seven Infosystem
EXPECTED START DATE 1 January – 2023
EXPECTED COMPLETION DATE 10 June - 2024
DEVELOPED BY Himalay Sagpariya, Kinnari Patel and
team of Seven Infosystem.
17) Agile roadmap/schedule

#
18) Agile project plan
19) Agile user story

ID Type of Users Task


1 Team Leader Set the objectives.
View the status of each key results of
objectives.
Guide a team members with proper
approach.
Feedback the performance.
2 Team Member Find a proper way to achieve goal as a
objective given by the team leader.
Request for feedback of performance.
Ready to learn from the colleagues.
Complete given task before deadline.

You might also like