Web Based Attendance Management System Paper

Project Report on
“Web Based Attendance Management System”
Submitted By:
MD. SHADEQUL ISLAM (ID - 1420118)
MD.SHOHEL RANA (ID -1420119)
KASHMERY AKATR (ID - 1420109)
Level-4, Semester- I
Course Code: CSE-401

Course Title: System Analysis & Design
Submitted To
Department Of Computer Science & Engineering (CSE)
Faculty of Computer Science & Engineering
Shahid Akbar Ali Science & Technology College (SASTC)
Baliadanggi , Thakurgaon
[Type text]
DEDICATED
TO
MY BELOVED PARENTS
&
HONORABLE SUPERVISOR
[Type text]
Online library management system
Justify
This is to certify that the Dissertation titled, Online library management system is a system
work done by MD.SHADEQUL ISLAM & MD.SOHEL RANA & KASHMERY AKTAR during
the academic session (2014-2018 ) is a partial fulfillment of CSE ( Level 4, Semester-I) has
been carried out under my direct supervision and guidance.
This report or a similar report on the topic has not been submitted for any other examination and
does not from a part of any other course undergone by the candidate.
------------------------ -------------------------------
Signature of Supervisor Signature of Co-Ordinator
Johurul Islam Bijoy
[Type text]
Justify
The satisfaction that accompanies that the successful completion of any task would
be incomplete without the mention of people whose ceaseless cooperation made it
possible, whose constant guidance and encouragement crown all efforts with success.
We are grateful to our project guide Johurul Islam sir for the guidance, inspiration and
constructive suggestions that helpful us in the preparation of this project.
We also thank to our Group who have helped in successful completion of the project.
We also specially thank to our co-supervisor for his Inspiration.
Abstract
[Type text]
Attendance is the act or fact of attending school or college. Also, attendance is
used to define the number of persons present on a particular day at school or
college .Over the years the manual attendance system has been carried across most
of educational institutions. To overcome the problem of manual attendance, now
we are using a web based attendance management system, which can be
implemented on any computer. This system is being developed to maintain easy
access of information from the database. The application makes use of MYSQL as
back end and HTML, CSS is used as front end. It tracks all the details of a student
attendance from day one to end of the course. The conventional method of taking
attendance by calling names or signing is very time consuming and insecure, hence
inefficient and some of the reasons are not reported to the parents or guardians
because the way of informing them is a traditional way and it takes a long process.
Here, we implement a system which is SMS broadcasting, which will help the
faculty to inform the parents about their student’s performance and attendance. The
final result of this project are very useful for the educational organizations to keep,
track and maintain the database of students.
Keywords — Web based attendance management system, Database, SMS

broadcast, Admin, User, Web Server.
[Type text]
TABLE OF CONTENTS
Chapter 1
INTRODUCTION
1.1 Introduction………………………………………………………………………
….
1.2 Problem
Statement…………………………………………………………………
1.3 Project aims and
Objectives………………………………………………………
1.4 Organization of this Project
Paper………………………………………………..
Chapter 2
Analysis of Project & Proposed System Solution
2.1 Introduction ………………………………………………………….

2.2 Present System
2.2.1 DFD for present system
2.2.2 Working Of The Present System…………………………….
2.2.3 Disadvantage of the present system…………………………..
[Type text]
2.3 Proposed System
2.3.1 Advantage of Proposed System …………………………………………
2.3.2 DFD for Proposed System ………………………………………..……..
2.3.2.1 0-Level DFD……………………………………………………
2.3.2.2 1-Level DFD…………………………………………………..
2.3.2.3 2-Level DFD…………………………………………………..
2.3.3 DFD For SMS Broadcast
2.4 Feasibility Study………………………………………………………………………

2.4.1 Technical Feasibility………………………………………………………….
2.4.2 Economic Feasibility………………………………………………………….
Chapter 3
DESIGN OF PROPOSED SYSTEM
3.1 Introduction……………………………………………………………………
3.1.1 System Design……………………………………………………………

3.1.1.1 Input Design………………………………………………………..
3.1.1.2 Output Design……………………………………………………..
3.1.1.3 Database Design…………………………………………………..
3.2 Flow Chart……………………………………………………………………. .
3.2.1 Module Diagram………………………………………………………
3.2.2 Use Case Diagram……………………………………………………
3.2.2.1 Use Case Diagram ADMIN………………………………….
[Type text]
3.2.2.2 Use Case Diagram User…………………………………….
3.2.3 Data Flow Diagram…………………………………………………….
3.3 E-R Diagram…………………………………………………………………...
Chapter 4
Implementation
4.1 Implementation Tools………………………………………………………..
4.2 Project Module………………………………………………………………

4.3 Module Description…………………………………………………………
4.4 Requirement Analysis………………………………………………………
4.4.1 Software Requirement………………………………………………..
4.4.2 Hardware Requirement……………………………………………..
4.5 Output Screen………………………………………………………………
Chapter 5
SYSTEM TESTING
5.1 Testing Procedure…………………………………………………………
5.2 Test Case………………………………………………………………………..
5.3 System Testing………………………………………………………………..
5.3.1 Unit Testing……………………………………………………………………
5.3.2 Integrated Testing……………………………………………………………
5.3.3 Validation Testing……………………………………………………………
5.3.4 Output Testing……………………………………………………………….
5.3.5 User Acceptance Testing…………………………………………………….
5.5 Maintenance………………………………………………………………………..
[Type text]
Chapter 6
CONCLUSION & FUTURE PLAN
6.1 Conclusion………………………………………………………………….
6.2 Future Scope………………………………………………………………..
REFERENCES
LIST OF THE FIGURES:
Fig N0-1.6 Organization of the project Papers
Fig N0- 2.2 DFD for Present System
Fig No-2.3.1 DFD of Proposed System
Fig No-3.2.1 Module Diagram
Fig No-3.2.2.1 Use Case Diagram Admin
[Type text]
Fig No-3.2.2.2 Use Case Diagram for Users
Fig No-3.2.3 Data Flow Diagram for Registration
Fig No-3.2.3 DFD of Login Database
Fig No-3.3 E-R Diagram For Library management system
CHAPTER 1
INTRODUCTION
[Type text]
1.1 INTRODUCTION
Web service for Student Attendance management is a simple application that runs
on the web. Attendance Management System (AMS) is software developed for
daily attendance of students. It 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. The traditional way of
taking attendance through the lecturers is a manually in a register book in which
they are used to do a manual calculation to maintain monthly attendance database
of the students. Such system takes so much time to generate record and many times
it creates an error. We are developed a system for managing daily student
attendance in schools, colleges and institutes for making the attendance system
more easier than before.
1.2 DRAWBACKS OF THE CURRENT EXISTING SYSTEM

The main drawback of manual system are
o Manually calculated maintenance of data.
o Suddenly searching for any type of related data is very difficult as well
as it create mess over there.
o It is not provide the accurate data of attendance of students in the
percentage calculation.
o Portability.
o Losing of data problem can be occurred easily.
o Manually fake data inserted through unknown recourses.
[Type text]
1.3 AIM AND OBJECTIVE
The main objectives of our work are:
o Data of student has been computerized using less manual effort.

o Parents get the SMS either he or she present or absent in the class.
o Easy to generate the report.
o Rapid access to any information regarding the students attendance.
1.4 Organization of this project paper

The rest of the report is divided into six parts such as Introduction, Analysis of
project& proposed system solution, Design of proposed system,
Implementation, System Testing and Future work and Conclusion .The
introduction Chapter list the need for building the system. This chapter
provides motivation, objective, project over overview, problem statement .The
chapter to provide analysis of proposed system. The chapter three provides
use cases to help the admin and students with their understanding, E-R
Diagram, DFD Diagram. It also gives a detailed explanation for each use case to
help with design and implementation and outlines .The constraints regarding
the software. The implementation chapter contains the detail design of the
system. The testing chapter also includes a detail test for each components as
well as the interaction of the class and it components with each other when
carrying out certain tasks, beside software Screen shots
Chapter 1
Introduction Part
Chapter 2
Analysis of Project &
proposed system
[Type text]
Chapter 3
Design of the Proposed System
Chapter 4
Implementation
Chapter 5
System Testing
Chapter 6
Conclusion & Future Plan
Fig 1.4 : Organization of the project papers documentation
[Type text]
Chapter 2
Analysis of Project & Proposed system solution
2.1 Introduction
Web based attendance management system is a project which aims in developing

[Type text]
a computerized system to maintain all the records of students. The “Web Based
attendance Management System” mainly focuses on basic operations in a school
or college like adding new students or teacher and updating new information,
searching specific student and calculated student average marks. This project has
many features which are generally not available in normal attendance
management systems like facility of student login and a facility of teacher login.
The teacher is able to generate different kinds of reports like lists of students,
their information and make report on the attendance of students. “Web Based
Attendance Management System” is designed to help teachers maintain
attendance.
2.2 Present System

2.2.1 DFD for Present System
Call though student ID / name

Teacher Student
With Pen &
Record
Book
Student response
Fig No 2.2.1 : present System Level -1 of the DFD
[Type text]
2.2.2 Working Of The Present System
In the present system all work is done on paper. The whole session attendance is
stored in register and at the end 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 60% attendance get a notice.
2.2.3 Disadvantage Of Present Working System
1. Not User Friendly: The existing system is not user friendly because
the retrieval of data is very slow and details not maintained efficiently.
2. Difficulty in report generating: We require more calculations to

generate the report so it is generated at the end of the session. And the
student not get a single chance to improve their attendance.
3. Manual control: All calculations to generate report is done manually

so there is greater chance of errors.
4. 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.
5. 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.3 Proposed System

[Type text]
The web based ATTENDANCE MANAGEMENT SYSTEM is a Web
application which avoids more manual hours in taking the attendance and
generating reports.
2.3.1 Advantage Of The Proposed System
Our proposed system has following advantages-
1. 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.
2. 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.
3. 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 become very
easy because there is no need to keep data on papers.
4. 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.2 DFD for Proposed system
2.3.2.1 0-Level DFD
SYSTEM OUTPUT
TEACHER/USER
[Type text]
DATABASE
Fig 2.3.2.1: 0-Level DFD
2.3.2.2 1-LEVEL DFD
Login Process Report

Generating
Attendance
Entry
Teacher Entry Student Entry
Fig 2.3.2.2 1-Level DFD
2.3.2.3 2-Level DFD
[Type text]
Fig 2.3.1.3 2-Level DFD
2.3.2 DFD for Describing the SMS Broadcast
Fig 2.3.2 Describing the SMS broadcast
[Type text]
2.4 Feasibility Study
Feasibility is the study of impact, which happens in the organization by the
development of the system. The feasibility study investigates the problem and the
information needs of the admin. It seeks to determine the resources required to
provide a Library systems solution, the cost and benefit of such a solution.
The goal of the feasibility study is to consider alternative information system

systems solution, evaluate the feasibility and propose the alternative most
suitable to the organization. The feasibility of a proposed solution is evaluated in
terms of its components. These components are –
2.4.1 Technical Feasibility:

The possibility of the organization can procure the necessary resource. This is
demonstrated if the needed hardware and software are available in the marketplace
or can be developed by the time of implementation to design Online Library
Management System.
2.4.2 Economic Feasibility:
Economic analysis could also be referred to as cost/benefit analysis. It is the most

frequently used method for evaluating the effectiveness of a new system. In
economic analysis the procedure is to determine the benefits and savings that are
expected from a candidate system and compare them with costs. If benefits
outweigh costs, then the decision is made to design and implement the system. An
entrepreneur must accurately weigh the cost versus benefits before taking an
action.
Possible questions raised in economic analysis are the system cost effective-
[Type text]
o The cost of doing full system study
o Estimated cost of hardware
o Estimated cost of software/software development
Chapter 3
Design of Proposed system
[Type text]
3.1 Introduction
Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.
Once the software requirements have been analyzed and specified the software design involves
three technical activities - design, coding, implementation and testing that are required to build
and verify the software.
The design activities are of main importance in this phase (3.1) because in this activity,
decisions ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decisions have the final bearing upon reliability and
maintainability of the system. Design is the only way to accurately translate the customer’s
requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a process
through which requirements are translated into a representation of software. Software design is
conducted in two steps. Preliminary design is concerned with the transformation of requirements
into data.
There are various kinds of methods in software design:
3.1.1 System Design

System design is an integral part in any working software worth implementing to design online
library management system. In this section we look into the data aspects and component
interface of the easy and secure online library management system. The online Library
management system has generally interacted with various entities from server and operating
system to internet service provider.
3.1.1.1 Input Design

Detail list about the Librarian & User Registration, Log in, Edit , update, delete , Log out
Insert the user information such as id, a password, Student Id, address, phone number, email
address. Book details information such as Categories, Title, Author, Publisher, quantity
3.1.1.2 Output Design

[Type text]
Produces form of book Resources in online.
The system shall now display if the book if exist or not and show where position of book in
library.
The system shall require a user to register, in order to carry out any transactions withit except for
checking the availability of book.
Ask the user to enter the following for Librarian
3.1.1.3 Database Design

Database Design are the storehouses of data used in the software system. In Online Library
management system The administrator and user information is stored separately into database.
The data is stored in the tables inside the database. Several Tables are created for the
manipulation of the data for the online system. Different tables are created to store different
categories of information in online library management system. In Library management system
two essential setting for a database are :
PRIMARY KEY: The field that is unique for all the record occurrences in online Library
management system such as Book id
FOREIGN KEY: The field use to set relation between tables. Normalization is a technique to
avoid redundancy in the table such as Book Name, Author, Publisher, Quantity, Address, Student
name Mobile Number Issue date, Return Book etc
3.2 FLOW CHART:
Flowchart show the flow of data from external entities into the system, and from one process to
another within the system . The flow show the flow of information from a source to its
destination. Data flow is represented by line, with arrowheads showing the direction of flow.
Information always flows to or from a process and may be written, verbal or electronic. Each
data flow may be represented by the process or data stores at its heat and tail, or by a description
of its contents.
[Type text]
3.2.1 Module Diagram:
Fig 3.2.1: Diagram for a Library database
3.2.2 Use Case Diagram:

The system’s use case diagram shows the admin and the Book detailed view of the system and
how the actor would interact with each other and with the system. The explanation for use case is
then provided bellow the system use case for the administrator and the user, helping the user to
understand who the actor areas are as well as and giving the description of each use case -
3.2.2.1 Use-Case Diagram: Admin
[Type text]
Administration section can manage the Homepage, Add Librarian, View Librarian, Edit Librarian,
Logout Librarian from the system.
HOME
Add Librarian
VIEW LIBRARIAN
Edit Librarian
Log Out
Fig No3.2.2.1: Use Case
[Type text]
3.2.2.2 Use- Case Diagram :

Members / Users section can have the Name, Address ,Email , Mobile num , ID items from the
system.
Name
Password
Email
Mobile Num
Address
User/Member
Fig 2: Use-Case Diagram for users
[Type text]
3.2.3 Data Flow Diagram

Data flow diagram shows the flow of information from a source to its description of the Online Library
system. Data flow is represented by a line, with arrowheads showing the direction of the flow.
Information always flows to or from a process and may be written, verbal. Each data flow is may be
referenced by the process or data stores at its head and tail, or by a description of its content.
DB
Check
User Enter Details Information
Log in
FIG 3.2.3: DFD of Registration
[Type text]
3.2.3 DFD System Log in Database
DB
Enter User Name & password Check Information

Member
Home
Fig 3.2.3: DFD Of Log in database
[Type text]
3.3 E-R Diagram:
[Type text]
Chapter 4
Implementation
4.1 Implementation tools:

The implementation phase is less creative than system design. It is primarily concerned with user training
dataset .Online library management system has two part one is admin side another is User side .If user
want to Issue any Book from the library he must need to make registration. Then Librarian keep details of
those members such as User information, Issue book date, User address etc
[Type text]
4.2 Project Modules:
The proposed system has the following techniques
Login component
1. Administrator (Admin of the Management system)
2. Librarian
3. User
Administrator Component
1. Administrator
Librarian Manager Component
1. Librarian Manager
Student Component
1. Books Details
2. Issue Details
4.3 Module Description:

User: Using login id and password user can the use Library online where users can
search for books and renewal books online. They can recommend for new books by just sending
messages to the librarian from anywhere in the college. They can view the issue and return dates
[Type text]
of any book and due they have to pay.
Registration: In the Registration module, user has to register himself by supplying his
personal information which gets store in data base which are using as backend. By registering
himself user will get his login id and Password so that he can access Library online. Separate
Register form should be designed for separate user .
Librarian Side : Librarian is a person who manages the Library. Librarian has the permission
that he can access the database. There are some tasks which are performed by the Librarian like:
 Addition of a new books.
 Modification of the books.
 Deletion of the books.
 Searching of the books.
 Managing Users
Member side :
Member is the user who can issue book from the online library
 Registration
 Login
 Search Book
 Send Order
 Add to chart
 Log out
4.4 Requirement Analysis

4.4.1 Software Requirement:
Operating System - WINDOWS7, WINDOWS10
MEMORY - 1GB RAM OR MORE
BROWSER -Mozilla Firefox, Opera, Internet Browser
DATABASE - MY SQL Connector
Server - Tomcat 9
[Type text]
Product Version - NetBeans 8.2
4.4.2 Hardware Requirement:

PROCESSOR - INTEL CORE PROCESSOR OR BETTER PERFORMANCE
Minimum 512MB RAM
40GB Hard disk for storage
4.5 Screen Shots
Home Page:
[Type text]
Librarian Page:
[Type text]
BOOKS FORM :
VIEW BOOK:
[Type text]
Chapter 5
System Testing
[Type text]
5.1 Testing Procedure:
After completing every part of the software there is the need for software testing to prove that the
module are functioning properly or not and it fulfills all requirement of the user. For this, the
programmer use various type of software testing techniques and strategies. Software can be
tested in one of two ways -:
 B l a c k - B o x Te s t i n g : K n o w i n g t h e s p e c i f i e d f u n c t i o n t h a t a
p r o d u c t h a s b e e n designed to perform, tests can be conducted that
demonstrate each function is fully operational while at the same time searching for
errors in each function.
 W h i t e – B o x Te s t i n g : K n o w i n g t h e i n t e r n a l w o r k i n g o f
p r o d u c t , t e s t s c a n b e conducted to ensure that “all gears mesh”, that is
internal operations are performed according to specification and internal component
have been adequately exercised.
5.2 TEST CASES:

The Test case for online library management system is a critical element of software quality
assurance and represents the ultimate review of specification, Design and coding. Errors are
founded and corrected by using the following Testing cases and Corrections are recorded for
future references. Thus Series of testing is performed on the system before it is already for
implementation
5.3 System Testing:

The Testing phase involves the testing of system using various tests of data. After preparation the
Test data, the system under study is tested.
The Various types of Testing on the system are –
 Unit Testing
 Integrated Testing
 Validation Testing
 Output Testing
 User Acceptance Testing

[Type text]
5.3.1 Unit Testing:
Unit Testing that focuses on the verification effort on the smallest unit of software design module.
Using the Unit testing plans, This testing is carried out during the programming itself. All independent
paths were exercised to ensure that all statements in the module are executed at least once and all
error-handling paths are tested.
At the end of these testing phases is unit is found to be working satisfactorily as regarded to the
expected out from the module
5.3.2 Integrated Testing
Integration testing is a symmetric technique for constructing tests to uncover errors associated with the
interface. All modules are combined in this testing step. Then the inter program is tested as a whole.
5.3.3 Validation Testing
Validation testing can be defined in many ways but a simple definition is that validation succeed when
the software function in manner that is reasonably expected by the consumer .In this application
validation test can be conducted one of two condition exists
The function or performance characteristics confirm to specification that are accepted.
A validation from specification is uncovered and a deficiency created
5.4.4Output Testing
After performing the validation testing the next step is output testing of the proposed system,
since a system is useful it does not produce the required output in the specific format required by
them tests the output generator displayed on the system under consideration. Here the output is
considered in two ways ; one is on screen and the other is printed format. The output format on
the screen is found to be correct as the format is design in the system design phase according to
the user needs. As far as hardcopies are
Are considered is goes in terms with the user requirement. Hence output testing does not result
any correction in the system.
5.4.5 Use Acceptance Testing
[Type text]
User acceptance of the system is a key factor for success of any system. The
system under consideration is tested for user acceptance by constantly
keeping in touch with prospective system and user at the time of developing
and making changes whenever required.
[Type text]
Chapter 6
Conclusion & Future plan
6.1 CONCLUSION:
[Type text]
The package was designed in such a way that future modifications can be done easily. The
following conclusions can be deduced from the development of the project.
 Library Management System of the entire system improves the efficiency.

 It provides a friendly graphical user interface which proves to be better when compared to the
existing system.
 It gives appropriate access to the authorized users depending on their permissions.
 It effectively overcomes the delay in communications.
 Updating of information becomes so easier.
 System security, data security and reliability are the striking features.
 The System has adequate scope for modification in future if it is necessary.
6.2 FUTURE SCOPE
This application can be easily implemented under various situations. We can add
new features as and when we require. Reusability is possible as and when require in
this application. There is flexibility in all the modules.
SOFTWARE SCOPE:
Extensibility: This software is extendable in ways that its original developers may not expect.
The following principles enhances extensibility like hide data structure, avoid traversing multiple
links or methods, avoid case statements on object type and distinguish public and private
operations.
Reusability: Reusability is possible as and when require in this application. We can update it
next version. Reusable software reduces design, coding and testing cost by amortizing effort over
several designs. Reducing the amount of code also simplifies understanding, which increases the
likelihood that the code is correct. We follow up both types of reusability: Sharing of newly
written code within a project and reuse of previously written code on new projects.
[Type text]
Understandability: A method is understandable if someone other than the creator of the method
can understand the code. We use the method, which small and coherent helps to accomplish this.
Cost-effectiveness: Its cost is under the budget and make within given time period. It is
desirable to aim for a system with a minimum cost subject to the condition that it must satisfy the
entire requirement. Scope of this document is to put down the requirements, clearly identifying
the information needed by the user, the source of the information and outputs expected from the
system.
[Type text]
REFFERENCES:
[Type text]

Web Based Attendance Management System Paper

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Web Based Attendance Management System Paper

Hochgeladen von

Copyright:

Verfügbare Formate

Project Report on

“Web Based Attendance Management System”

MD.SHOHEL RANA (ID -1420119)

KASHMERY AKATR (ID - 1420109)

Course Code: CSE-401

Shahid Akbar Ali Science & Technology College (SASTC)

Signature of Supervisor Signature of Co-Ordinator

Johurul Islam Bijoy

Online library management system

We also specially thank to our co-supervisor for his Inspiration.

Keywords — Web based attendance management system, Database, SMS

Analysis of Project & Proposed System Solution

2.1 Introduction ………………………………………………………….

2.4 Feasibility Study………………………………………………………………………

Online library management system

DESIGN OF PROPOSED SYSTEM

3.1.1 System Design……………………………………………………………

3.3 E-R Diagram…………………………………………………………………...

4.2 Project Module………………………………………………………………

Online library management system

Online library management system

LIST OF THE FIGURES:

Fig N0-1.6 Organization of the project Papers

Fig N0- 2.2 DFD for Present System

Fig No-2.3.1 DFD of Proposed System

Fig No-3.2.1 Module Diagram

Fig No-3.2.2.1 Use Case Diagram Admin

Fig No-3.2.3 Data Flow Diagram for Registration

Fig No-3.2.3 DFD of Login Database

Fig No-3.3 E-R Diagram For Library management system

Online library management system

1.2 DRAWBACKS OF THE CURRENT EXISTING SYSTEM

o Data of student has been computerized using less manual effort.

1.4 Organization of this project paper

Analysis of Project &

Design of the Proposed System

Conclusion & Future Plan

Fig 1.4 : Organization of the project papers documentation

Online library management system

Online library management system

Web based attendance management system is a project which aims in developing

2.2 Present System

Call though student ID / name

Fig No 2.2.1 : present System Level -1 of the DFD

Online library management system

2.2.3 Disadvantage Of Present Working System

2. Difficulty in report generating: We require more calculations to

3. Manual control: All calculations to generate report is done manually

4. Lots of paperwork: Existing system requires lot of paper work. Loss

5. Time consuming: Every work is done manually so we cannot

2.3 Proposed System

2.3.1 Advantage Of The Proposed System

Our proposed system has following advantages-

2. Reports are easily generated: Reports can be easily generated in the

4. Computer operator control: Computer operator control will be there

2.3.2 DFD for Proposed system

2.3.2.1 0-Level DFD

Fig 2.3.2.1: 0-Level DFD

2.3.2.2 1-LEVEL DFD

Login Process Report

Fig 2.3.2.2 1-Level DFD

2.3.2.3 2-Level DFD

2.3.2 DFD for Describing the SMS Broadcast