File For Online Attandance

Government Polytechnic , Gandhinagar
Attendance Management System
Chapter - 1 INTRODUCTION
A)PROJECT SUMMARY
B) PURPOSE
C) SCOPE
D) OBJECTIVE
Page 1
A) PROJECT SUMMARY
This is develop for maintain attendance of student and
as well as faculty information. This
system also include reminder to the parents for less attendance of student through the mail.
B) 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.
C) 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. But later on the
project can be modified to operate it online.
D) OBJECTIVE
Solve Problem of Searching Record: All the data easily can not search any record.
User Friendly :This system does not provides user friendly interface and easy navigation
Less Attendance Alert through SMS to the parents. We can easily filtering data.
Page 2
Chapter - 2 PROJECT PLANNING

A) Milestones and Deliverables
B) Project Scheduling
C) Risk Management
Page 3
A) Milestones and Deliverables

I have designed the new proposed system to the process of Internal Organization
Management System. This will store all information about our system. It makes all record in
security way so no person can make any change in a system. This record will be useful for other
users instantly. The complete control of the project is under the hands of authorized person who has
the password to access this project and illegal access is not supposed to deal with. All the control is
under the administrator and the other members have the rights to just see the records not to change
any transaction or entry. Admin Capable to Create and block New User.
B) Project Scheduling
Gantte Chart
2/7 to 10/8
11/8 to 17/11
20/3
21/3 to 21/5
18/1 to 28/3 1/3 to
Project
Specification
Analysis of the project

Design of project
Coding
Testing and
Docu
-mentation
Fig : chart
Page 4
C) Risk Management1
In contrast to software life cycle models, software process models often represent a networked
sequence of activities, objects, transformations, and events that embody strategies for
accomplishing software evolution. Such models can be used to develop more precise and
formalized descriptions of software life cycle activities. Their power emerges from their utilization
of a sufficiently rich notation, syntax, or semantics, often suitable for computational processing.
In the incremental model, there is a good chance that a requirements error will be
recognized as soon as the corresponding software is incorporated into the system. It is then not a
big deal to correct it. The waterfall model relies on careful review of documents to avoid errors.
Once a phase has been completed, there is limited provision for stepping back. It is difficult to
verify documents precisely and this is, again, a weakness of the waterfall model.
The incremental model is an intuitive approach to the waterfall model. Multiple development
cycles take place here, making the life cycle a multi-waterfall cycle. Cycles are divided up into
smaller, more easily managed iterations. Each iteration passes through the requirements, design,
implementation and testing phases.
A working version of software is produced during the first iteration, so you have working software
early on during the software life cycle. Subsequent iterations build on the initial software produced
during the first iteration.
Page 5
Chapter - 3 SYSTEM REQUIREMENT STUDY

A)User Characteristics
B)Hardware and Software Requirements
Page 6
A) User Characteristics
Admin: Can access all forms

Faculty: Can access Student, Attendance forms
Student: Can only show His/Her Attendance detail
B) Hardware and Software Requirements

Requirement of the System:
Operating System:
Microsoft Windows XP service pack 2
Front End: ASP.NET with C#

Back End: SQL server
Supporting-Tools:
Microsoft word - Documentation

Microsoft Power Point - Presentation
H/W Specification:
Processor
RAM
Hard Disk
:
:
:
Intel Core2 Duo 2.20GHz

1GB DDR2 RAM
Hitachi 320GB SATA
Page 7
Chapter-4 SYSTEM ANALISYS

A)Study of Current System
B) Problem and Weaknesses of Current System
C) Requirements of New System
D) Feasibility Study
> Technical Feasibility
> Schedule Feasibility
> Operational Feasibility
> Economic Feasibility
Page 8
A) Study of Current System

There is no computerized system for the attendance of student in the institute.
All work and calculation are done through manually and data stored in paper.
Current System does not provide facility to remind parents to automatically for their less
attendance.
B) Problem and Weaknesses of Current System

No user authentication
No Backup and Restore Facility
C) Requirements of New System

Solve Problem of Searching Record: All the data easily can not search any record.
User Friendly :This system does not provides user friendly interface and easy navigation
Less Attendance Alert through SMS to the parents. We can easily filtering data.
Page 9
D) Feasibility Study
Technical Feasibility
Development tool for our software is Language .net. Resources required for it
available and also the expertise. Research on Asset Management and Tracking has reached to
stage where it is technically feasible to implement it for real life application. The models
training application are developed and tested thoroughly by experts. Also those resources
available. So the proposed project is technically feasible.
are
the
for
are
Schedule Feasibility
It is not important that the project gets completed, but its very important that it
gets completed in allotted time. I had project duration of 4 months. As the work was divided into
the 4 months, there was very good division of labor. As a result, the project within the allotted time
period was possible. So my project is feasible with respect to schedule.
Operational Feasibility
Once the software is developed, the work does not get over here. After the developers
leave the company it should be easy to operate by the other members of the company for
whom the software was developed. This demands a very good user interface to be
implemented. As my project has got a very user friendly and an easy interface it can also be
used by novice users after a bit of training. Moreover, the employees who are going to use
my software are skilled professional so they will hardly find any difficulty in operation our
software. So on and all it is totally feasible to operate my software with great ease.
Economic Feasibility
This feasibility is of utmost importance in development of any software for any
particular company. The availability of the required hardware and software used to develop our
project makes it economically very feasible. Moreover, the time duration in which the whole
project is developed is appreciable. So it has indirect effect on the economy of the company, as a
very good product is delivered in very less time. As our project almost removes any kind1 of
manual work, the same Man power can be applied to some other work. So over all it is not only
feasible economically but it also helps to increase the efficiency and profit making.
Chapter-5 SYSTEM DESIGN

Page 10
A) E-R Diagram
B) Class Diagram
C) Activity Diagram
D) Use case Diagram
E) Sequence Diagram
F) Context Diagram
G) Data Flow Diagram (0 and 1 level)
A) E-R Diagram
Page 11
B) Class Diagram
Page 12
Page 13
C) Activity Diagram
Page 14
D) Use case Diagram
Page 15
E) Sequence Diagram
Page 16
F) Context Diagram
Get Faculty/Student
Give Attendance
Details
Details
Admin
Student Attendance Management System
Faculty
Managed Faculty / Student
Take Attendance /
Details
Details
Show
Attendan
ce
Search
Attendan
ce by
AdmNo
Student
Page 17
G) Data Flow Diagram (0 and 1 level)
Page 18
Chapter 6 DATA TABLE
Attendance
Batches
Faculty
Schedule
Student
Subject
Page 19
Attendance
Table Name: Attendance
Description: This Table is for fell Attendance
Constraint
Primary Key
Candidate Key
Candidate Key
FieldName
Adate
Weekno
Period
Fcode
admno
Status
Remarks
FieldName
adate
Period
Admno
Datatype
Datetime
Int
Int
varchar
Int
Char
Varchar
Size
10
1
50
Constraint
Primary Key
Not Null
Candidate Key
Not Null
Candidate Key
Not Null
Not Null
Batches
Table Name: Batches
Description: This Table is for Country
Constraint
Primary Key
FieldNam
e
bcode
Bno
FieldName
Bcode
Datatyp
e
Int
Int
Size
-
Constraint
Primary Key
Not Null
Page 20
Faculty
Table Name: Faculty
Description: This Table is for Faculty Detail
Constraint
FieldName
Primary Key
Fcode
FieldName
Datatype
Size
Constraint
Fcode
Varchar
10
Pwd
varchar
10
Fname
Varchar
50
Dept
Varchar
50
Primary Key
Schedule
Table Name: Schedule
Description: This Table is for Schedul of time table
Constraint
FieldName
Primary Key
Weekno
Candidate key
Bcode
Candidate key
Period
FieldName
Weekno
bcode
Period
Fcode
Scode
Datatype
Int
Int
Int
Varchar
Varchar
Size
10
10
Constraint
Primary Key
Candidate Key
Candidate Key
Not Null
Not Null
Page 21
Student
Table Name: Student
Description: This Table is for Student details
Constraint
Primary Key
Field Name
Admno
bcode
Sname
Field Name
Admno
Datatype
Int
Int
Varchar
Size
50
Constraint
Primary Key
Not Null
Not Null
Subject
Table Name: Subject
Description: This Table is for Subject Detail
Constraint
Primary Key
Field Name
Scode
Sname
Field Name
Scode
Datatype
Varchar
varchar
Size
10
50
Constraint
Primary Key
-
Page 22
Chapter 7 USER MANUAL
Page 23
Home Page
Page 24
Data Entry in Login Form
Page 25
Invalid Username or Password
Page 26
Successful Login
Page 27
Change Password Form
Page 28
Data Entry in Change Password Form
Page 29
Validation
Page 30
Password Changed Successfully
Page 31
Standard Master
Page 32
Subject Master
Page 33
Add New Subject
Page 34
Subject Stored Successfully
Page 35
Record Navigation
Page 36
Update Data
Page 37
Record Updated
Page 38
Record Deleted
Page 39
Faculty Master
Page 40
Add New Faculty
Page 41
Record Saved
Page 42
Record Navigation
Page 43
Student Master
Page 44
Add New Student
Page 45
Data Entry
Page 46
Record Stored Successfully
Page 47
Newly Stored Record in Gridview
Page 48
Record Navigation
Page 49
Update Record
Page 50
Record Updated Successfully
Page 51
Reports
Faculty Report
Page 52
Student Report
Page 53
Export Report to Word
Page 54
Ask for Save
Page 55
Stored Location
Page 56
Word File
Page 57
Faculty Login
Page 58
Fill Attendance
Page 59
Fill Attendance
Page 60
Fill Attendance
Page 61
Attendance Stored Successfully
Page 62
Search Student
Page 63
Student Found
Page 64
Show Attendance of Selected Student
Page 65
Old Attendance
Page 66
Enter Search Criteria
Page 67
Show Selected Attendance
Page 68
Edit Attendance
Page 69
Update Record
Page 70
Attendance Updated
Page 71
Faculties List
Page 72
Student Side Search Attendance
Page 73
Enter Student Admission No
Page 74
Another Students Attendance
Page 75
Chapter - 8 ADVANTAGES
Page 76
Admin Can Add , Update and Delete details of Faculty and Student.
Faculty Can Add and Update Student Attendance And Search Student.
Student can search their Attendance.
Page 77
Chapter - 9 TESTING
Page 78
Validation Mechanism
We have used required field validators with those fields which are compulsory. Eg. Username,
password, date of registration, book id, book name etc.
We have used Compare field validators with those field which should be compared with another
field. Eg. Password field
We have used Regular expression validators with those fields in which input should be done in
some specific manner like e-mail id, phone no, etc.
Page 79
Security Mechanism
There are mainly two types of user in our site. They are
1. Admin
2. Faculty
To identify which user can access which pages we have provided security for every page.
We have used Forms mode in Authentication in web.config file.
We have used special code which checks the user type at login time. And as per the type the pages
will be available to the user of the website.
We have also used session and cookies to store the detail of users login.
We have used login related controls like login view, login status, login name, etc to maintain login
detail.
Page 80
Proposed Enhancement
FUTURE ENHANCEMENT
Due to time limitations we cant provide following facilities in our project:
Online book purchase
Online payment
Online Bill
Pay pal
Page 81
Chapter - 10 CONCLUSIONS
Page 82
Any work may not be always perfect. There may be some error or some defect in the work.
We have taken enough care to make the project user friendly and more interactive. We have
tried our level best to make the service useful and to provide maximum facility.
We hope that "Attendance Management System" will prove to be a boon for our users.
Any suggestion to make this project more useful is always most welcome.
Page 83
REFERENCES
www.google.com
www.youtube.com
Page 84

File For Online Attandance

Transféré par

Informations du document

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

File For Online Attandance

Transféré par

Droits d'auteur :

Formats disponibles

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

Chapter - 2 PROJECT PLANNING

Government Polytechnic , Gandhinagar

Attendance Management System

A) Milestones and Deliverables

18/1 to 28/3 1/3 to

Analysis of the project

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

Chapter - 3 SYSTEM REQUIREMENT STUDY

Government Polytechnic , Gandhinagar

Attendance Management System

Admin: Can access all forms

B) Hardware and Software Requirements

Microsoft Windows XP service pack 2

Front End: ASP.NET with C#

Microsoft word - Documentation

Intel Core2 Duo 2.20GHz

Government Polytechnic , Gandhinagar

Attendance Management System

Chapter-4 SYSTEM ANALISYS

Government Polytechnic , Gandhinagar

Attendance Management System

A) Study of Current System

B) Problem and Weaknesses of Current System

C) Requirements of New System

Government Polytechnic , Gandhinagar

Attendance Management System

Chapter-5 SYSTEM DESIGN

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

D) Use case Diagram

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

G) Data Flow Diagram (0 and 1 level)

Government Polytechnic , Gandhinagar

Attendance Management System

Chapter 6 DATA TABLE

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System

Government Polytechnic , Gandhinagar

Attendance Management System