CONTENTS

Certificate 2
Acknowledgement 3
Abstract 4
Contents 5

CHAPTER 1-INTRODUCTION 7

1.1 Literature survey 8

1.2 Present state of art and its shortcoming 9
1.3 Introduction of the problem and work to be taken up 9
1.4 Broad line outline of the work 9
1.5 Feasibility study 9

CHAPTER 2-PROBLEM FORMULATION 11

2.1 Various aspects of problem 12
2.2 Significance of work 12
2.3 Proposed system 13

CHAPTER 3-SYSTEM ANALYSIS AND DESIGN 14

3.1 Information collection 15

3.2 Requirement specification 16
3.3 Analysis and development of actual solution (system) 17
3.4 Description of various modules 17
3.5 Choice of language 19
3.6 Choice of system for implementation 21

CHAPTER 4-SYSTEM IMPLEMENTATION AND TESTING 26

4.1 Hardware requirement 27
4.1 Software requirement 27
4.1 Input requirement 27
4.4 Output report to be obtained 27
4.5 System testing 27

CHAPTER 5-SCOPE AND CONCLUSION 31

5.1 Scope of the work: 32

5.2 Advantages of application 32
5.3 Limitation 33
5.4 Future extension
5.5 Conclusion and References 33
5.7 References/Bibliography 35

APPENDIX 36

A1 : DFD/System flow diagram etc 36

A2: UML diagrams 40

A3: ER diagrams 42

A4: Program listing-codes 43

A5 : Input (Test) data/screen /Sample output/ Reports/Screens 94

 Chapter-1

INTRODUCTION
 Computer applications and importance
Computers have their applications in almost every sphere of life – particularly in fields where
computations are required to be done at a very fast speed and where data is done at a very fast
speed and where data is so complicated that the human brain finds it difficult to cope up with.

Web service for Online Attendance System is a simple application that runs on the web. It is built
around the Web browser standards and can be used by any browser on any platform. The important
benefit of Web Services is typically work outside of private networks, offering developers a non-
proprietary route to their solutions. Services developed are likely, therefore, to have a longer life-
span, offering better return on investment of the developed service. Web Services also let
developers use their preferred programming languages. Web Services are virtually platform-
independent. Web Services allow the business logic of many different systems to be exposed over
the Web. This gives your applications the freedom to choose the Web Services that they need.
Instead of re-inventing the wheel for each client, you need only include additional application-
specific business logic on the client-side. This allows you to develop services and/or client-side
code using the languages and tools that you want. Web Services provide not a component-based
model of application development, but the closest thing possible to zero-coding deployment of
such services. This makes it easy to reuse Web Service components as appropriate in other
services. It also makes it easy to deploy legacy code as a Web Service.

In this project using web services we will be developing Online Attendance System. This system
is developed for Ttaking daily student attendance in schools, colleges and institutes. The purpose
of building this application is automating the traditional manual process of attendance, which
involved tedious

1.1Literature Survey

The literature survey method is an examination of information on specific subject. It is reviewing

what is known, and not what is assumed. It aims to create the final, precise representation of the
knowledge and research-based theory available topic. We see that in school & in collage
attendance are taken manually. It difficult to calculate a report. This is not a systematic method
where the form can be lost and may be damaged. And folders that it needs some spaces to put in
rack or cabinet. This software can reduce time and the database report can be viewed and be printed
immediately by the lecturer.

1.2Present State of art and its shortcoming

Till now Many schools, colleges and organization use process of manual attendance. This manual
attendance consumes time and inefficient resulting in false marketing of attendance. Attendance
record in hardcopy form and at the end of the semester the annual or term report is generated and
then is informed particular student about their attendance with cause lot of time. In this case a
lecturer may lose the attendance sheet. So,the record and time needs to be maintained properly.
1.3Introduction of the Problem and work to be taken up

After this, mechanism used to take online attendance was biometrics and hardware devices like
finger-prints, swapipng card, retina , which causes risk of hardware to get damage. This may cause
lose of data/information. Also the possibility of giving proxy attendance is also possible in
swapping card. In case of biometrics, if any damage or injury to finger will not identify the person.

1.4Broad outline of the work

The purpose of developing attendance management system is to computerize the tradition way of
taking attendance & to reduce the efforts of students. 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.5 Feasibility Study
A key part of the preliminary investigation that reviews anticipated costs and benefits and
recommends a course of action based on operational, technical, economic, and time factors. The
purpose of the study is to determine if the systems request should proceed further.

 Economically Feasibility:

The system being developed is economic with respect to School or College’s point of view. It is
cost effective in the sense that has eliminated the paper work completely. The system is also time
effective because the calculations are automated which are made at the end of the month or as per
the user requirement. The result obtained contains minimum errors and are highly accurate as the
data is required.

 Technical feasibility:

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

 Behavioural Feasibility:

The system working is quite easy to use and learn due to its simple but attractive interface. User
requires no special training for operating the system.
 Chapter-2

PROBLEM FORMULATION
The basic aim of the problem formulation is to obtain a clear understanding of the need of the
users, what exactly is desired from the software, and what the constraints on the solution are. The
problem formulation leads to the actual specification.

2.1 Various Aspects of Problem

In the present system all work is done on paper. The whole session attendance is stored in register
and at the and of the session the reports are generated. We are not interested in generating report
in the middle of the session or as per the requirement because it takes more time in calculation. At
the end of session the students who don’t have 75% attendance get a notice.
• Not User Friendly:
The existing system is not user friendly because the retrieval of data is very slow and data is not
maintained efficiently.
• Difficulty in report generating:
We require more calculations to generate the report so it is generated at the end of the session. And
the students not get a single chance to improve their attendance.

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

• Lots of paperwork:
Existing system requires lot of paper work. Loss of even a single register/record led to difficult
situation because all the papers are needed to generate the reports.

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

2.2 Significance of Work

• User Friendly:
The proposed system is user friendly because the retrieval and storing of data is fast and data is
maintained efficiently. Moreover the graphical user interface is provided in the proposed system,
which provides user to deal with the system very easily.
• Reports are easily generated:
Reports can be easily generated in the proposed system so user can generate the report as per the
requirement (monthly) or in the middle of the session. User can give the notice to the students so
he/she become regular
• Very less paper work:
The proposed system requires very less paper work. All the data is feted into the computer
immediately and reports can be generated through computers. Moreover work becomes very easy
because there is no need to keep data on papers.
• Computer operator control:
Computer operator control will be there so no chance of errors. Moreover storing and retrieving of
information is easy. So work can be done speedily and in time.

2.3 Proposed System:

This system contains three modules:
1)Admin:There can be only one account of admin. Admin can add the users. When a user tries to
register on prison management system then the request goes to admin and if the admin verifies
only then the user can register itself on it.
2)Teacher:Second module is handled by the TEACHER. He can add new classes of the subject.
He has right of taking daily attendance. He can access record of attendance of any student. He can
edit his profile
3)Student:Third module is STUDENT. He can view his record of attendance subject wise. He
can access his record anywhere, anytime. He can see the name of teacher corresponding to the
subject.

Chapter-3

SYSTEM ANALYSIS &

DESIGN
 3.1 Information Collection –

 Interview-Interviews are the main source of gathering data and to get acquainted with the
existing system. Almost all the information about the present system was gathered with the
help of interviews. The questions were pre-planned and asked according to the designation
of the users.
 Observations- Observations were personally made of what data is desired and how it is to
be graphically represented or in a tabular manner and how it is to be saved. The observation
of crucial information, data flows and functioning of the entire system was made carefully.
This helped to obtain the additional knowledge about the system and to view the system
more deeply. So all the aspects of the existing system are thoroughly observed which
includes how people perform their tasks, noting the things that they do, how they do it and
how much time they take. The records being manipulated and their frequency of updating
and flow of documentation are also observed. Observations were personally made of how
data can be possibly queried and represented by the user.
 Student Details- Students’ information like format of roll no etc is collected for the
required system.
 Subject’s Details- Information about the subject like subject code has been collected for
the system.
This helps to analyze the facts like:
  What is done?
 How it is being done?
 When it is done?
 How it is done?
 Where is it done?
 Why is it done?

3.2 Requirement Specification

3.2.1 FROM PEOPLES:

Interviewing: Preferred because:
Two- way communication including body language

Stimulates enthusiasm

Establishing trust between user & IS.

Different or opposing ideas can be expressed.

But answer will be:

Incomplete

Inaccurate

Not clear

Incorrect emphasis

3.2.2 FROM EXISTING SYSTEMS:

 The existing procedure that are going to be replaced

Similar system in other organizations

Standard software solutions

Description of similar system in publications

3.2.3 FROM EXPERIMENTAL METHODS:

Prototype: Combination of HW & SW exhibiting some features of the information system, but
incomplete.

3.2.4 FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF STUDENT

ATTENDANCE MANAGEMENT SYSTEM
Functional requirements of student attendance management system:-

The functional requirement of this is that it does what it is meant for. A functional requirement
describes what a software system should do, while non-functional requirements place constraints
on how the system will do so.

Functional requirements specify a function that a system or system component must be able to
perform. It can be documented in various ways. The most common ones are written descriptions
in documents and use cases.
Few of its functional requirements are as given below:-

User data should be fed into the system: this system is doing that properly in user entity.

Admin can add the users: Admin can verify and add the user, which is they are doing with this
system.

Non-Functional requirements of student attendance management system:-

Non-functional necessities square measure the other demand than practical necessities. This square
measure the necessities that specify criteria which will be wont to choose the operation of a system,
instead of specific behaviors.

Non-functional necessities square measure within the style of “system shall be “, associate degree
overall property of the system as a full or of a specific facet and not a particular operation. The
system’s overall properties remarkably mark the distinction between whether or not the event
project has succeeded or unsuccessful.

Non-functional necessities – are often divided into 2 main categories:

Execution qualities, like security and usefulness, that square measure evident at the run time.
Evolution qualities, like liabilities, maintainability, flexibility and quantifiable, that square
measure embodied within the static structure of the code.

Non-functional of student attendance management system necessities place restrictions on the

merchandise being developed, the event method, and specify external constraints that the
merchandise should meet

Our project qualifies all the criteria of functional and not functional accordingly and the system is
up to mark performance vise.Here we need to take care of few more things before heading towards
the system.

The most important feature of application world is that application’s ease of usage .application
will easy to use if made while keeping in mind that user need not think twice about searching any
feature.

Everything should be made distinctive by using the color combination such that everything needed
most frequently highlighted with focus colors. We can use simple layouts like the card and grid
layout etc.

By varying color and other UI combination, many good intuitive interfaces can be made. Which
ultimately makes interface easy to use for a long time

3.3 Analysis and Development of Actual Solution (system)

Analysis of online attendance system shows that it can be developed using the tools and technology
available as described earlier. The whole system can be divided into various modules which are
interconnected to each other. Various teacher modules can be registration, login, add class, take
attendance, statistics and short attendance. Student module include login using his roll no and
subject code and view attendance.
This system will work on client-server architecture. It will require an internet server and which
will be able to run PHP application. The system should support some commonly used browser
such as IE, Mozilla Firefox, chrome etc.

3.4 Description of Various Modules

The overall web system is divided into three major modules having the options available to
carry out the required tasks in order to successfully record the attendance. These modules include
the Admin the Teacher End and the student End.
3.4.1.ADMIN END
REMOVE TEACHER: The admin can remove the already registered teacher and subject if
required
REMOVE STUDENT: : The admin can remove the student if required if as the student is not
willing to continue or failed somehow.

3.4.2.TEACHER END
REGISTERATION+LOGIN: This is the front page which is displayed when someone visits the
web shop. This page contains login and register buttons and link to “contact us” page. From here
teacher can login to their account and if they are not registered yet then they can fill the registration
form. There they have to enter their name, mobile number, e-mail id, password etc.
Each time when a user visits the attendance system this home page is displayed to him/her.
By default login page is opened for teachers. A student can go to his login page by clicking
‘Student Dashboard’. All the registered teachers are saved in database.
PAGE HEADER:
 It contains name of the system ‘ONLINE ATTENDANCE’. This is displayed on all pages.
ADD CLASS:
 Teacher can add a new class by clicking on this option. There he has to enter the subject
code, year, section, semester, starting roll no and ending roll no.
TAKE ATTENDANCE:
 Teacher can take attendance using this option. He can mark present/absent in front of the
roll numbers of students of a class.
PROFILE:
 Teacher can view his profile using this option.
 He can also edit his profile if he wants.
STATISTICS:
  Here teacher can view attendance record classwise.
 He/she can also see the list of students whose attendance is short

LOGOUT:

After performing his work teacher can logout from his account for the class user has to
logout.

PAGE FOOTER:
 Contains copyrights information.