Project Report

On
E-ATTENDANCE SYSTEM
SUBMITTED FOR THE PRACTICAL FULFILMENT FOR THE AWARD OF THE DEGREE IN
BACHELOR OF COMPUTER APPLICATION
(Batch:2020-2023)

Submitted By:

RAHUL JENA
EXAM ROLL NO-2020023

Under the esteemed Guided of

MISS SAISRITA MOHANTY

Department of Computer Application

Maharaja Purna Chandra Autonomous College, Baripada
Month, Year
(April,2023)

1
 E-ATTENDANCE SYSTEM

Submitted By:
RAHUL JENA
EXAM ROLL NO-2020023

Department of Computer Application

Maharaja Purna Chandra Autonomous College, Baripada
Month, Year
(April,2023)

2
 EVALUATION OF PROJECT

E-ATTENDANCE SYSTEM

Internal Examiner:- External Examiner:-

3
 CERTIFICATE

This is to certified that the project entitled " E-ATTENDANCE"

submitted by RAHUL JENA bearing Class Roll number BCA20-011,
Examination Roll number 2020023 of M.P.C. Autonomous College,
Takhatpur, Baripada is a bonafide work carried out by him under my
supervision and guidance to the best of my knowledge the matter
embodied in this report furnished are right for this project and has not
been submitted to any other university/institute for the award of any
degree or diploma.

Signature of the guide

4
 DECLARATION

I RAHUL JENA do here by declare that dissertation entitled "E-ATTENDANCE" is being

submitted by me under the guidance of MISS SAISRITA MOHANTY.

I also declare that this dissertation report is a result of my endeavor and that no part of the
report has been submitted earlier for any other degree in any university or published any time
before on any form by me.

Place :- Signature of the Candidate

Date :-

5
 ACKNOWLEDGEMENT

At the outset, I would like to take the opportunity to thank MISS

SAISRITA MOHANTY for inspiring me to do this project. The opportunity
provided by him helped me to grow as a software developer as well as
an individual.
I am also grateful to MR GOBARDHAN MAHARANA, Head of the
Department for assigning me this interesting project and for his
valuable suggestion and encouragement at various stage of work. I am
also grateful to all the faculty of BCA for their valuable suggestions and
inputs during the course of the project work.
An assemblage of this nature could never have been attempted without
the reference and inspiration from the works of others whose details
are mentioned in reference section. I acknowledged my indebtedness
to all of them.
Last but clearly not the least, my sincere thanks to all my friends who
have patiently extended all sorts of help and my utmost thank to The
Almighty for giving me strength to complete my report on time .

RAHUL JENA

6
 OBJECTIVE

“E-Attendance Management System” is a software developed for

maintaining the attendance of the student and staffs on the daily basis
in schools and colleges. The staff, who are handling the subjects, will be
responsible to mark the attendance of the students. This system will
also help evaluate a student's attendance eligibility criteria. A report of
the student’s attendance on monthly basis is generated.

7
 ABSTRACT

E-Attendance management system deals with the maintenance of the

student’s attendance details. It generates the attendance of the
student and staffs on basis of presence in class. It is maintained on the
daily basis of their attendance.

The staffs handling the subjects responsible to make the

attendance for all students. Only if the student present on that day, the
attendance will be calculated. The students attendance reports based
on monthly and consolidate will be generated.

8
TABLE OF CONTENTS

1. Introduction
2. System Environment
i. Software Configuration
ii. Hardware Configuration
3. System Analysis
i. Existing System
ii. Proposed System
iii. Feasibility study
4. Software Requirement Specification
i. Architectural diagram
ii. Module Description
iii. Process Flow
5. System Design
i. E-R Diagram
ii. Data Flow Diagram (DFD)
iii. Unified modeling Language
6. Coding

7. Testing
i. Unit Testing

9
 ii. Module Testing
iii. Integration Testing
iv. Acceptance Testi0ng
7. Conclusion

10
 INTRODUCTION

As the attendance and information services community seeks to

cope with new patterns of information provision, new technology and
changing financial circumstances, it is critical to gain new thinking
across the profession. The Latest research, innovative theory and best
organizational practice are all presented in Attandance Management
System.

E-Attendance Management System website which is used to

supply the books to the user. This is done through Web
technologies(HTML, CSS, JAVA SCRIPT). This has various technical areas.
It includes WINDOWS 10 as the operating System, MySQL as Database.
The frontend deals with HTML, CSS, JAVA SCRIPT and source code deals
with PHP & MySQL (Backend).

The project definition name describe many ways, Student attendance

management system, Attendance portal, Online attendance System,
College attendance system etc.

11
 The main aim of Student attendance system project is to maintain
attendance records of student for any organization school or college. In
this project post we will discuss attendance system project for school
and college students. We developed this attendance system as website
application using HTML, CSS, JAVASCRIPT, PHP, MY SQL.

Vision

The Interface has to be simple to use, as the target end-users for the
system are non-technical persons. Our system also aims to provide a
complete IT solution in managing attendance.

This system aims to automate the functions performed by the

college. Operations such as taking attendance and managing staff are
included in this system. Our system aims to provide powerful
functionalities to the user by making use of simple easy-to-use
interface.

12
Scope

 Student attendance management system project used to maintain

and track student attendance records for any organization..
 It can be accessed by unlimited number of organizations.
 Each user will be assigned a different set of permissions for each
module of the system including basic searching, taking attendance,
managing staff and students etc.
 The user can take attendance, manage staff on daily basis .
 The administrator has to generate daily reports, which include the
details of students and staffs.

13
SYSTEM ENVIRONMENT

14
  Software Requirement
Operating System : Windows 10/11

User Interface : HTML, CSS,

BOOTSTRAP

Client-side Scripting : JavaScript

Programming Language : PHP

Web Technologies :

IDE/Workbench : Visual Studio

Database : MySQL 8.0

Server Deployment : XAMPP

 Hardware Requirement

Processor : Pentium IV

Hard Disk : 40GB

RAM : 1GB

15
SYSTEM ANALYSIS

16
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

17
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.
The Existing system is a
manual entry for the
students. Here the
attendance will
18
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

19
the wrong inputs are
entered, the application
resist to work. so the
user find it difficult to
use.
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

20
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.
The Existing system is a
manual entry for the
21
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

22
the respective field.
Suppose
the wrong inputs are
entered, the application
resist to work. so the
user find it difficult to
use.
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 retrival of the information is not as easy as the records
are maintained in the hand written registers.

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

Limitations in Existing System

Maintaining the data in excel sheets and files is very hard to

remember the file names in which the required data is feed. No easy
access to the required queries. Data redundancy, inconsistency, lot of
human work need to be done in order analyze the details present in the
23
excel sheets. It leads to wastage of time. No timely response to the end
users.

Proposed System

Proposed system is the one that is going to be automated, so that it

is easy to retrieve the responses from the system fastly and updating
the details once the response or services are provided to the end-users
upon their request without any difficulty and saves time.

The main aim of Student attendance system project is to maintain

attendance records of student for any organization school or college.

Advantages over Existing System

 The proposed system is automated that is faster than the existing

manually maintained system and can handle data easily.
 Computerization of the details of students and staffs.
 The System allow administrator to control all the activities hence
identifying the roles and accessibility of other users. Maintenance
time and cost are greatly reduced..
24
 Accurate information can be generated easily and quickly at
different levels.
 Report can be generated easily and quickly.

Features of the proposed system:

 User friendly.
 User can get the Timely Information from the database without any
delay regarding the query.
 This reduces the delay of response given to the Customer.
 User can generate reports very easily.

25
 Feasibility Study

Economic Feasibility

Economic feasibility attempts 2 weigh the costs of developing and

implementing a new system, against the benefits that would accrue
from having the new system in place. This feasibility study gives the top
management the economic justification for the new system.

A simple economic analysis which gives the actual comparison of

costs and benefits are much more meaningful in this case. In addition,
this proves to be a useful point of reference to compare actual costs as
the project progresses. There could be various types of intangible
benefits on account of automation. These could include increased
customer satisfaction, improvement in product quality better decision
making timeliness of information, expediting activities, improved
accuracy of operations, better documentation and record keeping.
faster retrieval of information, better employee morale.

26
 Operational Feasibility

Proposed project is beneficial only if it can be turned into

information systems that will meet the organizations operating
requirements. Simply stated, this test of feasibility asks if the system
will work when it is developed and installed. Are there major barriers to
Implementation? Here are questions that will help test the operational
feasibility of a project:

Is there sufficient support for the project from management from

users? If the current system is well liked and used to the extent that
persons will not be able to see reasons for change, there may be
resistance.

Are the current business methods acceptable to the user? If they are
not, Users may welcome a change that will bring about a more
operational and useful systems.

Have the user been involved in the planning and development of the
project?

Early involvement reduces the chances of resistance to the system and

in general and increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships

encountered. In the existing manual system, the new system was
considered to be operational feasible.

27
 Technical Feasibility

Evaluating the technical feasibility is the trickiest part of a

feasibility study. This is because, at this point in time, not too many
detailed designs of the system, making it difficult to access issues like
performance, costs on (on account of the kind of technology to be
deployed) etc. A number of issues have to be considered while doing a
technical analysis.

Understand the different technologies involved in the proposed

system before commencing the project we have to be very clear about
what are the technologies that are to be required for the development
of the new system. Find out whether the organization currently
possesses the required technologies. Is the required technology
available with the organization?

28
SYSTEM REQUIREMENT SPECIFICATION

29
 Architectural Diagram

Web
Browser

Apache

PHP

My SQL
RDBMS

30
 Module Description
o Admin Module
o Attendance System

Admin module – This module can add users(course & designation) and
can generate reports about students, staffs, student, student
attendance, staff attendance.

Attendance System – This module has four controls settings, students,

staffs and reports. In settings section we can add courses, batches, and
designations. In students section we can import students and update
students. In staff section we can add staffs. And in report section we
can generate reports on students and staffs.

31
 Process Flow Control

Authentication

a. Login to the system through the first page of the application.

b. Change the password after login to the application.
c. See his/her details and change it.
d. Help from the system.

Functions

The entities are

 Login
o Username
o Password
 Dashboard
o Settings
o Reports
o Attendence
 Setting
o Course
o Batch

32
 o Designation
o Student
o Staff
 Report
o Student
o Staff
o Student Attendence
o Staff Attendence

33
SYSTEM DESIGN


34
 E-R Diagram

35
  Data Flow Diagram

A graphical tool used to describe and analyze the moment of data

through a system manual or automated including the process, stores of
data, and delays in the system. Data Flow Diagrams are the central tool
and the basis from which other components are developed. The
transformation of data from input to output, through processes, may
be described logically and independently of the physical components
associated with the system. The DFD is also know as a data flow graph
or a bubble chart.

DFDs are the model of the proposed system. They clearly should show
the requirements on which the new system should be built. Later
during design activity this is taken as the basis for drawing the system's
structure charts. The Basic Notation used to create a DFD's are as
follows:

1. Dataflow: Data move in a specific direction from an origin to a

destination.

2. Process: People, procedures, or devices that use or produce

(Transform) Data. The physical component is not identified.

36
3. Source: External sources or destination of data, which may be
People, programs, organizations or other entities.
4.

37
 Client

Add or remove
Add or Remove
staff
Student Details
Details

Student Staff
Attendance Attendance

38
  UML Diagram

Unified Modeling Language:

The Unified Modeling Language allows the software engineer to

express an analysis model using the modeling notation that is governed
by a set of syntactic semantic and pragmatic rules.

A UML system is represented using five different views that describe

the system. from distinctly different perspective. Each view is defined
by a set of diagram, which is as follows.

 User Model View

i. This view represents the system from the users
perspective.
ii. The analysis representation describes a usage scenario
from the end-users perspective.

 Structural model view

i. In this model the data and functionality are arrived from

inside the system.
ii. This model view models the static structures.

 Behavioral Model View

39
 It represents the dynamic of behavioral as parts of the system,
depicting the interactions of collection between various structural
elements described in the user model and structural model view.

 Implementation Model View

In this the structural and behavioral as parts of the system are
represented as they are to be built.

 Environmental Model View

In this the structural and behavioral aspects of the environment

in which the system is to be implemented are represented.

UML is specifically constructed through two different domains they are:

 UML Analysis modeling, this focuses on the user model and

structural model views of the system.
 UML design modeling, which focuses on the behavioral modeling,
implementation modeling and environmental model views.

40
Use case Diagrams represent the functionality of the system from a
user's point of view. Use cases are used during requirements elicitation
and analysis to represent the functionality of the system. Use cases
focus on the behavior of the system from external point of view.

Actors are external entities that interact with the system. Examples of
actors include users like administrator, bank customer...etc., or another
system like central database.

 Diagram

Admin

Student Login Attendance

Staff

41
CODING

42
login.php
<?php
include 'connection.php';
session_start();
if(isset($_POST['submit'])){
$name = $_POST['name'];
$psw = $_POST['psw'];

if($con->connect_error){
die ("connection error $con");
}else{
$sql = "SELECT * FROM admin";
$result = $con->query($sql);
$row = $result->fetch_assoc();
if($name == $row['user_name']){
if($psw == $row['psw']){
$_SESSION['admin'] = $name;
?>
<script>
alert('Login Successfull');
window.location = 'index.php';
</script>
<?php
}else{
?>
<script>
alert('Invalid Password');
</script>
<?php
}
}else{
?>
<script>
alert('Invalid User Name');
</script>
<?php

43
 }
}
}

?>

<html>
<head>
<title>Login</title>
<meta charset="utf-8" name="viewport" content="width=device-width,
initial-scale=1.0, shrink-to-fit=no">
<link rel="stylesheet" type="text/css" href="css/mycss.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/bootstrap-
[email protected]/font/bootstrap-icons.css">
</head>
<body>

<div class="login-form">
<h2>ADMIN LOGIN</h2>
<form action="" method="POST">
<div class="input-field">
<i class="bi bi-person-circle"></i>
<input type="text" placeholder="Username" name="name"
required>
</div>
<div class="input-field">
<i class="bi bi-shield-lock"></i>
<input type="password" placeholder="Password" name="psw"
required>
</div>
<button type="submit" name="submit">Login</button>

</form>
</div>

index.php

44
<?php
session_start();
include 'connection.php';
if(!isset($_SESSION['admin'])){
header("location:login.php");
}
?>

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<title>Deshboard</title>
<style>
*{
margin: 0;
padding: 0;
box-sizing: border-box;
font-family: 'Poppins', sans-serif;
}
body {
min-height: 100vh;
}
a{
text-decoration: none;
}
li {
list-style: none;
}
h1,
h2 {
color: #444;
45
}
h3 {
color: #999;
}
.container {
position: absolute;
right: 0;
width: 83vw;
height: 100vh;
background: #f1f1f1;
}
.container .content {
position: relative;
margin-top: 1vh;
min-height: 90vh;
background: #f1f1f1;
}
.container .content .cards {
padding: 20px 15px;
display: flex;
align-items: center;
justify-content: space-between;
flex-wrap: wrap;
}
.container .content .cards .card {
width: 250px;
height: 150px;
background: white;
margin: 20px 10px;
display: flex;
align-items: center;
justify-content: space-around;
box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0,
0.19);
}
46
 </style>
</head>
<body>
<?php include 'navbar.php'; ?>
<div class="container">
<div class="content">
<div class="cards">
<div class="card">
<div class="box">
<?php
$sql = "SELECT id FROM student ORDER BY id";
$res = mysqli_query($con,$sql);
$row = mysqli_num_rows($res);
echo '<h1> '.$row.'</h1>';
?>

<h3>Students</h3>
</div>
<div class="icon-case">
<img src="image/students.png" alt="">
</div>
</div>
<div class="card">
<div class="box">
<?php
$sql = "SELECT id FROM staff ORDER BY id";
$res = mysqli_query($con,$sql);
$row = mysqli_num_rows($res);
echo '<h1> '.$row.'</h1>';
?>
<h3>Teachers</h3>
</div>
<div class="icon-case">
<img src="image/teachers.png" alt="">
</div>
47
 </div>
<div class="card">
<div class="box">
<h1>1</h1>
<h3>College</h3>
</div>
<div class="icon-case">
<img src="image/schools.png" alt="">
</div>
</div>
</div>
</div>
</div>

48
 TESTING

Software testing is the process used to help identify the correctness,

completeness, security, and quality of developed computer software.
Testing is a process of technical investigation, performed on behalf of

49
stakeholders, that is intended to reveal quality related information
about the product with respect to the context in which it is intended to
operate. This includes, but is not limited to, the process of executing a
program or application with the intent of finding errors. Quality is not
an absolute; it is value to some person. With that in mind, testing can
never completely establish the correctness of arbitrary computer
software; testing furnishes a criticism or comparison that compares the
state and behavior of the product against a specification. An important
point is that software testing should be distinguished from the separate
discipline of Software Quality Assurance (SQA), which encompasses all
business process areas, not just testing.

There are many approaches to software testing, but effective testing of

complex products is essentially a process of investigation, not merely a
matter of creating and following routine procedure. One definition of
testing is "the process of questioning a product in order to evaluate it",
where the "questions" are operations the tester attempts to execute
with the product, and the product answers with its behavior in reaction
to the probing of the tester[citation needed]. Although most of the
intellectual processes of testing are nearly identical to that of review or
inspection, the word testing is connected to mean the dynamic analysis
of the product-putting the product through its paces. Some of the
common quality attributes include capability, reliability, efficiency,

50
portability, maintainability, compatibility and usability. A good test is
sometimes described as one which reveals an error; however, more
recent thinking suggests that a good test is one which reveals
information of interest to someone who matters within the project
community.

Introduction:

In general, software engineers distinguish software faults from software

failures. In case of a failure, the software does not do what the user
expects. A fault is a programming error that may or may not actually
manifest as a failure. A fault can also be described as an error in the
correctness of the semantic of a computer program. A fault will become
a failure if the exact computation conditions are met, one of them
being that the faulty portion of computer software executes on the
CPU. A fault can also turn into a failure when the software is ported to a
different hardware platform or a different compiler, or when the
software gets extended. Software testing is the technical investigation
of the product under test to provide stakeholders with quality related
information.

51
Software testing may be viewed as a sub-field of Software Quality
Assurance but typically exists independently (and there may be no SQA
areas in some companies). In SQA, software process specialists and
auditors take a broader view on software and its development. They
examine and change the software engineering process itself to reduce
the amount of faults that end up in the code or deliver faster.

Regardless of the methods used or level of formality involved the

desired result of testing is a level of confidence in the software so that
the organization is confident that the software has an acceptable defect
rate. What constitutes an acceptable defect rate depends on the nature
of the software. An arcade video game designed to simulate flying an
airplane would presumably have a much higher tolerance for defects
than software used to control an actual airliner.

A problem with software testing is that the number of defects in a

software product can be very large, and the number of configurations
of the product larger still. Bugs that occur infrequently are difficult to
find in testing. A rule of thumb is that a system that is expected to
function without faults for a certain length of time must have already
been tested for at least that length of time. This has severe

52
consequences for projects to write long-lived reliable software. A
common practice of software testing is that it is performed by an

independent group of testers after the functionality is developed but

before it is shipped to the customer. This practice often results in the
testing phase being used as project buffer to compensate for project
delays. Another practice is to start software testing at the same
moment the project starts and it is a continuous process until the
project finishes.

Another common practice is for test suites to be developed during

technical support escalation procedures. Such tests are then
maintained in regression testing suites to ensure that future updates to
the software don't repeat any of the known mistakes. It is commonly
believed that the earlier a defect is found the cheaper it is to fix it.

Unit tests are maintained along with the rest of the software source
code and generally integrated into the build process (with inherently
interactive tests being relegated to a partially manual build acceptance
process).

53
The software, tools, samples of data input and output, and
configurations are all referred to collectively as a test harness.

History

The separation of debugging from testing was initially introduced by

Glen ford ). Myers in his 1978 book the "Art of Software Testing"
Although his attention was on breakage testing it illustrated the desire
of the software engineering community to separate fundamental
development activities, such as debugging, from that of verification.

Drs. Dave Gelperin and William C. Hetzel classified in 1988 the phases
and goals in software testing as follows: until 1956 it was the debugging
oriented period, where testing was often associated to debugging:
there was no clear difference between testing and debugging. From
1957-1978 there was the demonstration oriented period where
debugging and testing was distinguished now in this period it was
shown, that software satisfies the requirements. The time between
1979-1982 is announced as the destruction oriented period, where the
goal was to find errors. 1983-1987 is classified as the evaluation
oriented period: intention here is that during the software lifecycle a
product evaluation is provided and measuring quality. From 1988 on it

54
was seen as prevention oriented period where tests were to
demonstrate that software satisfies its specification, to detect faults
and to prevent faults. Dr. Gelperin chaired the IEEE 829-1988 (Test
Documentation Standard) with Dr. Hetzel writing the book "The
Complete Guide of Software Testing". Both works were pivotal in to
today's testing culture and remain a consistent source of reference. Dr.
Gelperin and Jerry E. Durant also went on to develop High Impact
Inspection Technology that builds upon traditional Inspections but
utilizes a test driver additive.

Testing Concepts

 Testing Methodologies
 Black box Testing.
 White box Testing.
 Gray Box Testing.

 Levels of Testing
 Unit Testing.
 Module Testing.
 Integration Testing.
 System Testing.
 User Acceptance Testing.

 Types Of Testing

55
  Smoke Testing.
 Sanitary Testing.
 Regression Testing.
 Re-Testing.
 Static Testing.
 Dynamic Testing.
 Alpha-Testing.
 Beta Testing.
 Monkey Testing.
 Compatibility Testing.
 Installation Testing.
 Adhoc Testing.
 Ext....

 TCD (Test Case Documentation)

 STLC
 Test Planning.
 Test Development.
 Test Execution.
 Result Analysis.
 Bug-Tracing.
 Reporting.

 Microsoft Windows - Standards

56
 Manual Testing
 Automation Testing (Tools)
 Win Runner.
 Test Director.

Testing:
 The process of executing a system with the intent of finding an
error.
 Testing is defined as the process in which defects are identified,
isolated, subjected for rectification and ensured that product is
defect free in order to produce the quality product and hence
customer satisfaction.
 Quality is defined as justification of the requirements
 Defect is nothing but deviation from the requirements
 Defect is nothing but bug.
 Testing The presence of bugs
 Testing can demonstrate the presence of bugs, but not their
absence
 Debugging and Testing are not the same thing!
 Testing is a systematic attempt to break a program or the AUT
 Debugging is the art or method of uncovering why the script
/program did not execute properly.
 Testing Methodologies:

57
 Black box Testing: is the testing process in which tester can
perform testing on an application without having any internal
structural knowledge of application. Usually Test Engineers are
involved in the black box testing.

 White box Testing: is the testing process in which tester can

perform testing on an application with having internal
structural knowledge. Usually The Developers are involved in
white box testing.

 Gray Box Testing: is the process in which the combination of

black box and white box tonics' are used.

58
OUTPUT SCREEN

59
Login

60
Index

61
Course

62
Batch

63
Student Attendance

64
Staff Attendance

65
 PROJECT SUMMARY

This application software has been computed successfully and was also
tested successfully by taking "test cases". It is user friendly, and has
required options, which can be utilized by the user to perform the
desired operations.

The software is developed using HTML as front end and PHP as back
end in Windows environment. The goals that are achieved by the
software are:
 Optimum utilization of resources.
 Efficient management of records.
 Simplification of the operations.
 Less processing time and getting required information.
 User friendly.
 Portable and flexible for further enhancement.

66
CONCLUSION

67
WORK DONE:

GOALS

 Reduced entry work

 Easy retrieval of information
 Reduced errors due to human intervention
 User friendly screens to enter the data
 Portable and flexible for further enhancement
 Web enabled.
 Fast finding of information requested

68
 BIBILIOGRAPHY

I. HTML Complete Reference by Herbert Schield

II. Database Programming with JDBC and Java by George Reese
III. Java and XML By Brett McLaughlin
IV. Wikipedia, URL: http://www.wikipedia.org.
V. Answers.com, Online Dictionary, Encyclopedia and much more,

URL: http://www.answers.com

VI. Google, URL: http://www.google.co.in

VII. Project Management URL:

69