PROJECT REPORT

ON

ONLINE ATTENDANCE MANAGEMENT

SYSTEM

SUBMITTED FOR THE PARTIAL FULFILLMENT OF THE REQUIREMENT FOR THE DEGREE OF

MASTER OF COMPUTER APPLICATON

BY

Deepankar Sandhibigraha

COLLEGE OF IT AND MANAGEMENT EDUCATION

BHUBANESWER
APRIL 2018
 A
PROJECT REPORT
ON
ONLINE ATTENDANCE MANAGEMENT SYSTEM

Submitted as partial fulfillment toward project submission,

Master of Computer Application, BPUT, Odisha

Department of Master of Computer Application,

College Of It and Management Education,
Bhubaneswar
2018
 EVALUTION SHEET

ITEMS OF PROJECT FOLL POINTS SECURED POINTS

Report Preparation
Report Contents
Project Presentation
Viva
Total

Signature of the teacher Signature of student

with date
 Declaration of Originality

This report is prepared as partial fulfillment of the requirements for 6 th semester

Master of Computer Application, Department of MCA, CIME, Bhubaneswar. No part of
this report and project shall be reproduced, stored in a retrieval system, or transmitted by
any means, electronic, mechanical, photocopying, recording or otherwise without
permission from Dept. of MCA, CIME, Bhubaneswar. The manuscript prepared and
include in this report is original and not presented anywhere for any purpose.

(Signature of the Guide)

 ACKNOWLEDGEMENT

We want to express our gratitude to all the people who have given their heart
whelming full support in making this compilation a magnificent experience. With deep
sense of gratitude, we would like to thank all faculty members, especially Mr.Susant
Behera , Mr. SSGN Mishra, Mr. Deepak kumar Panda, Mrs. Sabita Rani Behera and
Mr. Deepak Kumar Padhi for their generous help in various ways for the completion of
this thesis.
We are extremely grateful to our faculties for their constant guidance and
willingness to share their vast knowledge made us understand this project and its
manifestations in great depths and helped us to complete the assigned tasks .We also
thankful to the H.O.D. of MCA, & Our principal for continuous encouragement and
help.
Finally, yet importantly, we would like to express my heartful thanks to my
beloved parents for their blessings, my friends and classmates for their help and wishes
for the successful completion of this project.
Last but not the least, I thank Almighty God for reasons too numerous to mention.
 ABSTRACT
Attendance Management System is an innovative application designed to maintain
and managed the attendance of students of all the three departments i.e. MBA, MCA,
M.TECH in College of IT and Management Education. This project keeps the attendance
details of all students and which allows us to create flexible and configurable attendance
policies to manage proper time and scheduling among the students, faculties and admin.
The basic idea behind this project is to monitor activity of student attendance.
Objectives
The objectives behind this project are:

 Reduces admin work by integrating the details of the students of all the three
departments into a single database.

 Manual work for information retrieval on attendance becomes less as the work
becomes digitized.

 Easy access for students because they can view their attendance and make up for
the shortage of attendance accordingly.

 It is also time saving as manual work is less.

 There is less chance of error.

 It eliminates duplicate data entry in time and attendance entries.

 It can keep the parents informed about the student’s performance via Email and
SMS alerts.

 Auto-generation of various types of reports of student attendance.

 CONTENTS

1. SYNOPSIS
 INTRODUCTION
 PURPOSE
 SCOPE
2. OBJECT &SCOPE
3. TECHNICAL BACKGROUND
 TECHNOLOGY USED
 HARDWARE REQUIREMENT
 SOFTWARE REQUIREMENT
4. FEATURES OF THE LANGUAGES USED
 HTML BASIC FEATURES
 CSS BASIC FEATURES
 SERVLET BASIC FEATURES
 ORACLE BASIC FEATURES
5. DEFINATION OF THE PROBLEM
 PROBLEM DEFINITION
 MODULE DESCRIPTION
 WORKING OF THE PRESENT SYSTEM AND ITS
DISADVANTAGES
 CHARACTERISTICS OF THE PRESENT WORKING
SYSTEM
6. FEASIBILITY STUDY
 ECONOMIC FEASIBILITY
 TECHNICAL FEASIBILITY
 BEHAVIORAL FEASIBILITY
 OPERATIONAL FEASIBILITY
7. SYSYEM ANALYSIS &DESIGN
 EXISTING SYSTEM
  PROPOSED SYSTEM
 REQUIREMENT ANALYSIS AND SPECIFICATION
 FUNCTIONAL REQUIREMENTS
 NON-FUNCTIONAL REQUIREMENTS
8. SYSTEM PLANNING
 INPUT DESIGN
 OUTPUT DESIGN
9. METHODOLOGY ADOPTED
10. SYSTEM FLOW DIAGRAM
11. UML MODELLING
 CLASS DIAGRAM
 USE CASE DIAGRAM
 SEQUENCE DIAGRAM
 ACTIVITY DIAGRAM
12. DATA TABLES
13. SYSTEM TESTING
 INTRODUCTION
 TESTING METHODOLOGIES
 UNIT TESTING
 SYSTEM TESTING
 PERFORMANCE TESTING
 TEST CASES 24
14. SYSTEM IMPLEMENTATION
 PURPOSE
 SYSTEM MAINTENANCE
15. COST BENEFIT ANALYSIS
16. GRAFICAL USER INTERFACE
17. MOTIVATION
18. CONCLUSION
19. FUTURE WORK
20. BIBLIOGRAPHY
 SYNOPSIS

Introduction
Attendance Management System is a software developed for daily student attendance in schools,
colleges and institutes. It facilitates to access the attendance information of a particular student in a
particular class. The information is sorted by the operators, which will be provided by the teacher for a
particular class. This system will also help in evaluating attendance eligibility criteria of a student.
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 automatica lly
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. But later on the project can be modified
to operate it online.
 OBJECTIVE AND SCOPE
Objective
Our project is online attendance management system and the objectives are:

 Reduces admin work by integrating the details of the students of all the three departments into a
single database.

 Manual work for information retrieval on attendance becomes less as the work becomes
digitized.

 Easy access for students because they can view their attendance and make up for the shortage of
attendance accordingly.

 It is also time saving as manual work is less.

 There is less chance of error.

 It eliminates duplicate data entry in time and attendance entries.

 Auto-generation of various types of reports of student attendance.

Scope
The following project has much scope both in present as well as future. In present situation the system
can be accessed both in lappies and mobile devices.

The scope of the project any mobile device which has the acces to it’s server on which the project has
been deployed, i.e. the project is developed as a web application, and it will work for a particular
institute. But later on the project can be modified to operate for many institutes.
In future the system can be automated using students fingerprint.
 THEORETICAL BACKGROUND
Attendance management system is a project design in such a way that it can reduce workload of faculties
and provide attendance feedback to students.

Technologies Used &System Requirement

Technologies Used
LANGUAGES USED:
 HTML
 JAVA
 SQL

FRONT END:
 HTML
 CSS
 JAVASCRIPT

BACK END:
 ORACLE
 SERVLET
 TOMCAT SERVER 9.0

Hardware Requirements

 Pentium 4, 1.4GHZ or above

 512MB RAM or more
 20GB free Hard disk space
 Standard Colour Display
 NIC or Modem (For Remote Sources)
 LAN Network(For Remote source)
 Any smartphone
Software requirements
 Operating System : Any with modern browser supporting html5, JavaScript
 Language : HTML, CSS, JavaScript
 Server Technology : Servlet
 Backend : Oracle 11g, Tomcat 9
 DEFINATION OF THE PROBLEM

PROBLEM DEFINITION
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 effic ie nt
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.

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 with the allocation of roll no and personal details for new batch. It will generate
report of personal details of student and academic details of the students with the photos.

Faculty Details
It helps to allot the subject and the subject code to the particular staffs. It provides the facility to have a
user name and password to the staffs.

Attendance details
It will make to the attendance database all students. Entered attendance to store in the database subject,
period wise into the particular date. It will help the faculties to the get report of weekly and consolidate
of the attendance.

Report details
Report can be taken by daily, weekly and consolidate. Weekly report get all hour details of attendance
starting date to ending date and display the status.
Consolidate report get all student attendance details starting date to ending date status help for the
eligibility criteria of the student to attend the examination.

LOGIN MODULE

Attendance details
It assists the faculty to mark attendance to the students for their subject. This will authenticate the staff
before making the entry.
Report details
Weekly report get particular hour details of attendance from starting date to ending date and display the
status. Consolidate report get all student attendance details from starting date to ending date status help
for the eligibility criteria of the student to attend the examination.

VIEW MODULE

Student details
It deals with all personalized information of the students along with their academic details. It will be
shown by clicking on the course.

Attendance details
It contains the attendance database showing the number of classes taken, number of classes attended and
the percentage of attendance on a particular date owing to a particular subject.

WORKING OF THE 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.
DISADVANTAGES OF PRESENT WORKING SYSTEM
 Not User Friendly: The existing system is not user friendly because the retrieval of data is very slow
and data is not maintained efficiently.

 Difficulty in report generating: We require more calculations to generate the report so it is generated
at the end of the session and the student not get a single chance to improve their attendance.

 Manual control: All calculations to generate report is done manually so there is greater chance of
errors.

 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.

 Time consuming: Every work is done manually so we cannot generate report in the middle of the
session or as per the requirement.

CHARACTERSTIC OF THE PROPOSED SYSTEM

 User Friendly: 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.
 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 students so he/she become regular.
 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 become
very easy because there is no need to keep data on papers.
 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.

FEASIBILITY STUDY

Feasibility study is the initial design stage of any project, which brings together the elements of
knowledge that indicate if a project is possible or not.

WHAT IS THE FEASIBIITY STUDY?

A feasibility study includes an estimate of the level of expertise required for a project and who can
provide it, quantitative and qualitative assessments of other essential resources, identification of critical
points, a general timetable, and a general cost estimate.

Whether a project is viable or not, i.e. whether it can generate an equal or a higher rate of return during
its lifetime requires a thorough investigation of the investment per se as well as the level of current
expenditure. The preliminary design is the simple description of the conceived idea with an indicatio n
of the main factors to be considered in the study.

Factors that affect it such as economic, technological, legal and scheduling factors. Project managers
use feasibility studies to determine potential positive and negative outcomes of a project before investing
a considerable amount of time and money into it.

IMPORTANCE

Feasibility studies allow companies to determine and organize all of the necessary details to make a
business work. A feasibility study helps identify logistical problems, and nearly all business-related
problems, along with the solutions to alleviate them. Feasibility studies can also lead to the development
of marketing strategies that convince investors or a bank that investing in the business is a wise choice.

COMPONENTS
There are several components of a feasibility study:

 Description – a layout of the business, the products and/or services to be offered and how
they will be delivered.
 Market feasibility – describes the industry, the current and future market potential,
competition, sales estimations and prospective buyers.
 Technical feasibility – lays out details on how a good or service will be delivered, which
includes transportation, business location, technology needed, materials and labour.
  Financial feasibility – a projection of the amount of funding or start-up capital needed, what
sources of capital can and will be used, and what kind of return can be expected on the
investment.
 Organizational feasibility – a definition of the corporate and legal structure of the business;
this may include information about the founders, their professional background and the skills
they possess necessary to get the company off the ground operational.

ECONOMIC FEASIBILITY

DEFINITION

Economic feasibility is also known as COST/BENEFIT ANALYS. Analysis of a project’s costs and
revenues in an effort to determine whether or not it is logically possible to complete the purpose of an
economic feasibility study (EFS) is to demonstrate the net benefit of a proposed project for accepting or
disbursing electronic funds/benefits, taking into consideration the benefits and costs to the agency, other
state agencies, and the general public as a whole.

The EFS is composed of two required forms:

 Business Case
 Cost Benefit Analysis

HOW THE PROJECT IS ECONOMICALLY FEASIBLE?

 The system being developed is economic with respect to School or College’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.

 Development of this application is highly economically feasible. The only thing to be done is making
an environment with an effective supervision.

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.
TECHNICAL FEASIBILITY
The technical requirement for the system is economic and it does not use any other additional Hardware
and software. Technical evaluation must also assess whether the existing systems can be upgraded to
use the new technology and whether the organization has the expertise to use it.
OPERATIONAL 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. Technical performance include issues such as determining
whether the system can provide the right information for the Department personnel student details, and
whether the system can be organized so that it always delivers this information at the right place and on
time using intranet services. Acceptance revolves around the current system and its personnel.
 SYSTEM ANALYSIS & DESIGN

INTRODUCTION

Analysis can be defined as breaking up of any whole so as to find out their nature, function etc. It defines
design as to make preliminary sketches of; to sketch a pattern or outline for plan. To plan and carry out
especially by artistic arrangement or in a skilful wall. System analysis and design can be characterized
as a set of techniques and processes, a community of interests, a culture and an intellectual orientatio n.
The various tasks in the system analysis include the following.

 Understanding application.

 Planning.

 Scheduling.

 Developing candidate solution.

 Performing trade studies.

 Performing cost benefit analysis.

 Recommending alternative solutions.

 Selling of the system

 Supervising, installing and maintaining the system.

This system manages to the analysis of the report creation and develops manual entry of the student
attendance. First design the students entry form, staff and time table allocation forms. This project will
helps the attendance system for the department calculate percentage and reports for eligibility criteria of
examination. The application attendance entry system will provide flexible report for all students.
EXISTING SYSTEM
The Existing 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.
PROPOSED SYSTEM
To overcome the drawbacks of the existing system, the proposed system has been evolved. This project
aims to reduce the paper work and saving time to generate accurate results from the student’s attendance.
The system provides with the best user interface. The efficient reports can be generated by using this
proposed system.
ADVANTAGES OF PROPOSED SYSTEM

 It is trouble-free to use.

 It is a relatively fast approach to enter attendance

 Is highly reliable, approximate result from user

 Best user Interface

 Efficient reports

REQUIREMENT ANALYSIS AND SPECIFICATION

Application developed follows the steps of SDLC under which the SRS model developed for the system
is listed below:
The SRS model contains
 Functional requirements
 Non- Functional requirements

FUNCTIONAL REQUIREMENTS
The functional requirement part of the system discuss the functional behavior that should be possessed
by the system. Each requirement maps to a high level function that transforms the given set of input data
into output data. They are:-
 Attendance Management System provides online registration and information of the student and
their status.
 It provides to add students to their respective course which they want to study.
 It provides to track the percentage of the students attending the classes.
 It produces single or multiple attendance reports.
 It helps to debar the students from examination having less attendance than 75%.

DIFFERENT FUNCTIONAL REQUIREMENTS

Login
DESCRIPTION:
The faculty will login into the application with the given user- id and password. If the user- id and
password is correct, user will be prompt to proceed option else error message will be displayed.
INPUT: user id and password
OUTPUT: student detail form
VIEW COURSE TAKEN
DESCRIPTION:
After login, the faculty can view the list of courses taken by the user during the semester and then he
can get the list of student enrolled in that course.
INPUT: select the display option
OUTPUT: list of courses taken
VIEW DETAILS OF ENROLLED STUDENTS
DESCRIPTION:
The faculty can view the list of student enrolled in a particular course.
INPUT: select a course and select option to display student list
OUTPUT: enrolled student list
ANTAKE ATTENDCE
DESCRIPTION:
Faculty take attendance on a particular day by swiping over a student name to mark him absent.
INPUT: mark student present or absent
OUTPUT: confirmation message
SYNCHRONIZE DATABASE
DESCRIPTION:
At the end of the mouth or at any time when faculty wishes, he can upload the attendance details of a
particular subject in the online server.
INPUT:
OUTPUT:
SYSTEM PLANNING

INPUT DESIGN
Input design is part of overall system design that requires special attention designing input data is to
make the data entered easy and free from errors. The input forms are designed using the controls
available in HTML, CSS. Validation is made only for the login page and the other pages like view and
admin user only has to click on the course and view the details and update and modify too(in case of
admin) . Help information is provided for the users during when the user feels difficult.
Input design is the process of converting the user originated input to
computer based format. A system user interacting through a workstation must be able to tell thesystem
whether to accept the input to produce reports. The collection of input data is considered to be most
expensive part of the system design. Since it is planned in such a manner so as to get relevant
information, extreme care is taken to obtain pertinent information. This project first will entered to the
input of allocation forms it will be created on student details form and subject entry form, time table
form , it will helps to calculate subject wise attendance system. Next one if user wants any verifica tio n
on the data will also be available in detail show forms. Attendance is to be entered single subject wise
or all subject wise attendance system available in this project.

OUTPUT DESIGN
Output design this application on “Student Attendance management system” generally refers to the
results and information that are generated by the system for many end-users; output is the main reason
for developing the system and the basis on which they evaluate the usefulness of the application. The
output is designed in such a way that it is attractive, convenient and informative. Forms are designed
with various features, which make the console output more pleasing. As the outputs are the most
important sources of information to the users, better design should improve the system’s relations hips
with us and also will help in decision making. Form design elaborates the way output is presented and
the layout available for capturing information. One of the most important factors of the system is the
output it produces. This system refers to the results and information generated. Basically the output from
a computer system is used to communicate the result of processing to the user. Attendance manageme nt
system to show the report subject wise attendance maintaining by staffs. Taken as a whole report obtain
on a administrator privileges only. This forms will show weekly report and consolidate report generated
date, batch, and class wise to our end user. We have our report to convert Excel format.

METHODOLOGY ADOPTED
DESIGN
The design phase emphasizes on the transformation of customer requirements as defined in the SRS
document, into a form that is suitable for coding. The design phase can be broadly classified in 2 levels.
Preliminary or High Level Design
Detailed Design
The preliminary design can be further subdivided into 2 sub categories
Function Oriented Software Design
Object Oriented Software Design
Function Oriented Software Design
This design model can be represented by drawing the DFD’S (Data Flow Diagram) for the given SRS
document.
A data flow diagram is a graphical representation of the data flow through an information system which
is used to model the process aspects of the system. DFD is the prelimina ry step used to create an
overview of the system. DFD is used for structural design.
CONTEXT DIAGRAM
A context diagram is a structured graphical tool used for identifying the functional areas and the process
which are performed within and between the system and outside the system. Context diagram supports
a data-oriented approach for designing system. It helps in defining the boundaries of the proposed
system. The symbols used in the context diagram are the external entities, data storage, data flow and
process.
Here in the following diagram we represent our attendance management system which has one external
entity i.e. user of the system namely Faculty and the data flowing in and out of the system is the
attendance data.
LEVEL 1 DIAGRAM
The context- level DFD is then exploded to produce a level 1 DFD which models the details of the
system. The level 1 DFD shows how the system is divided into sub-systems (processes), and how each
process deals with one or more of the data flows to or from an external entity, and how the processes
together provide all the functionalities of the system. The level 1 DFD also justifies the internal data
stores which must be there for the system to do its job, and shows the data flow between the various
parts of the system.
In the below level 1 of the DFD the attendance system has been decomposed into 5 processes which are
namely Login, Admin, View courses taken, View enrolled student list, Upload attendance. Each process
is accessed by the faculty and the admin. There are data storage namely attendance table, enrolled
student list and course list and user details which are used in the system.
LEVEL 2 DIAGRAM
The level 2 DFD is the further decomposition of level 1 processes into sub-processes (sub-systems)
which give detailed description of the data flow in each process. Here we have decomposed the view
design in the sub-process view attendance. In this the user may be faculty, admin, parents, students and
others select the course ID and get the details of the students enrolled and then he can view the attendance
for that particular course. The data storage used in this level is the attendance details, course list and the
enrolled student list.
LEVEL 3 DFD
The level 3 DFD is the further decomposition of level 2 processes into sub-processes which again give
the detailed description of the data flow in each of the process shown below. Here the third module of
attendance management system the admin has been decomposed with its functionalities. The admin here
can either modify, view or update the faculties or the students in the institution. After that he can get
data stored from the respective faculty database and the student database and thereby get the details of
the attendance and view the attendance report.
 DFD Level 0:-

Attendance
User management Report
system

Database
 DFD Level 1:-

Faculty Admin

Login

Authentication
Check User data

Admin Student id View Course id ListS of students

Enrolled enrolled in
students particular course
3
Faculty Course id

Student list

Stored attendance data

Update of
attendance

Get all student

Stored
attendance Attendance attendance Attendance
Report table entity
 DFD Level 2:-
Stored
Data from
Student List View
Course id database
enrolled Access List of student
User enrolled in
particular course
Course id Student

Data of
attendance

Get attendance View

Attendance detail
attendance

DFD Level 3:-

Modified

Contribution Stored data

from database Student

Contribution
Admin View Access

Faculty
Stored data
Contribution from database

Update
Get detail

Attendance
Report detail
Object oriented software Design
In this design the system is viewed as a collection of entities (objects). Each object manages its own
properties (attributes) and state.

UML MODELLING
UML, as the name shows, is a modeling language. It is used to specify, draw, visualize and document
the parts of the software.
It provides a set of notations (such as rectangles, ellipses, lines etc.) to create the visual model of a
system. This phase is used to design different UML diagrams corresponding to the applicatio n
development. It is important to distinguish between the UML model and the set of diagrams of a system.
A diagram is a partial graphic representation of a system's model. The set of diagrams need not
completely cover the model and deleting a diagram does not change the model. The model may also
contain documentation that drives the model elements and diagrams (such as written use cases).

UML diagrams represent two different views of a system model:

• Static (or structural) view: emphasizes the static structure of the system using objects, attributes,
operations and relationships. It includes class diagrams and co diagrams.

 Dynamic (or behavioral) view: emphasizes the dynamic behavior of the system by showing
collaborations among objects and changes to the internal states of objects. This view includes
sequence diagrams, activity diagrams and state machine diagrams.

UML models can be exchanged among UML tools by using the XML Metadata Interchange (XMI)
format.

In UML, one of the key tools for behaviour modelling is the use-case model, caused by OOSE. Use
cases are a way of specifying required usages of a system. Typically, they are used to capture the
requirements of a system that system is supposed to do.

UML too has many types of diagrams, which are divided into two categories. Some types represent
structural information, and the rest represent general types of behavior, including a few that represent
different aspects of interactions. These diagrams can be categorized hierarchically as shown in the
following class diagram.
 Class
Diagram
Class Diagram is a type of static data structure that describes the structure of a system by showing the
system’s classes, their attributes, operations and the relationship among objects. Here in the class
diagram there are 9 classes namely Authentication, Faculty, Courses, Attendance Sheet, Attendance
Table, Attendance Report, Student, Admin and Parents. The classes in the class diagram represents both
the main elements, interactions in the application and the classes to be programmed. The classes in the
class diagram are represented in a rectangular box divided into 3 rows where the topmost part represents
the class name, second row represents its attributes and the third row represents the member functions.
The solid line connecting the two classes is the undirected associations representing static relations hips
between classes. Place association names above, on, or below the association line. Use a filled arrow to
indicate the direction of the relationship. Place roles near the end of an association. Roles represent the
way the two classes see each other. The symbols marked in the diagram represent the multiplicity. These
symbols indicate the number of instances of one class linked to one instance of the other class. For
example, one company will have one or more employees, but each employee works for just one
company. The solid line represented with a filled diagram and a hollow diagram specify compositio n
and aggregation. Composition is a special type of aggregation that denotes a strong ownership between
Class Parent, the whole, and Class Student, its part which is illustrated with a filled diamond. Use a
hollow diamond to represent a simple aggregation relationship, in which the "whole" class plays a more
important role than the "part" class, but the two classes are not dependent on each other. The diamond
ends in both composition and aggregation relationships point toward the "whole" class (i.e., the
aggregation).
In the class diagram shown faculty and admin both have to authenticate themselves by logging in valid
user id and password. After that faculty has to choose course which will show 3 courses i.e. MBA, MCA
and MTECH respectively. After choosing a particular course, faculty can insert, update and delete data
of students into the attendance sheet.
Now, the report once generated can be viewed by all i.e. admin, faculty, parents, and students. Then the
admin can add, modify, and update the faculty and the student details. He can get the student informa tio n
and their attendance details and can view them by choosing the course.

Use Case Diagram

A use case diagram is the primary form of system or software requirements for a new software program
under developed. It consists of 3 active participants:
Actors
Use Cases
Boundary of the System
The actors in the diagram drawn below are Faculty, Student, Admin, Parents and Others. The use cases
are Login, Courses Enrollment, Take Attendance, Attendance Report, View Attendance Report,
Maintain Faculty Details and Maintain Student Details. The rectangular box representing the system
boundary is potentially the entire system as defined in the requirements document.
An actor is a person and an external entity who interacts with the use case. He has responsibility towards
the system i.e. the input and have expectations from the system i.e. the output.
Use case is a system function which can be processed manually or automated to do some specific work.
In our project it is automated. The actors communicate with the use cases by a solid link, while some
use cases may not be connected with the actors. Some use cases also have functio nalities attached to
them.
In this use case diagram the first actor is the faculty who logs in to the system by giving a valid user id
and password. Then he chooses a particular course among the 3 courses i.e. MCA, MBA and MTECH.
After that he can view the list of students enrolled in particular course and take attendance. Then he can
generate the attendance report on basis of daily, weekly and consolidate entry owing to which he can
view the Attendance report. Daily, weekly and consolidate are the 3 functionalities attached to the
attendance report.
The other 3 actors student, parents and others have only to view the attendance report.
Last but not the least, admin comes into the picture by maintaining the faculty and student details. The
admin can insert, delete and update the student and faculty details. Again these are the functionalities
attached to the two use cases by dotted lines.
Sequence Diagram
A sequence diagram shows object interactions arranged in time sequence. It depicts the objects and
classes involved in the scenario and the sequence of messages exchanged between the objects needed to
carry out the functionality of the scenario. Sequence diagrams are typically associated with use case
realizations in the Logical View of the system under development. Sequence diagrams are sometimes
called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that live
simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which
they occur. This allows the specification of simple runtime scenarios in a graphical manner.
If the lifeline is that of an object, it demonstrates a role. Leaving the instance name blank can represent
anonymous and unnamed instances. Messages, written with horizontal arrows with the message name
written above them, display interaction.
Solid arrow heads represent synchronous calls, open arrow heads represent asynchronous messages, and
dashed lines represent reply messages.[1] If a caller sends a synchronous message, it must wait until the
message is done, such as invoking a subroutine. If a caller sends an asynchronous message, it can
continue processing and doesn’t have to wait for a response. Asynchronous calls are present in
multithreaded applications, event-driven applications and in message-oriented middleware. Activatio n
boxes, or method-call boxes, are opaque rectangles drawn on top of lifelines to represent that processes
are being performed in response to the message (Execution Specifications in UML).
Activity Diagram
The Unified Modelling Language includes several subsets of diagrams, including structure diagrams,
interaction diagrams, and behaviour diagrams. Activity diagrams, along with use case and state machine
diagrams, are considered behaviour diagrams because they describe what must happen in the system
being modelled.
Stakeholders have many issues to manage, so it's important to communicate with clarity and brevity.
Activity diagrams help people on the business and development sides of an organization come together
to understand the same process and behaviour.
Benefits of activity diagrams
Activity diagrams present a number of benefits to users. Consider creating an activity diagram to:

 Demonstrate the logic of an algorithm.

 Describe the steps performed in a UML use case.
 Illustrate a business process or workflow between users and the system.
 Simplify and improve any process by clarifying complicated use cases.
 Model software architecture elements, such as method, function, and operation.

Basic components of an activity diagram

Before you begin making an activity diagram, you should first understand its makeup. Some of the most
common components of an activity diagram include:

 Action: A step in the activity wherein the users or software perform a given task. In Lucid chart,
actions are symbolized with round-edged rectangles.
 
 Decision node: A conditional branch in the flow that is represented by a diamond. It includes a
single input and two or more outputs.
 Control flows: Another name for the connectors that show the flow between steps in the
diagram.
 Start node: Symbolizes the beginning of the activity. The start node is represented by a black
circle.
 End node: Represents the final step in the activity. The end node is represented by an outlined
black circle.

These activity diagram shapes and symbols are some of the most common types found in UML
diagrams.

Action flow

Action flows, also called edges and paths, illustrate the transitions from one action state to another. They
are usually drawn with an arrowed line

Object flow Initial State or Start Point

A small filled circle followed by an arrow represents the initial action state or the start point for any
activity diagram. For activity diagram using swim lanes, make sure the start point is placed in the top
left corner of the first column.

Activity or Action State

An action state represents the non-interruptible action of objects. You can draw an action state in Smart
Draw using a rectangle with rounded corners.
Object flow

Object flow refers to the creation and modification of objects by activities. An object flow arrow from
an action to an object means that the action creates or influences the object. An object flow arrow from
an object to an action indicates that the action state uses the object.

Decisions and
Branching

A diamond represents a decision with alternate paths. When an activity requires a decision prior to
moving on to the next activity, add a diamond between the two activities. The outgoing alternates should
be labelled with a condition or guard expression. You can also label one of the paths "else."

Guards

In UML, guards are a statement written next to a decision diamond that must be true before moving next
to the next activity. These are not essential, but are useful when a specific answer, such as "Yes, three
labels are printed," is needed before moving forward.
Synchronization

A fork node is used to split a single incoming flow into multiple concurrent flows. It is represented as a
straight, slightly thicker line in an activity diagram.

A join node joins multiple concurrent flows back into a single outgoing flow.

A fork and join mode used together are often referred to as synchronization.

Time Event

This refers to an event that stops the flow for a time; an hourglass depicts it.

Merge Event

A merge event brings together multiple flows that are not concurrent.
Sent and Received Signals

Signals represent how activities can be modified from outside the system. They usually appear in pairs
of sent and received signals, because the state can't change until a response is received, much like
synchronous messages in a sequence diagram. For example, an authorization of payment is needed
before an order can be completed.

Interrupting Edge

An event, such as a cancellation, that interrupts the flow denoted with a lightning bolt.

Final State or End Point

An arrow pointing to a filled circle nested inside another circle represents the final action state.
 DATA TABLE
Student Table
SL Field Name Data Description
no. type
1 Regdno. Number This is the registration no of student
2 Rollno. Number This is the roll no of student
3 name Varcher2 This is the name of student
4 Department Varcher2 Department under which student is studying i.e.
MBA, MCA,MTECH
5 Semester Number This is the semester in which student is studying
6 yop Number This is the year of passing of student

7 mobile Varchar2 This is the phone no of student

8 Email Varchar2 This is the Email id of student
9 Gender Varchar2 Male/Female

FacultyAdmin Table For Login Details

SL Find Name Data type Description
no.
1 User id Varchar2 Store user id for logging in whether admin or faculty
2 Name Varchar2 Name of the faculty
3 Category number Admin or Faculty
4 Phone number Phone no of the person

5 Email id Varchar2 Email id of the person

6 Password number Password for Login
7 Gender number Male/Female
8 Department number MCA,MBA,MECH
Table for Each Semester
We have 6 semester in MCA, 4 semester in MCA & MTECH according to which tables are designed

SL Field Name Data type Description

no.
1 Subid Varchar2 Unique Subject code
2 Dateofclass Varchar2 Date of attendance taken
3 Many columns as the Varchar2 1 for present & 0 for absent
strength of that class
 SYSTEM TESTING
Introduction
Once source code has been generated, software must be tested to uncover (and correct) as many errors
as possible before delivery to customer. Our goal is to design a series of test cases that have a high
likelihood of finding errors. To uncover the errors software techniques are used. These techniques
provide systematic guidance for designing test that exercise the internal logic of software components,
and exercise the input and output domains of the program to uncover errors in program functio n,
behaviour and performance.
Steps:
Software is tested from two different perspectives:
• Internal program logic is exercised using ―White box‖ test case design techniques.
• Software requirements are exercised using ―block box‖ test case

Design techniques. In both cases, the intent is to find the maximum number of errors with the minimum
amount of effort and time.

Testing Methodologies
A strategy for software testing must accommodate low-level tests that are necessary to verify that a
small source code segment has been correctly implemented as well as high-level tests that validate major
system functions against user requirements. A strategy must provide guidance for the practitioner and a
set of milestones for the manager. Because the steps of the test strategy occur at a time when deadline
pressure begins to rise, progress must be measurable and problems must surface as early as possible.
Following testing techniques are well known and the same strategy is adopted during this project testing.

Unit testing
Unit testing focuses verification effort on the smallest unit of software design-the software component
or module. The unit test is white-box oriented. The unit testing is implemented in every module of
student attendance management system by giving correct manual input to the system,the data are stored
in database and retrieved. If user want required module to access the input or get the output from the
End user. If any error will accrued the time will provide handler

System testing
System testing is actually a series of different tests whose primary purpose is to fully exercise the
computer-based system. Below we have described the two types of testing which have been taken for
this project. It is to check all modules worked on input basis if you want change any values or inputs
will change all information so specified input is must.
Performance Testing
Performance testing is designed to test the run-time performance of software within the context of an
integrated system. Performance testing occurs throughout all steps in the testing process. Even at the
unit level, the performance of an individual module may be assessed as white-box tests are conducted.
This project reduce attendance table, codes. It will generate report fast having no extra time or waiting
of results. Entry of correct data will show results in a few millisecond. It just uses only low memory of
our system. This software automatically do not get access at another software. Get user permissio n
and access to other applications.

Test cases
Test case is an object for execution for other modules in the architecture does not represent any
interaction by itself. A test case is a set of sequential steps to execute a test operating on a set of
predefined inputs to produce certain expected outputs. There are two types of test cases:-manual and
automated.
A manual test case is executed manually while an automated test case is executed using
automation. In system testing, test data should cover the possible values of each parameter based on the
requirements. Since testing every value is impractical, a few values should be chosen from each
equivalence class. An equivalence class is a set of values that should all be treated the same. Ideally, test
cases that check error conditions are written separately from the functional test cases and should have
steps to verify the error messages and logs. Realistically, if functional test cases are not yet written, it is
ok for testers to check for error conditions when performing normalfunctional test cases. It should be
clear which test data, if any is expected to trigger errors.
 SYSTEM IMPLEMENTATION
Purpose
System implementation is the important stage of project when the theoretical design is tuned into
practical system. The main stages in the implementation are as follows:
Planning
Training
System testing
Changeover Planning

Planning is the first task in the system implementation. At the time of implementation of any system
people from different departments and system analysis involve. They are confirmed to practical
problem of controlling various activities of people outside their own data processing departments. The
line managers controlled through an implementation coordinating committee. The committee considers
ideas, problems and complaints of user department, it must also consider:

• The implication of system environment

• Self selection and allocation for implementation tasks
• Consultation with unions and resources available
• Standby facilities and channels of communication

Student Attendance management system will implement student details, staff handle subjects details,
separate login details ,time table details. It will used to entered subject wise attendance .This applicatio n
elaborate attendance table generate weekly, consolidate report provide to the End user. Mostly this
application will calculate date wise attendance. To select starting date to end date generate reports at the
time of activities.

SYSTEM MAINTENANCE & EVALUATION

Software maintenance is far more than finding mistakes. Provision must be made for environme nt
changes, which may affect either the computer, or other parts of the computer based systems. Such
activity is normally called maintenance. It includes both the improvement of the system functions and
the corrections of faults, which arise during the operation of a new system. It may involve the continuing
involvement of a large proportion of computer department recourses. The main task may be to adapt
existing systems in a changing environment. Back up for the entire database files are taken and stored
in storage devices like flash drives, pen drives and disks so that it is possible to restore the system at the
earliest. If there is a breakdown or collapse, then the system gives provision to restore database files.
Storing data in a separate secondary device leads to an effective and efficient maintains of the system.
The nominated person has sufficient knowledge of the organization’s computer passed based system to
be able to judge the relevance of each proposed change.

COST BENEFIT ANALYSIS

Feasibility elements include, but are not limited to:

 Increased agency revenue,

 Decreased agency revenue,
 Increased agency costs,
 Decreased agency costs,
 Increased revenue to Economic other agencies and/or the general public,
 Decreased revenue to other agencies and/or the general public,
 Increased costs to other agencies and/or the general public,
 Decreased costs to other agencies and/or the general public, and,
 Other public benefits.

These items are to be described in detail in the Business Case, and the associated dollar amounts for
these items included in the Cost Benefit Analysis. The elements for the agency should be separated
from those of other state agencies and the general public so that the potential funding requirements can
be discerned.

MOTIVATION
In older method we took attendance using paper and there is possibility of proxy and it is hassles of roll
calling.
This increased manual work of teachers such as attendance calculation etc.

We have designed a better attendance management system for students so that records are mainta ined
with ease and accuracy which was an important key behind motivating this project..

This would improve accuracy of attendance records because it will remove all the hassles of roll calling
and will save valuable time of the students as well as teachers. Designing an online student attendance
management system manages records for attendance in our institution.
 CONCLUSION

To conclude, Project Data Grid works like a component which can access all the databases and picks up
different functions. It overcomes the many limitations incorporated in the attendance.
Easy implementation Environment
Generate report Flexibly
The Attendance Management System is developed using fully meets the objectives of the system
which it has been developed. The system has reached a steady state where all bugs have been eliminated.
The system is operated at a high level of efficiency and all the teachers and user associated with the
system understands its advantage. The system solves the problem. It was intended to solve as
requirement specification.

FUTURE WORK
The project has a very vast scope in future. The project can be implemented in other colleges with extra
technologies and also in future. It can also be implemented in some other institutes too. Project can be
updated in near future as and when requirement for the same arises, as it is very flexible in terms of
expansion. With the proposed software of database Space Manager ready and fully functional the client
is now able to manage and hence run the entire work in a much better, accurate and error free manner.

The following are the future scope for the project:

Discontinue of particular student eliminate potential attendance.

Attendance management system can be accessed through mobile devices.

Individual Attendance system using login for only faculty and admin and rest others can view the
attendance.
 BIBILOGRAPHY

http://www.stackoverflow.com
http://www.javatpoint.com
http://www.w3schools.com
http://www.tutorialspoint.com
http://blog.oracle.com