Aryabhatta International College of Technical

Education
Ajmer, Rajasthan

A
PROJECT REPORT
ON
Online Attendance Management System
Submitted in partial fulfilment for the
Award of the Degree of
BACHELOR OF COMPUTER APPLICATION
2018 – 2019
Submitted to:
Guide
Varun Ambrose Thomas
Submitted by:
Riddhi Chouhan
 ABSTRACT

Over the years the manual attendance management has been carried across
most of educational institutions. To overcome the problems of manual
attendance, I have developed “web-based attendance Management System”.
Attendance Management System is based on web server, which can be
implemented on any computer. In This application, PHP is server-side
language, MySQL and PHP is used as back-end design and HTML, CSS and
JavaScript are used as front-end tools. The system communicates with
database residing on a remote server. The system facilitates the end users
with interactive design and automated processing of attendance
management.
 ACKNOWLEDGEMENT

I am thankful to Varun Ambrose Thomas for his valuable time and he has
devoted us and given us a lot of knowledge and help about the project. I am
also thankful to my Principal and Head of Department and other teachers for
their expert guidance. It is a great experience for us.
Words defeat us in expressing our deep sense of gratitude for our friends,
whose continued resourceful support and guidance enabled us to overcome
our all the challenges we faced whilst developing the project.

Riddhi Chouhan
 Table of Contents
ABSTRACT.....................................................................................................i
ACKNOWLEDGEMENT...............................................................................ii
Table of Contents........................................................................................... iii
List of Figures................................................................................................. v
List of Tables..................................................................................................vi
Chapter 1: Introduction................................................................................... 1
1.1 Problem Description..............................................................................1
1.2 Proposed Solution................................................................................. 1
1.3 Assumptions and Abbreviations............................................................1
Chapter 2: Development Tools.....................................................................................................2
2.1Hardware and Software used for Development...............................................2
2.2Hardware and Software used for using the Project.......................................2
2.3 Behavioural Feasibility Analysis.............................................................................2
2.3.1. Technical Feasibility..................................................................................................2
2.3.2.Economically Feasibility..........................................................................................3
Chapter 3: Techniques and Technologies...............................................................................4
3.1PHP.............................................................................................................................................4
3.2MySQL.....................................................................................................................................4
3.3Development Strategy.....................................................................................................5
3.3.1.Data Flow Diagram.....................................................................................................5
3.3.2.Entity Relationship Diagrams...............................................................................7
Chapter 4: Implementation.............................................................................................................9
4.1Functional Requirements...............................................................................................9
4.2Design – Interface (User Manual).........................................................................11
4.3Design – Database...........................................................................................................17
Chapter 5: Limitation and Future Enhancements...........................................................22
5.1Limitations...........................................................................................................................22
5.2 Future Aspects / Enhancements.............................................................................22
Conclusion.............................................................................................................................................24
References..............................................................................................................................................25
 List of Figures
Figure 1.5: Description
Figure 2.1: Description
And so on…
 List of Tables
Table 1.5: Description
Table 2.1: Description
And so on…
 Chapter 1: Introduction
1.1 Problem Description
Attendance Management System is a software developed for daily student attendance in
schools, colleges and institutes. If 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.

1.2 Proposed Solution

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 automatically at the end of the session or in the between of the session

1.3 Assumptions and Abbreviations

We assume that the Office personnel do all the data entry based and the correct values
obtained from forms and registers. We assume that the computers that will use the
software will be part of the college LAN. Users with administrator access should be
careful in deleting or modifying any information knowingly or unknowingly which will
lead to inconsistency of the database. The end users of this software are assumed to have
basic level of computer knowledge i.e. point and click.

1
 Chapter 2: Development Tools

2.1 Hardware and Software used for Development

1. Sublime: sublime text is proprietary cross-platform source code editor with a
python application programming interface (API). It natively supports many
programming languages and markup languages, and functions can be added by
users with plugins, typically community-built and maintained under free software
licenses.
2. Plugins: jQuery is a lightweight, "write less, do more", JavaScript library. The
purpose of jQuery is to make it much easier to use JavaScript on our website.
jQuery takes a lot of common tasks that require many lines of JavaScript code to
accomplish, and wraps them into methods that we can call with a single line of
code. jQuery also simplifies a lot of the complicated things from JavaScript, like
AJAX calls manipulation.

3. XAMPP: XAMPP is a free and open-source cross-platform web server solution

stack package developed by Apache Friends, consisting mainly of the Apache
HTTP Server, MariaDB database, and interpreters for scripts written in the PHP
and Perl programming languages. Since most actual web server deployments use
the same components as XAMPP, it makes transitioning from a local test server to
a live server possible.
4. MySQL workbench: MySQL Workbench is a Visual database designing and
modelling access tool for MySQL server relational database. It facilitates creation
of new physical data models and modification of existing MySQL databases with
reverse/forward engineering and change management functions.

2.2 Hardware and Software used for using the Project

Here you explain the tools, IDEs, plugins, operating system, testing tools, browsers or
simulators / emulators and their configuration or any other things that you have used for
using the application in the project.

2.3 Behavioural Feasibility Analysis

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.

2.3.1. Technical Feasibility

The technical requirement for the system is economic and it does not use any other
additional hardware and software

2
2.3.2. Economically Feasibility
The system being developed is economic with respect in 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 error and highly accurate as the data is required.

3
 Chapter 3: Techniques and Technologies
Here you explain the technologies that you have used in the project. PHP/Android project
people will have to explain the PHP/Android and questions like:
1. What is PHP/Android?
2. Where is it used?
3. What is its scope?
4. What are the versions?
5. Which version is better and why?
6. How different it is from its counterpart?
7. What is its applicability?
Which model did you use? (1 tier, 2 tier, 3 tier)
How you divided your system?
What is your client tier (front end), back end tier (database) and middleware (coding)?

Following is an example, not to be copied, and is just for illustrative purposes.

3.1 PHP
PHP stands for Pre-processor Hypertext and is a server-side language. This means that the
script is run on your web server, not on the user’s browser, so you do not need to worry
about compatibility issues. PHP is relatively new (compared to languages such as Perl
(CGI) and Java) but is quickly becoming one of the most popular scripting languages on
the Internet.

3.2 MySQL
MySQL is a relational database management system (RDBMS) which has more than 11
million installations. The program runs as a server providing multi-user access to a
number of databases.
MySQL is owned and sponsored by a single for-profit firm, the Swedish company
MySQL AB, now a subsidiary of Sun Microsystems, which holds the copyright to most of
the codebase. The project's source code is available under terms of the GNU General
Public License, as well as under a variety of proprietary agreements.

4
 3.3 Development Strategy
Here you explain the model by which you proceeded with the project. Here you mention
the SDLC model that you followed for developing the project.

Figure 3.1 SDLC Model (Waterfall)

3.3.1. Data Flow Diagram

This is the context level D.F.D of the proposed system the whole system has been
depicted in a single bubble, primary input and output has been carefully noted and
depicted in the way so that information flow continuity should not be lost in the next
level. The purposed system is shown as a whole process and the inputs and outputs are
shown with incoming and outgoing arrow from the system.
A DFD provides no information about the timing of processes, or about whether
processes will operate in sequence or in parallel. It is therefore quite different from a
flowchart which shows the flow of control through an algorithm, allowing a reader to
determine what operations will be performed, in what order, and under what
circumstances, but not what kinds of data will be input to and output from the system,
nor where the data will come from and go to, nor where the data will be stored (all of
which are shown on a DFD).

5
You have to show and explain the diagram in brief.

Figure 3.2 Data Flow Diagram depicting something

6
 3.3.2. Entity Relationship Diagrams
The Entity Relationship Diagram (ERD) is the graphical notations of relationship
between data object and attributes. The RED was originally proposed by Peter
Chen for the design of relational database systems and has been extended by
others. Sets of primary contents are identified for the RED: data objects,
attributes, relationship, and various type indicators. The primary purpose of the
RED is to represent data objects and their relationship.
You have to show and explain the diagram in brief.

Figure 3.3 ERD of Hospital Management System

You must also include Activity/Use Case/Sequence Diagram as and where
applicable.

7
8
 Chapter 4: Implementation
In this chapter you mention all the details you specified in SRS about the functional
requirements.

4.1 Functional Requirements

In software engineering and systems engineering, a functional requirement defines a
function of a system or its component, where a function is described as a specification of
behaviour between outputs and inputs.
Functional requirements may involve calculations, technical details, data manipulation
and processing, and other specific functionality that define what a system is supposed to
accomplish. Behavioural requirements describing all the cases where the system uses the
functional requirements are captured in use cases. Functional requirements are supported
by non-functional requirements (also known as "quality requirements"), which impose
constraints on the design or implementation (such as performance requirements, security,
or reliability). Generally, functional requirements are expressed in the form "system must
do <requirement>," while non-functional requirements take the form "system shall be
<requirement>." The plan for implementing functional requirements is detailed in the
system design, whereas non-functional requirements are detailed in the system
architecture.
A Profile’s Module contents should be:
o Entries should be made user-friendly
o It should contain a unique user name in order to provide security.
o All the necessary requirements should be filled
o Can purchase anything only by registering themselves.
o If the user is not registered, then he can only visit the site.
A Purchase’s Module contents should be:
o User should able to purchase all the products available in different
categories.
o Can edit list of the selected products present in my-cart.
o See total amount of purchase.
o Make payment by Credit-card or Debit-card.
o Log-out or can give feedbacks.

9
You also give details about the Users of the system/application and their roles.
Example:
Admin
o Login: -Admin can Login in our web site.
o Manage Furniture and Furniture category: Admin can manage all
type Furniture and Furniture category.
o Manage Customer: Admin can manage customer and his/her Order.
o Manage Payment Detail: Admin can manage payment detail PayPal

10
 4.2 Design – Interface (User Manual)
1. Home:

2. Login:

This login Form is made For Security purpose. So only Authenticated User only Access in
to the Project. There are two Type of persons can enter in the project
1. Administrator
2. Faculty

2.1 Login To Administrator:

11
 This form is showed when authorized administrator enters his correct User
Name and Password. This Form gives the option to fill the name of Students and
the name of Teacher if a new faculty has joined.
2.1.1 Add Faculty:
This Form is made for Administrator to fill up the name of teachers when
teacher Id is changed automatically. If a new teacher joined the collage its
name also is included in the System

2.1.2 View Faculty:

12
 2.1.3 Add Student:
This form enables the Administrator to fill the name of Students and there Semester
where the Student Id will change automatically when a Student is saved in the Database.
And course Will Be remain same because this System is made for BCA Students

2.1.4 View Students:

13
2.1.5 Allot Subject:

2.1.6 Courses:

14
2.1.7 Batchs:

2.2 Login To Faculty :

2.2.1 Mark Attendance:
(I)

15
(II)

2.2.2 View Attendance:

3. My Profile:

16
4.3 Design – Database
1. User Table :

2. Attendance Table :

17
3. Academic Records Table :

4. Attendance Records Table :

5. Employees Profile Table :

18
6. Students Profile Table :

7. Subjects Table :

8. Subject Allotment Table :

19
9. Classes Table :

10.Courses Table :

11.Batches Table :

12.Sessions Table :

20
21
 Chapter 5: Limitation and Future Enhancements

5.1 Limitations
Example: Each and every thing in this world have some limitations. Nothing
is there in this world, which do not have any limitations. And it is also the
case with E-Commerce Application. E-Commerce has also its limitations.
Let’s discuss some of the limitations of our E-Commerce Application. In our
E-Commerce Application we have not provided the functionality of
bidding/auctioning. Here user cannot make any bids and win the product in
lower prices. If any user wants to cancel his order then he has to write the e-
mail to the administrator to cancel his order. He cannot tell the administrator
directly to cancel the order.
If any user wants to sell his items he cannot sell his item from our E-
Commerce Application. No user can sell his item from our web store. We
have not provided any links to other sites where you can find the related
products and other related stuffs.
For the purpose of advertisement administrator cannot upload the flash file
or multimedia files to be displayed on any pages of our E-Commerce
Application. There is no provision for the management of advertisements.

5.2 Future Aspects / Enhancements

Example: Our application can be enhanced in the future to give much
functionality, which we have not yet included. As you all know the E-
Commerce is so wide an area there are so many things, which can come
under it. It is not possible to provide all the functionality as per budget of the
client and limitations of resources. So here we will discuss some of the
enhancements, which can be made to our application.
We can enhance our E-Commerce Application to sell the products of the
user. We can enhance the application so that user can upload his product

22
with its specification and features. It will make the user happy that he can
sell his product without moving out of his home easily.
Another enhancement, which we can provide is that the user, can auction the
products. As per the rule the highest bidder will win the product. The
auctioning makes the product sometime very cheap that a product of
thousand rupees will be sold in hundred rupees. So, it will make the user
very happy to buy the product at very lowest price.
We can enhance our application to manage the advertisements to be
displayed on the pages of our application. There can be a management panel
for the advertisement, which selects the advertisements to be displayed.
Because of the advertisement management panel, the administrator can let
others to advertise on the website and to earn the money.

23
 Conclusion
It can be conclusion from the above discussion that a reliable, secure, fast
and can be implemented in academic institutes for better results regarding
the management of attendance .The system will save time, reduce the
amount of work the administration to do and will replace the stationery
material with electronic apparatus .Hence a system with expected results has
been developed but there is still some room for improvement.

24
 References
Books
1. PHP & MySQL Web Development
Author: Luke Welling & Laura Thompson
Edition: 4th Edition
Press: McGraw Hill

2. Learning PHP, MySQL, JavaScript ,CSS & HTML5

Author: Robin Nixon
Edition: 2003 Edition
Press: DreamTech Press, New Delhi
3. Brett McLaughlin

4. PHP & MySQL :The Missing Manual

Author: Brett McLaughlin
Edition: 2th Edition
Press: McGraw Hill

Websites
Materialize css
o https://materializecss.com
W3schools
o https://www.w3schools.com

25