Banarsidas Chandiwala

Institute of Information Technology

(BCIIT)

ATTENDANCE MANAGEMENT SYSTEM

MASTER OF COMPUTER APPLICATION

(MCA)
SEMESTER 3rd
Submitted to

Submitted by
Roll:

CERTIFICATE
I, Mr. Ajit Kumar Roy Roll No. 0311104415 certify that the Project Report/Dissertation
entitled ATTENDANCE MANAGEMENT SYSTEM is done by me and it is an authentic
work carried out by me at BANARSIDAS CHANDIWALA INSTITUTE OF
INFORMATION TECHNOLOGY. The matter embodied in this project work has not been
submitted earlier for the award of any degree or diploma to the best of my knowledge and
belief.

Signature of the Student

Date:
Certified that the Project Report/Dissertation entitled ATTENDANCE MANAGEMENT
SYSTEM done by Ms Ajit Kumar Roy, Roll No. 0311104415, is completed under my guidance.

Countersigned
Director/HOD

Signature of the Guide:

Date:
Name of the Guide:
Designation:
Address:
Banarsidas Chandiwala Institute of
Information Technology, Kalkaji,
New Delhi-110019

ACKNOWLEDGEMENT
I am extremely grateful and remain indebted to my guide MRS GURBRINDER KAUR
for being a source of inspiration and for his constant support in the Design, Implementation and
Evaluation of the project. I am thankful to her for constant constructive criticism and invaluable
suggestions, which benefited me a lot while developing the project on ATTENDANCE
MANAGEMENT SYSTEM .She has been a constant source of inspiration and motivation for
hard work, he has been very co-operative throughout this project work. With candor and
pleasure I take opportunity to express my sincere thanks and obligation to her. Through this
column, it would be my utmost pleasure to express my warm thanks to her for the
encouragement, co-operation and consent without which I mightnt be able to accomplish this
project.

CONTENTS

S No

Topic

Certificate

Acknowledgement

Chapter-1: Introduction/Problem Definition

Chapter-2: Systems Requirement Analysis

Chapter-3: System Design

Chapter-4: System Development And Testing

Chapter-5:Conclusion

References and Bibliography

CHAPTER-1
PROBLEM DEFINATION
1.1 ORGANIZATION:
I am doing this project in Banarsidas Chandiwala Institute of Information Technology
(BCIIT).It was established in 1999 to run Three-Year Master of Computer Application (MCA)
programme. The Institute is affiliated with Guru Gobind Singh Indraprastha University, Delhi for
awarding the degree and is approved by the All India Council of Technical Education (AICTE),
Ministry of HRD; Government of India. The Institute is established under the aegis of Sri
Banarsidas Chandiwala Sewa Smarak Trust Society, a charitable Society working in the field of
health and education since 1952.

1.2. NEED OF THE NEW SYSTEM

Manually keeping information is very tedious task so its basic objective is to automate
the whole internal working of ATTENDANCE.
It helps employees to keep information regarding the students.
It helps in saving papers.
3
1.3 OBJECTIVE
The web app ATTENDANCE MANAGEMENT SYSTEM is a user interactive web app.
The purpose of developing attendance management system is to computerized the traditional way of taking
attendance. Another purpose for developing this software is to generate the report automatically at the end
of the session or in the between of the session.

CHAPTER-2
SYSTEM REQUIREMENTS ANALYSIS
A Software Requirement Specification (SRS) is a requirements specification for a
software system that is a complete description of the behaviour of a system to be
developed. It includes a set of use cases that describe all the interactions the users will have with the
software.
ITERATIVE ENHANCEMENT MODEL

The basic idea of using this model is that the software should be developed in increments, where
each increment adds some functional capability to the system until the full system is
implemented. At each step extensions and design modification can be made.
The aim of the waterfall prototyping model is the delivery of a complete, operational and good
product. The complete product is divided into releases and the developer delivers the product
release by release.

ADVANTAGES OF MODEL:
In iterative model we are building and improving the product step by step. Hence we can
track the defects at early stages. This avoids the downward flow of the defects.

In iterative model we can get the reliable user feedback. When presenting sketches and
blueprints of the product to users for their feedback, we are effectively asking them to
imagine how the product will work.

In iterative model less time is spent on documenting and more time is given for
designing.

Fig1: Iterative Enhancement Model

1. Requirement analysis and specification phase:
The goal of this phase is to understand the exact requirements of the customer and to
documents them properly.So,firstly all the requirements of student result management
system were gathered that what all function it will do eg. Generating reports,keeping
records etc. This activity is usually executed together with the customer, as the goal is to
document functions, performance and interfacing requirements for the software.Then all
the hardware requirements and software requirements were documented and are specified
below.The requirements describes the what of a system, not the how, this phase
produces a large document, written in normal language.
2.

Design phase:
The SRS document is produced in the previous phase, which contains the exact
requirements of the customer. The goal of this phase is to transform the requirements
specification into structure that is suitable for implementation in some programming
language. Here, overall software architecture is defined, and the high level and detailed
design work is performed. We designed use case diagram, dfd 0 level, Flow chart
diagram for our project which are specified below. This work is documented and known
as software design description (SSD) document.

3. Implementation and unit testing phase:

During this phase, design is implemented , if the SSD is complete, the implementation or
coding phase, design is implemented or coding phase proceeds smoothly, because all the
conformation needed by the software developers is contained in the SSD.
During testing, the major activities are centred around the examination and modification
of the code. Initially, small modules are tested in isolation from the rest of the software
7

product. There is problems association with testing a module in isolation. How do we run
a module without anything to call it, to be called by it or, possibly, to output intermediate
values obtained during execution? Such problems are solved in this phase and modules
are tested after writing some overhead code.
4. Integration and system testing phase:
This is very important phase. Effective testing will contribute to the delivery of higher
quality software products , more satisfied users, lower maintenance costs, and more
accurate and reliable results. It is a very expensive activity and consumers one third to
one- half of the cost of a typical development project.
The purpose of unit testing is to determine that each independent module is correctly
implemented. this gives little chance to determine that the interface between modules is
also correct, and for this reason integration testing is performed,. System testing involves
the testing of the entire system, whereas software is a part of the system.
5. Operation and maintenance phases:
Software maintenance is a task that every development group has to face, when the
software is delivered to the customers sites, installed and Its operational. Therefore,
release of software inaugurates the operation and maintenance phase of the cycle. The
time spent and effort required to keep the software operational after release is very
significant. Despite the fact that is a very important and challenging task; it is routinely
the poorly managed headache that nobody wants to face.

2.2 HARDWARE REQUIREMENTS

Processor

Ram

Peripherals

Pentium 400MHz or Better

128MB RAM

Keyboard and Mouse

2.3 SOFTWARE REQUIREMENTS

Operating System

Windows 8/Vista/XP

Programming language

Php

Database

mySQL

CHAPTER-3
SYSTEMS DESIGN
3.1. PHYSICAL DESIGN
3.11 USE CASE DIAGRAM

3.2 DATA FLOW DIAGRAM (DFD)

10

3.2.1 CONTEXT LEVEL

3.3 ER DIAGRAM

11

12

INTERFACE DESIGN

Output Design

13

14

Source code
Attendance form
<?php $pagetitle="AttendenceForm";
include "includes/header.php"; ?>
<div class="container">
<div class="row">
15

<div class="templatemo-line-header" style="margin-top: 0px;" >

<div class="text-center">
<hr class="team_hr team_hr_left hr_gray"/><span class="span_blog txt_darkgrey
txt_orange">Attendance Form</span>
<hr class="team_hr team_hr_right hr_gray" />
</div>
</div>
</div>
<?php
error_reporting(E_ALL ^ E_DEPRECATED);
include("config.php");?>
<div class="form-container">
<form method="post" action="AttendenceForm.php" role="form">
<!-- <div class="container"> -->
<div class="col-lg-3">
<div class="form-group">
<?php
$qs=mysqli_query($connect,"select * from student_table");
?>
<?php
echo "<select class='form-control' name='stid' >";
while($stid=mysqli_fetch_row($qs))
{
echo"
<option value=$stid[0]>$stid[1] </option>";
}
echo "</select>"."<br>";
?>
</div>
16

</div> <!--col-lg-4-->
<div class="col-lg-3">
<?php
$qs1=mysqli_query($connect,"select * from subject_table");
echo "<select class='form-control' name='subjid'>";
while($subjid=mysqli_fetch_row($qs1))
{
echo"
<option value=$subjid[0]>$subjid[1] </option>";
}
echo "</select>";?>
</div> <!--col-lg-4-->
<input type="radio" name="present" value="P" />Present
<input type="radio" name="present" value="A" />Absent
<button type="submit" name="save" value="Save" class="btn btn-success btn-sm">Save</button>

</form>
</div> <!--form-container-->
</div><!--container-->
<?php include "includes/footer.php"; ?>

Login page
<?php
error_reporting(E_ALL & ~ E_NOTICE);
session_start();
$pagetitle="LogIn Page";

17

?>
<?php
if ($_POST['submit']){
include 'connection.php';
$username=($_POST['username']);
$password=($_POST['password']);

$sql="SELECT id, username, password FROM users WHERE username='$username' AND

activated='1' LIMIT 1";
$query=mysqli_query($dbcon, $sql);
if($query){
$row= mysqli_fetch_row($query);
$userId= $row[0];
$dbusername=$row[1];
$dbpassword=$row[2];
}
if($username== $dbusername && $password== $dbpassword){
$_SESSION['username']=$username;
$_SESSION['id']=$userId;
header('Location:home.php');
}else{
echo "<span style='color:red;'>User name or password is incorrect!</span>";
}
}
?>
<link href="css/bootstrap.css" rel='stylesheet' type='text/css'>
<link href="css/semantic.min.css" rel="stylesheet">
<link href="css/templatemo_style.css" rel='stylesheet' type='text/css'>
<link href="css/mystyle.css" rel='stylesheet' type='text/css'>
<div class="container">

18

<div class="row">
<div class="templatemo-line-header" style="margin-top: 40px;" >
<div class="text-center">
<hr class="team_hr team_hr_left hr_gray"/><span class="span_blog txt_darkgrey
txt_orange">Welcome to LOG IN</span>
<hr class="team_hr team_hr_right hr_gray" />
</div>
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-md-4 col-md-offset-4">
<div class="login-panel panel panel-default">
<div class="panel-heading">
<h3 class="panel-title">Teacher login</h3>
</div>
<div class="panel-body">
<form role="form" method="post" action="login.php">
<div class="form-group">
<input class="form-control" placeholder="User name" name="username"
type="username" autofocus>
</div>
<div class="form-group">
<input class="form-control" placeholder="Password" name="password"
type="password" value="">
</div>
<div class="checkbox">
<label> <input name="remember" type="checkbox" value="Remember
Me">Remember Me</label>
</div>

19

<button type="sumbit" name="submit" value="login" class="btn btn-lg btn-success

btn-block">Login</button>
</form>
</div>
</div>
</div>
</div>
</div>

<?php include "includes/footer.php"; ?>

Student entry
<?php
$pagetitle="Students Registration";
include "includes/header.php"; ?>

<?php
if (isset($_POST['register'])) {

$studentName = $_POST['name'];
$dob = $_POST['dob'];
$gender = $_POST['gender'];
$email = $_POST['email'];
$phone= $_POST['phone'];
$add= $_POST['add'];
$session = $_POST['session'];
$program= $_POST['program'];
20

$semester= $_POST['semester'];

$db = new db();

if($db->std_entry($conn,$studentName,$dob,$gender,$email,$phone,$add,
$session,$program,$semester)){
echo "New entry was created";
}
else{
echo "unable to create new entry.";
}
}
?>

<div class="container">
<div class="row">
<div class="templatemo-line-header" style="margin-top: 0px;" >
<div class="text-center">
<hr class="team_hr team_hr_left hr_gray"/><span
class="span_blog txt_darkgrey txt_orange">Students Entry</span>
<hr class="team_hr team_hr_right hr_gray" />
</div>
</div>
</div>

21

<div class="form-container">
<form action="#" method="post" role="form">

<div class="container">
<div class="row">
<div class="col-lg-4">
<div class="form-group">
<label for="name" > Student Name(*) </label>
<input type="text" class="form-control" required id="name"
placeholder="student name" name="name">
</div>
</div>
<div class="col-lg-4">
<div class="form-group">
<label for="dob"> Date Of Birth </label>
<input type="date" class="form-control" id="dob" name="dob">
</div>
</div>
</div>
</div> <!-- col-container-->

<div class="container">
<div class="row">
<div class="col-lg-4">

<div class="form-group">
22

<label for="gender" >Gender(*)</label>

<select class="form-control" required id="sex" name="gender">
<option>-------select-------</option>
<option value="male">Male</option>
<option value="female">Female</option>
</select>
</div>
</div>
<div class="col-lg-4">

<div class="form-group">
<label for="email" >Email address </label>
<input type="email" class="form-control" required id="email"
placeholder=" Email" name="email">
</div>
</div>
</div>
</div><!-- col-container-->

<div class="container">
<div class="row">
<div class="col-lg-4">
<div class="form-group">
<label for="phone" >Phone </label>
<input type="text" class="form-control" id="phone" placeholder="Phone
Number" name="phone">
23

</div>
</div>
<div class="col-lg-4">

<div class="form-group">
<label for="add" >Address</label>
<input type="text" class="form-control" id="add" placeholder="Your
address please" rows="3" name="add"></input>
</div>
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-lg-4">

<div class="form-group">
<label for="session" >Session</label>
<input type="text" class="form-control" id="session"
placeholder="session" name="session">
</div>
</div>
<div class="col-lg-4">
<div class="form-group">
<label for="program" class="col-sm-2 control-label">Program</label>

24

<select class="form-control" name="program" required id="program"

name="program">
<option></option>
<option >MCA</option>
<option >BCA</option>
<option >BHM</option>
</select>
</div>
</div>
</div>
</div>

<div class="col-lg-4">
<div class="form-group">
<label for="semester" class="col-sm-2 control-label">Semester</label>
<select class="form-control" name="semester" required id="semester" >
<option>------ </option>
<option>1st</option>
<option>2nd</option>
<option>3rd</option>
<option>4th</option>
<option>5th</option>
<option>6th</option>
</select>
</div>
</div>
25

<br><br>
<div class="ui mini buttons col-sm-offset-3 col-sm-3">
<button type="submit" class="ui mini positive button"
name="register">Register</button>
<div class="or"></div>
<button type="reset" class="ui mini red button"
name="back">Clear</button>
</div>
</form>
</div><!--form-container-->
</div> <!--container-->
<?php include "includes/footer.php"; ?>

CHAPTER 4
26

SYSTEM DEVELOPMENT

UNIT TESTING
Unit Testing is essential for the verification of the code produced during the
coding phase and hence the goal is to test the internal logic of the modules.
Using the detailed design description as a guide,important paths are tested to
uncover errors within the boundary of the modules. These test were carried
out during the programming stage itself. All units here were successfully
tested.

TESTING

Software
phase
ofbeing
software
testing
iserror.
quality
afor
critical
assurance.
It
of
code
design
and
has
been
must
maximum
before
possible
errors,
on
aspecification,
set
of
methods
the
creation
of
test
objectives.
software
testing
are
as
follows:
executing
error
in
it.
agenerated,
program
tosoftware
find
have
abe
high
probability
of
finding
yet-undiscovered
an
as-as-yetconsidered
successful
if
it an
uncovers
undiscovered
an
erro

Software testing is a critical phase of software quality assurance. It indicates the ultimate
review of specification, design and code generation. Once source code has been
generated, software must be tested to uncover and correct maximum possible errors,
before being delivered. Testing emphasizes on a set of methods for the creation of test
cases that fulfill overall testing objectives.
The primary objectives of software testing are as follows:
1. Testing is a process of executing a program to find an error in it.
2. A good test case should have a high probability of finding an asyet-undiscovered error.
3. A test case will be considered successful if it uncovers an as-yetundiscovered error.

TESTING TECHNIQUE USED:

1. UNIT TESTING:- Unit testing aims the verification effort on the smallest unit of software
design i.e., a software component or module. It uses procedural design as a guide to test major
control paths and uncover errors within the module boundary. It is a White box oriented and the
step can be conducted in parallel for multiple components. Unit testing is a dynamic method for
verification, where the program is actually compiled and executed. It is one of the most widely
used methods, and the coding phase is sometimes called coding and unit testing phase. The
goal of unit testing is to test modules or units, not the whole software system. Unit testing is
most often done by the programmer himself/herself. The goal of Unit testing is to isolate each

27

part of the program and show that the individual parts are correct. A unit test provides a strict,
written contract that the piece of code must satisfy. As a result, it affords several benefits.
Railway Reservation

In Registration page FirstName, LastName, Gender, PhoneNumber, UserId, Password are

submitted. The user data goes in user database and he/she is registered and can now login using
user name and password.
In PNR Status page, name and pnr number is submitted. If pnr number and name donot matched
the record the warning message is displayed.

2. INTEGRATION TESTING:- Integration testing is a phase of software testing in which

individual software modules are combined and tested as a group. It follows snit testing
and precedes system testing. The major objective of integration testing is to tackle the
problem of integration i.e. putting all the modules together. One module can have an
inadvertent, adverse effect on another, sub functions, when combined, may not be
magnified to unacceptable levels; global data structure can cause problems and to
truncate this list of problems we use integration testing. Integration testing strategy used
is Bottom-Up Integration Testing. In it all the bottom or low level modules, procedures or
functions are integrated and then tested. After the integration testing of lower level
integration modules, the next level of modules will be formed and can be used for
integration testing. This approach is helpful only when all or most of the modules of the
same development level are ready. This method helps to determine the levels of software
development and makes easier to report testing progress in the form of a percentage.

3. VALIDATION TESTING:- At the climax of integration testing, software is developed

as a package having all the errors uncovered and corrected. At this time, a final series of
software test May being. It is called validation testing. Validation succeeds when software
function in a reasonably expectable manner. Validation attempts to uncover errors, but the
emphasis is on the requirements level i.e. the things that will be immediately apparent to
the customer.

28

CHAPTER 5

CONCLUSION

Rather than designing manually we have made use of computer as once that
datas are input it performs accurate function. There is no chance of fault or
miscalculation if the data are feeded correctly. Use of the computers has
solved many problems, which are faced while manual calculation. This is
not the end but beginning of the versatile, efficient and outsourcing
ATTENDANCE MANAGEMENT SYSTEM. This is the one which is
ATTENDANCE MANAGEMENT SYSTEM compatible to all operating
system.

REFERENCES AND BIBLIOGRAPHY

BOOKS USED
PHP Complete Reference by Steven Holzner
29

Html ,Dhtml,Javascript and Php by Ivan Bayross

30