SHETH N.K.T.

T COLLEGE OF COMMERCE &

SHETH J.T.T COLLEGE OF ART

PROJECT ON
ONLINE STUDENT ATTENDANCE SYSTEM

SUBMITTED BY
MISS.------ ------ ------

UNDER THE GUIDENCE OF

PROF.Ms.-Sonali Saraf
DEPARTMENT OF INFORMATION TECHNOLOGY
FOR ACADEMIC YEAR 2016-17
 CERTIFICATE
This is to certify that the project entitled “ONLINE SRUDENT
ATTENDANCE SYSTEM” Under the guidance of PROF.Ms. ------ ------
, is successfully completed by MISS. ----- ------, Roll No.07, Examination
Seat No. ______during the period of 2016-2017, as per the syllabus and
fulfillment for the completion of the BSc degree in Information
Technology of University of Mumbai. This certifies that this is the
original work of the candidate done during the academic year 2016-2017.

Place: Mumbai

Date:

INTERNAL EXAMINER PRINCIPAL HEAD OF

DEPARTMENT
 PREFACE

Over the last few years, efforts have been made to make the efficient use
of technology and resources. The Information Technology is one of those fields
where maximum use of technology is made and made sure the end users are
satisfied and the job is done in efficient manner.

Today almost all industries and firms are dependent on computer to store
their large amount of data. This popularity is going to spread as and when year
passes by. To cope up with this speed efforts have been made by every I.T.
professionals and Students to sincerely make the industry more popular.

With the help of this following project one more sincere effort is been added
and contributed towards this industry.
 ACKNOWLEDGEMENT
It is a great pleasure to get this opportunity and sincerely thank all the
people, who have showed me the way to create a successful JAVA project and
helped me a lot during the completion of the project.

I am highly obliged to the teaching and non-teaching staff members of

the Information System Department who spared efforts in making the project a
successful one with their guidance, appropriate advice and encouragement and
of course inspiration without which the project would be ineffective difficult
task.

It gives a great pleasure in presenting this project report. It justification

will never sound good if I do not express my vote of thanks to our college

I sincerely thank and express my profound gratitude and indebtedness to

our Project guides Prof.Mrs. ------ ----- (HOD), Prof. Ms ----- -----, for their
timely and prestigious guidance required for the project completion at each
phase of the project development apart from the inspiration and motivation.

I also to owe my Friends who have been a constant source of help to

solve my problems that cropped up during the development of project and for
being an encouraging and guiding force towards the successful completion of
the project.

Submitted By:
 SIGNED SHEET
Class : T.Y.B.Sc.(I.T.) Exam Seat No.:
Signed sheet details are as follows (As Per Practical):
PHASE PHASE TITLE EXPECTED ACTUAL GUIDE’S
No. DATE OF TIME OF SIGNATURE
COMPLETION COMPLETION

1 Preliminary
investigation
2 Project
Finalization
3 Investigation
of system
requirement
4 System
Analysis
5 System Design
6 Coding
7 Interface
Coding
8 Database
Connectivity

9 Validation
Coding
10 Report Coding
11 Implementation
12 Developer
Testing

13 Project
Delivery

14 Project Report
Submission

15 Project Report
Hard Copy
Checking
16 Project
Submission

INDEX
Sr. No. Title Page No.

1 Preliminary Investigation:
 a. Organizational Overview.

b. Description Of System.

c. Limitations Of Present System.

d. Proposed System and Its

Advantages.
e. Feasibility Study.

d. Stakeholders.
Technology Used:
a. Software Specifications.

b. Hardware Specifications.

Gantt Chart.
2 System Analysis:
a. Event Table.

b. ER Diagram .

c. Class Diagram

d. Use Case.

e. Sequence Diagram.

f. Collaboration Diagram.

g. Activity Diagram.

h. State Diagram.
3 System Design:

a. Component Diagram.

b. Deployment Diagram.
4 System Coding:

a. Menu Tree.

b. Validations.

c. Screen Layout.

d. Report Layer.

e. Screen Layouts.

f. Test Cases.

5 Conclusion.

6 System Implementations.

7 Future Enhancements.

8 References and Bibliography.

PRELIMINARY INVESTIGATION
 1.1 ORGANIZATION OVERVIEW

Name : Online Student attendance System.

Location : Thane.

Goal : To Save Time and Paper Work.

This Project has been prepared for “Online Student attendance

System.”.It handles all the management related to Attendance System.
 1.2 DESRIPTION OF SYSTEM
This system developed will reduce the manual work and avoid
redundant data. By maintaining the attendance manually, then efficient reports
cannot be generated. The system can generate efficient weekly, consolidate
report based on the attendance. As the attendances are maintained in registers it
has been a tough task for admin and staff to maintain for long time. Instead the
software can keep long and retrieve the information when needed.

Attendance Management System basically has two main modules for

proper functioning :

Admin module : has rights for creating any new entry of faculty and
student details.

Staff : has a rights of making daily attendance, generating Attendance

report. Attendance report can be taken by given details of student details, date,
class.

Module Description : The system should be designed in such a way

that only authorized people should be allowed to access some particular
modules. The records should be modified by only administrators and no one
else. The user should always be in control of the application and not the vice
versa. The user interface should be consistent so that the user can handle the
application with ease and speed. The application should be visually,
conceptually clear.

Administrator Module:
Student Details:

In this module deals personal details for new Student. It will generate of
personal details of student and academic details of the students .

Staff Details:

In this module deals personal details for new Staff .It provides the facility
to have a user name and password to the staffs .
Staff Modules:
Attendance details:

Entered attendance to stored in the database into the particular date.

It will help to the get report of weekly and consolidate of the attendance.
 1.3 LIMITATIONS OF PRESENT SYSTEM
system is a manual entry for the students. Here the attendance will be
carried out in the hand written registers. It will be a tedious job to maintain the
record for the user. The human effort is more here. The retrieval of the
information is not as easy as the records are maintained in the hand written
registers. This application requires correct feed on input into the respective
field. Suppose the wrong inputs are entered, the application resist to work. so
the user find it difficult to use.

This system developed will reduce the manual work and avoid redundant
data. By maintaining the attendance manually, then efficient reports cannot be
generated. The system can generate efficient weekly, consolidate report based
on the attendance. As the attendances are maintained in registers it has been a
tough task for admin and staff to maintain for long time. Instead the software
can keep long and retrieve the information when needed.
 1.4 PROPOSED SYSTEM

GOALS TO BE ACHIEVED:
 Software must have security on accessing data.
 User should be able to view, add, delete or modify all the data inside the
database through front end only.
 Software should avoid repetition of such data which must be unique.
 Software should provide all the report in such a way that it should be
easily compared with the other reports.
 The layout of Software should be as simple as possible and should be
comfortable for the user for daily use.

FEATURES OF PROPOSED SYSTEM:

 Less time Consuming and Simple.
 Software can easily handled by different users.
 By this system, the information can be retrieved at a faster rate compared
to manually.
 It does not allow the other user to access system. So, Security of the data
is well maintained by this system.

1.5 ADVANTAGES OF PROPOSED SYSTEM

 The system should provide feature like Enquiry, Booking, Cancellation,
Updating, Report Generation and Edit.
 Report should include all details of Customers, list of all destinations,
waiting list of customers, Reschedules of packages.
 The process like Enquiry, Booking, Cancellation can be done from
anywhere to any place.
 The system should be fast, Accurate, Reliable and Informative
 The main advantage of this system, it can be used to analyze the method
of calculating daily income of booking cost.
 The system is user friendly.
 Easy to keep records and maintain database.
 1.6 FEASIBILITY STUDY
 Economically Feasibility:

The system being developed is economic with respect to School or Collage’s

point of view. It is cost effective in the sense that has eliminated the paper 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 user 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.

 Behavioural 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.

 Working Of Present 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. At the end of session the
students who don’t have 75% attendance get a notice.
 1.7 STAKEHOLDERS

Stakeholders are a group or an organization. In Student Attendance

System, there are two types of stakeholders namely, Administrator and
Customer.

1. Administrator:
Administrator is the person who deals with the database operations like
Inserting Records, Deleting Records, and Updating Records. An Administrator
has all rights including Settings of student’s details and report generation.

2. Staff:
A Staff is the person who uses the data in the database, means accessing data
from database.

Staff has the right to access sections that includes take attendance, make
defaulter and display defaulter list.
 1.8 HARDWARE & SOFTWARE REQUIREMENT

Hardware Requirements:-
 512MB or Higher DDR2 RAM
 Intel Pentium Processor or Higher
 Up to 64GB of Hard Disk Space
 Color Monitor

Software Requirements:-
 NetBeans IDE 8.0.2
 Mysql
 Windows XP or Higher operating system
 Xampp
1.8 GANTT CHART:
SYSTEM ANALYSIS
 2.1 FACT FINDING TECHNIQUE

Examination of Existing System:

Register which are normally used in the existing system were examined.
Visited the tours booking center to learn about the processes included its
working and the documents included in the process. This helps us to find the
data flow from one process to another.

Interview Techniques:
Interviewed the Administrator and operator, i.e. the right people using
the existing system, to find out what data dose the system produce and
consume, what function must the system perform, what behaviour dose the
system exhibit, what interfaces are define and what constrains apply? Also
during the interview, normal requirement, expected requirements and existing
requirement were checked out.

This process helps to know about the procedures which are not recorded
but form and important part of the system. This technique also helps in solving
ambiguities, misinterpretations and misunderstandings.

Expectation of User:
The user expects the system to be user-friendly and flexible to their
needs.

The Administrator/Operator expects right information at the right time.

Problem Definition:
The computerized system in consideration is developed on the basis of
the working and the concepts of the existing manual system with the main aim
of overcoming the problem that are face by the existing manual system.

After implementing the fact finding technique and the further analysis
the following problems were found in the existing manual system.

It is difficult and tedious to keep track of packages and collection

records.

It is difficult to keep a check on data redundancy and inconsistency (i.e.

various copy of same data no longer agree).

Integrity problems are faced that is data values stored in the files must
satisfy certain types of consistency constraints which is difficult to achieve in
the files system.

Data isolation is difficult to be achieved since data are scattered in

various files and files may be in different formats, it is difficult to retrieve the
required information.

Over and all too much paperwork increases maintenance cost and it is
tedious and time consuming for preparing reports all this leads to a delay in
decision making.
 2.2 EVENT TABLE

Srno Event Trigger Sourc Activity Respons Destinati

e e on
Checks for Opens
Admin Login Admin valid navigation Admin
1. Login username page
and
password
Logs out The
2. Admin Logout Admin Of Admin Applicatio Admin
Logout n navigated
to home
page
Entering Adding New
3. Add student’s Admin new student Admin
Student Details students to gets added
application

Entering Adding New staff

Add Staff staff’s Admin new staff to gets added Admin
4. Details application

Displays Displaying Student’s

Shows Student’s Admin Student record get Admin
5. Student Details record Displayed
Record

Displays Displaying Staff’s

Shows Staff’s Admin Staff record get Admin
6. Staff Details record Displayed
Record
 Checks for Opens
Staff Login Staff valid navigation Staff
7. Login username page
and
password
Logs out The
Staff Logout Staff Of Admin Applicatio Staff
8. Logout n navigated
to home
page
Takes Marks Stores Stores
attendanc Attendance Staff attendance attendance Staff
9. e status status record

Shows Displays Shows Displays

attendanc Attendance Staff attendance attendance Staff
10. e Record Record Record record

Displays Displays Displays Displays

Less than Defaulter Staff Student defaulter Staff
11. 75% Attendance
Defaulter record

Displays Displays Displays Displays

0% Defaulter Staff Student defaulter Staff
12. Defaulter Attendance
record
2.3 ENTITY RELATIONSHIP DIAGRAM
Symbols Use in ERD –

E-R diagram
 2.4 CLASS DIAGRAM

In software engineering, a class diagram in the Unified Modeling

Language (UML) is a type of static structure diagram that describes the
structure of a system by showing the system's classes, their attributes, and the
relationships between the classes.

The class diagram is the main building block in object oriented modeling. It is
used both for general conceptual modeling of the systematic of the application,
and for detailed modeling translating the models into programming code.

The classes in a class diagram represent both the main objects and or
interactions in the application and the objects to be programmed. In the class
diagram these classes are represented with boxes which contain three parts:

The upper part holds the name of the class

The middle part contains the attributes of the class

The bottom part gives the methods or operations the class can take or

Undertake.
 2.6 USE CASE DIAGRAM

Use Case Diagram in Unified Modeling Language is a type of behavioral

diagram defined by and created from a use case analysis.

The main purpose of the use case diagram is to show what system functions are
performed for which actor.

In the use case diagram actor are represented by stick figure and functions are
represented by ovals.

The functions in ovals are methods of the classes in the object model.

Use case represents typical sets of scenarios that help to structure, relate and
understand essential requirements.

In Online Student Attendance System, Use Case Diagram categorized into three
parts:

1. Admin

2. Staff

3. Student
2.9 ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise

activities and actions with support for choice, iteration and concurrency. In the
Unified Modeling Language, activity diagrams can be used to describe the
business and operational stepby-step workflows of components in a system. An
activity diagram shows the overall flow of control.

Activity diagrams are constructed from a limited repertoire of shapes, connected

with arrows.

The most important shape types:

Rounded rectangles represent activities;

Diamonds represent decisions;

Bars represent the start (split) or end (join) of concurrent activities;

A black circle represents the start (initial state) of the workflow;

An encircled black circle represents the end (final state).

SYSTEM DESIGNING
 3.3 COMPONENT DIAGRAM

Component Diagrams describe the organization of components,

including source code, run-time (binary) code, and executables.

Component Diagrams:

Give the physical view of the system in terms of implementation aspect.

This is important for reusability and performance purpose.

constitute the Components, their interfaces and realizations, and dependencies

between Components

Component Diagrams are used:

To depict organizations and dependencies among Component type.

To show allocation of “classes” and “objects” to Components (also referred to

as modules) in the physical design of the system.

To indicate the “physical layering” and “partitioning” of the system architecture

(during development / implementation phases).
 3.4 DEPLOYMENT DIAGRAM

Deployment diagrams are used to visualize the topology of the

physical components of a system where the software components are deployed.

So deployment diagrams are used to describe the static deployment view of a

system. Deployment diagrams consist of nodes and their relationships.

Note: The element that provides the execution environment for the components
of a system. Depicted by a cube with the name of the object in it, preceded by a
colon, and underlined.

Connection: Similar to the relation/association used in class diagrams to define

the interconnection between nodes.
SYSTEM CODING
 4.1 MENU TREE

MAIN FORM

LOGIN Admin Staff student

Admin Adds Takes Check

Staff Reco Staff Attendan Attendan
ce ce Record
Staff
Adds Makes
Checks
Student Attendan
Defaulter
student ce record
List
Staff Makes
Record Attendan Logs off
ce Reord
Student
Shows
Record
Defaulter
4.2 DATA DICTONARY