Attandance Management System Project Documenatation

Attendance Management System
Abstract
This document is meant for describing all the features and procedures that were followed
while developing the system.
This document specially mentions the details of the project how it was developed, the
primary requirement, as well as various features and functionalities of the project and the
procedures followed in achieving these objectives.
Attendance System forms the lifeline of the business institute to manage the Employee
and its salary. It is very essential for an Institute to handle the Salary and their scale. It is very
useful for an Institute to test its employee attendance continuously for their mutual development.
The IT initiatives have encouraged various Organizations to develop systems to facilitate

their day to day operations. The Attendance System will include various parts (Salary, Employee
Entry, Salary Scale Entry, etc) for conducting salary Sheet. This system helps in conducting
Attendance quickly and can thus help in saving time and the operations will be carried out
efficiently.
With the effective use, any Institute can apply the Attendance Management System
for conducting quick attendance and getting better results in less time.
1
Company Profile
Unitech Automation is organization.

Address : Unitech Automation,
258, G.I.D.C, Dediyasan,
Mehsana-384002, Gujarat, India
Mr. Sandip Patel is owner of Unitech Automation organization.
It was started in 1998.
55 employees are work in this Organization.
It sales the control panel board in many cities.
It sales many category of control panel.
2
Tables
Tables
List of Figures
3
Sr.No. Figure No Title Page No.
1 2.2 Waterfall Model 19
2 5.1 Data Flow Diagram 36
3 (I) Context Diagram 35
4 (II) Data Flow Diagram (Level 1) 36
5 (III) Data Flow Diagram (Level 2) 37
6 5.2 System Flowchart 38
7 5.3 Entity Relationship Diagram 40
List of Tables
4
Sr.No. Title Page No.
1 Login 42
2 Attendance Entry 43
3 Department 44
4 Employee 45
5 Holiday 47
6 Leave Details 48
7 Salary 49
8 Scale 51
9 Working day 52
Topic 1
5
Introduction
Introduction
Introduction
Introduction
1.1 Project Profiles
1. Project Partners:
6
Strength: 2
Name: Patel Reena (096500307511)

Patel Aarti (096500307513)
2. Hardware / Software Environment:
Hardware:
PENTIUM 4 or later.
700 M.B HARD DISK DRIVE (FREE SPACE MEMORY).
256 MB RAM or more.
Software:
Operating System: Windows XP or later.
Development Tools:
Front End: C#. Net (VISUAL STUDIO 2008).

Back End: MS SQL SERVER 2005.
Documentation & Presentation Tools:
Microsoft Word 2003.

Microsoft PowerPoint 2003.
1.2 System Overview
Introduction:-
7
Attendance Management System is software developed for daily student

attendance in schools, colleges and institutes. If facilitates to access the attendance
information of a particular Employee in a particular industry. The information is sorted by
the operators, which will be provided by the employee for a particular working day. This
system wills also help in evaluating attendance eligibility criteria of a employee.
Purpose:-
The purpose of developing attendance management system is to computerized the

tradition way of taking attendance. Another purpose for developing this software is to
generate the report automatically at the end of the session or in the between of the session.
Scope:-
The scope of the project is the system on which the software is installed, i.e. the
project is developed as a desktop application, and it will work for a particular institute or
organization. But later on the project can be modified to operate it online.
Employee Profile:-
Employee Personal information: Name, Date of Birth, Age, Marital Status,

address (permanent and present) and contact person details, Email, Contact no., Blood
group, Nationality, Category, employee profile, Date of joining, Service up to, employee
current position and job profile, family background details, employee local address and
references details, Passport No., PF No, ESI No, Bank A/c No., Qualification details and
previous work experiences.
Leave Management:-
8
Manage leaves of all types for employees Manage different types of employee
leave status: permanent, rolling contract and contract Leave ledger of employee Leave
application management to be handled by HR Leave structure and policy management.
Time Management :-
Prior intimation to HR in case of late coming, early going, absence due to travel
on duty Management of shifts Managing overtime of employee Manual attendance
entries in the system by HR in case of scanner failure
The benefits of using a time and attendance management solution at your

workplace can not be underestimated. With thousands and thousands of employees
working in many companies around the world, the need of an efficient organizational
system or programs are getting more and more vital. Therefore, there are many
companies implementing time management solutions in order to improve productivity.
Attendance Management System covers the requirements of the Personnel

Department in terms of Manpower Analysis, day-to-day monitoring of the Attendance,
Maintaining Statutory Registers, Monitoring of Leave Records, Calculation of Overtime
and transfer of relevant information to the Payroll System. It also works well as a
member database. You can create customized attendance reports, event schedules,
membership rosters, and attendance forms. The program is easy to use, and it's well
suited for any organization that needs to keep track of attendance.
1.3 Objective
Create a Window application to be used in place of old paper based user Employee Salary
manage process.
9
Use .NET and SQL Server technology to create strong and secured database connectivity.
Incorporate the server software within the code.
Runtime package and deployment instructions are given.
1.4 Scope
The scope of the project is the system on which the software is installed, i.e. the project is
10
developed as a desktop application, and it will work for a particular institute or organization. But
later on the project can be modified to operate it online.
The intention of developing Attendance Management System is to computerized the

tradition way of taking attendance. Another purpose for developing this software is to generate
the desired reports automatically at the end of the session or in the between of the session as they
require. This project is basically a desktop application which means self contained software runs
on the system on which it has been installed under the user control and it will work for a
particular institute or college only.
Topic 2
11
Project
ProjectManagement
Management
2.1 Project Development Approach
Software Process Model:
12
To solve actual problems in an industry, software developer or a team of

developers must incorporate a development strategy that encompasses the process,
methods and tools layers and generic phases. This strategy is often referred to as process
model or a software developing paradigm. A process model for software developing is
chosen based on the nature of project and application, the methods and tools to be used,
and the controls and deliverables that are required. All software development can be
characterized as a problem solving loop in which four distinct stages are encountered:
Status quo, Problem definition, technical development and solution integration.
Regardless of the process model that is chosen for a software project all of the stages
coexist simultaneously at some level of detail.
Our Project Follows the Waterfall Model:
The Waterfall Model:
The steps of the typical Waterfall Model are:

1. Requirement Definition.
2. System & Software Design.

3. Implementation.
4. Integration & System Testing.
5. Operation and Maintenance.
. 2.2 The Waterfall Model
13
There have been some variations from the typical waterfall model for this project
lifecycle.
They are:
1. Maintenance has been omitted from the current project.

2. Not all testing methods which are present in theoretical model are implemented.
14
Week 1
Work Task D1 D2 D3 D4 D5
Analysis
2.3 Time Line Chart
Get project title
Discuss about
projects
functionality with
project guide.
Week 2
Make the System

Flow Diagram.
Make Data Flow
Diagram.
Make
modifications in
System Flow Dia.
And DFD.
Week 3
Make the Data

Dictionary related
to project
requirement.
Identify features
and functionality
to be added.
Visit related sites
and do the
compartmentalizat
ion 15
Milestone
Analysis is Complete
l
Week 4
Design
Design home,
login, and logout
forms.
Designing of
Statements related
pages, Mini
Statement and
Full Statement.
Week 5
Design of
Departmental
form for the user
or customer.
Design of Update
citizens forms for
inter and intra
transferring of
data.
Week 6
Design of Sports
Department forms
of user or
customer.
Design of
Request to access
the data.
Design of form
for changing the
Parent Field.
Milestone
Design is Complete.
Week 7
16
Work Task
D1 D2 D3 D4 D5
Coding
Coding of home,
login, and logout
forms.
Coding of
Statements
related forms.
Week 8
Coding of Sports
Department
Coding of data
accessing from
the citizens
master table to
the sports
department.
Week 9
Coding of data
transfer forms.
Coding of forms
for data
transferring
between intra and
inter department.
17
Week 10
Coding
Coding of
Education
department forms
for the
government.
Coding of
Request to
administrator
form.
Coding of the
page for blocking
the data access.
.
Week 11
Coding of the
form for
changing the pin
value of the
customer or user.
Mile
Stone
Coding is Complete
Week 12
D1 D2 D3 D4 D5
18
Work Task
Testing
Testing of home,
login, and logout
forms and made
changes.
Testing of
accessing of
citizens data by
the various
departments
using the specific
search
Week 13
Testing
departmental
transfer of data
between the
various
departments and
made changes.
Week 14
19
Testing of Data
Transfer forms
for inter and intra
department.
Testing of
accessed data
forms of user or
customer and
Request form and
made changes.
Week 15
Testing of
blocking data
forms and form
for changing the
accessing of the
data and made
changes.
Mile
Stone
Testing is Complete.
Topic 3
20
System
SystemRequirement
RequirementStudy
Study
3 .1 User Characteristics
21
This system will be used in one User Modules which are Administrator. As all of these
have different requirements the modules are designed to meet their needs and avoid any type of
confusion. The Uses of all three User Modules have been described below.
[1] System User can do the following functions in the System.
Add , Edit & Delete Attendance Detail
Add , Edit & Delete Employee Detail
Add , Edit & Delete Salary Detail
Add , Edit & Delete Holiday Detail
Add , Edit & Delete Salary Scale Detail

View Results
Generate Reports
3 .2 System Requirement
22
Hardware:
Pentium IV.
700 MB Hard Disk Space.
256 MB RAM.
Software:
Operating System: Windows XP or later.
Front End: C#. Net (VISUAL STUDIO 2008).
Back End: MS SQL SERVER 2005.
3 .3 Constraints
3.3.1 Security and Reliability Requirements:

23
1. Housework:
Hours of work can be defined employee wise or shift wise.
2. Shifts:
Shifts are user definable. Grace Time, both at the Start and End of the shift can
be defined for individual shifts.
3. Type of Shifts:
Shifts can be either as per a predefined roster, open shift or a break shift.
4. Duty Roster Generation:
Based on the pre-defined shifts you can generate a pattern of work known as a
DUTY ROSTER. These DUTY ROSTERS can then become a template for future
roster generation.
5. Weekly offs:
Weekly off days can be defined employee wise or roster wise.
6. Holidays:
Holidays can either be general holidays for all staff or it can be defined for a set of
employees.
7. Overtime:
Overtime hours are calculated by the system based on punch timings. The said
overtime hours are transferred to payroll only after the departmental head has
24
sanctioned it. The system allows the user to specify which employee or a set of
employees is eligible for overtime.
3.3.2 Organizational Requirements:
Implementation Requirements:
It requires good skill for implementation of project. As This project is using 3- tier business
architecture. All the classes, Functions, procedures and objects are created in the system wise
Architecture. The three tiers are given below.
1) GUI
2) Business Logic Layer
3) Data Access Layer
Entire coding will be done using Microsoft Visual .Net 2005 and Microsoft SQL Server
2005. Soft copy for the Documentation is provided in Microsoft Word Format. Entire Coding
would not be shown to the client for any reasons. Implementation does not require any more
software support without as mentioned below in the system requirements.
Standards Requirements:
Industry standards will be followed by us in any Negotiation or deal related to the

product software. Coding, Documentation and final product delivery will be followed by the
standards.
3.3.3 External Requirements:
Ethical Requirements:
Product Software should be negotiated with human Ethics and it is wished that the
25
software should be used with Ethical requirements. Any non ethical use of this software will be
at the users own risk.
Legislative Requirements:
(1) Privacy Requirements:
Privacy of any particular things and strategy will be served based on prior negotiation
and it should be cleared purposed for that requirement.
(2) Safety Requirements:
Safety will be provided based on the requirement of the members and necessary critical
points.
Topic 4
26
System
SystemAnalysis
Analysis
4.1 Study & Weaknesses of Current System
4.1 STUDY & WEAKNESSES OF CURRENT SYSTEM.
27
Current System
In the present system all work is done on paper. The whole session attendance is stored in
register and at the end of the session the reports are generated. We are not interested in
generating report in the middle of the session or as per the requirement because it takes more
time in calculation. So, We are not able to get employees regularity report and take necessary
action on employees whenever we want because of having very time consuming process.
Weaknesses in Current System
1. Not User Friendly:

The existing system is not user friendly because the retrieval of data is very slow
and data is not maintained efficiently.
2. Difficulty in report generating:
We require more calculations to generate the report so it is generated at the end of

the session. And the employee not gets a single chance to improve their Attendance.
3. Manual control:
All calculations to generate report are done manually so there is

greater chance of errors.
4. Lots of paperwork:
Existing system requires lot of paper work. Loss of even a single register/record
led to difficult situation because all the papers are needed to generate the reports.
28
5. Time consuming:
Every work is done manually so we cannot Generate report in the middle of the
session or as per the requirement because it is very time consuming.
4.2 Requirements of New System
4.2 Requirements of New System:
4.2.1 User Requirements.
29
The User requirements for the new system are to make the system fast, flexible, less
prone to errors and reduce expenses and save time.
Time can be saved in scheduling the salary if it were available to make question banks
to store questions for different Employee in advance and can be used as per required.
.
A system that can automate the checking of answers which are pre-stored so that results
can be generated as soon as the Employee gives the reason.
A facility that can generate result charts as per required without manual interference for
providing how a task is to be done instead only asking what is to be done.
The system should have Employee & its salary records on hand which can be used as
per required only by authorized personnel.
The New system should be more secure in managing Employee records and reliable
enough to be used in any condition.
Finally, it should prove cost effective as compared to the current system.
4.3 Feasibility Study
4.3 Feasibility Study:
A key part of the preliminary investigation that reviews anticipated costs and
benefits and recommends a course of action based on operational, technical, economic,
and time factors. The purpose of the study is to determine if the systems request should
30
proceed further.
Economically Feasibility:
The system being developed is economic with respect to Business or point of

view. It is cost effective in the sense that has eliminated the salary work completely. The
system is also time effective because the calculations are automated which are made at the
end of the month or as per the employee requirement. The result obtained contains
minimum errors and are highly accurate as the data is required.
Technical feasibility:
The technical requirement for the system is economic and it does not use any
other additional Hardware and software.
Behavioral Feasibility:
The system working is quite easy to use and learn due to its simple but attractive
interface. user requires no special training for operating the system.
4.4 Features of the New System
4.4 Features of the New System.
The new system has been designed as per the user requirements so as to fulfill
almost all them.
1. User Friendly: -
31
The proposed system is user friendly because the retrieval and storing of
data is fast and data is maintained efficiently. Moreover the graphical user
interface is provided in the proposed system, which provides user to deal with the
system very easily.
2. Reports are easily generated:-
Reports can be easily generated in the proposed system so user can generate
the report as per the requirement (monthly) or in the middle of the session. User
can give the notice to the employees to be regular.
3. Very less paper work:
The proposed system requires very less paper work. All the data is feted into
the computer immediately and reports can be generated through computers.
Moreover work becomes very easy because there is no need to keep data on
papers.
4. Computer operator control:
Computer operator control will be there so no chance of

errors. Moreover storing and retrieving of information is easy. So
work can be done speedily and in time.
Topic 5
32
System
SystemDesign
Design
5.1 Data Flow Diagram
It is a graphical representation of the data. It identifies the path the data will take, what
process will take place to it from one from to another.
A DFD is a graphical representation of the flow of data through an information system. It

can be used to provide a clear representation of any function. It doesnt provide information
about the timing of processes or about whether processes will operate in sequence. Therefore it is
different from a flowchart.
33
Data Flow Diagrams are composed of the four basic symbols shown below.
The External Entity symbol represents sources of data to the system or destinations
of data from the system.
The Data Flow symbol represents movement of data.
The Data Store symbol represents data that is not moving (delayed data at rest).
The Process symbol represents an activity that transforms or manipulates the data
(combines, reorders, converts, etc.).
Any system can be represented at any level of detail by these four symbols.
1. Data Flow:
It is represented by a line arrowhead showing the direction of flow. It

shows the flow of information from source to its destination. Information always
flows to or from process and may be written, verbal or electronic.
Symbol:
2. Process:
A circle represents a process. It shows the procedures those use

the data in the system.
Symbol:
1. External Entities :
34
A Rectangle represents an external entity. They either supply data or

receive data.
They do not process data.
Symbol:
2. Data Store:
A process references the data store in the system.The data flow is shown
by the opened ended rectangles.
Symbol:
CONTEXT DIAGRAM:
The context diagram is a top-level view of an information system that

shows the boundaries and scope. It describes the main objective of the system and the entities
involved.
35
DATA FLOW DIAGRAM (Level 1)
36
DATA FLOW DIAGRAM (Level 2)
37
5.2 System Flow Chart
38
Continue:
39
5.3 E-R Diagram
40
41
5.4 Data Dictionary
Table Name: Login

Description: Login table Keep the information about user in this system.
42
Sr.No Field Name Data type Constraints Size Description
1. Login Id int Primary Key Login Id
2. Username Varchar Not null 50 Username
3. Password Varchar Not null 50 Password
4. Role Varchar Not null 50 Role
Table Name: Attendance

Description: Attendance table Keep the Information about Employee Attendance.
43
1. Attendance _Id int Primary Key Attendance Id
2. att_date Date Time Not null 50 Attendance date
3. emp_code int Not null 50 Employee code
4. is_present int Not null 50 Is present
Table Name: Department
44
Description: - Department Table Keep the information about different type of Department
Sr.N Field Data Constrai Siz Description

o Name type nts e
1. dep_id int Primary Key Department id
2. dep_code Date Time Not null 50 Department code
3. dep_name int Not null 50 Department Name
Employee
45
Table Name:
1. emp_id int Primary Key Employee id
3. Name Varchar Not null 50 Employee Name
4. address Varchar Not null 50 Employee address
5. city Varchar Not null 50 Employee city
6. pin code int Not null 50 Employee pin code
7. phone Varchar Not null 50 Employee phone
8. mobile int Not null 50 Employee mobile
9. Email Varchar Not null 50 Employee Email
10. Blood group Varchar Not null 50 Employee Blood group
11. Designation Varchar Not null 50 Employee Designation
46
Continue:
12. basic decimal(18, 0) Not null 18,0 Employee basic
13. birth date date time Not null 10 Employee birth date
Description: Employee Table Keep The Information About Employee.
14. joindate datetime Not null 10 Employee join date
15. bank account varchar Not null 50 Employee bank account
16. scale varchar Not null 50 Employee scale
17. category varchar Not null 50 Employee category
18. gpfno Varchar Not null 50 Employee Gpfnumber
19. Emp type varchar Not null 50 Employee type
20. last_institutename Varchar Not null 50 Employee Last institute

name
21. qualification varchar Not null 50 Employee qualification
22. experience varchar Not null 50 Employee experience
23. phy_hand varchar Not null 50 Employee phy hand
24. remark varchar Not null 50 Employee remark
25. pan_no varchar Not null 50 Employee pan no
26. department Varchar Not null 50 Employee department
47
Holiday
1. holi_id int Primary Key Holiday id
2. year int Not null 10 Holiday year
3. month Varchar Not null 50 Holiday month
4. date DateTime Not null 10 Holiday date
5. details Varchar Not null 50 Holiday details
Table Name:
Description: Holiday Table Keep the information about holiday in every Month.
48
Table Name: Leave Details

Description: Leave Detail Table Keep the Information about Employee Who Take a Leave
1. leave_id int Primary Key Leave id
2. leave_date Date Time Not null 10 Leave date
3. emp_id int Not null 10 Employee id
4. emp_name Varchar Not null 50 Employee name
5. leave_type Varchar Not null 50 Leave type
6. leave_resion Varchar Not null 50 Leave resion
for Any Resion.
49
Table Name: Salary

Description: Salary Table Keep the information About Employee Salary in This System.
1. salary_id int Primary Key Salary id
2. month Varchar Not null 50 Salary month
3. year int Not null 50 Salary year
5. emp_name Varchar Not null 50 Employee name
6. w_day int Not null 50 Employee w day
7. p_day int Not null 50 Employee p day
8. basic Decimal(18,2) Not null 18,2 Employee basic
9. da Decimal(18,2) Not null 18,2 Employee da
10. hra Decimal(18,2) Not null 18,2 Employee hra
11. ma Decimal(18,2) Not null 18,2 Employee ma
12. pha Decimal(18,2) Not null 18,2 Employee pha
13. hma Decimal(18,2) Not null 18,2 Employee hma
50
Continue:
14. pf Decimal(18,2) Not null 18,2 Employee pf
15. pt Decimal(18,2) Not null 18,2 Employee pt
16. loan Decimal(18,2) Not null 18,2 Employee loan
17. oa Decimal(18,2) Not null 18,2 Employee oa
18. arriars Decimal(18,2) Not null 18,2 Employee arriars
19. oded Decimal(18,2) Not null 18,2 Employee oded
20. grins Decimal(18,2) Not null 18,2 Employee grins
21. advit Decimal(18,2) Not null 18,2 Employee advit
22. gross Decimal(18,2) Not null 18,2 Employee gross
23. tot_ded Decimal(18,2) Not null 18,2 Employee tot ded
24. netsal Decimal(18,2) Not null 18,2 Employee netsal
25. remark varchar Not null 50 Employee remark
51
Table Name: Scale

1. scale_id int Primary Key Scale id
2. month int Not null 10 Scale month
3. year int Not null 10 Scale year
4. da_per decimal(10, 2) Not null Scale da per

10, 2
5. hra_per decimal(10, 2) Not null Scale hra per
10, 2
6. ma_per decimal(10,2) Not null Scale ma per
10, 2
7. pha_per decimal(10,2) Not null Scale pha per
10, 2
8. hma_per decimal(10,2) Not null Scale hma per
10, 2
9. pf_per decimal(10,2) Not null Scale pf per
10, 2
10. pt_per decimal(10,2) Not null Scale pt per
10, 2
Description: Scale Table Keep the Information about Scale Means Which employee gets
How Many Scale in His/her Salary
52
Scale
Table Name: Working day
1. working_id int Primary Key Working id
2. year int Not null 10 working year
3. month int Not null 10 working month
4. working day int Not null 50 working day
Description: Working Day table Keep the information About the Month working day.
53
Topic 6
Summary
Summary
54
Project Title:
Attendance Management System.

Software Used:
Microsoft Visual Studio 2008

Microsoft SQL Server 2005
Documentation Tools:
Microsoft Word 2003.

Microsoft PowerPoint 2003.
External Project Guide:
Mr. Sandip Patel

Organization:
Unitech Automation,Mehsana
Internal Project Guide:
Mr. Parth Patel
Submitted By:
Patel Reena (096500307511)

Patel Aarti (096500307513)
Submitted To:
Department of computer engineering,

Swami Sachchidanand Polytechnic College, Visnagar-384315
Project Duration:
5th and 6th sem
55
Topic 7
Conclusion
Conclusion
56
The main aim of this system was to put what we learnt in our software engineering
class into practice. The Attendance system designated to our team allowed us to fully
exercise the techniques of XP.
We were able to attain our set objectives, and this helped us again confidence in
writing our own code and our own applications. In addition, the use of serialization was an
experimentation to cut down the time taken in designing.
The front-ends and back-ends of applications separately. With our OOP approach and
serialization, we only concentrated on designing the objects/classes, and then just serialized
them on disk. So we did not spend any time on designing how to store data.
We also worked as a team, and gained some experience on how professional

programmers work in the industry.
There is always room for improvement, and the software we created can also be
improved. This is especially because we had to create it within a limited time. With more
time, the software can be improved to include security and different types of users. This
would be the first step in marking the software network-enabled, and eventually web-
enabled.
This was our original after-thought to programming the software, and we had chosen
XML. In addition, the software can also be improved in terms of the calculations it addition,
the software can also be improved in terms of the calculations it can do, and more flexibility
in the rates used in calculations per employee.
57
Topic 8
Screen
ScreenLayout
Layout
58
Splace Screen
59
Login
60
MDI Form
Create New User

61
Change Password
62
Attendance Entry
63
Attendance
64
Department
65
Department List
66
Employee Detail
67
Employee List
68
Holiday
69
Holiday Detail
70
Leave Detail
71
Leave List
72
Salary Calculation
73
Salary List
74
Scale Detail
75
Scale List
76
Workingday Detail
77
Workingday List
78
Employee Report
79
Salary Report
80
Topic 9
81
Bibliography
Bibliography
Reference:
Appendix A List of Useful Websites
http://www.microsoft.com
http://projectabstracts.com
http://www.wikipedia.org
82
Appendix A List of Useful Book
ASP.NET 2.0 Website Programming: Problem-Design-Solution
(Programmer to Programmer) by Marco Bellinaso
Professional ASP.NET 2.0 by Bill Evjen, Scott Hanselman, Farhan
OReilly (E-Book) Programming in .Net
Oreille (E-Book) Framework + Essentials.pdf
Beginner ASP.NET 2.0 Unleashed
PL/SQL Programming Evan Bayross
83

Attandance Management System Project Documenatation

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Attandance Management System Project Documenatation

Încărcat de

Drepturi de autor:

Formate disponibile

Attendance Management System

The IT initiatives have encouraged various Organizations to develop systems to facilitate

Unitech Automation is organization.

Sr.No. Figure No Title Page No.

1 2.2 Waterfall Model 19

2 5.1 Data Flow Diagram 36

3 (I) Context Diagram 35

4 (II) Data Flow Diagram (Level 1) 36

5 (III) Data Flow Diagram (Level 2) 37

6 5.2 System Flowchart 38

7 5.3 Entity Relationship Diagram 40

Sr.No. Title Page No.

1.1 Project Profiles

Name: Patel Reena (096500307511)

2. Hardware / Software Environment:

Operating System: Windows XP or later.

Front End: C#. Net (VISUAL STUDIO 2008).

Documentation & Presentation Tools:

Microsoft Word 2003.

1.2 System Overview

Attendance Management System is software developed for daily student

The purpose of developing attendance management system is to computerized the

Employee Personal information: Name, Date of Birth, Age, Marital Status,

The benefits of using a time and attendance management solution at your

Attendance Management System covers the requirements of the Personnel

The intention of developing Attendance Management System is to computerized the

2.1 Project Development Approach

Software Process Model:

To solve actual problems in an industry, software developer or a team of

Our Project Follows the Waterfall Model:

The Waterfall Model:

The steps of the typical Waterfall Model are:

2. System & Software Design.

. 2.2 The Waterfall Model

1. Maintenance has been omitted from the current project.

Make the System

Make the Data

[1] System User can do the following functions in the System.

Add , Edit & Delete Attendance Detail

Add , Edit & Delete Employee Detail

Add , Edit & Delete Salary Detail

Add , Edit & Delete Holiday Detail

Add , Edit & Delete Salary Scale Detail

3.3.1 Security and Reliability Requirements:

4. Duty Roster Generation:

Weekly off days can be defined employee wise or roster wise.

3.3.2 Organizational Requirements:

Industry standards will be followed by us in any Negotiation or deal related to the

3.3.3 External Requirements:

(1) Privacy Requirements:

(2) Safety Requirements:

4.1 Study & Weaknesses of Current System

4.1 STUDY & WEAKNESSES OF CURRENT SYSTEM.

Weaknesses in Current System

1. Not User Friendly:

2. Difficulty in report generating:

We require more calculations to generate the report so it is generated at the end of

All calculations to generate report are done manually so there is

4.2 Requirements of New System

4.2 Requirements of New System:

4.2.1 User Requirements.

Finally, it should prove cost effective as compared to the current system.

4.3 Feasibility Study