RFID Based Employee Attendance System Complete Report

Final Year
Project
Report
RFID Based Employee

Attendance System
PIET/2011-2012/VII/IT/IC/13
Final Year Project Report (Project Stage-1) Academic Session 2011-2012, PIET, Jaipur
Chapter 1
Introduction
RFID Based Attendance System is a system developed for daily employee attendance in
companies. Employee’s proper attendance management is till date a critical issue in many
companies. Attendance plays a vital role in managing salaries of employees and also in
tracking the regularity & sincerity of employee’s towards their occupation. The process of
tracking attendance manually using pen and paper has become an outdated approach. It
not only involves fake entries by employees but even sometimes lead to improper
evaluation of attendance. There always exist a threat of records/register getting misplaced
or may get damage due to unfavorable circumstances. To overcome all these drawbacks
and many more than that we intend to develop a system which not only removes the
tedious task of tracking attendance manually but also helps in maintaining a system which
will help an organization in proper & appropriate evaluation of salary, regularity & even
punctuality of an employee based on attendance. The purpose of
developing attendance management system is to computerized the tradition way of
taking attendance.
The attendance of the employee will be taken by rfid tags and will automatically get stored
in the database .According to number of working days attended by the employee salary will
be generated. Provision has also been made to alert employees via sms, mails etc regarding
their attendance & salary. The system records details such as arrival and departure of
employees besides maintaining information regarding their personal and official profiles.
Official employee information such as designation, department, shift, location, leaves status,
compensation, etc. can be linked to any payroll software to automate the complete process.
1.1 Introduction to RFID

1.1.1 History
In a very interesting article, the San Jose Mercury News tells us about Charles Walton, the
man behind the radio frequency identification technology (RFID). Since his first patent about
it in 1973, Walton, now 83 years old, collected about $3 million from royalties coming from
his patents. Unfortunately for him, his latest patent about RFID expired in the mid-1990s.
So he will not make any money from the billions of RFID tags that will appear in the years
to come. But he continues to invent and his latest patent about a proximity card with
incorporated PIN code protection was granted in June 2004.
1
Team Id-PIET/2011-2012/VII/IT/IC/13
1.1.2 What is RFID?

RFID is short for Radio Frequency Identification. Generally a RFID system consists of 2 parts
viz a reader, and one or more Transponders, also known as tags. RFID systems evolved
from barcode labels as a means to automatically identify and track products and people.
You will be generally familiar with RFID systems seen in:
 Access Control.
RFID Readers placed at entrances that require a person to pass their proximity card
(RF tag) to be read before the access can be made.
 Contactless Payment System
RFID tags used to carry payment information. RFIDs are particular suited to
electronic Toll connection systems. Tags attached to vehicles, or carried by
people transmit payment information to a fixed reader attached to a Toll station.
Payments are then routinely deducted from a users account, or
information is changed directly on the RFID tag.
 Product Tracking and Inventory Control
RFID systems are commonly used to track and record the movement of ordinary
items such as library books, clothes, factory pallets, electrical goods and numerous
items.
1.1.3 How RFID works?

Shown below is a typical RFID system. In every RFID system the transponder tags contain
information. This information can be as little as a single binary bit, or be a large array of
bits representing such things as an identity code, personal medical information, or literally
any type of information that can be stored in digital binary format.
2
Shown is a RFID transceiver that communicates with a passive Tag. Passive tags have no
power source of their own and instead they derive power from the incident electromagnetic
field. Commonly the heart of each tag is a microchip.
When the tag enters the generated RF field it is able to draw enough power from the field to
access its internal memory and transmit its stored information.
When the transponder Tag draws power in this way the resultant interaction of the RF fields
causes the voltage at the transceiver antenna to drop in value. This effect is utilized by the
Tag to communicate its information to the reader. The Tag is able to control the amount of
power drawn from the field and by doing so it can modulate the voltage sensed at the
Transceiver according to the bit pattern it wishes to transmit.
1.1.4 Components of RFID
A basic RFID system consists of three components:
 An antenna or a coil
 A transceiver
 A transponder (RF tag)
These are described below:

1. Antenna
The antenna emits radio signals to activate the tag and read and write data to it.
Antennas are the conduits between the tag and the transceiver, which controls the
system's data acquisition and communication. Antennas are available in a variety of
shapes and sizes; they can be built into a door frame to receive tag data from persons
or things passing through the door, or mounted on an interstate tollbooth to monitor
traffic passing by on a freeway. The electromagnetic field produced by an antenna can
be constantly present when multiple tags are expected continually. If constant
interrogation is not required, a sensor device can activate the field.
Often the antenna is packaged with the transceiver and decoder to become a reader
(a.k.a. interrogator), which can be configured either as a handheld or a fixed-mount
device. The reader emits radio waves in ranges of anywhere from one inch to 100 feet
or more, depending upon its power output and the radio frequency used. When an RFID
tag passes through the electromagnetic zone, it detects the reader's activation signal.
The reader decodes the data encoded in the tag's integrated circuit (silicon chip) and the
data is passed to the host computer for processing.
3
2. Transceiver
The RF transceiver is the source of the RF energy used to activate and power the passive
RFID tags. The RF transceiver may be enclosed in the same cabinet as the reader or it
may be a separate piece of equipment. When provided as a separate piece of
equipment, the transceiver is commonly referred to as an RF module. The RF transceiver
controls and modulates the radio frequencies that the antenna transmits and receives.
The transceiver filters and amplifies the backscatter signal from a passive RFID tag.
3. Transponder
An RFID tag is comprised of a microchip containing identifying information and an
antenna that transmits this data wirelessly to a reader. At its most basic, the chip will
contain a serialized identifier, or license plate number, that uniquely identifies that item,
similar to the way many bar codes are used today. A key difference, however is that
RFID tags have a higher data capacity than their bar code counterparts. This increases
the options for the type of information that can be encoded on the tag, including the
manufacturer, batch or lot number, weight, ownership, destination and history (such as
the temperature range to which an item has been exposed). In fact, an unlimited list of
other types of information can be stored on RFID tags, depending on application needs.
An RFID tag can be placed on individual items, cases or pallets for identification
purposes, as well as on fixed assets such as trailers, containers, totes, etc.
4
Tags come in a variety of types, with a variety of capabilities. Key variables include:
"Read-only" versus "Read-write"
There are three options in terms of how data can be encoded on tags:
(1) Read-only tags contain data such as a serialized tracking number, which is pre-
written onto them by the tag manufacturer or distributor. These are generally the least
expensive tags because they cannot have any additional information included as they
move throughout the supply chain. Any updates to that information would have to be
maintained in the application software that tracks SKU movement and activity.
(2) "Write once" tags enable a user to write data to the tag one time in production or
distribution processes. Again, this may include a serial number, but perhaps other data
such as a lot or batch number.
(3) Full "read-write" tags allow new data to be written to the tag as needed—and even
written over the original data. Examples for the latter capability might include the time
and date of ownership transfer or updating the repair history of a fixed asset. While
these are the most costly of the three tag types and are not practical for tracking
inexpensive items, future standards for electronic product codes (EPC) appear to be
headed in this direction.
RFID Tag
Data capacity
The amount of data storage on a tag can vary, ranging from 16 bits on the low end to as
much as several thousand bits on the high end. Of course, the greater the storage capacity,
the higher the price per tag.
Form factor
The tag and antenna structure can come in a variety of physical form factors and can either
be self-contained or embedded as part of a traditional label structure (i.e., the tag is inside
what looks like a regular bar code label—this is termed a 'Smart Label') companies must
choose the appropriate form factors for the tag very carefully and should expect to use
5
multiple form factors to suit the tagging needs of different physical products and units of
measure. For example, a pallet may have an RFID tag fitted only to an area of protected
placement on the pallet itself. On the other hand, cartons on the pallet have RFID tags
inside bar code labels that also provide operators human-readable information and a back-
up should the tag fail or pass through non RFID-capable supply chain links.
Passive versus active

“Passive” tags have no battery and "broadcast" their data only when energized by a reader.
That means they must be actively polled to send information. "Active" tags are capable of
broadcasting their data using their own battery power. In general, this means that the read
ranges are much greater for active tags than they are for passive tags—perhaps a read
range of 100 feet or more, versus 15 feet or less for most passive tags. The extra capability
and read ranges of active tags, however, come with a cost; they are several times more
expensive than passive tags. Today, active tags are much more likely to be used for high-
value items or fixed assets such as trailers, where the cost is minimal compared to item
value, and very long read ranges are required. Most traditional supply chain applications,
such as the RFID-based tracking and compliance programs emerging in the consumer goods
retail chain, will use the less expensive passive tags.
Frequencies
Like all wireless communications, there are a variety of frequencies or spectra through
which RFID tags can communicate with readers. Again, there are trade-offs among cost,
performance and application requirements. For instance, low-frequency tags are cheaper
than ultra high-frequency (UHF) tags, use less power and are better able to penetrate non-
metallic substances. They are ideal for scanning objects with high water content, such as
fruit, at close range. UHF frequencies typically offer better range and can transfer data
faster. But they use more power and are less likely to pass through some materials. UHF
tags are typically best suited for use with or near wood, paper, cardboard or clothing
products. Compared to low-frequency tags, UHF tags might be better for scanning boxes of
goods as they pass through a bay door into a warehouse. While the tag requirements for
compliance mandates may be narrowly defined, it is likely that a variety of tag types will be
required to solve specific operational issues. You will want to work with a company that is
very knowledgeable in tag and reader technology to appropriately identify the right mix of
RFID technology for your environment and applications.
6
EPC Tags
EPC refers to "electronic product code," an emerging specification for RFID tags, readers
and business applications first developed at the Auto-ID Center at the Massachusetts
Institute of Technology. This organization has provided significant intellectual leadership
toward the use and application of RFID technology. EPC represents a specific approach to
item identification, including an emerging standard for the tags themselves, including both
the data content of the tag and open wireless communication protocols. In a sense, the EPC
movement is combining the data standards embodied in certain bar code specifications,
such as the UPC or UCC-128 bar code standards, with the wireless data communication
standards that have been developed by ANSI and other groups.
1.1.5 Typical applications of RFID
 Automatic Vehicle identification

 Inventory Management
 Work-in-Process
 Container/ Yard Management
 Document/ Jewellery tracking
 Patient Monitoring
1.1.6 The Advantages of RFID Over Bar Coding
1) No "line of sight" requirements: Bar code reads can sometimes be limited or

problematic due to the need to have a direct "line of sight" between a scanner
and a bar code. RFID tags can be read through materials without line of sight.
2) More automated reading: RFID tags can be read automatically when a tagged
product comes past or near a reader, reducing the labor required to scan product
and allowing more proactive, real-time tracking.
3) Improved read rates: RFID tags ultimately offer the promise of higher read
rates than bar codes, especially in high-speed operations such as carton
sortation.
4) Greater data capacity: RFID tags can be easily encoded with item details
such as lot and batch, weight, etc.
5) "Write" capabilities: Because RFID tags can be rewritten with new data as
supply chain activities are completed, tagged products carry updated information
as they move throughout the supply chain.
7
1.1.7 Common Problems with RFID
Some common problems with RFID are reader collision and tag collision. Reader collision
occurs when the signals from two or more readers overlap. The tag is unable to respond to
simultaneous queries. Systems must be carefully set up to avoid this problem. Tag collision
occurs when many tags are present in a small area; but since the read time is very fast, it is
easier for vendors to develop systems that ensure that tags respond one at a time.
1.2 Users of the System
RFID Based Attendance System will be having 4 different kind of users with varying access
levels.
Users are:
1. Admin: Admin will be the user having access to almost everything in the system.He
can manipulate system as per his wish.
2. Operator: Operator will also have access level next to Admin, Operator will operate
the system as per Admin requirement.
3. Employee: Employee will be having access to his personal information only like
profile, attendance, salary etc.
4. Guest: Guest user will have the lowest level of access rights to the system. A guest
only can see company’s basic details.
8
Chapter 3 Client Survey
9
Chapter 3 Requirements of Client
RFID Based Employee Attendance System is a system which completely revolves around
proper management of an organization’s employees attendance tracking and hence
evaluation of salaries as per attendance. The project lays most of the effort in making the
system easy to handle and manage by the end users and providing optimum benefits to
them in concern to managing attendance of employees and hence their equivalent salary
against their attendance. Efforts will be made to make the system more and more feasible.
3.1 Functional Requirements

1) Secure registration of employees in the office
2) Search employees based on different criteria
3) Setup the basic details of organization such as working hours, number of working
days per month to calculate the salaries
4) Set the hierarchy of the organization
5) Send automatic mails to employees regarding salaries, attendance, holidays etc
6) Send messages to mobiles if employee absent or issued salaries or general messages
regarding holiday’s wishes etc.
7) Issue of salaries
8) Employee must be able to view and update his details, view his attendance reports
9) Visitor must be able to view the organization basic details
3.2 Non Functional Requirements

1) Secure access of confidential data (user’s details). SSL can be used.
2) 24 X 7 availability
3) Better component design to get better performance at peak time
4) Flexible service based architecture will be highly desirable for future extension
3.3 Optional Requirements

1) Employee chat
2) Employee discussion forum
10
Chapter 4 Decomposition of Functional Requirements
RFID Based Employment Attendance System doesn’t only provides flexible attendance
system for employees but also provide an organization with a fully organized system which
take cares of new employee registration, making existing employees enable to view their
profile, allows organization to take up a new project from clients, schedule management,
provision of discussion forum and many more useful features.
4.1 Key Modules

1. Registration: Registration module as the name goes will deal with the basic
registration process of employees in the organization. Registration process will go in
a hierarchy which means registration of employees will be done by operator and
those of operators will be done by admin.
2. Salary& Accounting: Salary & Accounting module will deal with salary
management of employees. Salary will be evaluated on the basis of employee’s
attendance. All the necessary allowances and reduction are being made with the
salary which will amount to the gross salary of employee.
3. Searching: Searching will enable operators and admin to search employees on
different criteria viz as per department, as per pay scale, by employee Id or by
employee’s name.
4. Notifications: All the important updates regarding organization, updates to
employee via sms or email regarding any issue or greetings to employees in case of
any festive occasion etc will all come under notifications module.
5. Communication: Communication module will deal with the interaction among
employees of organization or interaction with organization’s operators regarding any
specific topic or related to any issues. This module also holds the provision for online
chat for employees.
6. Attendance: Attendance module is the heart of the project as the whole story goes
around it. I will aim at complete maintenance of employee attendance, in time of an
employee; out time of an employee etc.It will also keep track of all the requests
being made by an employee regarding any leaves and then further approval of it by
operator.
11
7. Work Assignment: Work assignment modules deals with the assignment of work to
employees as per their skills and department. Projects undertaken by company will
get split up into modules which will be then assigned to the employees.
8. Login: This will be a simple login module which will ask the employee for their
username and password. After providing correct username and password employee
will be able to access his/her profile.
9. Schedule Management: Entire organizations day to day schedule as well as
modification in organizations activity calendar will be handled by this module.
10.Profile Management: Profile Management as the name suggest will deal with
management of employees’ personal profile. He/she can update his/her profile as per
requirements following certain norms.
4.2 Modules Description

 Registration
Admin End
 Operator Registration Form
 Fill Registration Details
 Submit
 If correct syntax
 Operator added successfully
 Redirect to same page
 If incorrect syntax
 Validation Rules Check
 Correct erroneous fields
 Cancel
 Redirect to same page
 Registration
Operator End
 Employee Registration Form
 Fill Registration Details
 Submit
 If correct syntax
 Employee added successfully
 If incorrect syntax
12
 Validation Rules Check

 Correct erroneous fields
 Cancel
 Profile Management
Admin End
 View Employee/Operator Details as per search
 Admin can edit only the important fields (e.g. Designation ,Salary ,Account No
,Department)
 If correct syntax
 Are you sure you want to make the changes permanent?
 Yes
 Update changes into database
 No
 If Incorrect syntax
 Validation Rules Check
 Correct erroneous fields
 Deactivate an Employee (Special feature reserved only for Admin)
 Are you sure you want to deactivate this employee
 Yes
 Employee status changed to ‘inactive’
 No
Operator End
 View Profile
 Edit Profile (Only basic information e.g. phone no., profile picture, address etc)
 Yes
13

 No
Employee End
 Operator can view employee profile
 View Profile
 Edit Profile (Only basic information e.g. phone no., profile picture, address etc)
 Yes
 No
 Login
 Admin
 Enter User Id and Password
 If correct
 Login to Admin account
 Logout
 Redirect to login page
 If incorrect
 Redirect to login page
 Login
Common for operator & employees
14
 Enter User Id (RFID No.)

 Enter Password
 If correct
 Login to respective account
 Logout
 Redirect to login page
 If incorrect
 Redirect to Login Page
 Forget Password
 Enter User Id
 Send verification code to mobile
 Enter verification code
 Email sent to user mail id
 Notifications
 Admin End
 Select operator
 Add information of message
 Select mode of message
 Mail
 If correct Syntax
 Prompt Message Successfully.
 If incorrect Syntax
 Redirect to same page with appropriate messages.
 Messages
 Message sent successfully.
 Return to home page.
 If incorrect Syntax.
 Prompt message sending failed.
 Redirect.
 Operator End
Notification to Employees
 Select Employees.
 Select Category
15
 Absent
 Wishes
 Salary
 Add information
 Mail
 Prompt Message Successfully.
 If incorrect Syntax
 Redirect to same page with appropriate messages.
 Messages
 Message sent successfully.
 Return to home page.
 If incorrect Syntax.
 Prompt message sending failed.
 Redirect.
 Search
Admin End
 Search Employee based on:
 ID Wise
 Department Wise
 Name Wise
 Suggestion List will be shown.
 Project Wise
 On Click Search button
 If result found populate list.
 Else record not found.
Operator End
 ID Wise
 Department Wise
 Name Wise
16
 Project Wise
 If result found populate list.
Employee End
 ID Wise
 Department Wise
 Name Wise
 Project Wise
 If result found, populate list.
 Communication
Admin End
 Query Handling
 View all queries
 Select query
 Reply to operator via Email
Operator End
 Query Handling
 View all queries
 Select query
 Forward query to admin(if required)
 Reply to employee via Email
 Discussion Forum
 View report abuse posts.
 Verify post
 Remove posts.
17
Employee End
 Ask Query
 Query form
 Select query type
 Write query
 Send query to operator
 Discussion Forum
 Start new discussion
 View current discussions
 Reply to posts
 Report abuse
 Attendance
Admin End
 Attendance Home
 Available employee list
 Search employee based on:
 ID
 Department
 Name with suggestion list
 Today’s unavailable employee list
 If employee absent>7 days
 Message will be sent to that employee
 Else on official leave
 View full description
 Task involvement
 View current running tasks
 On clicking task
 Populate list of employees involved in that task
 Change the deadline of the task
 Project involvement
 View all company’s project
 Projects have three status:
 Completed
18
 Running
 Not started
 Categories project session wise
 On selecting certain project
 Populate list of all employees’ related to that project
 Attendance tracking
 Track attendance which includes:
 Today’s available employees consisting 3 status:
 In
 Lunch
 Out
 Today’s’ absent employees’
 On clicking any employee
 Redirect to its full profile
 Leave Request
 View list who made leave request, along with 3 status:
 Approved
 Rejected
 Pending
 On clicking any request
 Full description will be shown
 If request
 Approved
 Status changed from pending to approved
 Rejected
 Status changed from pending to approved
 No action
 Status remain pending
 Approved leave request
 List of approved leave request is shown
 On clicking request
 Full description is shown
Operator End
 Attendance tracking
19
 Track attendance which includes:

 Today’s’ available employees consisting 3 status:
 In
 Lunch
 Out
 Today’s’ absent employees’
 On clicking any employee
 Redirect to its full profile
 Generate report
 Shows attendance of all employees’
 Two option to generate employee report:
 Pdf
 Report generated in pdf format
 Excel
 Report generated in excel sheet
Employee End
 View Attendance
 Employee view his attendance:
 Weekly
 Daily
 Monthly
 Yearly
 Ask query
 Employee can report for verification of attendance
 Query form
 Select query type
 Write query
 Send query to operator
 Schedule Management
Admin End
 Add/Update Time slot
 Add new time slot
20
 Select day which is divided in three timeslot:

 Work Time
 Lunch Time
 Coffee Time
 Add time
 If user wants same time slot for all 6 days
 Click on copy to all
 Else add individual time for different days
 Click on save
 Check validation
 If OK save the time slot
 Else redirect to same page with error message
 Add Event
 Add event form
 Fill all necessary details
 Click on save
 If OK send notification to Operator
 Add Task
 Show’s add task page
 Select project
 Enter task name
 Start and Due date
 Set priority:
 High
 Medium
 Low
 Click on save
 If OK redirect to same page with all fields blank
 Add projects
 Fill all necessary project details
 Select tasks involved with the project
21
 Start and Due date

 Set priority:
 High
 Medium
 Low
 Click on save
 Add holiday
 Fill add holiday details
 Start and End date
 Click on save
Employee End
 View Time Slot
 View Holidays
 Work Assignment
Operator End
 Assign Projects
 Assign projects page
 Select project from list
 Select employees to be added to that project
 ID
 Department
 Name
 With suggestion list
 Assign tasks to the employees
 Assign role
 Click on save
22
 Assign Time Slot
 Select employees
 ID
 Department
 Name
 Assign Time slot
 Click on save
 Manage Events
 Manage events created by Admin
 Select event
 Select employees
 ID
 Department
 Name
 Add Guest email address.
 Add Attachments
 Click on send
 If OK send Email & SMS to all employees as well as guest
Employee End
 View assigned projects & tasks
 View Emails & notification related to Events & meetings
23
 Salary & Accounting

Admin End
 Salary assignment as per hierarchy
 Set Bonus schemes
Operator End
 Salary computation as per attendance
 Generate Excel sheet for salary
 Send excel sheet to bank
24
Chapter 5 Modules Division
RFID Based Employee Attendance System comprises of several modules viz registration,
schedule management, salary and accounting etc. Our team comprises of 4 members and
an equal amount of work has been assigned to each and every team member. Following
table shows the module assignment to different team member as per his/her convenience
and skill.
S.No Module Name Assigned To

1 Registration Bharat Marwah
2 Salary & Accounting Mohit Jain
3 Searching Vivek Singh
4 Notifications Abhay Gupta
5 Communication Mohit Jain
6 Attendance Vivek Singh
7 Work Assignment Abhay Gupta
8 Login Bharat Marwah
9 Schedule Management Vivek Singh
10 Profile Management Abhay Gupta
25
Chapter 6 Work Plan
According to standard terminology, "A Work Plan is a deliverable-oriented hierarchical

decomposition of the work to be executed by the project team to accomplish the project
objectives and create the required deliverables. It organizes and defines the total scope of
the project. Each descending level represents an increasingly detailed definition of the
project work."
A work plan is an outline of all tasks that need to be complete in order to finish an entire
project. A work plan includes management’s layout for each member in the team and the
tasks that each individual will be performing.
6.1 Gantt Chart

A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts
illustrate the start and finish dates of the terminal elements and summary elements of
a project. Terminal elements and summary elements comprise the work breakdown
structure of the project. Some Gantt charts also show the dependency (i.e., precedence
network) relationships between activities.
A Gantt chart is a graphical representation of the duration of tasks against the progression
of time. A Gantt chart is a useful tool for planning and scheduling projects.
A Gantt chart is helpful when monitoring a project's progress. A Gantt chart is a type of bar
chart that illustrates a project schedule. Gantt charts illustrate the start and finish dates of
the terminal elements and summary details of project. Terminal elements and summary
elements comprise the work breakdown structure of the project. Some Gantt charts also
show the dependency relationships between activities.
Gantt charts give a clear illustration of project status, but one problem with them is that
they don't indicate task dependencies - you cannot tell how one task falling behind schedule
affects other tasks. The PERT chart, another popular project management charting method,
is designed to do this. Automated Gantt charts store more information about tasks, such as
the individuals assigned to specific tasks, and notes about the procedures. They also offer
the benefit of being easy to change, which is helpful. Charts may be adjusted frequently to
reflect the actual status of project tasks as, almost inevitably; they diverge from the original
plan.
26
Gantt chart
Gantt charts only represent part of the triple constraints (cost, time and scope) of projects,
because they focus primarily on schedule management. Moreover, Gantt charts do not
represent the size of a project or the relative size of work elements, therefore the
magnitude of a behind-schedule condition is easily miscommunicated. If two projects are
the same number of days behind schedule, the larger project has a larger impact on
resource utilization, yet the Gantt does not represent this difference.
Although project management software can show schedule dependencies as lines between
activities, displaying a large number of dependencies may result in a cluttered or
unreadable chart.
27
6.2 CPM and PERT Chart

A PERT chart is a project management tool used to schedule, organize, and coordinate tasks
within a project. PERT stands for Program Evaluation Review Technique, a methodology
developed by the U.S. Navy in the 1950s to manage the Polaris submarine missile program.
A similar methodology, the Critical Path Method (CPM) was developed for project
management in the private sector at about the same time.
A PERT chart presents a graphic illustration of a project as a network diagram consisting of
numbered nodes (either circles or rectangles) representing events, or milestones in the
project linked by labeled vectors (directional lines) representing tasks in the project. The
direction of the arrows on the lines indicates the sequence of tasks.
These tasks are called parallel or concurrent tasks. Tasks that must be completed in
sequence but that don't require resources or completion time are considered to have event
dependency. These are represented by dotted lines with arrows and are called dummy
activities.
The PERT chart is sometimes preferred over the Gantt chart, another popular project
management charting method, because it clearly illustrates task dependencies. On the other
hand, the PERT chart can be much more difficult to interpret, especially on complex
projects. Frequently, project managers use both techniques.
CPM provides the following benefits:
 Provides a graphical view of the project.
 Predicts the time required to complete the project.
 Shows which activities are critical to maintaining the schedule and which are not.
CPM models the activities and events of a project as a network. Activities are depicted as
nodes on the network and events that signify the beginning or ending of activities are
depicted as arcs or lines between the nodes.
Steps in CPM Project Planning
1. Specify the individual activities.
2. Determine the sequence of those activities.
3. Draw a network diagram.
4. Estimate the completion time for each activity.
5. Identify the critical path (longest path through the network)
6. Update the CPM diagram as the project progresses.
28
Activity No Activity Expected completion Dependency

time
1. Team Selection, Client 1 -

Identification & Project Survey
2. Requirements Gathering & Fixation 2 1
3. SRS Submission & Presentation 2 2
4. High Level & Low Level Design 3 3

Submission
5. User Interface & Project Design 2 3,4
6. Database Design 1 3,5
7. Connectivity & Integration 1 5,6
1 2 3 4
6 5
29
TE=1 TE=2 TE=2 TE=3
====== ====== ====== ======

1
dfgf 2
dfgf 3
dfgf 4
dfgf
dg11 dg11 dg11 dg11
1111 1111 1111 1111
TE=1 6 5 TE=2
======
======
dfgf dfgf
dg11 dg11
1111
1111 7
TE=1
======
dfgf
dg11
1111
30
Chapter 7 Software Requirement Specification
7.1 Introduction:
7.1.1 Purpose:
Attendance Management System is an online application developed for daily employee
attendance in companies. The attendance of the employee will be taken by rfid tags and will
automatically stored in the database .According to working hour of the employee salary will
be generated .information about the salary, holidays etc will be sent to the mobile and mail.
Employee can see his/her details, attendance and can also update. Searching of the
employee based on different criteria is provided.
7.1.2 Scope:
This document provides the road map for design of Prototype and development and
maintenance of the attendance management project. This application can be adapted by
any of the organization or firm having distinct number of departments and employees.
The attendance management system is a web application development tool which will be
used across the organization to track the Employee attendance and its information. Some of
the features are:
i. The system provides secure registration of employees in the office
ii. The system provides search employees based on different criteria
iii. Setup the basic details of organization such as working hours, number of working
days per month to calculate the salaries
iv. It also sends automatic mails to employees regarding salaries, attendance, holidays
etc
v. It also provides messages facility to mobiles if employee absent or issued salaries or
general messages regarding holiday’s wishes etc.
vi. Issue of salaries
vii. Employee is able to view and update his details, view his attendance reports
7.1.3 Definition, Acronyms & Abbreviations:

SRS – software Requirement Specification
RFID-Radio Frequency Identification Detection
AMS-Attendance Management System
31
7.1.4 References:
http://www.adcnordic.com/news/mobility-developer-assistant.php
http://www.phidgets.com/
http://rfidrange.com/rfid-programming-with-c-net/
www.workforce.com
www.codeguru.com
7.1.5 Overview:
The SRS will provide a detailed description of the Attendance Management System. This
document will provide the outline of the requirements, overview of the characteristics and
constraints of the system.
7.2 Overall Description:

7.2.1 Product Perspective:
The RFID based AMS System is a package to be used by Companies to improve the
efficiency of Employee Management System. The RFID based AMS System reduces the
overhead in maintain the Employee Attendance. The system provides various features like
calculating the employee salary of Employees at the end of the month based on his
attendance. The Company Administrator keeps the track of all employees enrolled under it.
It is a part of a largest system. The RFID System working can be understood by the given
below figure.
DOOR
8051
Tx POR
T2
R DATA
x PIN
RFID
TAG
RFID BASED SECURITY CUM ATTANDENCE
SYSTEM
32
7.2.2 Interfaces
7.2.2.1 System Interfaces

Following hardware will be required by the system:
 RFID Based Employee Attendance System will interact with
external system by RFID Tags and RFID readers.
 RFID Based Employee Attendance System will maintain the
employee’s attendance by using RFID technology.
7.2.2.2 User Interfaces

Following user interface will be required by the system:
 RFID Based Employee Attendance System will require every
employee to carry a RFID tag stick onto their Id card
 RFID Based Employee Attendance System will also require a RFID
reader installed at the entrance section of office.
7.2.2.3 Software Interfaces:

Software required for the interaction with Application layer is:
 XHTML
Name-Extensible Hyper Text Markup Language
Version -1.1
Source- W3C (World Wide Web Consortium)
Purpose of Using- It is most widely used as Front-end due to its
compatibility with all browsers.
 JavaScript
Name-JavaScript
Version-1.8.5
Source-Mozilla Foundation
Purpose of Using-It is most widely used Client-side Scripting
supported by all Browsers.
Software required for the interaction with Business layer are:

 C#.net
Name-C#.net
Version -4.0
33
Source-Microsoft
Purpose of Using-It provides ease and better environment to the
user to make the business layer more efficient and secure.
 XML
Name-Extensible Markup Language
Version-1.1
Source-W3C (World Wide Web Consortium)
Purpose of Using-It is a light weight file used to store the data; it is
more extensible as compared to any other data storing
technologies.
Software required for the interaction with Data layer are:

 SQL SERVER
Name-Sql Server
Version -2008 R2
Source-Microsoft
Purpose of Using-support for large-scale data centers and
warehouses and also its graphical user interface makes it easier for
users to use.
7.2.2.4 Hardware Interfaces

Following hardware will be required by the system:
RFID Reader: RFID readers are required to detect employee’s
entrance into the office.
RFID Tag: RFID tags will be required by employee’s to make their
attendance recorded.
7.2.2.5 Communication Interfaces:

For the communication purpose we are using following protocols:
 HTTP(Hyper Text Transfer Protocol)
 FTP(File Transfer Protocol)
 SMTP(Simple Mail Transfer Protocol)
34
7.3 Product Function

Following points illustrate the product major functionalities:
 Secure registration of employees in the office
 Search employees based on different criteria
 Setup the basic details of organization such as working hours, number of
working days per month to calculate the salaries
 Set the hierarchy of the organization
 Send automatic mails to employees regarding salaries, attendance, holidays etc
 Send messages to mobiles if employee absent or issued salaries or general
messages regarding holiday’s wishes etc.
 Issue of salaries
 Employee must be able to view and update his details, view his attendance
reports
 Visitor must be able to view the organization basic details
7.4 User Characteristics

The Project consists of four main users:
a) Administrator
b) Operator
c) Employee
d) Guest User
Characteristics of Different Users are as follows:
a) Administrator:
 Admin has all the privilege to grant and revoke the rights to other
users in the system.
 Maintain the records of lower level of hierarchy like Operator and
Employees.
 Admin is able to send notifications to users of the System.
b) Operator:
 Registration of Employees in the Organization.
 Manage employee details like attendance, personal information etc.
 The Operator will issue salary to different employees according to
the attendance.
 Send messages and greetings on festivals and other occasions.
 Issuing and maintaining projects to the different employees.
35
c) Employee:
 View his personal information and make request to the operator in
case he wants to change the information.
 Make a request for having leave.
 Upload assignment and records related to his work.
 Participate in Discussion Forum
7.5 Constraints:
 RFID reader must be installed at the entry point.
 Each employee must have RFID tag.
7.6 Architecture Design

7.6.1 Application Architecture:
In the 3-Tier Architecture of any project we separate all the three layers.
These layers are namely:
 Application Layer: In this layer we include the designing part of our website. It is
also called as “Presentation Layer”. We are using HTML for the designing of our
website.
 Business Logic Layer: In this layer we apply the logic. We write our logic on the .cs
page in Visual Studio.
 Data Layer: This is the 3rd layer in which we keep our database tables. It is kept
separate from other two layers for safety purposes so that no one can steel our
database.
 Presentation GUI: This is the interface which will be provided to the end user.
 Presentation Logic: This will contain all the HTML pages, all script code, AJAX etc.
 BLL: This is the Business Logic Layer. It will contain all the C sharp pages.
 DAL: This is the Data Application Layer. It consists of 3 parts.
o Database
o XML
o Utility Layer
Following figure demonstrate the complete Application Architecture
36
Presentation Layer Presentation GUI
Presentation Layer
Presentation Logic
(HTML pages, java scrip, AJAX)
BLL
Business Layer
(Asp.net with c#)
Business Layer
DAL
Database XML Utility Layer

Data Layer (Stored procedures, SQL (Classes)
server 2008)
Model layer
(Classes)
7.6.2 Process Model: The waterfall model is one of the earliest structured models for
software development. It consists of the following sequential phases through which the
development life cycle progresses:
 System feasibility. In this phase, you consider the various aspects of the targeted
business process, find out which aspects are worth incorporating into a system, and
evaluate various approaches to building the required software.
 Requirement analysis. In this phase, you capture software requirements in such a
way that they can be translated into actual use cases for the system. The
requirements can derive from use cases, performance goals, target deployment, and
so on.
37
 System design. In this phase, you identify the interacting components that make
up the system. You define the exposed interfaces, the communication between the
interfaces, key algorithms used, and the sequence of interaction. An architecture and
design review is conducted at the end of this phase to ensure that the design
conforms to the previously defined requirements.
 Coding and unit testing. In this phase, you write code for the modules that make
up the system. You also review the code and individually test the functionality of
each module.
 Integration and system testing. In this phase, you integrate all of the modules in
the system and test them as a single system for all of the use cases, making sure
that the modules meet the requirements.
 Deployment and maintenance. In this phase, you deploy the software system in
the production environment. You then correct any errors that are identified in this
phase, and add or modify functionality based on the updated requirements.
Changed
Requirements
Communicated
Requirements
Requirements
Requirements Specification
Engineering
Design
Design Specification
Executable
Software
Programming Maintenance
Modules
Integrated
Software
Integration Product
Delivered
Software
Delivery
Product
Waterfall Model
38
7.7 Process Flow Diagram
7.7.1 Class Diagram
39
7.7.2 Sequence Diagram
Communication Sequence Diagram
Login QuerySection Operator Admin
1: EmployeeLogin
2: Ask Query
3: Reply
4: ForwardQuerytoAdmin
5: Reply
Discussion Sequence Diagram
Login Discussion Server Database
1: Employee Login
2: AddPost
3: ExecuteQuery
4: StartNew
5: ExecuteQuery
6: Operator Login
7: AddPost
8: ExecuteQuery
9: StartNew
10: ExecuteQuery
40
Login Sequence Diagram
user server
account
1: enter userid and password
2: validate
3: if valid
4: on invalid redirect to login page
5: Forget password
6: send verification code to mobile
7: Enter verification code
8: validate
9: if valid Email sent to user mail id
10: Logout
41
Notification_admin Sequence Diagram
Admin Operator Notification Server
admin login
fill details and send
validation
if valid send notification to operator
if invalid show error message
Notification_operator Sequence Diagram
Operator Employee Notification Server
operator login
fill details and send
validation
if valid send notification to employee
if invalid show error message
42
Registration Employee Sequence Diagram
employee operator server database
1: submit details
2: fill form of info of employee
3: check validation
4: if valid update database
5: on invalid show error message
Registration Operator Sequence Diagram
operator admin server database
1: view details
2: fill form of info of operator
3: check validation
43
Profile Sequence Diagram
Database
Login Profile server
1: employee login
2: request view profile
3: execute querry
4: display record
5: edit/update profile
6: check validation
9: operator login
10: request view profile
11: execute querry
12: display record
14: check validation
16: if invalid show error message
17: request view employe profile
18: execute querry
19: display record
20: admin login
21: request view employee/operator profile
22: execute querry
23: display record
28: deactivate employee
29: validation
31: if invalid show error
44
Salary Sequence Diagram
Login Salary Server Database
1: Admin Login
2: ManageSalary
3: Validation
4: if[Valid] SendToDatabase
5: If[Invalid] ErrorMessage
6: OperatorLogin
7: Issue Salary
8: Transaction
9: SuccessfulTransaction
10: Unsuccessful Transaction
Search Sequence Diagram
Login Search Database
1: Admin Login
2: SearchEmployee/Operator
3: SearchResult
4: OperatorLogin
5: SearchEmployee
6: SearchResult
45
Schedule Management Sequence Diagram
Database
Login Schedule server
Management
1: employee login
2: view time slot
3: execute querry
4: display record
5: view holidays
6: execute querry
7: display record
8: admin login
9: add/update time slot
10: validation
13: add events
17: add holidays
18: validation
20: if invalid show error
21: add task
22: validation
24: if invakid show error message
25: add project
26: validation
46
Work Assignment Sequence Diagram
Database
Login Work server
Assignment
1: operator login
2: assign project
3: validation
6: assign timeslot for work
7: validation
10: manage event
11: validation
14: employee login
15: view assigned project/task
16: execute querry
17: display record
47
7.8 Database Diagram
7.8.1 ERD Diagram
Buy SmartDraw !- purchased copies print this

document without a watermark .
Visit www.smartdraw.com or call 1-800-768-3729.
48
7.8.2 Schemas
Table Name Column Name Data Type Constraint
Employee_tbl Emp_id nvarchar(50) Primary Key,Not

Null
Emp_name nvarchar(MAX) Not Null
Emp_dob datetime Not Null
Gender varchar(50) Not Null
Marital_status nvarchar(50) Not Null
Language nvarchar(50) Not Null
Phone_no Decimal(30,0) Allow null
Web_address nvarchar(MAX) Allow Null
Im_address nvarchar(50) Allow Null
Address nvarchar(MAX) Null
State nvarchar(50) Not Null
City nvarchar(50) Not Null
Pincode nvarchar(50) Not Null
Postion nvarchar(50) Not Null
Location nvarchar(50) Not Null
Department nvarchar(50) Not Null
Photo_path nvarchar(MAX) Allow null
Status nvarchar(20) Not Null
Operator Table Opr_id nvarchar(50) Primary Key,Not

Null
49
Opr _name nvarchar(MAX) Not Null
Opr _dob datetime Not Null
Project Table Project_id nvarchar(50) Primary Key,Not

Null
P_title nvarchar(MAX) Not Null
P_description nvarchar(MAX) Not Null
Start_date datetime Not Null
50
End_date datetime Not Null
Priority nvarchar(50) Not Null
Attch nvarchar(MAX) AllowNull

Null
51

Null
Login_tbl Username nvarchar(50) Not Null
Password nvarchar(50) Not Null
52
Usertype nvarchar(50) Not null
Theme Nvarchar(50) Not null

Null
Query Table queryId nvarchar(50) Primary Key, Not

Null
53
querySubject nvarchar(MAX) Not Null
queryDetail nvarchar(MAX) Not Null
queryType varchar(50) Not Null
queryDate datetime Not Null
empId nvarchar(50) Not Null
Discussion Table discussionId nvarchar(50) Primary Key, Not

Null
discussionTopic nvarchar(MAX) Not Null
discussionType nvarchar(50) Not Null
discussionTagLine nvarchar(MAX) Null
discussionPost nvarchar(MAX) Not Null
discussionDateTime datetime Not Null
empType nvarchar(50) Not Null
Salary Accounting departmentId Varchar(50) Not Null

Table
Designation Varchar(50) Not Null
Basic Pay Decimal(18,0) Not Null
DA Decimal(2,2) Not Null
HRA Decimal(2,2) Not Null
CCA Decimal(2,2) Not Null
GPF Decimal(2,2) Not Null
SI Decimal(2,2) Not Null
54
incomeTax Decimal(2,2) Not Null
Rebate Decimal(2,2) Not Null
Reduction Decimal(2,2) Not Null
Date Datetime Not Null

Null
55
AddProject_tbl Project_id nvarchar(50) Primary Key,Not

Null

Null
56
7.9 Use Case Diagram
Admin Use Case
Login
Operator Registration
Admin
View/Edit Employee Details
Notifications
View Attendance
Salary Assignment
57
Employee Use Case
Login
View/Edit Profile
Discussion Forum
Employee View Attendance
View Schedule
View Alloted Projects
Ask Query
58
Operator Use Case
Login
Employee registration
View/Edit Employee Details
Notifications
Query Handling
Operator
Discussion Forum
View Attendance
Work Assignment
59
Guest Use Case
View Company Basic Details
Guest User
View News & Updates
View Discussions
7.10 Assumption and Dependencies

1. During registration process of employee it is required that all the relevant
Information must be provided by the employee
2. To track attendance of employee’s it is assumed that every employee is occupied
with a RFID tag & reader is installed properly.
7.11 Use Case Reports
 Module Number:1.0
 Module Name: Registration
 Prepared By: Bharat Marwah
60
 Description: Registration of the employees will be done under this module. It includes
all the information regarding the personal, social, internet and bank details of the
employee.
 Layout
o Screenshot
o Control Listing & Description
Caption Contr Field Contro Type Siz Defau Navigation Validation Remarks
ol l type e lt
Name
Home _Hom -- Link -- -- -- Employee’s -- --
elink home page
Services _Servi -- Link -- -- -- Company’s

ceslink services
Track _ -- Link -- -- -- Tracking

Attendan Track employee’s
Attend
ce Attendance
anceli
61
nk
Leave _ -- Link -- -- -- Checking

Request Leave Employee’s
Reque
Leave
stlink
Requests
Contact _Cont -- Link -- -- -- Company’s

actLin Contact
k
Details
About _Abou -- Link -- -- -- Company’s

tLink basic details
Assign _Assig -- Link -- -- -- Company’s

Project nProje Project
ctLink
Assign _Assig -- Link -- -- -- Company’s

Task nTask Task
Link
Notificati _Notifi -- Link -- -- -- Company’s

on cation notification
Link
Updates _Upda -- Link -- -- -- Company’s

tesLin Update
k
Personal _ -- Panel -- -- -- Enter

Informat Person employee
al
ion personal
Inform
ationP information
nl
Title -- Label, Char 30 -- Select Title

Dropdo
wn
Name Emp_na Label, Char 20 --

me Textbox
62
Date of Emp_do Label, --

Birth b Textbox
Gender Gender Label, Male

Radio select
button ed
Marital Marital_s Label, --

Status` tatus Dropdo
wn
Languag Languag Label, --

e e Textbox
Phone Phone_n Panel --

Numbers o
Internet -- Panel --
Web Web_ad Label, --

Address dress Textbox
Email -- Label, --
Address Textbox
IM Im_addr Label, --
address ess Textbox
Address Address Panel --
State State Label, --

Dropdo
wn
City City Label, --

Dropdo
wn
63
Postal Pincode Label, --

Code Textbox
Employ -- Panel --
ment
Position Postion Label, --

Dropdo
wn
Location Location Label, --

Multilin
e
Textbox
Departm Departm Label, --

ent ent Dropdo
wn
Submit -- Button --
Cancel -- Button --
o Database Detail
Table Name Column Name Key Data Type Constraint

Employee_tbl Emp_id Primary nvarchar(50) Not Null
Key
Emp_fname nvarchar(50) Not Null
Emp_mname nvarchar(50) NotNull
Emp_lname nvarchar(50) NotNull
Title Varchar(50) NotNull
email nvarchar(50) NotNull
64

Phone_no nvarchar(50) Not Null
Mobile phone nvarchar(50) Allow null
Home fax nvarchar(50) Allow null
Pager nvarchar(50) Allow null
Country nvarchar(50) NotNull
o Business Rules
1. Special character should not be used in the Textboxes
2. Radio Button is to be checked before searching
3. Dropdown will get filled at time of page load
4. On clicking submit button employee is to be registered in company database.
5. Employee Name must not exceed more than 50 words.
6. All validations must be checked before submitting the page.
o User Characteristics
N/A
o Form Validations
1. Employee Name=Allow Null
2. Employee Id=Allow Null
3. Department=Allow Null
65
4. All fields must be reset

5. Selectshould be the first item for all dropdown.
 Module Number: 2.0

 Module Name: Login
 Description: Login provides security to the website as only authenticated user can
only use and access the website. Each user in the system have user Id and
password which is used for authentication in the whole system.
 Layout
o Screenshot
66
ol l type e lt
Name
Home _hom -- Link -- -- -- Employee’s -- --
e home page
Services _servi -- Link -- -- -- Company’s -- --

ces services
Contact _conta -- Link -- -- -- Company’s -- --

ct Contact
Details
About _abou -- Link -- -- -- Company’s -- --

t basic details
Updates _upda -- Link -- -- -- Company’s -- --

tes Update
Login _Login -- Panel -- -- -- Enter login -- --

pnl details
Usernam _User -- Label -- -- -- -- -- --

e nameL
bl
Usernam _User Usernam Textbox nvarc 50 -- Enter User Yes --

e nameT e har Id
xt
Passwor _Pass Label, -- -- -- -- -- --

d wordL
bl
Passwor _pass Passwor Textbox nvarc 50 -- Enter Yes --

d wordT d har Password
xt
Rememb -- Label, -- -- Unche Check to -- --

er checkb cked remember
67
ox
Login -- Button -- -- -- Click on -- --

Login
Cancel -- Button -- -- -- Click to -- --

Cancel
o Database Details

Key
68


o Business Rules
2. Checkbox is to be checked if user wants to remember me
3. All validations must be checked before login
4. On clicking login button redirect to the corresponding user profile.
5. Username must not exceed more than 50 words.
N/A
o Form Validations
1. Username=Not Null
2. Password =Not Null
3. Checkbox= default not checked
69

 Module Name: Forgot Password
 Description: This module provides provision to employee’s to retain their
password in case they forget their password
 Layout
o Screenshot
Caption Contr Field Control Type Siz Defaul Navigation Validation Remarks
ol type e t
Name
Email _email Email TextBox nvarc 50 Yes
txt har
70
Captcha _captc -- TextBox nvarc 50 Yes

hatxt har
Send _send -- Button -- -- -- Loginpage

but
with
message
Cancel _canc -- Button -- -- -- Login Page

elbut
o Database Details

Key
71

o Business Rules
5. Username must not exceed more than 50 words
o User Characteristic
N/A
o Form Validations
72

 Module Name: Change Password
 Description: This module provides provision to employee’s to change their
password and set a new password
 Layout
o Screenshot
ol l type e lt
Name
oldpassw _oldpa Passwor TextBo nvarc 50 -- -- Yes --
ord sstxt d x har
73
newpass _newp -- TextBo nvarc 50 -- -- -- --

word asstxt x har
Confirm _conp -- Button -- -- -- -- Yes --

passwor asstxt
Update _upda -- Button -- -- -- Confirm new -- --

tebut password
page
Cancel _canc -- Button -- -- -- Redirect on -- --

elbut same page
-
o Database Details

Key
74

o Business Rules
5. Username must not exceed more than 50 words.
N/A
75
o Form Validations

 Module Name: Salary & Accounting
 Prepared By: Mohit Jain
 Description: Salary & Accounting module will deal with the complete evaluation
process of salary for employees. Admin will manage the important constraints related
to salary while the operator will involve in task of issuing salary to employees.
 Layout
o Screenshot
76
ol type e t
Name
Departme _depa departmen Label, varch 50 Select -- Yes --
nt rtment tName ar
Name Dropdo
drp
wn
Designati _desig Designati Label, varch 50 Select -- Yes --

on nation on Dropdo ar
drp
wn
Basic Pay _basic Basic Pay Label, decim 10 -- -- Yes --

Paytb Textbox al
Allowanc -- -- Fieldset -- -- No --
es
DA _datb DA Label, decim 10 -- -- Yes --

Textbox al
HRA _hratb HRA Label, decim 10 -- -- Yes --

Textbox al
CCA _ccatb CCA Label, decim 10 -- -- Yes --

Textbox al
Deduction -- -- Fieldset -- -- No --
PF _pftb PF Label, decim 10 -- -- Yes --

Textbox al
ESI _esitb ESI Label, decim 10 -- -- Yes --

Textbox al
Rebate _rebat Rebate Label, decim 10 -- -- Yes --

etb Textbox al
77
Saving _reduc Reduction Label, decim 10 -- -- Yes --

Reduction tiontb Textbox al
Income _inco incomeTa Label, decim 10 -- -- Yes --

Tax meTax x Textbox al
tb

nt rtmtnt tName ar
drp Dropdo
wn
Designati _desig Designati Label -- Select -- Yes --

on nationl on
bl
Basic Pay _basic Basic Pay Label -- -- -- Yes --

Paylbl
Allowanc -- -- Label -- -- -- Yes --

es
DA _dalbl DA Label -- -- -- Yes --
HRA _hralb HRA Label -- -- -- Yes --

l
CCA _ccalb CCA Label -- -- -- Yes --

l
Deduction _dedu -- Label -- -- -- No --

ctionlb
l
PF _pflbl PF Label -- -- -- No --
ESI _esilbl ESI Label -- -- -- No --
Rebate _rebat Rebate Label -- -- -- No --

elbl
Saving _reduc Reduction Label -- -- -- No --

Reduction tionlbl
78
Income _inco incomeTa Label -- -- -- No --

Tax meTax x
lbl
Edit _editb -- Button -- -- Edit Edit Salary No --

tn Page
o Database Details

Salary departmentId Primary Key Varchar(50) Not Null
Accounting Table
departmentName -- Varchar(50) Not Null
Designation -- Varchar(50) Not Null
Basic Pay -- Decimal(18,0) Not Null
DA -- Decimal(2,2) Not Null
HRA -- Decimal(2,2) Not Null
CCA -- Decimal(2,2) Not Null
GPF -- Decimal(2,2) Not Null
SI -- Decimal(2,2) Not Null
incomeTax -- Decimal(2,2) Not Null
Rebate -- Decimal(2,2) Not Null
Reduction -- Decimal(2,2) Not Null
Date -- Datetime Not Null
o Business Rules
1. Values to be filled in DA, HRA, CCA, GPF, and ESI are in terms of
percentage.
2. DA will get increment yearly.
N/A
79
o Form Validations
1. Department dropdown will get fill automatically.
2. Designation dropdown will get fill according to department.

 Module Name: Edit Salary
 Description: Edit Salary module will totally be in hands of Admin. Admin can
make changes in the attributes counting to gross salary of employees
 Layout
o Screenshot
80
ol type e t
Name
nt rtment tName ar
Name Dropdo
drp
wn
Designati _desig Designati Label, varch 50 Select -- Yes --

drp
wn
Basic Pay _basic Basic Pay Label, decim 10 -- -- Yes --

Paytb Textbox al
Allowanc -- -- Fieldset -- -- No --
es
DA _datb DA Label, decim 10 -- -- Yes --

Textbox al
HRA _hratb HRA Label, decim 10 -- -- Yes --

Textbox al
CCA _ccatb CCA Label, decim 10 -- -- Yes --

Textbox al
Deduction -- -- Fieldset -- -- No --
PF _pftb PF Label, decim 10 -- -- Yes --

Textbox al
ESI _esitb ESI Label, decim 10 -- -- Yes --

Textbox al
Rebate _rebat Rebate Label, decim 10 -- -- Yes --

etb Textbox al
81
Saving _reduc Reduction Label, decim 10 -- -- Yes --

Reduction tiontb Textbox al
Income _inco incomeTa Label, decim 10 -- -- Yes --

Tax meTax x Textbox al
tb

nt rtmtnt tName ar
drp Dropdo
wn
Designati _desig Designati Label -- Select -- Yes --

on nationl on
bl
Basic Pay _basic Basic Pay Label -- -- -- Yes --

Paylbl
Allowanc -- -- Label -- -- -- Yes --

es
DA _dalbl DA Label -- -- -- Yes --
HRA _hralb HRA Label -- -- -- Yes --

l
CCA _ccalb CCA Label -- -- -- Yes --

l
Deduction _dedu -- Label -- -- -- No --

ctionlb
l
PF _pflbl PF Label -- -- -- No --
ESI _esilbl ESI Label -- -- -- No --
Rebate _rebat Rebate Label -- -- -- No --

elbl
Saving _reduc Reduction Label -- -- -- No --

Reduction tionlbl
82
Income _inco incomeTa Label -- -- -- No --

Tax meTax x
lbl
Save _save -- Button -- -- Save Redirect to No --

btn same page
with
appropriate
message
Revert _rever -- Button -- -- Revert Redirect to No --

tbtn salary page
o Database Details

Accounting
Table
83
o Business Rules
percentage.
N/A
o Form Validations
o Department dropdown will get fill automatically.
o Designation dropdown will get fill according to department.
o Selectshould be the first item for all dropdown.

 Module Name: Issue Salary
 Description: Issue salary module deals with issuing of salary to employees by
operator. Operator will issue salary to employees as per department & designation of
employee.
 Layout
o Screenshot
84
ol type e t
Name
Departme _depa departmen Label, varch 50 Select -- Yes
nt rtment tName ar
drp Dropdo
wn
Designati _desig Designati Label, varch 50 Select -- Yes

drp
wn
Select All _selec -- Label,C -- -- -- -- No Select All

aAllcb heckbox Employees
Issue _issue -- Button -- -- Issue -- No --

btn
o Database Details

Accounting Table
85

o Business Rules
percentage.
N/A
o Form Validations
1. Department dropdown will get fill automatically.
2. Designation dropdown will get fill according to department.

 Module Name: Communication
 Description: Employees can communicate & share their views through discussion
forums. Also, employees can post their queries to operator regarding issues related
to salary, project etc.
 Layout
o Screenshot
86
ol l type e lt
Name
Home -- -- Link -- -- Employee’s No --
home page
Services -- -- Link -- -- Company’s No --

services
Forum -- -- Link -- -- Discussion No --

Forum
Portfolio -- -- Link -- -- Company’s No --

Portfolio
Contact -- -- Link -- -- Company’s No --

Contact
Details
About -- -- Link -- -- Company’s No --
87
basic details
My -- -- Link -- -- Employee’s No --
Attendan attendance
ce status
Salary salary details
Profile Profile
Project project
details
Queries queries
section
Query _quer queryTy Dropdo Varch 50 -- -- Yes --

Type yType pe wn list ar
drp
Subject _subje querySu Textbox Varch 50 -- -- Yes --

cttb bject ar
Query _quer queryDet Textbox Varch MA -- -- Yes --

yDetai ail ar X
ltb
I accept -- -- Hyperli -- -- -- Yes --

the nk
condition
s
Submit _subm -- Button -- -- -- No --

itbtn
Cancel _canc -- Button -- -- -- No --

elbtn
88
Search _searc -- Textbox -- Search -- No --

Here htb Here
Active _activ -- Label -- -- -- No --

Board eBoar
dlbl
Started _start empId Label -- -- -- Yes --

By edBylb
l
Posts _posts -- Label -- -- -- No --

lbl
Last Post _lastP -- Label -- -- -- No --

ostlbl
Others _other -- Label -- -- -- No --

slbl
Forum _statis -- Label -- -- -- No --

Statistics ticslbl
Topics _topic -- Label -- -- -- No --

slbl
Total _total -- Label -- -- -- No --

Posts Postsl
bl
Available _avail -- Label -- -- -- No --

Users ableUs
erslbl
Start _start -- Label -- -- -- No --

New Newlbl
Discussi
on
Category _categ discussio Label. Varch 50 Select -- Yes --

orydrp nCategor Dropdo ar Categ
y wn ory
Topic _topic discussio Label, Varch 50 -- -- Yes --
89
tb nTopic Textbox ar
Tag Line _tagLi discussio Label,T Varch 50 -- -- Yes --

netb nTagLine extbox ar
Post _postt discussio Label, Varch MA -- -- Yes --

b nPost Textbox ar X
Post _postl discussio Label -- -- -- No --

bl nPost
Posted _poste empId Label -- -- -- No --

By dBylbl
Date/Ti _datel Date Label -- -- -- No --

me bl
Start _start -- Link -- -- Start New No --

New Newlb Button discussion
tn
discussio
n
Page _page -- Label, -- 1 Navigate to No --

drp Dropdo specified
wn page
Sorted _sorte -- Label,D Varch 50 Last -- No --

By dBydr ropdow ar Modifi
p
n ed
Add Your _addP -- Label, Varch MA -- -- Yes --

Post osttb Textbox ar X

itbtn
90
o Database Details

Query Table queryId nvarchar(50) Primary Key,Not
Null
Null
o Business Rules
1. Length of query subject must not exceed 50 words
2. Conditions checkbox must be checked to post query
3. Discussion Forum will get filled at time of page load
4. Posts will be sorted as per they get modified after page load
5. Tag Line must not exceed more than 50 words.
6. Topic must not exceed more than 30 words
N/A
o Form Validations
o Query Subject=Not Null
o Query Detail=Not Null
91
o Discussion Topic=Not Null

o Discussion Post=Not Null

 Module Name: Active Board Post
forums. Also, employees can post their queries to operator regarding issues related to
salary, project etc.
 Layout
o Screenshot
92
ol l type e lt
Name
home page

services

Forum

Portfolio

Contact
Details

basic details
Attendan attendance
ce status
Profile Profile
Project project
details
Queries queries
93
section

drp

cttb bject ar

yDetai ail ar X
ltb

the nk
condition
s

itbtn

elbtn

Here htb Here
Active _activ -- Label -- -- -- No --

Board eBoar
dlbl

By edBylb
l

lbl

ostlbl

Statistics ticslbl
94

slbl

Posts Postsl
bl

Users ableUs
erslbl

New Newlbl
Discussi
on

y wn ory

tb nTopic Textbox ar



bl nPost

By dBylbl

me bl

tn
discussio
95

wn page

p
n ed


itbtn
o Database Details

Null
Null
96
o Business Rules
N/A
o Form Validations

 Module Name: Employee Post
forums. Also, employees can post their queries to operator regarding issues related
to salary, project etc.
97
 Layout
o Screenshot
ol l type e lt
Name
home page

services

Forum

Portfolio

Contact
98
Details

basic details
Attendan attendance
ce status
Profile Profile
Project project
details
Queries queries
section

drp

cttb bject ar

yDetai ail ar X
ltb

the nk
condition
s

itbtn
99

elbtn

Here htb Here

By edBylb
l

lbl

ostlbl
Others _other -- Label -- -- -- No --

slbl

Statistics ticslbl

slbl

Posts Postsl
bl

Users ableUs
erslbl

New Newlbl
Discussi
on

y wn ory

tb ar
100
nTopic Textbox



bl nPost

By dBylbl

me bl

tn
discussio
n

wn page

p
n ed


itbtn
101
o Database Details

Null
Null
o Business Rules
N/A
o Form Validations
102


 Module Name: Employee Attendance
 Prepared By: Vivek Singh
 Description: Operator and Admin will track the attendance of the employee; at
the end of the month based on the employees attendance the salary is issued.
Employees can view & download their attendance in excel format.
 Layout
o Screenshot
ol l type e lt
Name
Home -- -- Link -- -- -- Employee’s -- --
home page
Services -- -- Link -- -- -- Company’s -- --

services
103
Track -- -- Link -- -- -- Tracking -- --

Attendan employee’s
ce Attendance
Leave -- -- Link -- -- -- Checking -- --

Request Employee’s
Leave
Requests
Contact -- -- Link -- -- -- Company’s -- --

Contact
Details
About -- -- Link -- -- -- Company’s -- --

basic details
Project -- -- Link -- -- -- Company’s -- --

Project
Task -- -- Link -- -- -- Company’s -- --

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday
Add -- -- Link -- -- -- Adding new -- --

Event Event
Schedule -- -- Link -- -- -- Add -- --

Company’s
Schedule
Available _avail Employe Grid -- -- -- -- -- --

Employe ableE e_tbl view
mploy
es
eegv
Unavaila _unav Employe Grid -- -- -- -- -- --

ble ailable e_tbl view
Emplo
Employe
yeegv
104
es
Category _categ -- Label, -- -- -- -- -- --

oryrb Radio
Buttons
Employe _empI Emp_Id Label, varch 50 -- -- --

e Id dtb Textbox ar
Employe _emp Emp_na Label, Varch 50 -- -- --

e Name Namet me Textbox ar
b
Departm _depa Dept Label, varch 50 -- -- --

ent rtment Dropdo ar
drp
wn
Match _matc -- Radio Match -- --

All/Any hrb Button Any
Search _searc -- Button -- Redirect to --

hbtn same page
Reset _reset -- Button -- Revert --

btn
o Database Details

Employee_tbl Emp_id Primary nvarchar(50) Primary
Key Key,Not Null
105

o Business Rules
3. Grid view will get filled at time of page load
4. On clicking search button result is to be shown on selected grid view.
Employee must possess a RFID tag.
o Form Validations
4. By default Match any radio button is checked

 Module Name: Available Employees List
 Description: This module will provide the admin & operator with the list of all
available employees.
106
 Layout
o Screenshot
ol l type e lt
Name
home page

services

ce Attendance

Leave
107
Requests

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event

Company’s
Schedule

mploy
es
eegv

Emplo
Employe
yeegv
es

oryrb Radio
Buttons

dtb ar
108
e Id Textbox

b

drp
wn


hbtn same page

btn
o Database Details

Key Key,Not Null
109

o Business Rules
o Form Validations

 Module Name: Unavailable Employees List
 Description: This module will provide the admin & operator with the list of all
unavailable or absent employees.
110
 Layout
o Screenshot
ol l type e lt
Name
home page

services

ce Attendance

Leave
Requests
111

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event

Company’s
Schedule

mploy
es
eegv

Emplo
Employe
yeegv
es

oryrb Radio
Buttons

e Id dtb Textbox ar
112

b

drp
wn


hbtn same page

btn
o Database Details

Key Key,Not Null
113

o Business Rules
o Form Validations

 Module Name: Searching
 Description: This module will provide the admin & operator with the facility to
search an employee on basis of various parameters like designation, department
etc. Provision for advance search has also been provided.
114
 Layout
o Screenshot
ol l type e lt
Name
home page

services

ce Attendance

Leave
115
Requests

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event

Company’s
Schedule

mploy
es
eegv

Emplo
Employe
yeegv
es

oryrb Radio
Buttons

dtb ar
116
e Id Textbox

b

drp
wn


hbtn same page

btn
o Database Details

Key Key,Not Null
117

o Business Rules
o Form Validations

 Module Name: Schedule Management
 Description: Schedule Management module assists Admin in adding and updating
company schedules like adding projects. Tasks, timetable, events etc.
118
 Layout
o Screenshot
ol l type e lt
Name
home page

services

ce Attendance

Leave
Requests
119

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event

Company’s
Schedule
Project _ptitle Project Label, Varch 50 -- -- Yes --

Title tb Title textbox ar
Descripti _descr Descripti Multilin Varch Ma -- -- -- --

on iptiont on e ar x
b
textbox
Start _start Start Label, Dateti -- -- -- Yes --

date dateca date calende me
l
r
End Date _endd End Date Label, dateti -- -- -- yes --

atecal calende me
Priority _priori Priority Label, Varch 50 -- -- -- --

tydrp Dropdo ar
120
wn
Status _statu Status Label, Varch 50 -- -- -- --

sdrp Dropdo ar
wn
Attachm _attac Attachm Upload varch ma -- -- -- --

ent upl ent control ar x
Add _addb -- Button -- -- -- Redirect to -- --

tn same page
Reset _reset -- Button -- -- -- Redirect to -- --

btn same page
o Database Details

AddProject_tbl Project_id Primary nvarchar(50) Primary Key,Not
Key Null
121
o Business Rules
2. Validation is to used in assigning date
4. On clicking Add button Project is to added in project list.
5. Project Title must not exceed more than 100 words.
N/A
o Form Validations
1. Project Tile =Not Null
2. Project Description=Not Null
3. Priority=Not Null
4. Start and End Date= Not Null

 Module Name: Notifications
 Prepared By: Abhay Gupta
 Description: Notification module provides facility to admin to view notifications
regarding their salary, attendance, holidays, leave request etc. Admin can delete
the notification. Admin can view details of notification and can reply.
 Layout
o Screenshot
122
ol l type e lt
Name
Home -- -- Link -- -- -- Admin’s -- --
home page

services

Leave
Requests

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event

Company’s
Schedule
Notificati _notifi notificati Gridvie -- -- -- -- -- --

ationLi
123
on List stgv on_tbl w with

checkb
ox and
link
Delete _delbt -- Button -- -- -- Redirect on -- --

n same page
Cancel _canc -- Button -- -- -- Revert

elbtn
Reply _reply -- Button -- -- -- Reply -- --

btn notification
page
o Database Details

Notification_tbl Notification_id Primary nvarchar(MAX) Primary
Key Key,Not Null
Notification_detail -- datetime Not Null
Notification_type -- varchar(50) Not Null
Sending_type -- nvarchar(50) Not Null
Sender -- nvarchar(50) Not Null
Receiver -- Decimal(30,0) Allow null
o Business Rules
5. Project Title must not exceed more than 100 words.
124
N/A
o Form Validations
1. To=Not Null
2. Subject=Not Null
3. Message=Message Null

 Module Name: Mail Notifications
 Description: Notification module provides facility to admin to send notifications to
operator regarding salary, attendance, holidays, leave request etc.
 Layout
o Screenshot
125
ol l type e lt
Name
Home -- -- Link -- -- -- Admin home -- --
page

services

ce Attendance

Leave
Requests

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event
126
Company’s
Schedule
Operator _opLis Operator Gridvie -- -- -- -- -- --

List tgv _tbl w with
checkb
ox and
link
To _totb -- Multilin varch 50 -- -- yes --

e ar
textbox
,Lable
Subject _subtb -- Label, -- -- -- -- Yes --

Textbox
Message _msgt -- Label, -- -- -- -- Yes --

b Multilin
eTextbo
x
Send _send -- Label, -- -- -- -- -- --

Email Emailb Button
tn
Operator _opIdt op_Id Label, varch 50 -- -- --

Id b Textbox ar
Operator _opNa op_name Label, Varch 50 -- -- --

Name metb Textbox ar

drp
wn

127

hbtn same page

btn
o Database Details

Key Key,Not Null
Notification_detai -- datetime Not Null
l
Key Key,Not Null
Emp_name -- nvarchar(MAX) Not Null
Emp_dob -- datetime Not Null
Gender -- varchar(50) Not Null
Marital_status -- nvarchar(50) Not Null
Language -- nvarchar(50) Not Null
Phone_no -- Decimal(30,0) Allow null
Web_address -- nvarchar(MAX) Allow Null
Im_address -- nvarchar(50) Allow Null
Address -- nvarchar(MAX) Null
State -- nvarchar(50) Not Null
City -- nvarchar(50) Not Null
Pincode -- nvarchar(50) Not Null
Postion -- nvarchar(50) Not Null
Location -- nvarchar(50) Not Null
128
Department -- nvarchar(50) Not Null

Photo_path -- nvarchar(MAX) Allow null
Status -- nvarchar(20) Not Null
o Business Rules
5. Project Title must not exceed more than 100 words
N/A
o Form Validations
1. To=Not Null
2. Subject=Not Null

 Module Name: Message Notifications
 Description: Message Notification module provides facility to admin to send
notifications to operator regarding salary, attendance, holidays, leave request etc
via sms.
 Layout
o Screenshot
129
ol l type e lt
Name
Home -- -- Link -- -- -- Admin home -- --
page

services

ce Attendance

Leave
Requests

Contact
130
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event

Company’s
Schedule
Operator _opLis Operator Gridvie -- -- -- -- -- --

List tgv _tbl w with
checkb
ox and
link

e ar
textbox
,Lable
Subject _subtb -- Label, -- -- -- -- Yes --

Textbox

b Multilin
eTextbo
x
131
Send _send -- Label, -- -- -- -- -- --

Email Emailb Button
tn
Operator _opIdt op_Id Label, varch 50 -- -- --

Id b Textbox ar
Operator _opNa op_name Label, Varch 50 -- -- --

Name metb Textbox ar

drp
wn


hbtn same page

btn
o Database Details

Key Key,Not Null
Notification_detai -- datetime Not Null
l
Key Key,Not Null
Emp_name -- nvarchar(MAX) Not Null
132
Emp_dob -- datetime Not Null

Gender -- varchar(50) Not Null
Marital_status -- nvarchar(50) Not Null
Language -- nvarchar(50) Not Null
Phone_no -- Decimal(30,0) Allow null
Web_address -- nvarchar(MAX) Allow Null
Im_address -- nvarchar(50) Allow Null
Address -- nvarchar(MAX) Null
State -- nvarchar(50) Not Null
City -- nvarchar(50) Not Null
Pincode -- nvarchar(50) Not Null
Postion -- nvarchar(50) Not Null
Location -- nvarchar(50) Not Null
o Business Rules
N/A
o Form Validations
1. To=Not Null
2. Subject=Not Null
133

 Module Name: Reply Notifications
 Description: Notification module provides facility to admin to reply particular
notification to the sender.
 Layout
o Screenshot
ol l type e lt
Name
Home -- -- Link -- -- -- admin’s -- --
home page

services
134
Leave
Requests

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event

Company’s
Schedule
Notificati _notifi notificati Gridvie -- -- -- -- -- --

on List ationLi on_tbl w with
stgv
checkb
ox and
link
Cancel _canc -- Button -- -- -- Revert -- --

elbtn
Reply _reply -- Button -- -- -- Reply -- --

btn notification
page
135
o Database Details

Key Key,Not Null
o Business Rules
N/A
o Form Validations
1. To=Not Null
2. Subject=Not Null
136

 Module Name: Search Mail Notifications
 Description This module provides facility to admin to search particular operator by
using advance search option. It will generate the list of operator for notification. In
the list admin can select operators.
 Layout
o Screenshot
ol l type e lt
Name
Home -- -- Link -- -- -- Admin -- --
home page

services
137

Attenda employee’s
nce Attendance

Leave
Requests

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event
Schedul -- -- Link -- -- -- Add -- --

e Company’s
Schedule
Operato _opLis Operator Gridvie -- -- Searc -- -- --

r List tgv _tbl w with hed
checkb emplo
ox and yee
link list
138
e ar
textbox
,Lable
Subject _subt -- Label, -- -- -- -- Yes --

b Textbo
x

b Multilin
eTextb
ox
Send _send -- Label, -- -- -- -- -- --

Email Email Button
btn
operator _opId op_Id Label, varch 50 -- -- --

Id tb Textbo ar
Operato _opNa op_nam Label, Varch 50 -- -- --

r Name metb e Textbo ar

ent rtmen Dropdo ar
tdrp
wn

Search _sear -- Button -- Redirect to --

chbtn same page

btn
139
o Database Details

Key Key,Not Null
o Business Rules
N/A
o Form Validations
1. To=Not Null
2. Subject=Not Null

 Module Name: Search Message Notifications
140
 Description This module provides facility to admin to search particular operator by

using advance search option. It will generate the list of operator for notification. In
the list admin can select operators.
 Layout
o Screenshot
ol l type e lt
Name
Home -- -- Link -- -- -- Admin -- --
home page

services

nce Attendance
141

Leave
Requests

Contact
Details

basic details

Project

Task
Add -- -- Link -- -- -- Issue -- --

Holiday Holiday

Event Event
Schedul -- -- Link -- -- -- Add -- --

e Company’s
Schedule
Operato _opLis Operator Gridvie -- -- Searc -- -- --

r List tgv _tbl w with hed
checkb emplo
ox and yee
link list

e ar
textbox
,Lable
142
Subject _subt -- Label, -- -- -- -- Yes --

b Textbo
x

b Multilin
eTextb
ox
Send _send -- Label, -- -- -- -- -- --

Email Email Button
btn

Id tb Textbo ar


ent rtmen Dropdo ar
tdrp
wn


chbtn same page

btn
143
o Database Details

Key Key,Not Null
o Business Rules
N/A
o Form Validations
1. To=Not Null
2. Subject=Not Null
144

 Module Name: View Profile
 Description: Employee can view his profile by using this module. He can also
redirect to edit page by using edit button can edit his profile.
 Layout
o Screenshot
ol l type e lt
Name
Home -- -- Link -- -- Employee’s -- --
home page
Services -- -- Link -- -- Company’s -- --

services
Leave -- -- Link -- -- Checking -- --

Leave
145
Requests
Contact -- -- Link -- -- Company’s -- --

Contact ---
Details
About -- -- Link -- -- Company’s -- --

basic details
First _first First Lable,T Varch 50 First -- -- --

name Name name extbox ar name
tb
Middle _midd Middle Lable,T Varch 50 Middle -- -- --

name leNam name extbox ar name
etb
Last _lastN Last Lable,T Varch 50 Last -- -- --

name ametb name extbox ar name
Date of _dobc Date of Label, Dateti Date -- -- --

birth al birth calende me of
r birth
Gender _gent Gender Lable,T Varch Gende -- -- --

b extbox ar r
Marital _mstb Marital Lable,T Varch 50 Marita -- Yes --

status status extbox ar l
status
Spoken _spok Spoken Lable,T Varch Ma Spoke -- -- --

languag enlan languag extbox ar x n
guage
e e langu
tb
age
Address _addr Address Lable,T Varch Ma Addre -- yes --

esstb extbox ar x ss
Country _coun Country Lable,T Varch 50 Count -- -- --

trytb extbox ar ry
146
State _state State Lable,T Varch 50 State -- yes --

tb extbox ar
City _cityt City Lable,T Varch 50 City -- yes --

b extbox ar
Postal _pinc Postal Lable,T decim 20 Postal -- yes --

code odetb code extbox al code
Home _hom Home Lable,T decim 12 Home -- yes --

phone ePhon phone extbox al phone
etb
Mobile _mobi Mobile Lable,T decim 12 Mobile -- yes --

phone lePho phone extbox al phone
netb

fax eFaxt fax extbox al fax
b
Pager _page Pager Lable,T 20 Pager -- yes --

rtb extbox
Employe _emo Employe Lable,T varch 50 Emplo -- -- --

e code codet e code extbox ar yee
b
code
Wage _wage Wage Lable,T decim 20 Wage -- -- --

rate(hou tb rate(hou extbox al rate(h
rly) rly) ourly)
Salary _salar Salary Lable,T decim 20 Salary -- -- --

grade ygrad grade extbox al grade
etb
Salary _salar Salary Lable,T Varch 50 Salary -- -- --

amount yamtt amount extbox ar amou
b
nt
Hire _hired Hire Lable,T varch -- Hire -- -- --

date atetb date extbox ar date
147
Departm _dept Departm Lable,T Varch 50 Depar -- -- --

ent Name ent extbox ar tment
tb
name name name
Position _posit Position Lable,T Varch 50 Positio -- -- --

iontb extbox ar n
update _upda Button -- -- -- Redirect to -- --

tebtn registration
page
Cancel _canc Button -- -- -- -- -- --

elbtn

Id tb Textbo ar


ent rtmen Dropdo ar
tdrp
wn


chbtn same page

btn
148
o Database Details

Employee_tbl Emp_id Primary nvarchar(50) Primary Key,
Key Not Null
Pin code nvarchar(50) Not Null
Position nvarchar(50) Not Null
Operator Table Opr_id nvarchar(50) Primary Key,
Not Null
149

o Business Rules
2. All details will get filled at time of page load
3. On clicking Update button profile will update
N/A
o Form Validations
1. Address=Not Null
2. Country=Not Null
3. State=Not Null
4. City= Not Null
5. Postal code= Not Null
6. Home Phone= Not Null
7. Mobile Phone=Allow Null
8. Home Fax= Not Null
9. Pager= Not Null

 Module Name: Edit Profile
 Description: Employee can edit his profile by using this module. He can also
redirect to edit page by using edit button can edit his profile.
150
 Layout
o Screenshot
ol l type e lt
Name
Home -- -- Link -- -- Employee’s -- --
home page
Services -- -- Link -- -- Company’s -- --

services
Leave -- -- Link -- -- Checking -- --

Leave
Requests
Contact -- -- Link -- -- Company’s -- --

Contact ---
Details
151
About -- -- Link -- -- Company’s -- --

basic details
First _first First Lable,T Varch 50 First -- -- --

name Name name extbox ar name
tb
Middle _midd Middle Lable,T Varch 50 Middle -- -- --

name leNam name extbox ar name
etb
Last _lastN Last Lable,T Varch 50 Last -- -- --

name ametb name extbox ar name
Date of _dobc Date of Label, Dateti Date -- -- --

birth al birth calende me of
r birth
Gender _gent Gender Lable,T Varch Gende -- -- --

b extbox ar r
Marital _mstb Marital Lable,T Varch 50 Marita -- Yes --

status status extbox ar l
status
Spoken _spok Spoken Lable,T Varch Ma Spoke -- -- --

languag enlan languag extbox ar x n
guage
e e langu
tb
age
Address _addr Address Lable,T Varch Ma Addre -- yes --

esstb extbox ar x ss
Country _coun Country Lable,T Varch 50 Count -- -- --

trytb extbox ar ry
State _state State Lable,T Varch 50 State -- yes --

tb extbox ar
City _cityt City Lable,T Varch 50 City -- yes --

b extbox ar
152
Postal _pinc Postal Lable,T decim 20 Postal -- yes --

code odetb code extbox al code

phone ePhon phone extbox al phone
etb
Mobile _mobi Mobile Lable,T decim 12 Mobile -- yes --

phone lePho phone extbox al phone
netb

fax eFaxt fax extbox al fax
b
Pager _page Pager Lable,T 20 Pager -- yes --

rtb extbox
Employe _emo Employe Lable,T varch 50 Emplo -- -- --

e code codet e code extbox ar yee
b
code
Wage _wage Wage Lable,T decim 20 Wage -- -- --

rate(hou tb rate(hou extbox al rate(h
rly) rly) ourly)
Salary _salar Salary Lable,T decim 20 Salary -- -- --

grade ygrad grade extbox al grade
etb
Salary _salar Salary Lable,T Varch 50 Salary -- -- --

amount yamtt amount extbox ar amou
b
nt
Hire _hired Hire Lable,T varch -- Hire -- -- --

date atetb date extbox ar date
Departm _dept Departm Lable,T Varch 50 Depar -- -- --

ent Name ent extbox ar tment
tb
name name name
Position _posit Position Lable,T Varch 50 Positio -- -- --
153
iontb extbox ar n
update _upda Button -- -- -- Redirect to -- --

tebtn registration
page
Cancel _canc Button -- -- -- -- -- --

elbtn

Id tb Textbo ar


ent rtmen Dropdo ar
tdrp
wn


chbtn same page

btn
o Database Details

Employee_tbl Emp_id Primary nvarchar(50) Primary Key,
Key Not Null
154

Operator Table Opr_id nvarchar(50) Primary Key,
Not Null
155
o Business Rules
5. All details will get filled at time of page load
6. On clicking Update button profile will update
N/A
o Form Validations
1. Address=Not Null
2. Country=Not Null
10. State=Not Null
11. City= Not Null
12. Postal code= Not Null
13. Home Phone= Not Null
14. Mobile Phone=Allow Null
15. Home Fax= Not Null
16. Pager= Not Null

 Module Name: Work Assignment
 Description: Employees can view their tasks on their profile and also can view
notifications regarding to the work assignment. Employees will download details of
task assigned to their.
156
 Layout
o Screenshot
ol l type e lt
Name
home page

services

nce Attendance

Leave
157
Requests

Contact
Details

basic details
Project _proje -- Gridvie -- -- -- -- -- --

list(Id,T ctListg w,Link
v
ask
name,pr
oject
name,st
atus,det
ails)
o Database Details

Project Table Project_id Primary nvarchar(50) Primary
Key Key,Not Null
Key Key,Not Null
158

o Business Rules
N/A
o Form Validations
159

 Module Name: Project Assignment
 Description: Operator can view project list. Operator can also select particular
project from the list and can redirect to employee list page. He can also search
employees by using search button.
 Layout
o Screenshot
ol l type e lt
Name
home page

services
160

nce Attendance

Leave
Requests

Contact
Details

basic details
Project _proje -- Gridvie -- -- -- -- -- --

list(Id,T ctListg w,Link
v
ask
name,pr
oject
name,st
atus,det
ails)
o Database Details

Key Key,Not Null
161

Key Key,Not Null
o Business Rules
N/A
o Form Validations
162

 Module Name: Search Work Assignment
 Description: Operator can search for employees using advance search and can
also check details of employees by redirecting to employee list page.
 Layout
o Screenshot
ol l type e lt
Name
Home -- -- Link -- -- -- Operator -- --
home page

services

163
nce Attendance

Leave
Requests

Contact
Details

basic details
Cancel _canc -- Button -- -- -- Redirect to -- --

elbtn same page
Name _nam empNa Label,t Varch 50 -- -- Yes --

etb me extbox ar
Departm _dept -- Label,d -- -- -- -- yes --

ent Name ropdow
drp
n
Workexp _work -- Label,d -- -- select -- -- --

ireance experi ropdow
anced
n
rp
Search _sear -- Label,b -- -- -- Redirect to -- --

chbtn utton same page
o Database Details

Key Key,Not Null
164

Key Key,Not Null
o Business Rules
N/A
165
o Form Validations

 Module Name: Select Employee Work Assignment
 Description: Operator will assign project and tasks to employees. Operator has to
select employees from list. He will select employee by using check box and by using
save button can assign tasks to employees.
 Layout
o Screenshot
166
ol l type e lt
Name
home page
services
nce Attendance
Leave
Requests
Contact
Details
basic details
Save _save -- Button -- -- -- Redirect to -- --

btn
same page
Employe _emp -- Gridvie -- -- -- -- -- --

Listgv
e w,Link
167
list(Id,na
me,depa
rtment,r
ole)
cancel _canc -- Button -- -- -- Redirect to -- --

elbtn
search page
o Database Details

Key Key,Not Null
Key Key,Not Null
168

o Business Rules
N/A
o Form Validations
169
Chapter 8 Client Comments
170
Chapter 9 Guide Comments
171
Chapter 10 Expert Comments
172
FAQ About Project
173

RFID Based Employee Attendance System Complete Report

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

RFID Based Employee Attendance System Complete Report

Transféré par

Droits d'auteur :

Formats disponibles

Final Year

RFID Based Employee

1.1 Introduction to RFID

1.1.2 What is RFID?

1.1.3 How RFID works?

1.1.4 Components of RFID

A basic RFID system consists of three components:

These are described below:

Passive versus active

1.1.5 Typical applications of RFID

 Automatic Vehicle identification

1.1.6 The Advantages of RFID Over Bar Coding

1) No "line of sight" requirements: Bar code reads can sometimes be limited or

1.1.7 Common Problems with RFID

1.2 Users of the System

Chapter 3 Client Survey

Chapter 3 Requirements of Client

3.1 Functional Requirements

3.2 Non Functional Requirements

3.3 Optional Requirements

Chapter 4 Decomposition of Functional Requirements

4.1 Key Modules

4.2 Modules Description

 Validation Rules Check

 Update changes into database

 Enter User Id (RFID No.)

 Track attendance which includes:

 Select day which is divided in three timeslot:

 Start and Due date

 Salary & Accounting

Chapter 5 Modules Division

S.No Module Name Assigned To

Chapter 6 Work Plan

According to standard terminology, "A Work Plan is a deliverable-oriented hierarchical

6.1 Gantt Chart

6.2 CPM and PERT Chart

Activity No Activity Expected completion Dependency

1. Team Selection, Client 1 -

2. Requirements Gathering & Fixation 2 1

3. SRS Submission & Presentation 2 2

4. High Level & Low Level Design 3 3

5. User Interface & Project Design 2 3,4

6. Database Design 1 3,5

7. Connectivity & Integration 1 5,6

TE=1 TE=2 TE=2 TE=3

====== ====== ====== ======

Chapter 7 Software Requirement Specification

7.1.3 Definition, Acronyms & Abbreviations:

7.2 Overall Description:

7.2.2.1 System Interfaces

7.2.2.2 User Interfaces

7.2.2.3 Software Interfaces:

Software required for the interaction with Business layer are:

Software required for the interaction with Data layer are:

7.2.2.4 Hardware Interfaces

7.2.2.5 Communication Interfaces:

7.3 Product Function

7.4 User Characteristics

7.6 Architecture Design

Following figure demonstrate the complete Application Architecture

Presentation Layer Presentation GUI

(HTML pages, java scrip, AJAX)