MCSP - 060

COLLEGE MANAGEMENT SYSTEM

by
BHAVNA SHARMA
Enrolment No: 157778260
Under Guidance
of
RAHUL SHARMA

Submitted to the School of Computer and Information Sciences,

IGNOU in partial fulfilment of the requirements for the award of the
degree

Master of Computer Applications (MCA)

2017

Indira Gandhi National Open University

Maidan Garhi
New Delhi – 11006

1|Page
SCHOOL OF COMPUTER AND INFORMATION SCIENCES

IGNOU, MAIDAN GARHI, NEW DELHI – 110 068

II. PROFORMA FOR THE APPROVAL OF MCA PROJECT PROPOSAL (MCSP-060)

(Note: All entries of the proforma of approval should be filled up with appropriate and complete
information. Incomplete proforma of approval in any respect will be summarily rejected.)

Enrolment No.: 157778260

Study Centre: 07121P
project Proposal No ………………...
Regional Centre: RC Code:38
(for office use only)
E-mail: [email protected]

Mobile/Tel No.: 7289890609

1. Name and Address of the Student RZ G-25 VIJAY ENCLAVE , DWARKA PALAM

NEW DELHI 110045

2. Title of the Project*** COLLEGE MANAGEMENT SYSTEM

3. Name and Address of the Guide RZ G-25 VIJAY ENCLAVE , DWARKA PALAM

NEW DELHI 110045

Ph. D* M.Tech.* B. E*/B.Tech.* MCA

M.Sc.*

4. Educational Qualification of the

Guide (Attach bio-data also)

(*in Computer Science / IT only)

5. Working / Teaching experience of the Guide**

(**Note: At any given point of time, a guide should not provide guidance for more than 5 MCA students of IGNOU)

6. Software used in the Project** .NET

2|Page
7. If already pursued BCA/BIT from IGNOU,
mention the title of the project (CS-76) and the s/w used NO

8. Project title of the Mini Project (MCS-044) and the s/w used ONLINE GROCERY ( PHP) .

9. Is this your first submission? Yes No

Signature of the Student Signature of the Guide

Date: ………………… Date: …………………….

For Office Use Only Name…………………………..............

…………………………………………….

Signature, Designation, Stamp of the

Project Proposal Evaluator

ApprovedNot Approved Date: …………………….

Suggestions for reformulating the Project:

3|Page
INDEX

1) Intoduction And Objective ……………....….………………………….10

2 Requirement Specification ………………………….…………………… 11

2.1) Hardware specifications ……….…………………………………………………………...11

2.2) software requirement ...…………………………………………………………………12

2.3) Fucntional requirement …………………………………………………………….. 12-17

2.4) Performance requirement …………………………………………………………….. 18

3) Design contraints …………………………………………………………19-20

4) Project category ………………………………………………………….21-24

4.1 ) MICROSOFT VISUAL Studio 2010……………………………………………………. 21

4.2) SQL Server Management Studio 2008(DATABASE)… ………………..……………… 21

4.3) RFID MODULE …….………………………………………………………………...22-23

4.4) RFID Tags ……………………………………………………..……………………. 23-24

5) Feasibility study……………………………………………...…………. 25-26

6) Problem Definition ………………………………………………………..27

4|Page
7)Database Design……………………………….…...…………………… 28-29

8)Class Diagram ………………………………………………………... 30-34

8.1 User Class 1 – Student ...................................................................................................... 30

8.2 User Class 3 – Teachers/Employee .................................................................................31

8.3) User Class 3 – Marks ………………………………………………………………….32

8.3User Class 2 – Lecture …………………………........................................................... 33

8.4 User Class4 –User Table ………....................................................................................... 34

9)RolesOfUserAndDataFlow……………………………………………………………………34-36

10) Future Scope .......…………............................................................................37

11) Bibiliography …..…………............................................................................37

5|Page
E-mail: [email protected]
Rahul Sharma  +91-9582636463

Career Objective To pursue a challenging and growth oriented career in an organization that
offers opportunities to learn & grow by delivering the results.

BCA 2014 SRU 68%

Education
12th 2006 MPBSE 73%

10th 2004 MPBSE 76%

Organisation : Saburi Global Services
Experience : 2 years 10 months
Position : Team Lead
Period : Jan 2015 to present

Organisation : HCL .
Experience : 6 months
Position : CSE
Period : July 2014 to Dec 14
Work Experience
Organisation : SS Consultancies
Experience : 2 years
Position : Senior Executive
Period : June 2012 to June 2014

● Self learner
Skills & Strengths ● A good team player
● Adaptable
.
Interest and Hobbies
Listening Music & Interacting with People

Personal Details Date of Birth : 11th Feb.,1992

Father’s Name : Sh. Arun Sharma
Languages known : English, Hindi
Address : G-25, Vijay Enclave, New Delhi -110045

Achievements Co-ordinated Annual IT fest TROKIA-2011 at my college.

I hereby declare that the above mentioned details are true to the best of my knowledge.

Date:

Place: (Rahul Sharma)

6|Page
7|Page
8|Page
COLLEGE

MANAGEMENT

SYSTEM

9|Page
INTRODUCTION AND OBJECTIVE

Introduction:

This system provides the detail structure of the college campus and its departments. College
Management System synchronizes the working of all the departments. It looks on all aspects of a
college, its students, faculties, Departments, marks and other co – curricular activities. CMS is
the easiest way to manage all functionalities of a college. It is a value-added service offered by
NEURAL, which facilitates colleges to maintain the functionality related to college employees
and their students. College Management Software is a simple yet powerful one joint integrated
platform that connects all the various departments of an institution like Administration,
Attendance, Staff details and many more specialized modules.

Objective/ vision :
The aim of the project is to detect which student is entering and leaving the
college. At the end of the month based on the attendance. This scenario though
mentioned Universal Identification for Student in University, is basically
Identification system for all the students/employees of the university through
RFID, hence the term wherever used for employee refers to university staff and
similarly student applications can be conceived within the ambit of university.
Project Perspective :

Student Attendance Using RFID System is automatic record of student

Attendance develops especially for university. This system consists of two
modules which are RFID module and Visual Studio 2010 module. Both modules
will be combined together in order for this system fully functioning. Each module
carries own function and special features which will be discussed

10 | P a g e
HARDWARE AND SOFTWARE REQUIREMENT

This section contains all of the functional and quality requirements of the system. It gives a
detailed description of the system and all its features.

User interfaces
A first-time user of the application should see the log-in page when he/she opens the application.
If the user has not registered, he/she should be able to do that on the signup page.
If the user is not a first-time user, he/she should be able to see the search page directly when the
application is opened,. Here the user chooses the type of search he/she wants to conduct.

Every user should have a profile page where they can edit their e-mail address, phone number
and password. Also, the user can set the mobile application to his/her preferred language. The
“P” icon shows where the user can click to navigate to his/her profile page The administrators
interact with the system through a web-portal. A administrator should be able to change and
manage the information. An administrator should also be able to log in to the web-portal where
he/she can administer the system by for instance editing user information.

.
Hardware Requirement-:
 Monitor
 Keyboard
 Printer
 Mouse
 RAM 512 MB
 Hard Disk 1 GB and above
 CPU p4 and above

11 | P a g e
Software Requirement -:

 MySQL ( As Back-End)
 Browser
 Windows XP and higher versions

Functional requirements:
This section includes the requirements that specify all the fundamental actions of
the software system.

User 1) student:

Req. 1 - a student id should have the access to the every possible record about the particular
student

Req. 2 - The student should be allowed to enter the campus after swapping the card only

Req. 3 - the card of students should be allowed to access only to specific areas like their class,
labs, Auditorium (only the study related places.)

Req.4 - the in time and out time should be captured properly.

Req. 5 - specific reports about the progress of student in the class should be sent the parents at
the end of the month containing the marks and other related stuff.

Req. 6 – student should not be allowed to enter the record keeping room. His card should not
have access to that.

Req. 7 – after entering the computer lab the pc’s should be distributed according to the student id
so that proper records can be maintained.

12 | P a g e
Req.8 - students should have their separate accounts in which they can get the news of future
events and other educational events going to happen

Req. 9 - the password of the student accounts should be changed every month (recommended).
And can change their passwords whenever they want.

Req.10 - the student with special responsibility of the class should have access to other student’s
record but can’t change anything to that record only can add the info regarding the class events.

Req. 11 - library (books borrowing & returning) work can be done only by the use of student id.

Req. 12 - entry without the student id should be prohibited in places like cafeteria .

Req. 13 - the attendance of the student (in time and out time) should be maintained in the real
time . So that the records can be checked where the student currently is.

Req.14 - the student should be able to retrieve password in case he forgets after providing the
correct details of the security check.

Req.15 - on the attempt of three incorrect logins the account should be blocked temporarily.

Req.16 – Student record should have the fee structure, and should contain all the fee details of a
particular SEM. It should have the fee pending column which also shows which department’s
payment is due. (Account dept)

Req.17 – it should also have a fine column which should include the activity due to which the
fine was imposed. (Account dept)

User 2) Teachers:

Req.1 - Teachers should get the info about every class which he is supposed to take lecture.

Req.2 - Teachers should have access to every room as per his need apart from the record keeping
room.

Req.3 - Teachers should be allowed to enter the campus after swapping the card.

13 | P a g e
Req.4 - the in time and out time should be captured properly.

Req. 5 - specific reports about the progress of student of the particular subject of the teacher
should be sent to the H.O.D at the end of the month containing the marks and other related stuff.

Req. 6 – teachers should not be allowed to enter the record keeping room . Their card should not
have access to that.

Req. 7 – in the computer lab the pc of teachers should be separate.

Req.8 - teachers should have their separate accounts in which they can get the news of their
meetings, lectures and future events and other educational events going to happen

Req. 9 - the password of the teachers accounts should be changed every month (recommended).
And can change their passwords whenever they want.

Req.10 - the teacher with special responsibility of the class (class teacher) should have access to
other student’s records.

Req. 11 - library (books borrowing & returning) work can be done only by the use of teachers id.

Req. 12 - entry without the teacher id should be prohibited in places like cafeteria.

Req. 13 - in time and out time should be maintained in the real time.

Req.14 - teachers should be able to retrieve password in case he forgets after providing the
correct details of the security check.

Req.15 - on the attempt of three incorrect logins the account should be blocked temporarily.

Req.16 - online assignments should be provided by teachers should reach the students account in
real time

Req.17 - lab incharges should have lab manual uploaded with them with updated details

14 | P a g e
User 3) Administrator:

There are various kind of users in this category:

1) Accounts
2) Record keeping
3) H.O.D

Req.1 - these above mentioned roles should be categorized and given authority of access
accordingly. No other user apart from super admin or record keeping can have access to the
records of the students .

Req.2 - Admins should have access to every room as per their need apart from the record
keeping room. Only super admin and record keeping staff are allowed to enter

Req.3 - no one should be allowed to enter the campus w/o swapping the card .

Req.4 - the in time and out time should be captured properly .

-Req.5 - admins should have their separate accounts in which they can get the news of their
meetings , lectures and future events and other educational events going to happen.

Req. 6 - the password of their resp. accounts should be changed every month(recommended).
And they can change their passwords whenever they want.

Req.7 - the super admin should be able to check the log of the entry and exit whenever he/ she
wants .

Req.8 - only the record keeping head or the super user is allowed to change or update the data of
anyone in the university .

Req.9 - Special security check should be maintained to check the malicious and other illegal
activity in the admin account .

15 | P a g e
Req.10 - the verification of the students and teachers which enter the school as a new entry
should firstly be approved by the record keeping staff (their record should be created ) or else
they should not e allowed to enter the campus .

Req.11 – visitors account should be maintained in case of the visits made by parents or various
people and it should have access to every room apart from admin rooms . log should be
maintained as per the entry and exit of visitor as for security purpose.

Req.12 – multiple user roles should be maintained as per need as one can be student and teacher
both or parent and teacher both . special care of such records should be taken to generate the
login as per the need of user .

Req.13- log of update, delete or insert should be maintained to check the monthly progress of the
every department.

Req.14 – account department should have all the details about the a particular students fee
pending and paid and the fine due structure. It should be linked with the other departments in
which any account work is related.

Req.15 – Admin account should be made department wise so that there should be no problem in
maintaining the accounts.

Req.16 – Admin account holder can contact each other through the link provided.

16 | P a g e
User 4 ) Parents :

Req. 1 - a parent id should have the access to the every possible record about their child

Req. 2 - The parents should be allowed to enter the campus after swapping the card only

Req. 3 - the card of parents should be allowed to access only to specific areas like their child’s
class, labs, Auditorium (only the study related places.)

Req.4 - the in time and out time should be captured properly .

Req. 5 - specific reports about the progress of their child in the class should be sent the parents at
the end of the month containing the marks and other related stuff.

Req. 6 – parents should have their separate accounts in which they can get the news of future
events and other educational events and the details of their going to happen

Req.7 - every smallest detail about the child’s activity should be maintained in the parents
account .

Req. 8 - the password of the parent accounts should be changed every month(recommended).
And can change their passwords whenever they want.

Req.9 - the attendance of the student (in time and out time ) should be maintained in the real
time and shall be updated in the parents account

Req.10 - the parents should be able to retrieve password in case he forgets after providing the
correct details of the security check .

Req.11 - on the attempt of three incorrect logins the account should be blocked temporarily .

17 | P a g e
Performance requirements :

The requirements in this section provide a detailed specification of the user interaction with the
software and measurements placed on the system performance.

Req.1 -The search feature should be prominent and easy to find for the user. RAT: In order to for
a user to find the search feature easily.

Req.2- The different search options should be evident, simple and easy to understand. RAT: In
order to for a user to perform a search easily.
Req.3- The results displayed in the list view should be user friendly and easy to understand.
Selecting an element in the result list should only take one click. RAT: In order to for a user to
use the list view easily.

Req.4 -The results displayed in the map view should be user friendly and easy to understand.
Selecting a pin on the map should only take one click.

Req.5 - The information link should be prominent and it should be evident that it is a usable link.
Selecting the information link should only take one click. RAT: In order to for a user to use the
information link easily.

18 | P a g e
Design constraints:

This section includes the design constraints on the software caused by the hardware.

Req.1 - Hard drive space. SCALE: The application’s need of hard drive space. METER: MB.
MUST: no more than 20 MB. PLAN: No more than 15 MB. WISH: No more than 10 MB.

Req.2 - The amount of Operate System memory occupied by the application. SCALE: MB.
METER: Observations done from the performance log during testing MUST: No more than 20
MB. PLAN: No more than 16 MB WISH: No more than 10 MB Operate System: DEFINED:
The mobile Operate System which the application is running on. MB: DEFINED: Megabyte.

Software system attributes:

The requirements in this section specify the required reliability, availability, security and
maintainability of the software system.

Req.1 - The average system availability (not considering network failing) and reliability that the
system gives the right result on a search should be maximum.
Req.2 -The application should be connected to the Internet.
Req.3 – Communication Security .The messages should be encrypted for log-in
communications, so others cannot get user-name and password from those messages.
Req.4 -The application should be easy to extend. The code should be written in a way that it
favors implementation of new functions
Req.5 -Test environments should be built for the application to allow testing of the applications
different functions
Req.6 -The application should be portable with iOS and Android.

19 | P a g e
Functional requirements :

1. Secure registration of employees in the office(including professors, administration

people)
2. Search employees based on different criteria
3. Setup the basic details of employees in organization such as working hours, number of
working days per month to calculate the salaries
4. Set the hierarchy of the organization
5. Send automatic mails to employees regarding salaries, attendance, holidays etc

6. Send messages to mobiles if employee absent or issued salaries or general messages

regarding holidays wishes etc.
7. Issue of salaries
8. Employee must be able to view and update his details, view his attendance reports
9. Visitor must be able to view the organization basic details

PROJECT CATEGORY
Software Specifications:

Microsoft visual studio:-

Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is

used to develop console and graphical user interface applications along with Windows
Forms or WPF applications, web sites, web applications, web services, and also Windows Store
apps in both native code together with managed code for all platforms supported by Microsoft

20 | P a g e
Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact
Framework and Microsoft Silver light.

SQL Server Management Studio:

(ssms) is a software application first launched with the Microsoft SQL Server 2005 that is used
for configuring, managing, and administering all components within Microsoft SQL Server. The
tool includes both script editors and graphical tools which work with objects and features of the
server.

(Version used) SQL Server 2008 R2:

SQL Server 2008 R2 (10.50.1600.1, formerly codenamed "Kilimanjaro") was announced at

TechEd 2009, and was released to manufacturing on April 21, 2010. SQL Server 2008 R2 adds
certain features to SQL Server 2008 including a master data management system branded
as Master Data Services, a central management of master data entities and hierarchies.

Also Multi Server Management, a centralized console to manage multiple SQL Server 2008
instances and services including relational databases, Reporting Services, Analysis Services &
Integration Services.

Student Attendance Using RFID System is automatic record of student

Attendance develops especially for university. This system consists of two modules which are

RFID module and Visual Studio 2010 module.

Both modules will be combined together in order for this system fully functioning. Each module
carries own function and special features which will be discussed in detail in this chapter.

21 | P a g e
Figure 2.0: Overall System of Student Attendance Using RFID System and Student

RFID MODULE:

RFID Reader
The RFID reader sends a pulse of radio energy to the tag and listens for the
Tag’s response. The tag detects this energy and sends back a response that contains the tag’s
serial number and possibly other information as well.
In simple RFID systems, the reader’s pulse of energy functioned as an on-off
Switch; in more sophisticated systems, the reader’s RF signal can contain commands to the tag,
instructions to read or write memory that the tag contains, and even passwords.

RFID Tag:
The tag, also known as the transponder (derived from the terms transmitter
And responder), holds the data that is transmitted to the reader when the tag is interrogated by
the reader. The most common tags today consist of an Integrated Circuit with memory,
essentially a microprocessor chip. Other tags are chip less and have no onboard Integrated

22 | P a g e
circuit. Chipless tags are more effective in applications where simpler range of functions is all
that is required; although they can help achieve more accuracy and better detection range, at
potentially lower cost than their Integrated Circuit-based counterparts. From here on out, we will
use the term tag to mean Integrated Circuit-based tag. We will refer to chipless tags explicitly,
when
Needed. RFID tags come in two general varieties which are passive and active tag. Passive tags
require no internal power source, thus being pure passive devices (they are only active when a
reader is nearby to power them), whereas active tags require a power source, usually a small
battery.

Passive tags:
Passive RFID requires stronger signals from the reader, and the signal strength returned from the
tag is constrained to very low levels. Active RFID allows very low-level signals to be received
by the tag (because the reader does not need to power the tag), and the tag can generate high-
level signals back to the reader. Additionally, the Active RFID tag is continuously powered,
whether in the reader field or not. Active tags can also ‘beacon,’ or initiate communication with a
reader (or other tags) when certain conditions are present. Active tags can contain external
sensors to monitor temperature, humidity, motion, and other conditions.
To study on data transfer between RFID system and Visual Studio 2010:
The data that was read by RFID reader will communicate with interface on
Visual Studio 2010 for display and to compare with database.

To develop graphical user interface (GUI) using Visual Basic 6 that will integrate with
RFID system to capture and record student attendance:

The main objective is to developed student attendance with RFID system. We need to build
interface that will integrate with RFID system and will show the card code. Another interface
also need to capture and record student attendance.

Use appropriate RFID Tag & Reader for this application:

23 | P a g e
There are lots of RFID reader and tag sold at market. Not only brand, but also frequencies of the
RFID itself need to be considered. Since this system will be applied to a university, the RFID
reader must used same frequencies as university student ID card.

Design and implement a system in student attendance using RFID:

The RFID reader will use to detect the student ID card code. The code will
Use to compare with Access database and the information in database will be display and store
by using interface on Visual Basic 6.

CHAPTER: - FEASIBILITY STUDY

Preliminary investigation examines project feasibility; the likelihood the system will be useful to
the organization. All systems are feasible if they are given unlimited resources and infinite time.
There are aspects in the feasibility study portion of the preliminary investigation.

24 | P a g e
• Technical Feasibility
• Operational Feasibility
• Economic Feasibility

TECHNICAL FEASIBILITY
The technical issue usually raised during the feasibility stage of the investigation includes the
following:
• Does the necessary technology exist to do what is suggested?
• Do the proposed equipment’s have the technical capacity to hold the data required to use
the new system?
• Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
• Can the system be upgraded if developed? Are there technical guarantees of accuracy,
reliability, ease of access and data security?

OPERATIONAL FEASIBILITY

User-friendly
User will use the forms for their various transactions i.e. for adding new information.
Reliability
The transactions are completed at once, completely.
Security
The web server and database server should be protected from hacking, virus etc.
Portability
The application will be developed using standard open source software (Except Oracle) like
Java, tomcat web server, Internet Explorer Browser these software will work both on Windows
and Linux o/s. Hence portability problems will not arise.

ECONOMIC FEASILITY

25 | P a g e
The computerized system takes care of the present existing system’s data flow and procedures
completely and should generate all the reports of the manual system besides a host of other
management reports.
It should be built as a web based application with separate web server and database server. This
is required as the activities are spread throughout the organization user wants a centralized
database. Further some of the linked transactions take place in different locations.

CHAPTER

Problem Definition

Main aim in developing College Management System is to provide an easy way not only to
automate all functionalities of a college, but also to provide full functional reports to top
management of college with the finest of details about any aspect of college. College

26 | P a g e
Management System is software has the perspective of attaining attraction of those colleges
which don’t have one good performing software for keeping their information secure and make
their management easier. College Management System provides one attractive environment
where you can manipulate data and information about students and staff easily. So we can say
the Core purpose of designing “College Management System” is to manage the task related to
the college students/employees and to reduce time to searching of appropriate candidates in
college view.

27 | P a g e
Chapter:- Database Design

INTRODUCTION

Database design is the process or art of designing the structure, components, and data for a
system to satisfy specified requirements. One could see it as the application of dB design theory
to product development. There is some overlap and synergy with the disciplines of systems
analysis, systems architecture and systems engineering.

UML DIAGRAMS

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.

1. 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.
2. 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.
3. Behavioral Model View
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.
4. Implementation Model View
In this the structural and behavioral as parts of the system are represented as they are to be built.
5. Environmental Model View

28 | P a g e
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:

1. UML Analysis modeling, this focuses on the user model and structural model views of the
system.
2. UML design modeling, which focuses on the behavioral modeling, implementation modeling
and environmental model views.

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.

29 | P a g e
CLASS DIAGRAM:

DATABASE AND TABLES

Student :-

30 | P a g e
TEACHERS :-

31 | P a g e
Marks :-

LECTURES :-

32 | P a g e
User Tables :-

33 | P a g e
Roles Of User & Data Flow :

Student Attendance Using RFID System is automatic record of student

Attendance develops especially for university. This system consists of two
modules which are RFID module and Visual Studio 2010 module. Both modules
will be combined together in order for this system fully functioning. Each module
carries own function and special features which will be discussed.

34 | P a g e
Users of the system:

 Admin

 Student

 Professor

 Parent

Fig. : Admin Roles

35 | P a g e
Fig . : Student Roles

Fig. : Professor roles

36 | P a g e
CHAPTER :- CONCLUSION & FUTURE SCOPE
Now this application is working as expected, I must say that It was great expreince while
developing it. It is different from common database management systems where different protals
offere different types of data managing s/w’s.

Conclusion

To conclude, Project Data Grid works like a component which can access all the databases and
picks up different functions. It overcomes the many limitations incorporated in the attendance.
Easy implementation Environment and Generate report flexibly

Scope for future development:

The project has a very vast scope in future. The project can be implemented on intranet in future.
Project can be updated in near future as and when requirement for the same arises, as it is very
flexible in terms of expansion. With the proposed software of database Space Manager ready and
fully functional the client is now able to manage and hence run the entire work in a much better,
accurate and error free manner. The following are the future scope for the project.

1. Discontinue of particular student eliminate potential attendance.

2. Bar code Reader based attendance system.
3. Individual Attendance system with photo using Student login

CHAPTER: - BIBLIOGRAPHY

ONLINE REFERENCE

1. www.codeproject.com
2. www.stackoverflow.com
3. www.tutorialspoint.com
4. www.w3schools.com
5. google.com for image detection js files.

37 | P a g e
38 | P a g e