Introduction

Attendance Management System is software developed for dailystudent attendance in schools,

colleges and institutes. It facilitates
toaccess 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
alsohelp in evaluating attendance eligibility criteria of a student.
Sinceages, attendance system has remained one of the most importantsystems for evaluating the
working time of students in any college or school. In short, this project is used to mark the number of
days present/absent in any academic year of students in a college, schooletc.

1.1 Overview:-

Attendance Management System basically has twomain modules for proper functioning.• First
module is admin which has right for creating space for new batch, entry of new faculty, updating any
subject if necessary, andsending notice.• Second module is handled by the user which can be a faulty
or anoperator. User has a right of making daily attendance, generatingreport.Attendance can be
taken in two ways:• On the basis of Subject and month.• On the basis of Class.

1.2 Scope

: - The scope of the project is the system on which

thesoftware is installed, i.e. the project is developed as a desktopapplication, and it will work for a
particular institute. But later on the project can be modified to operate it online.

1.3 Purpose

: - The purpose of developing attendance management system is to computerized the tradition way
of taking attendance .It isalso used to generate the report automatically at the end of the session or
in the between of the session. Also, the purpose of the project is to develop a student attendance
system, which has better data security, performance and user interface than the current system. In
the currentsystem, the attendance is maintained manually, due to which the people concerned with
maintaining the attendance report have to face lot of problems like: problem of data security, not
properly storage of data, increases the work load, takes a lots of time etc. It is also a verytedious job
and as manipulation of data is very easy it is error prone. So, to solve these problems we
computerized the student attendance system.
 2.System Requirements
2.1 Software Requirement

:-1. Language – Java Servlets, HTML, Apache Tomcat etc.2. Backend - MS-Access, Xara3. Operating
System - Windows-7

2.2 Minimum Hardware Requirement:-

1.RAM -256 MB (Preferably 2GB or higher)2.Hard Disk -40 GB3.Processor -

Intel Pentium 44.SVGA Monitor 5.Keyboard6.Two Button Mouse7.Operating System -Windows XP Ser
vice Pack2.

3.Literature Survey & Introduction of Methodology

3.1 Working of Present System

: - In the present system all work isdone on paper. The whole session attendance is stored in register
andat the end of the session the reports are generated. We are notinterested in generating report in
the middle of the session or as per the requirement because it takes more time in calculation. At the
endof 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

becausethe retrieval of data is very slow and data is not maintainedefficiently.•

Difficulty in report generating

: We require more calculations togenerate the report so it is generated at the end of the session and
thestudent does not get a single chance to improve their attendance.•

Manual control

: All calculations to generate report is donemanually 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 becauseall the papers are needed to generate the reports.•

Time consuming

: Every work is done manually so we cannotgenerate report in the middle of the session or as per the
requirement because it is very time consuming.•

Less security

: Security of data is less in manual systems. This because majority of the records are stored as statem
ents or inregisters. Moreover, these data can be accessed by anyone and eventhey can modify any
important data
Proposed System

-This Application is built for automating the processing of attendance.It also enhances the speed of
the performing attendance task easily. Italso generates periodic reports to keep a check on the
students whoare regular & who are not.A Faculty has to login to the system & then in the
attendanceoption they have to select appropriate class, semester and subject. Sothis will display the
list of the students who are eligible to appear inthis session. So now the faculty has to just select the
students namefrom the manual attendance sheet according to their roll number andthen submit the
sheet. This will add the selected students as presentstudent in that particular session.This system is
very useful to the office staff also because theycan generate various types of reports and submit
them to respectivefaculties also or also can be submitted to the College
Coordinator.Office staff can also generate black list of students who haveattendance less than 50%
or80%. So this kind of various reports can be generated

Characteristics of the proposed system-• User Friendly

:-The proposed system is user friendly because theretrieval and storing of data is fast and data is
maintained efficiently.Moreover the graphical user interface is provided in the proposedsystem,
which provides user to deal with the system very easily.

• Reports are easily generated

:- reports can be easily generated

inthe proposed system so user can generate the report as per therequirement (monthly) or in the
middle of the session. User can givethe 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 becomesvery easy
because there is no need to keep data on papers

• Computer operator control

:- Computer operator control will

bethere so no chance of errors. Moreover storing and retrieving of information is easy. So work
can be done speedily and in time.

Software Engineering Model-

The model employed to materialize the Student AttendanceManagement System is the iterative wat
erfall model. A commonmistake is to consider "iterative" and "incremental" as synonyms,which they
are not. In software/systems development, however, theytypically go hand in hand. The basic idea is
to develop a systemthrough repeated cycles (iterative) and in smaller portions at a
time(incremental), allowing software developers to take advantage of whatwas learned during
development of earlier parts or versions of thesystem. Learning comes from both the development
and use of thesystem, where possible key steps in the process start with a
simpleimplementation of a subset of the software requirements anditeratively enhance the evolving
versions until the full system isimplemented. At each iteration, design modifications are made
andnew functional capabilities are added.The procedure itself consists of the initialization step, the
iterationstep, and the Project Control List. The initialization step creates a baseversion of the system.
The goal for this initial implementation is tocreate a product to which the user can react. It should
offer a samplingof the key aspects of the problem and provide a solution that is simpleenough to
understand and implement easily

3.2Introduction of Methodology

:-Student Attendance Management System has been developed inInstitute for computerised
attendance submission and it’s
monitoring by Teachers, Head of Departments, Dean Academic Affairs andDirector. Students/
Guardians also have access to view their attendance. In this the teachers engaging different classes a
rerequired to submit the attendance of the students present in their classregularly. Detailed
guidelines for its use are as under. Teachers willsubmit their attendance through this Student
Attendance ManagementSystem.Attendance Management System basically has two main modules
for proper functioning• First module is admin which has right for creating space for new batch, any
entry of new faculty, updating a subject if necessary, andsending notice.• Second module is handled
by the user which can be a faulty or anoperator. User has a right of making daily attendance,
generatingreport

4.System RequirementSpecification (S.R.S.)

4.1 Overview & Summary:-

Attendance Management System is a software developed for dailystudent attendance in schools,

colleges and institutes

If facilitates toaccess the attendance information of a particular student in a particular class. This
system will also help in evaluating attendanceeligibility criteria of a student.The purpose of
developing attendance management system is tocomputerized the tradition way of taking
attendance. The scope of the project is the system on which the software is installed, i.e. the
projectis developed as a desktop application, and it will work for a particular institute.

4.2 Functional Requirements:-

The functional requirement of the project is defined under threemodules. The first module allows
the system Administrator(admin) tolog into his account and has the privileges to do multiple things
someof the include adding a new branch, adding a new subject, adding
anew teacher, adding new student, modifying student information,modifying branch information, an
d modifying student information,also there is a provision to change login password.The second
module of the project defines itself in terms of
beingused by the Teachers; Teachers have to enter their loginid and password in system. After that
the id is verified and the records of student of particular semester are displayed on the screen.
Teacher now mark the attendance of student who is present in class, teacherscan also change their
password.The third module of the project allows the students to log
intothe system and view their current attendance statistics. No other privileges are given to the
student

4.3 Non-Functional Requirements:-

Hardware requirements-Hardware Interface 1: The system should be embedded in
thePC/Laptop.Hardware Interface 2: 40 GB hard disk and 256 MB RAM.

Software requirement-Software Interface: Student Attendance management System

5.Design and Development

5.1 Design of Project:-

GUI 1: Main provides the basic navigation access to the user allowinghim to choose his login type as
Administrator, Faculty or
Student.GUI 2: Based on the users’ selection on the first screen he isnavigated to the other screen on
the basis of selection he/she made.GUI 3: This screen is the users main work area from the
navigationmenu the user selects for the operation to be performed and is taken tothe respective
domain of the project.

5.2 Use Case Diagram:-

A use case diagram in the Unified Modeling Language (UML) is atype of behavioral diagram defined
by and created from a Use-
caseanalysis. Its purpose is to present a graphical overview of thefunctionality provided by a system
in terms of actors, their goals(represented as use cases), and any dependencies between those
usecases.The main purpose of a use case diagram is to show what systemfunctions are performed for
which actor. Roles of the actors in thesystem can be depicted.Use Case diagrams are formally
included in two modeling languagesdefined by the OMG: the Unified Modeling Language (UML) and
theSystems Modeling Language (SysML).
 5.3 Data Flow Diagram:-

A data flow diagram (DFD) is a graphical representation of the "flow"of data through an information
system. It differs from the systemflowchart as it shows the flow of data through processes instead
of hardware.The DFD a way of expressing the system in a graphical formatin a modular design was
developed by Larry Constrains. This DFD isalso known as “Bubble Chart” has the purpose to classify
the systemrequirement and to identify the major information that will be a program in system
design.A Data Flow Diagram is logical model of the system and showsthe flow of the data and the
flow of logic so this all thing describeswhat takes place in a proposed system, not how the activities
areaccomplished.We have noted that the DFD describes what the flow is rather then how they are
processed, so it means the DFD doesn’t depend onthe hardware, software, data structure or file
organization.DFD consist of a series of symbols joined together by a line.There may be a single DFD
for the entire system or it may beexploded into various levels.

1.Context Free Diagram

2.First Level DFD

3.Second Level DFD

5.5 Entity Relationship Diagram:-
An entity-relationship diagram is a data modeling technique thatcreates a graphical
representation of the entities, and the relationships between entities, within an information
system.The three main components of an ERD are:
• The entity is a person, object, place or event for which data iscollected. For example, if you
consider the information systemfor a business, entities would include not only customers,
but thecustomer's address, and orders as well. The entity is represented by a rectangle and
labeled with a singular noun.
•The relationship is the interaction between the entities. In theexample above, the customer
places an order, so the word"places" defines the relationship between that instance of
acustomer and the order or orders that they place. A relationshipmay be represented by a
diamond shape, or more simply, by theline connecting the entities. In either case, verbs are
used tolabel the relationships.
•The cardinality defines the relationship between the entities interms of numbers. An entity
may be optional
: for example, asales rep could have no customers or could have one or manycustomers; or
mandatory
The steps involved in creating an ERD are:
• Identify the entities.
• Determine all significant interactions.
• Analyze the nature of the interactions
Entity Relationship Diagram Notations
Peter Chen developed ERDs in 1976. Since then Charles Bachmanand James Martin
have added some slight refinements to the basicERD principles.
Entity
An entity is an object or concept about which you wantto store information.
Weak Entity
Attributes are the properties or characteristics of an entity.
Key attribute
A key attribute is the unique,distinguishing characteristic of the entity. For example,
anemployee's social securitynumber might be theemployee's key attribute.
Multivalued attribute
A multivalued attribute canhave more than one value. For example, an employee entitycan
have multiple skill values.
7.Maintenance
Software maintenance in software engineering is the modification of
asoftware product after delivery to correct faults, to improve performance or
other attributes.A common perception of maintenance is that it is merely fixing
bugs.However, studies and surveys over the years have indicated that
themajority, over 80%, of the maintenance effort is used for non-corrective actions (Pigosky
1997). This perception is perpetuated
byusers submitting problem reports that in reality are functionalityenhancements to the
system.Software maintenance and evolution of systems was first addressed by Meir M.
Lehman in 1969. Over a period of twenty years, hisresearch led to the formulation of eight
Laws of Evolution (Lehman1997). Key findings of his research include that maintenance is
reallyevolutionary developments and that maintenance decisions are aided by
understanding what happens to systems (and software) over time.Lehman demonstrated
that systems continue to evolve over time. Asthey evolve, they grow more complex unless
some action such ascode refactoring is taken to reduce the complexity.In the late 1970s, a
famous and widely cited survey study by Lientzand Swanson, exposed the very high fraction
of life-cycle costs thatwere being expended on maintenance. They categorized
maintenanceactivities into four classes:

Adaptive – dealing with changes and adapting in the softwareenvironment

Perfective – accommodating with new or changed user requirements which concern functio
nal enhancements to thesoftware

Corrective – dealing with errors found and fixing it
Preventive – concerns activities aiming on increasing softwaremaintainability and prevent
problems in the future.The survey showed that around 75% of the maintenance effort was
onthe first two types, and error correction consumed about 21%.
Manysubsequent studies suggest a similar magnitude of the problem.Studies show that
contribution of end users are crucial during the newrequirement data gathering and
analysis. And this is the main cause of any problem during software evolution and
maintenance. So softwaremaintenance is important because it consumes a large part of
theoverall lifecycle costs and also the inability to change softwarequickly and reliably means
that business opportunities are lost
7.1 Software maintenance planning:-
The integral part of software is the maintenance part which
requiresaccurate maintenance plan to be prepared during softwaredevelopment and should
specify how users will request modificationsor report problems and the estimation of
resources such as cost should be included in the budget and a new decision should address
todevelop a new system and its quality objectives. The softwaremaintenance which can last
for 5–6 years after the development
callsfor an effective planning which addresses the scope of softwaremaintenance, the tailori
ng of the post delivery process, thedesignation of who will provide maintenance, an
estimate of the life-cycle costs.
7.2 Software maintenance processes:-
This section describes the six software maintenance processes as:1.The implementation
processes contains software preparation andtransition activities, such as the conception and

creation of the maintenance plan, the preparation for handling problemsidentified

during development, and the follow-up on productconfiguration

management.2.The problem and modification analysis process, which isexecuted once the
application has become the responsibility
of the maintenance group. The maintenance programmer mustanalyze each request,
confirm it (by reproducing the situation)and check its validity, investigate it and propose a
solution,document the request and the solution proposal, and, finally,obtain all the required
authorizations to apply the modifications.3.The process considering the implementation of
the modificationitself.4.The process acceptance of
the modification, by confirming themodified work with the individual who submitted the
request inorder to make sure the modification provided a
solution.5.The migration process (platform migration, for example) isexceptional, and is not
part of daily maintenance tasks. If thesoftware must be ported to another platform without
any changein functionality, this process will be used and a maintenance project team is likely
to be assigned to this task.6.Finally, the last maintenance process, also an event which
doesnot occur on a daily basis, is the retirement of a piece of software.
8.Testing
8.1 System Testing
System testing is a critical aspect of Software Quality Assurance andrepresents the ultimate
review of specification, design and coding.Testing is a process of executing a program with
the intent of findingan error. A good test is one that has a probability of finding an as
yetundiscovered error. The purpose of testing is to identify and correct bugs in the
developed system. Nothing is complete without testing.Testing is the vital to the success of
the system.In the code testing the logic of the developed system is tested. For thisevery
module of the program is executed to find an error. To performspecification test, the
examination of the specifications stating whatthe program should do and how it should
perform under variousconditions.Unit testing focuses first on the modules in the proposed
system tolocate errors. This enables to detect errors in the coding and logic thatare
contained within that module alone. Those resulting from theinteraction between modules
are initially avoided. In unit testing stepeach module has to be checked separately.System
testing does not test the software as a whole, but rather thanintegration of each module in
the system. The primary concern is thecompatibility of individual modules. One has to find
areas wheremodules have been designed with different specifications of datalengths, type
and data element
name.Testing and validation are the most important steps after theimplementation of the de
veloped system. The system testing is performed to ensure that there are no errors in the im
plementedsystem. The software must be executed several times in order to findout the
errors in the different modules of the system
Validation refers to the process of using the new software for thedeveloped system in a live
environment i.e., new software inside theorganization, in order to find out the errors. The
validation phasereveals the failures and the bugs in the developed system. It will become to
know about the practical difficulties the system faces
whenoperated in the true environment. By testing the code of theimplemented software,
the logic of the program can be examined. Aspecification test is conducted to check whether
the specificationsstating the program are performing under various conditions. Apartfrom
these tests, there are some special tests conducted which aregiven below:Peak Load Tests:
This determines whether the new system will
handlethe volume of activities when the system is at the peak of its processing demand. The
test has revealed that the new software for the agency is capable of handling the demands
at the peak time.Storage Testing: This determines the capacity of the new system
tostore transaction data on a disk or on other files. The proposedsoftware has the required
storage space available, because of the useof a number of hard disks.Performance Time
Testing: This test determines the length of the timeused by the system to process
transaction
data.In this phase the software developed Testing is exercising thesoftware to uncover errors
and ensure the system meets definedrequirements. Testing may be done at 4 levels:-

Unit Level

Module Level

Integration & System

Regression
8.1.1 Unit Testing:-
A Unit corresponds to a screen /form in the package. Unit testingfocuses on verification of
the corresponding class or Screen.
Thistesting includes testing of control paths, interfaces, local datastructures, logical
decisions, boundary conditions, and error handling.Unit testing may use Test Drivers, which
are control programs to co-ordinate test case inputs and outputs, and Test stubs, which
replacelow-level modules. A stub is a dummy subprogram.
8.1.2 MODULE LEVEL TESTING:-
Module Testing is done using the test cases prepared earlier. Moduleis defined during the
time of design.
8.1.3 INTEGRATION & SYSTEM TESTING:-
Integration testing is used to verify the combining of the softwaremodules. Integration
testing addresses the issues associated with
thedual problems of verification and program construction. Systemtesting is used to verify,
whether the developed system meets therequirements.
8.1.4 REGRESSION TESTING:-
Each modification in software impacts unmodified areas, whichresults serious injuries to
that software. So the process of re-testingfor rectification of errors due to modification is
known as regressiontesting
 9.Conclusion
The Attendance Management System is developed using

JavaServlets and fully meets the objectives of the system

which it has been developed. The system has reached a

steady state where all bugshave been eliminated. The

system is operated at a high level of efficiency and all the

teachers and user associated with the systemunderstands

its advantage. The system solves the problem. It wasintended to solve as requirement
specification