My Project 003

AUTOMATED EMPLOYEE SERVICES PROVIDER SYSTEM

University of Gujrat

Faculty of Computer Science & Information Technology

Final Project Documentation

Computer Science & Information Technology


Version 1.0

© Project Management Office Faculty of Computer Science & Information Technology, University Of Gujrat.

Page 1



Faculty of Computer Science & Information TechnologyUniversity of Gujrat


Page 2


STATEMENT OF SUBMISSION

This is to certify that Muhammad Umer Rafiq Roll No.11050856-014 has successfully completed the final project named as: AUTOMATED EMPLOYEE SERVICES PROVIDER SYSTEM, at the Faculty of CS/IT, University of Gujrat, to fulfill the partial requirement of the degree of Masters in Computer Science or Information Technology.

_____________________Project Management Office

CS/IT, UOG

_____________________________ ________________________Project Advisor Director /HOD of CS/IT Designation UOGCS/IT, UOG


Page 3


APPROVALS

I Ms. Qamar-un-Nisa am willing to guide these students in all phases of thesis titled “Automated employee service provider system” as advisor. I have carefully seen the Title and description of the thesis and believe that it is of an appropriate difficulty level for the number of students named above.

_______________ _________________Date Signature of Advisor

Submission Date: _____________


Page 4


Proofreading Certificate

It is to certify that I have read the document meticulously and circumspectly. I am convinced that the resultant project does not contain any spelling, punctuation or grammatical mistakes as such. All in all I find this document well organized and I am in no doubt that its objectives have been successfully met.

_____________________

Miss Qamar un Nisa UOG

Table of Contents


Page 5


CHAPTER 1.................................................................................................................9

PROJECT TITLE:...............................................................................................9

AUTOMATED EMPLOYEE SERVICES PROVIDER SYSTEM...........................91.1 INTRODUCTION AND BACKGROUND:..............................................................91.2 PROBLEM STATEMENT:.......................................................................................91.3 OBJECTIVES OF THE PROJECT:............................................................................101.4 SPECIFIC PROJECT GOALS:................................................................................101.5 SCOPE OF THE PROJECT (ABSTRACT):............................................................101.6 PROJECT OVERVIEW STATEMENT TEMPLATE...................................................11

Objectives:............................................................................................................12Risks of the Project:.............................................................................................13

CHAPTER 2...............................................................................................................14

2. BENEFITS OF THE PROJECT..........................................................................14

2.1 DIRECT CUSTOMERS / BENEFICIARIES OF THE PROJECT....................................142.2 OUTPUTS EXPECTED FROM THE PROJECT...........................................................14

CHAPTER 3...............................................................................................................14

3. PROJECT DESCRIPTION.................................................................................14

3.1 FUNCTIONAL SPECIFICATION:.............................................................................143.1.1 Functions Performed:..................................................................................143.1.2 Limitations and Restrictions:......................................................................143.1.3 Application Architecture:............................................................................153.1.4 Equipment Configuration............................................................................16

3.2 IMPLEMENTATION PLAN..................................................................................173.2.1 Deliverable Items:....................................................................................173.2.2 Milestone Identification:..........................................................................173.2.3 Project Schedule / Milestone Chart:...........................................................17

CHAPTER 4...............................................................................................................18

4. QUALIFICATIONS:.............................................................................................18

4.1 PERSONAL BACKGROUND:.............................................................................184.2 COURSES TAKEN:...........................................................................................194.3 FINAL PROJECT RELATED COURSES:...............................................................19

CHAPTER 5...............................................................................................................20

5. USE CASES............................................................................................................20

5.1 ADMINISTRATOR PANEL......................................................................................20Administrator use case diagram :.......................................................................20

5.2 EMPLOYEE’S PANEL............................................................................................24Employee’s use case diagrams :.........................................................................24

5.3 VISITING EMPLOYEE’S PANEL............................................................................30visiting Employee’s use case diagrams :.............................................................30

USECASE DIAGRAM:.............................................................................................35

CHAPTER 6...............................................................................................................36


Page 6


6. DOMAIN MODEL:............................................................................................36

6.1 DOMAIN MODEL DESCRIPTION:...........................................................................36CHAPTER 7................................................................................................................377.1 EMPLOYEE CLASS DIAGRAM :...........................................................................377.2 ADMINISTRATOR CLASS DIAGRAM:.....................................................................38

CHAPTER 8...............................................................................................................39

ENTITY RELATIONSHIP DIAGRAM :................................................................39

CHAPTER 9...............................................................................................................40

SEQUENCE DIAGRAM...........................................................................................40

9.1 Sequence diagram of admin panel:...............................................................409.2 Sequence diagram of add employee use case:...............................................419.3 Sequence diagram of edit emoployee use case:............................................429.4 Sequence diagram of delete user use case:....................................................439.5 Sequence diagram of send notification of leave use case:.............................439.6 Sequence diagram of calculate salary use case:............................................44

SEQUENCE DIAGRAM OF EMPLOYEE PANEL:.............................................................459.7 Sequence diagram of employee login:............................................................459.8 Sequence diagram of employee mark attendance use case:...........................469.9 Sequence diagram of Apply leave use case:...................................................479.10 Sequence diagram of view profile:...............................................................489.11 Sequence diagram of edit profile use case:..................................................499.12 Sequence diagram of check salary:..............................................................509.13 Sequence diagram of check attendance:.....................................................51

9.14 SEQUENCE DIAGRAM OF VISITING EMPLOYEE PANEL:......................................52Sequence diagram of visiting employee login use case:......................................529.15 Sequence diagram of visiting employee mark attendance use case:............539.16 Sequence diagram of Apply leave use case:.................................................549.17 Sequence diagram of visitor view profile:....................................................559.18 Sequence diagram of visitor edit profile use case:.......................................569.19 Sequence diagram of visitor check salary:...................................................579.20 Sequence diagram of visitor check attendance:..........................................58

SNAPSHOTS..............................................................................................................59

CHAPTER 10.............................................................................................................60

HOMEPAGE…............................................................................................................60LOGIN PANEL:...........................................................................................................61ADMINISTRATION PANEL:.........................................................................................62ADMIN VIEW ATTENDENCE OF EMPLOYEES:..............................................................63ATTENDANCE VIEWED BY EMPLOYEE THROUGH SEARCH BOX…………….............64ATTENDENCE VIEW BY ADMIN:................................................................................64MANAGE EMPLOYEE:................................................................................................65ADD EMPLOYEE:.......................................................................................................66ADD PERMANENT EMPLOYEE:...................................................................................67EMPLOYEE CREATED.................................................................................................68DELETE EMPLOYEE...................................................................................................69SEARCH EMPLOYEE FOR DELETION...........................................................................70


Page 7


UPDATE EMPLOYEE…...............................................................................................71UPDATE EMPLOYEES:................................................................................................72NOTIFICATION...........................................................................................................73CREATE ACCOUNT....................................................................................................74

EMPLOYEE PANEL:...............................................................................................75

MARK ATTENDANCE.................................................................................................76LEAVE APPLICATION FORM.......................................................................................77VIEW PROFILE...........................................................................................................78NOTIFICATION...........................................................................................................79PERMANENT EMPLOYEE PAYROLL............................................................................80GENERATE PAYROLL.................................................................................................81CHANGE PASSWORD..................................................................................................82

Chapter 1

Project Title:

AUTOMATED EMPLOYEE SERVICES PROVIDER SYSTEM.

1.1 Introduction and Background:


Page 8


Every organization is using online attendance, leaves submission and payroll system for their employees. This online system is essential for any organization that pays salary to their employees on the basis of their attendance. University employee system is manual. Using a paper based attendance system employee mark their attendance in a register. It is a time to switch to an online employee attendance, leave and pay bill management system. This system will get speed, accuracy and ease in your attendance management. We have decided to develop an online system for the employees of university. With the help of attendance and leave system we can generate pay bill for employees. This system will work fast. This system will give assurance of accuracy, security and validation.We are developing three modules in this employee service provider system Online attendance system Online leave submission system Online Pay bill /salary systemThe Payroll system will work online, with a secure login. The system will be fully secure and protected from unauthorized access. With a user-friendly interface all payroll/ pay bill tasks can be completed quickly and accurately. As the system is online, it can access and view the attendance record with the help of internet from anywhere in the world.

1.2 Problem Statement: Employee’s attendance and leave system is manual. This

system has many drawbacks. It is time consuming. It never gives the assurance of accuracy, security and validation. This manual attendance and leave system can be lost. It is not recoverable. Leave application process is totally manual which deals with many complications. And making of pay bill according to the attendance and leave considerations, it become more complicated (especially for visiting staff).

1.3 Objectives of the Project: Online attendance system Online leave submission system Online Pay bill /salary system

1.4 Specific Project Goals:o Attendance tracking and reportingo To apply Leave, Approve leave, Manage Leave onlineo Automatic request generation to the head of department for leave

applications

o Official visit plans (duty leave) and applications should be managed

o Online Pay bill generation and management system with a secure login


Page 9


o It will assist and manage pay bill system

o To monitor the employees working time

o To monitor the overall performance of staff

1.5 Scope of the project (Abstract): The system will be used by the administrator and the employees of the university.Administrator will have the access to handle teacher’s attendance, leave submission and pay bill and also have the authority to accept or reject. Each user will have their own interface and have their own login. This database system would maintain the data of employees. Not only the admin but also the employees would also have the access to handle their own attendance, leave and pay bill online.

1.6 Project Overview Statement Template

Project Title:

Group Leader: Muhammad Umer Rafiq

Project Members:

Name Registration #

Email Address Signature

Hafsa Bibi 11002256042 [email protected]

Saba Rafee 11002256043 [email protected]

Muhammad Umer Rafiq

09010100118 [email protected]


Page 10

mailto:[email protected]






Project Goal: project main goal is to eliminate paper based system and minimize the manpower for manual management. Develop an online system for the employees that provide them a facility to mark their attendance, send their leave and check their annual salary using this system.

Objectives:

Sr.#

OBJECTIVES

1 Convert manual system to online system.2 Manage time attendance system

3 Attendance tracking and reporting

4 Apply Leave, Approve leave, Manage Leave online

5 Automatic request generation to the head of department for leave applications

6 Official visit plans (duty leave) and applications should be managed

7 Online Pay bill generation and management system with a secure login

8 System will monitor the employees working time

9 System will monitor the overall performance of staff

Project Success criteria:

Project to be completed within specified time


Page 11


Risks of the Project: Non availability of required resources, equipments i.e. computers, Local Area

Network etc.

Power Failure.

Software if corrupted at any stage of development

Viruses attacks on machines.

(Please mark where applicable) Low Medium High

Technical risk

Timing risk

Budget risk

Type of project: Research Development configuration

Target End users: professionals, employees

Development Technology: Object Oriented Structured

Platform: Web based Distributed

Desktop based Setup Configurations

Other_____________________

Suggested Project Supervisor:

Approved By:

Date:


Page 12


Chapter 22. Benefits of the Project

2.1 Direct Customers / Beneficiaries of the Project Employees Administration

2.2 Outputs Expected from the Project Online attendance management system. Online leave submission and management.

Online pay bill generation and management.

Chapter 3 3. Project description

3.1 Functional Specification:

3.1.1 Functions Performed: There are some functions that will be developed in theSystem such as admin sign in, admin sign out, view records employees, register for newEmployees, view employees working time, total of employees who work over time, totalOf employees who apply medical leave, total of employees who apply leave, list if leaveApplied by the employees and various reports generated, print reports as references,Employee sign in and sign out their attendance, apply leave and check leave. The Payroll system works online, with a secure login. The system will be fully secure and protected from unauthorized access. With a user-friendly interface all payroll tasks can be completed quickly and accurately.

3.1.2 Limitations and Restrictions: This system will restrict access to mark previous attendance. Employee only view the attendance could not mark the previous attendance.


Page 13


3.1.3 Application Architecture:

USER

INTERFACE

COMPONENTS

CENTRAL DATABASE


Page 14

USER

LEAVE

ATTENDENCE

DATABASE

ATTENDENCE

LEAVE PAY ROLL


3.1.4 Equipment Configuration

3.1.4.1 Hardware Specification: Intel Dual Core or above. Hard disk- 40GB (min) RAM- 1GB (min)

3.1.4.2 Software specification: OS-Windows XP or any upgraded version Web Server Dreamweaver SQL Server

3.1.4.3 Supported Web Browsers: Microsoft IE 6.0 – 7.0 or upgraded version Mozilla Firefox 2.0 or upgraded version Google Chrome

3.1.4.4 Man power requirements: A team of 3 students can complete this in 5-6 months.

3.1.5 Implementation Tools and Technology:

3.1.5.1 Databases: SQL server or MYSQL

3.1.5.2 Development tools: Dreamweaver XAMP/WAMP Visio or smart draw Microsoft word and PowerPoint

3.1.5.3 Development Technology: HTML CSS JavaScript PHP

3.1.5.4 Size of the development effort:The size of the development effort is medium according to the scope of

the project, but if we want to enhance this project this will be large scope and consequently the large development effort.


Page 15


3.2 Implementation PlanFollowing are the stages of the implementation the system;

3.2.1 Deliverable Items: Project Proposal Analysis document Complete SRS (system requirement specifications) Complete Design of the system Final deliverable of the system

3.2.2 Milestone Identification:

A. Key Milestones and Deliverables:

The information given in this table will be the basis of monitoring by Project Coordination Office.No.

Elapsed time from start (in months) of the project

Milestone Deliverables

1. 2 weeks Project Planning One Page Proposal2. 2 weeks Requirement collection 3. 2 weeks Proposal Final Proposal4. 2 weeks Analysis5. 1 Month Design 2nd Deliverable6. 2 Month, 2 weeks Development7. 10 days Implementation8. 5 days Testing9. 5 days Final product Final Project 10. 5 days Maintenance

3.2.3 Project Schedule / Milestone Chart:


Page 16


Figure 1: milestone chart

Chapter 4 4. Qualifications:

4.1 Personal Background:As a student’s we have no external experience in the market in

form of work but we have performed well in the term projects of different subjects which make the base for the project development.

4.2 Courses Taken:We have studied these courses in 3 semesters.

Sr # Subject Department

1 Programming Fundamentals CS /IT2 Introduction to Information and Communication

TechEnglish

3 Data Communication and Networks CS /IT4 English Communication Skills English5 Information Systems CS /IT6 Principles of Management Business7 Object Oriented Programming CS /IT8 Database System CS /IT9 Network Security CS /IT10 Software Engineering CS /IT11 Business & Technical Writing English


Page 17


12 Organizational Behavior Business11 Data Structure CS /IT14 Operating system CS /IT15 Advance Communication System CS /IT16 Research Methodologies CS /IT17 Web System & Technologies CS /IT

4.3 Final project related courses:

CoursesDatabase SystemWeb System and TechnologyProgramming FundamentalsObject Oriented Programming

Data Structure

Chapter 55. use cases

5.1 Administrator panel

Administrator use case diagram :

Figure 2: use case diagram


Page 18


Use case # 1Use case Name Admin Login Use case ID 1Scope System is under design

Level Admin goalPrimary actor AdministratorStake holder and their interests

Want to login to perform administrative tasks

Actions 1. Administrator enters name and password.

2. System checks the authentications.3. If name and password is not correct

show message to check name and password, else successfully login the user.

Preconditions Application must be running.Post conditions After giving name and password admin will be

loginExtensions If error occurs system will ask to check

validation.Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case # 2

Use case Name Add employeeUse case ID 2Scope System is under design

Level Admin goalPrimary actor AdministratorStake holder and their interests

Want to add employee

Actions 1. Admin clicks on add employee window.

2. System will show a form to fill.3. Administrator fill the form according to

the information needed.4. Admin will click the add button.5. Employee will be successfully added.

Preconditions Application must be running.Post conditions After giving name and password admin will be

login


Page 19


Extensions If error occurs system will ask to check validation.

Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case # 3

Use case Name Edit employeeUse case ID 3Scope System is under design

Level Admin goalPrimary actor administratorStake holder and their interests

Want to manage user.

Actions 1. Admin clicks the view all users.2. System will show interface where

administrator search the specific user.3. System will show the records.4. Admin successfully edit the desired

user.Preconditions Administrator must be login.Post conditions Employee will be edited.Extensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case #4Use case Name Delete employeeUse case ID 4Scope System is under design


Want to delete employee.

Actions 1. Admin clicks the view all users.2. System will show interface where

administrator search the specific user.3. System will show the records.4. Admin will click the delete button.5. Admin successfully delete the desired

user.Preconditions Employee must be in the database.Post conditions Employee will be deleted.Extensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system


Page 20


Use case # 5

Use case Name Send notifications of leave Use case ID 5Scope System is under design


Want to send requests and approvals to head of department and to employee correspondingly.

Actions 1. Admin click the notification panel.2. System will show leave requests from

the specific employees.3. Admin will forward these requests to

head of department.4. When receive approval of leave from

head of department.5. Forward approvals to employees who

apply for leave

Preconditions Employee must apply for leavePost conditions Employee will receive approvalsExtensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case # 6

Use case Name Calculate salaryUse case ID 6Scope System is under design


Want to calculate employee’s salary

Actions 1. Admin clicks the calculate salary button.

2. System will show interface 3. Admin will start pay transaction for

the specified date.4. System will find all those employees

that should be paid upon specified date.

5. System will then calculate how much they owed, and make deductions.

6. System will print checks for the


Page 21


employees.Preconditions Admin must have all information about

salary.Post conditions Checks will be printedExtensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

5.2 Employee’s panel

Employee’s use case diagrams :

Figure 3: use case diagram of employee

use case # 7Use case Name employee Login Use case ID 7Scope System is under design

Level Employee goalPrimary actor EmployeeStake holder and their interests

Want to login to perform tasks

Actions 1. Employee enters name and password.2. System checks the authentications.3. If name and password is not correct

show message to check name and


Page 22


password, else successfully login the user.

Preconditions Application must be running.Post conditions After giving name and password admin will

be loginExtensions If error occurs system will ask to check


Use case # 8

Use case Name Mark attendanceUse case ID 8Scope System is under design


Want to mark attendance

Actions1. employee will open interface to mark

attendance2. Employee will mark attendance

against specified date.3. System will check specifications

against attendance.4. System will generate error if MAC

address not match else Attendance will be marked against specific employees.

Preconditions User must login from provided mail account MAC address.

Post conditions Attendance will be marked.Extensions Employee must be login from specific MAC

address otherwise attendance will not acceptable.


Use case # 9

Use case Name Apply leaveUse case ID 9Scope System is under design

Level Employee goalPrimary actor Employee


Page 23


Stake holder and their interests

Want to get leave

Actions1. Employee will open interface to apply

for leave2. System will show a Leave form.3. Employee will fill the form.4. Send leave to administrator to be

approved by the head of department.5. Receive notification of

acceptance/rejection of leave.

Preconditions User must have reason/ leave type Post conditions Employee send leave request to administratorExtensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case #10Use case Name View profileUse case ID 10Scope System is under design


Want to view profile

Actions1. Employee will open interface to view

profile2. System will show all information

about employee.3. Employee will view profile.

Preconditions User must have provided all necessary information

Post conditions Employee will view profile.Extensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case #11Use case Name Edit profileUse case ID 11Scope System is under design

Level Employee goalPrimary actor EmployeeStake holder and their Want to edit profile


Page 24


interestsActions

1. Employee will open interface to edit profile

2. System will show all information about employee.

3. Employee will edit profile as needed.

Preconditions Profile should be open in editable form.Post conditions Employee will view profile.Extensions Provide information according constraints

provided.Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case #12

Use case Name Check/view employee’s salaryUse case ID 12Scope System is under design


Want to check salary

Actions1. Employee will open interface to check

salary2. System will show all information

about employee’s salary.3. Employee will check/view salary.


Post conditions Employee will check/view salary.Extensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case #13

Use case Name Check attendanceUse case ID 13Scope System is under design

Level Employee goalPrimary actor EmployeeStake holder and their Want to check attendance


Page 25


interestsActions

1. Employee will open interface to check attendance

2. System will show list of employee’s attendance.

3. Employee will check/view attendance.


Post conditions Employee will check/view salary.Extensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

5.3 Visiting Employee’s panel

visiting Employee’s use case diagrams :

Figure 4: use case of visitor

Use case #14Use case Name Visiting employee Login Use case ID 14Scope System is under design

Level Employee goalPrimary actor Visiting Employee


Page 26


Stake holder and their interests

Want to login to perform tasks

Actions 1. Employee enters name and password.2. System checks the authentications.3. If name and password is not correct

show message to check name and password, else successfully login the user.

Preconditions Application must be running.Post conditions After giving name and password admin will

be loginExtensions If error occurs system will ask to check


Use case #15Use case Name Mark attendanceUse case ID 15Scope System is under design


Want to mark attendance

Actions1. employee will open interface to mark

attendance2. Employee will mark attendance

against specified date.3. System will check specifications

against attendance.4. System will generate error if MAC

address not match else Attendance will be marked against specific employees.

Preconditions User must login from provided mail account MAC address.

Post conditions Attendance will be marked.Extensions Employee must be login from specific MAC

address otherwise attendance will not acceptable.


Use case #16Use case Name Apply leaveUse case ID 16


Page 27


Scope System is under designLevel Employee goalPrimary actor EmployeeStake holder and their interests

Want to get leave

Actions1. Employee will open interface to apply

for leave2. System will show a Leave form.3. Employee will fill the form.4. Send leave to administrator to be

approved by the head of department.5. Receive notification of

acceptance/rejection of leave.

Preconditions User must have reason/ leave type Post conditions Employee send leave request to administratorExtensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case #17Use case Name Check/view visiting employee’s salaryUse case ID 17Scope System is under design


Want to check salary

Actions1. Employee will open interface to check

salary2. System will show all information

about employee’s salary.3. Employee will check/view salary.


Post conditions Employee will check/ view salary.Extensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case #18

Use case Name View profile


Page 28


Use case ID 18Scope System is under design


Want to view profile

Actions1. Employee will open interface to view

profile2. System will show all information

about employee.3. Employee will view profile.


Post conditions Employee will view profile.Extensions Nil Special requirements Interface should be simple and user friendly.Author Employee’s online system

Use case diagram:

Use Case diagram for Employee Attendance System is shown below. The various participants of the same are detailed below:-

Actors: - Employee, Manager, Owner

the corresponding use cases for these actors are:- Employee: log in, Mark Attendance, apply leave ,apply check leave,get

salary,view,receive notification,log out. Administrator :log in ,edit ,delete , Calculate Salary, approval of leave,send

notification ,log out Visitor: log in , Mark Attendance, apply leave ,apply check leave, get

salary,view,receive notification, log out


Page 29


Usecase Diagram:

Figure 5: use case diagram


Page 30


Chapter 6

6. Domain model:

Figure 6: domain model

6.1 Domain model description:

Employee has id, name, login, and password. Mark his attendance with his login. Employee submits his leave and payroll. Employee can view his profile.


Page 31


Chapter 7

7.1 Employee class diagram :

Attendance Attendance id Date No of hours Mark attendance() Check attendance()

Employee

Employee _id Employee name Phone no Address Date join Designation login() edit profile() check attendance() check salary() apply leave() mark attendance () view profile() logout()

Leave Leave id Day Date Apply leave()

View profile

Employee _id Employee name Phone no Address Date join Designation View profile()

Payroll Payroll id Payroll date View() Generate report()

Figure 7: class diagram of employee


Page 32


7.2 Administrator class diagram:

Figure 8: administration class diagram


Page 33


Chapter 8Entity relationship diagram :

Figure 9: ERD


Page 34


Chapter 9 Sequence Diagram

9.1 Sequence diagram of admin panel:

OES admin 1:login 2: login()

Sd loop

3: if incorrect id or password

4: tries agin

Else 5: logi

9.2 Sequence diagram of add employee use case:


Page 35


Admin OES 1:add employee 2: add employee

Sd loop

3: show a form to fill

4: admin will fill the form

5: user added successfully

9.3 Sequence diagram of edit emoployee use case:


Page 36


Admin OES 1:edit employee 2: edit employee

Sd loop

3: show record of user

4: edit the record

5: user is edited successfully

9.4 Sequence diagram of delete user use case:

Admin OES 1:delete employee 2: delete employee

Sd loop

3: show record of user

4: delete record

5: user deleted successfully


Page 37


9.5 Sequence diagram of send notification of leave use case:

Admin OES 1:send notification to employee 2: send notification

Sd loop

3: system will show leave request

4: forward request to HOD

5.receive approval of leave form

6. Farward approvals to employee

9.6 Sequence diagram of calculate salary use case:


Page 38


Admin OES 1:click calculate salary 2: calculate salary

Sd loop

3: system will show interface

4: start pay transaction

5.print checks for employees


Page 39


Sequence diagram of employee panel:

9.7 Sequence diagram of employee login: OES admin 1:login 2: login()

Sd loop


4: tries agin

Else 5: login

9.8 Sequence diagram of employee mark attendance use case:

OES employee


Page 40


1:open interface to mark attendence 2: mark attendence

Sd loop


4: mark attendance against specifiv date

5.generate error if Mac does not match

9.9 Sequence diagram of Apply leave use case:

OES employee 1:open interface to apply leave 2: apply leave

Sd loop

3: system will show leave form

4: fill form

5.send leave to administrator

6..notification of acceptance/rejection


Page 41


9.10 Sequence diagram of view profile:

OES employee 1:open interface to view profile 2: view profile

Sd loop

3: system will show information about employee

4: employee will view profile

9.11 Sequence diagram of edit profile use case:

OES employee 1:open interface to edit profile 2: edit profile

Sd loop


4: employee will edit profile


Page 42


9.12 Sequence diagram of check salary:

OES employee 1:open interface to check salary 2: view salary

Sd loop

3: system will show information about employee salary

4: employee will check salary

9.13 Sequence diagram of check attendance:

OES employee 1:open interface to check attendence


Page 43


2: check Atendence

Sd loop

3: system will show list of employee attendence

4: employee will check attendence

9.14 Sequence diagram of visiting employee panel:

Sequence diagram of visiting employee login use case: OES admin 1:login 2: login()

Sd loop


4: tries agin

Else 5: log


Page 44


9.15 Sequence diagram of visiting employee mark attendance use case:

OES employee 1:open interface to mark attendence 2: mark attendence

Sd loop


4: mark attendance against specifiv date

5.generate error if Mac does not match

9.16 Sequence diagram of Apply leave use case:

OES employee 1:open interface to apply leave 2: apply leave

Sd loop


Page 45


3: system will show leave form

4: fill form

5.send leave to administrator

6..notification of acceptance/rejection

9.17 Sequence diagram of visitor view profile:

OES employee 1:open interface to view profile 2: view profile

Sd loop


4: employee will view profile

9.18 Sequence diagram of visitor edit profile use case:

OES employee


Page 46


1:open interface to edit profile 2: edit profile

Sd loop


4: employee will edit profile

9.19 Sequence diagram of visitor check salary:

OES employee 1:open interface to check salary 2: view salary

Sd loop

3: system will show information about employee salary

4: employee will check salary

9.20 Sequence diagram of visitor check attendance:


Page 47


OES employee 1:open interface to check attendence 2: check Atendence

Sd loop

3: system will show list of employee attendence

4: employee will check attendence


Page 48


SNAPSHOTS


Page 49


Chapter 10

Homepage…

Every user can access the home page. Admin and user access their login through home page using their login

from login menu.

Login panel:


Page 50


Admin can login account by putting user name and password. Click on login button. If there is mistake in its name or password, he can reset it. To access home page, user click on back to home button.

Administration panel:


Page 51


Admin can view attendance.Admin can manage employees by add, edit, update and delete users..Admin can send notification of acceptation and rejection of leave.Admin can aproval of leaves with gets notifications.Admin can create account for any user.Admin can logout his login.

admin view attendence of employees:


Page 52


Click on permanent employee to view attendance of a permanent user.Click on visitor employee to view attendance of visitor employee.

Attendance viewed by employee through search box……………..


Page 53


Attendence view by Admin:

Manage employee:


Page 54


Admin can add employee.Admin can delete employee.Admin can update employee.Admin can view employee.

Add employee:


Page 55


Admin can add permanent employee.Admin can add visitor employee.

Add permanent employee:


Page 56


Fill all blanks to create a new employee.Enter employee Email id.Set a new employee password.Enter employee first name.Enter last name.Enter contact number.Enter address.Click on create new employee button.Employee created

Employee created


Page 57


After filling form click on create employee button.Employee created.

Delete employee


Page 58


Admin can delete permanent employee.Admin can delete visitor employee.

Search employee for deletion


Page 59


Employee deleted:

Update employee…...


Page 60


Click on permanent employee to update permanent employees.Click on visitors employee to update visitor employees.

update employees:


Page 61


Admin can update employees record .

Notification


Page 62


Admin accept or reject the leave notifications of employees.

Create account


Page 63


Enter user name.Type password.Enter valid Email id.Enter create account .Account has been created.

Employee panel:


Page 64


Employee can mark attendance.Employee can apply for leave.Employee can view his profile.Employee can send and get notification.Employee can generate his payroll form.Employee can change his password.Employe can logout from account.

Mark attendance


Page 65


Employee id ,name and department is retrieved from data base of employees for mark attendance.Employee can mark attendance and submit it through mac address. Only employees can mark attendance whose mac is saved in database.

Leave application form


Page 66


Enter total days of leaves.Chose nature of leave.chose month.submit by clicking on submit button.

View profile


Page 67


Notification


Page 68


Permanent Employee payroll


Page 69


Generate payroll


Page 70


Change password


Page 71


Enter current password.Set new password.Enter new password again for confirmation.Click to save changes.


Page 72

Documents

My Project 003