E Library

www.freestudentprojects.comwww.sourcecodefiles.
com
www.studentprojectcode.com
CONTENTS
Chapter 1: Synopsis
(1-8)
1.1
1.2
1.3
1.4
1.5
1.6
1.7
Title of the project

Members name with reg.no
External guide name
Objectives of the project
Problem statement
Project category
Hardware and software requirements
1.7.1 Software specifications
1.7.2 Hardware specifications
1.8 Methodology(including a summary of the project)
1.9 Module description
1.10 What contribution would the project make?
1.11 Limitations
1.12 Future scope of the project
Chapter 2: System Requirement and Specifications

2.1 Introductions
2.1.1 Purpose
2.1.2 Scope
2.1.3 Definition, Acronyms, Abbreviations
2.1.4 References
2.1.5 Overview
2.2 Overall Descriptions
2.2.1 Product Perspective
2.2.2 Product Features
2.2.3 User classes and Characteristics
2.2.4 Assumptions and Dependencies
2.3 Specific Requirements
2.3.1 External Interface Requirements
2.3.1.1 User Interface
2.3.1.2 Hardware Interface
2.3.1.3 Software Interface
2.3.2 Functional Requirements
2.3.2.1 Book Module
2.3.2.2 Student Account Module
2.3.2.3 Book Issue Module
2.3.2.4 Return Book Module
2.3.2.5 Student History
2.3.3 Other Non-functional Requirements
(9-14)
www.freestudentprojects.comwww.sourcecodefiles.com
2.3.3.1 Performance Requirements

2.3.3.2 Safety Requirements
2.3.3.3 Security Requirements
2.3.4 Software Quality Attributes
2.3.4.1 Reliability
2.3.4.2 Availability
2.3.4.3 Security
2.3.4.4 Maintainability
2.3.4.5 Portability
Chapter 3: System Design
( 15-24)
___________________________________________________________
3.1 Introduction
3.2 Applicable Documents
3.3 Functional Decomposition
3.4 Description of the Document
3.5 Context Flow Daigram(CFD)
3.6 Data Flow Diagram(DFD)
3.7 Description of the Module
3.7.1 Login
3.7.2 Book
3.7.3 Student Account
3.7.4 Book Request
3.7.5 Book Issue
3.7.6 Book Return
3.7.7 History
3.7.8 Registration
3.7.8 Penalty settings
Chapter 4: Database Design
( 25-34)
___________________________________________________________
4.1 Introduction
4.2 Database Description
4.3 Description of Table and Fields
4.3.1 Admin_reg
4.3.2 Book Table
4.3.3 Book Return Table
4.3.4 Book Category table
4.3.5 Book_issue Table
4.3.6 Course Table
4.3.7 Penalty Table
4.3.8 Penalty Setting
4.3.9 Staff Table
4.3.10 Student Table
4.4 E-R Diagram
4.4.1 Entity
4.4.2 Relationships
4.4.3 Attributes
Chapter 5: Detailed Design
(35-39)
___________________________________________________________
5.1 Introduction
5.2 Applicable Documents

5.3 Structure of Software Package
5.4 Modular Decomposition of Components
5.4.1 Log in Table
5.4.1.1 Design Assumption, if any
5.4.1.2 Identification of Modules
5.4.1.3 Structure Chart
5.4.1.4 Data Structure shared among Modules
5.4.1.5 Admin Module
5.4.1.6 Design Assumption
5.4.1.7 Identification of Modules
5.4.1.8 Structure Chart
5.4.1.9 Data Structure shared among Modules
5.5 Module Design of Admin
5.5.1 Staff Module
5.5.1.1 Inputs
5.5.1.2 Procedural Details
5.5.1.3 File I/O Interfaces
5.5.2 Student Module
5.5.2.1 Inputs
5.5.2 Book Module
5.5.3.1 Inputs
5.6 User Module
5.6.1 Identification of Modules
5.6.2 Structure chart
Chapter 6: Coding and Implementation
(40-95)
___________________________________________________________
6.1 Introduction
6.2 Coding Standards
6.2.1 Code Review and Walkthroughs
Chapter 7: Testing
(96-112)
___________________________________________________________
7.1 Introduction
7.2 Testing Objectives
7.3 Unit Testing
7.4 White Box Testing
7.5 Black Box Testing
7.6 Unit Test Cases
Chapter 8: Screenshots
(113-121)
___________________________________________________________
Chapter 9: Conclusion
122
___________________________________________________________
Conclusion
Chapter 10: Future Enhancement
123
___________________________________________________________
Chapter 11: Bibliography
124
___________________________________________________________
SYNOPSIS
1. SYNOPSIS
1.1 Title of the project
E- Library Management System
1.3Objective of the project

E-Library Management System
will deal in all the requirements
needed for managing libraries.

It will deal with the process of maintaining data about the books
and many other things as well as transactions, which are taking
place in the library with respect to the issue, return and renewal
of the books.
It helps the administrator to accomplish his tasks at ease.
It lets the users sign-up to the library initially and then sign-in
every time they want to find some item in the library.

The user can also maintain and edit his profile details. A user can
sign-in and search for items, borrow items if they are present in
the library.
All details of the users and library information are stored in the
database. The
user need not visit the library every time to find
an item; instead, he/she can search items from his/her own

PC/laptop
1.5 Problem statement
Proposed System:
E-Library Management system is used to provide a medium for the libraries
to computerize their entire functioning and would contribute as a first step in
digitalizing their libraries. Libraries had their entire records on paper which again
required maintenance and the problem of finding relevant information proved to
be a difficult task. Even if the required information was found it was usually at
cost of much valuable time. E-Library Management would not only simplify this
process but also speedup the entire functioning of the library. It will also
contribute towards increasing the efficiency of the libraries a whole, right from the
data entry to maintaining the historical records. One major purpose is to provide
user or the library members the opportunity to not only search through the books
online but to reserve books that are issued by other users and also request newer
books
1.6 Project category
Web Application.
1.7 Languages used

17.1 Front -end
Apache Web Server
Apache is generally recognized as the world's most popular Web server
(HTTP server). Originally designed for UNIX environments, the Apache Web
server has been ported to Windows and other network operating systems. The
Apache Web server provides a full range of Web server features, including CGI,
SSL, and virtual domains. Apache also supports plug-in modules for extensibility.
Apache is free software, distributed by the Apache Software Foundation that
promotes various free and open source advanced Web technologies.
Apache is developed and maintained by an open community of developers
under the auspices of the Apache Software Foundation. The application is
available for a wide variety of operating systems, including UNIX, GNU,
FreeBSD, Linux, Solaris, Novell NetWare, AmigaOS, Mac OS X, Microsoft
Windows, OS/2, TPF, and eComStation. Released under the Apache License,
Apache is characterized as open-source software.
XAMPP is a free and open source cross-platform server solution package,

consisting mainly of the Apache HTTP Server, MySQL database, and interpreters
for scripts written in the PHP and Perl programming languages. XAMPP's name
is an acronym for- X (to be read as "cross", meaning cross-platform),Apache
HTTP Server, MySQL, PHP
The program is released under the terms of the GNU General Public
License and acts as a free web server capable of serving dynamic pages. XAMPP
is available for Microsoft Windows, Linux, Solaris, and Mac OS X, and is mainly
used for web development projects. This software is useful while you are creating
dynamic web pages using programming languages like PHP, JSP, and Servlets.
PHP
PHP is a server-side, cross-platform, HTML-embedded scripting language.
PHP (recursive acronym for PHP: Hypertext Pre-processor) is a widely-used open
source general-purpose scripting language that is especially suited for web
development and can be embedded into HTML.
Currently there are over half a million domains running PHP. Much of PHPs
syntax is borrowed from C, Java and Pearl with a couple of unique PHP-specific
features thrown in. The goal of the language is to allow web developers to write
dynamically generated pages quickly. PHP eliminates the need for numerous
small CGI programs by allowing you to place simple scripts directly in your
HTML files. It also makes it easier to manage large web sites by placing all
components of a web page in a single html file.
PHP is a general-purpose scripting language originally designed for web
development to produce dynamic web pages. For this purpose, PHP code is
embedded into the HTML source document and interpreted by a web server with
a PHP processor module, which generates the web page document. It also has
evolved to include a command-line interface capability and can be used in
standalone graphical applications. PHP can be deployed on most web servers and
as a standalone interpreter, on almost every Operating system and platform.
One of the strongest and most significant features in PHP is its support for a wide
range of databases. Writing a database-enabled web page is incredibly simple
using one of the database specific extensions (e.g., for MySQL), or using an
abstraction layer like PDO, or connect to any database supporting the Open
Database Connection standard via the ODBC extension. Other databases may
utilize URL or sockets, like Couch DB.
JavaScript
JavaScript (JS) is a dynamic computer programming language. It is most
commonly used as part of web browsers, whose implementations allow clientside scripts to interact with the user, control the browser, communicate
asynchronously, and alter the document content that is displayed. It is also being
used in server-side programming, game development and the creation of desktop
and mobile applications.
JavaScript is a prototype-based scripting language with dynamic typing and has
first-class functions. Its syntax was influenced by C. JavaScript copies many
names and naming conventions from Java, but the two languages are otherwise
unrelated and have very different semantics. The key design principles within
JavaScript are taken from the self and Scheme programming languages. It is
a multi-paradigm language, supporting object-oriented, imperative, and functional
programming styles.
HTML
HTML or Hypertext Mark-up Language is the main language for creating web
pages and other information that can be displayed in a web browser.
HTML is written in the form of HTML elements consisting of tags enclosed in
angle (like <html>), within the web page content. HTML tags most commonly
come in pairs like <h1> and</h1>, although some tags represent empty
elements and so are unpaired, for example <img>. The first tag in a pair is
the start tag, and the second tag is the end tag (they are also called opening
tags and closing tags). In between these tags web designers can add text, further
tags, comments and other types of text-based content.
The purpose of a web browser is to read HTML documents and compose

them into visible or audible web pages. The browser does not display the HTML
tags, but uses the tags to interpret the content of the page.
AJAX
Ajax is a group of interrelated web development techniques used on
the side to create asynchronous web applications. With Ajax, web applications can
send data to, and retrieve data from, a server asynchronously (in the background)
without interfering with the display and behaviour of the existing page. Data can
be retrieved using the XML Http Request object. Despite the name, the use of
XML is not required, and the requests do not need to be asynchronous.
Ajax is not a single technology, but a group of technologies. HTML and CSS can
be used in combination to mark up and style information. The DOM is accessed
with JavaScript to dynamically display, and allow the user to interact with, the
information presented. JavaScript and the XMLHttpRequest object provide a
method for exchanging data asynchronously between browser and server to avoid
full page reloads.
1.7.2 Back end

MySQL
MySQL is a Relational Database Management System (RDBMS) that runs as a
server providing multi-user access to a number of databases. The SQL phrase stands
for Structured Query Language. MySQL is a popular choice of database for use in
web applications, and is a central component of the widely used LAMP open source
web application software stackLAMP is an acronym for "Linux, Apache,
MySQL, Perl/PHP/Python". MySQL is written in C and C++. Its SQL parser is
written in yacc. Applications which use MySQL databases include: Joomla,
WordPress, Drupal and other software built on the LAMP software stack.
MySQL works on many different system platforms, including BSDi, FreeBSD,

i5/OS, Linux, Mac OS X, Microsoft Windows, NetBSD, Novell NetWare,
OpenBSD, OpenSolaris, Solaris, Symbianetc. Many programming languages with
language-specific APIs include libraries for accessing MySQL databases. MySQL is
primarily an RDBMS and ships with no GUI tools to administer MySQL databases
or manage data contained within the databases. Users may use the included
command line tools, or download MySQL front-ends from various parties that have
developed desktop software and web applications to manage MySQL databases,
build database structures, and work with data records.
MySQL is the world's most popular open source database software, with over 100
million copies of its software downloaded or distributed throughout its history. With
its superior speed, reliability, and ease of use, MySQL has become the preferred
choice for Web, Web 2.0, SaaS, ISV, Telecom companies and forward-thinking
corporate IT Managers because it eliminates the major problems associated with
downtime, maintenance and administration for modern, online applications.
1.7 Hardware and Software requirements

1.7.1 Software specifications:
Technology Implemented : Apache Server
Language Used
: PHP 5.3
Database
: My SQL 5.5
User Interface Design
: HTML, AJAX
Web Browser
Software
: Mozilla, Google Chrome, IE8
: XAMPP Server
1.7.2 Hardware requirements:
Operating System
40 GB hard disk and above

1 GB RAM and above
Peripheral devices
: Windows XP/Windows 7 or above
1.8 Methodology (including a summary of the project)

E-Library Management System is a web based application. Here the student
having an account can request the book and the librarian can issue the book based on
his request. If the student does not return the book on time fine will be added. Student
can search for other books or can view the details. If the book is not available the
student can reserve the book for them.
1.9 Module Description

Books: This module consist the details of the books available in library and their
categories. It also contains the list of books in each category and their details.
Manage Books: In this module you can check which book is available and issued.
Student Account: To issue a book from the library, one should have an account in
the library. The registration contains all the details about the student like
registration number, name, address, contact number etc.
Book Request: This module is used by the student to request a book from the
library. The search can be performed by using name of the book, author name, and
subject name.
Issue of books: This module is used by the librarian to issue a book based on the
request made by the student.
Renewal of books: This module is used by the admin to renew
the book. If the book is already reserved for others then that book
should not be renewed
Returning Books: In this module the librarian maintains the details of
the books returned by the student, which also includes the fine details,
damage book details, lost book details.
Reports: This module includes the details about the issued books, returned books,
student reports, fine reports, or details of the book which are not returned.
1.10 What contribution would the project make?

The main objective of the proposed system is to help the user. The system can
be hand to the user in the following reasons:
To provide multi user login facility and a user friendly system.
To manage the details about the previous issued books, requested books and returned
books etc.
To generate reports based on the records available.
Reduce the manual work and time consumption

E-Online Library Management Software can be applied to large databases with
more information. Hence it reduces time consumption and speed up the work
1.11 Limitations
Internet connection is required.
If the server is down it takes time for loading.
1.12 Future scope of the project
Book reading facility can be provided through on-line
SOFTWARE
REQUIREMENT
SPECIFICATION
2. SOFTWARE REQUIREMENTS SPECIFICATION

2.1 Introduction
SRS is a complete description of the behaviour of a system to be developed. It
includes a set of user cases that describe all the interactions the users will have with the
software. It deals with the requirements of the proposed system. It describes what the
proposed System should do without describing how the System will do it. An SRS provides
a reference for the validation of the final product i.e.; the SRS helps the client to determine
if the System meets the requirements.
2.1.1 Purpose
This document is meant to serve as a guide to the developer on one hand and a software
validation document for the client on the other. The purpose of this document is to specify
all the information required to design, develop and test the software. This to ensure that the
person reading the document understands what he or she is looking at. It provides the
visibility in the design and provides information needed for software support.
2.1.2 Scope
The scope of this project includes our group of developers assisted by our customer.
The scope thus far has been the completion of the basic interfaces that will be used to build
the system. The database used, has been set up and given the necessary permissions. This
Application works in Multiple PCs installed on multiple Computers by sharing same
database by which users of different departments can use it sitting at different locations
simultaneously
2.1.3 Definitions, Acronyms, Abbreviations
E-LMS
Electronic Library Management
SRS
Software Requirements specifications
DFD
E-R
RAM
DBMS
Data Flow Diagram

Entity Relationship diagram
Random Access Memory
Data Base Management System
2.1.4 References
Software Engineering Book- Ian Sommerville
An Integrated Approach to Software Engineering by Pankaj Jalote
2.1.5 Overview
The SRS is organized into two main sections. The first is The Overall Description
and the second is the Specific Requirements. The Overall Description will describe the
requirements of the library management system from a general high level perspective.
The Specific Requirements section will describe in detail the requirements of the
system.
The primary purpose of this application is to implement the above stated

functionality. It will be having user friendly GUIs that will guide the user to easily
achieve the same.
2.2 overall descriptions

This section of the SRS describes all general factors of the product and its
requirements.
2.2.1 Product Perspective:
This section aims to describe both the existing and the proposed systems, with
respect to why the proposed system is needed.
After understanding the existing manual system and understanding the need for
developing a new system, library staffs have been consulted for the collection of
requirements. The data needed for the study has been collected from the library.
The computerization of this system would reduce the paper works. The system helps
the user to see any documents, tasks, activities with details at the click of a button.
The record data is maintained and backed up such a way that data is not loss. The
speed of the system could also be increased.
E-Library Management System is a online application that supports multi user. It is

mainly used for maintaining the book details, details about issued book, details about
returned books, details about lost or damaged books, fine statements, student login
details, etc.
2.2.2 Product Features

The major features of the E-Library Management System are organized according to
its main components. The features of the E-Library Management System are as follows:
Keeps the track of the book details.
Student history.
Fine Statement.
Status of the book.
Up-to-date Reports are generated.
Reduces manual work and time consumption
Provides Data security
No Data loss and Misuse of data is avoided.
2.2.3 User classes and Characteristics

General users with basic computer skill can use this software This software can be
used by librarian, library staffs, and only registered students.
User friendly
Very easy to use and understand
Trained to use the software
2. 2.4 Assumption and dependencies

The users should have basic knowledge of computers. They must be trained well to
handle the features provided by this system. Some of the details are required to be
entered by the user and may not be generated automatically. The project depends on
the users ability to understand the features of the Library Management System and
able to use to the best of his/her use.
2. 3 Specific Requirements
2.3.1 External Interface Requirements
2.3.1.1 User Interface
The user of the product will get very user friendly forms which will be very easy to
work with.
2.3.1.2 Hardware Interface
Hardware requirements are:
Processor: Intel dual core or above
Processor Speed: 1.0 GHZ or above
RAM: 1 GB RAM or above
Hard Disk: 20 GB hard disk or above
2.3.1.3 Software Interface

Software Requirements are:
Technology Implemented
: Apache Server
Language Used
PHP
Database
MySQL
User Interface Design
: HTML, CSS
Web Browser
: Google Chrome,
Operating system
:Windows xp /windows 7 and above
2.3.2 Functional Requirements:

2. 3.2.1 Book Module:
Introduction: This module has the details regarding the books.
Input: Entering the book number, ISBN, book title, author, publisher, and
category.
Processing: Book information will be stored.
Output: Proper data will be stored as well as can be retrieved.
2.3.2.2 Student Account Module:
Introduction: To access the library management application student have to

register. The registration contains all the details about the student. One should
have an account in the library.
Input: Entering the registration number, name, address, contact number etc..
Processing: Student details will be stored.
2.3.2.3 Book Issue Module:
Introduction: This module is used by the librarian to issue a book to the

student.
Input: Librarian enters the book details, student details, issue date, due date.
Processing: Librarian checks the student history and issues the book to the
student.
2.3.2.4 Return Book Module:
Introduction: In this module the librarian maintains the details of the books
returned by the student, which also includes the fine details, damage book
details, lost book details.
Input: Librarian enters the book details, student details, return date, fine
details.
Processing: Book status is updated.
2.3.2.4 Student History:
Introduction: In this module both the student and librarian can view the
details about the previous issued books, requested books and returned books
etc.
Input: Entering the student register umber.
Processing: Student histories will be generated.
Output: Reports are generated
2.4 Other non-functional Requirements

2.4.1 Performance Requirements
The system is supposed to be having good memory space and a Bigger Ram
above 512 MB preferably.
2.4.2 Safety Requirements
To avoid data loss backups can be done regularly.
There should be Antivirus to protect the software.
2.4.3 Security Requirements
Authenticated users are able to access the system.
2.4.4 Software Quality Attributes

2.4.4.1 Reliability:
Specify the factors required to establish the required reliability of the software
system at time of delivery.
2.4.4.2 Availability:
The system shall be available during the operating hours of library.
2.4.4.3 Security:
Administrators will be able to log in to the Library management System.

Administrator will provide the permissions to Access the Sub Functions
for the Users.
2.4.4.4 Maintainability:
This system can update and add new functionality whenever required
because it is designed in a modular way.
2.4.4.5 Portability:
The system can be portable to another machine which has the required
software installed.
SYSTEM
DESIGN
3. SYSTEM DESIGN
3.1 Introduction:
The purpose of the design phase is to a solution of the problem specified in the
requirements document. This is the first step in moving from the problem domain to the
solution domain. The design of a system is perhaps the most critical factor affecting the
quality of software; it has a major impact on the later phases is the design document. This
document is similar to a blue print or a plan for the solution and is used later during
implementation, testing and maintenance.
The design activity is often divided into separate phases System design
Detailed design
System design is sometimes also called top level design. System design aims to
identify the modules that should be in the system, the specification of these modules, and
how they interact with each other to produce the desired result. At the end of the system
design all the major data structures, file formats, output formats and the major modules in
the system and their specifications are decided.
3.2 APPLICABLE DOCUMENTS:
SRS
System Design
Database Design
The system design document refers to the entire requirements

specified in the requirement document.
The detailed design document follows all designs approach followed
in the system design document.
The detailed design document uses the entire database designed
document.
3.3 FUNCTIONAL DECOMPOSITION:

The software package contains of following functional components:
1. Login
2. Admin
Staff
Student
Books
Configurations
Change password
3. Student
Search Books
Request Books
View History
4. Staff
Student
Books
Configurations
Change password
3.3 DESCRIPTION OF THE DOCUMENT:

The notations used in flow diagram are:
The bubble represents a process or transformation that is
applied to the data which changes in some way. Each bubble
is assigned a number.
This rectangle is called an entity which represents a

producer or a customer of the information.
The arrow represents the data flow. All arrows in the data
flow diagrams are labelled. The arrow head indicates the
dictionary of data flow
Represents a repository of data that is to be stored for use

by one or more processes.
3.4 CONTEXT FLOW DIAGRAM (CFD):

A context flow diagram is a top level (also known as level 0) data flow diagram. It only
contains one process node (process 0) that generalizes the function of the entire system in
relationship to external entities. In context diagram the entire system is treated as a single
process and all its inputs, outputs, sinks and sources are identified and shown.
The environment in which the software used is specified in this picture. CFD shows
external entity action on software in a single process.
3.5 DATA FLOW DIAGRAM (DFD):

A data flow diagram is a graphical representation of the flow of data through an
information system. A dataflow diagram can also be used for the visualization of data
processing. It is common practice for a designer to draw a context level DFD first which
shows the interaction between the system and outside entities. This context-level DFD is
then exploded to show more detail of the system being modelled.
A DFD represents flow of data through a system. Data flow diagrams are commonly
used during problem analysis. It views a system as a function that transforms the input into
desired output. A DFD shows movement of data through the different transformation or
processes in the system.
Figure a: Context flow diagram
LEVEL 1 FOR ADMIN
LEVEL 1 FOR MEMBER
LEVEL 2 FOR MEMBER
LEVEL 2 FOR ADMIN
LEVEL 2 FOR ADMIN
3.6 DESCRIPTION OF THE MODULE

3.6.1. Login
Input
: User name and password
Process definition
: If user name and password is correct then it goes to

the appropriate main Page otherwise display
Error message.
Output
: If valid then user can access further features else an error

message will be displayed.
3.6.2. Book:
Input
: Entering the book details
Process definition
: Book details are stored
Output
: Proper data is retrieved and updated
3.6.3. Student Account:

Input
: Entering the student details
Process definition
: Student details are stored
Output
: Proper data is retrieved and updated
3.6.4. Book Request:

Input
:Register no, book title, author.
Process definition
: If data is correct then it goes to the appropriate Page

Otherwise display error message
Output
: Allows user to request for book
3.6.5. Book Issue:

Input
:Student details, book details.
Process definition
:If data is correct then book is issued to the student.
Output
: Requested book issued to student
3.6.6. Book Return:

Input
:Entering student detail, book details.
Process definition

otherwise display error message.
Output
:Allow user to return book
3.6.7. History:
Input
:Entering username and password.
Process definition

otherwise display error message
Output
: Display book issue history of the user
3.6.8 Penalty settings:

Input
Process definition
: Enter student details, issue date, return date.

: all data will be stored
Output
:Penalty will be calculated if the return date is exceeded.
DATABASE
DESIGN
4. DATABASE DESIGN
4.1 Introduction
This document describes the tables that are used to design the software; its
attributes, data type, constraints and relationship among table are defined through
Entity Relationship Diagram(ER-Diagram).
4.2 Database description

The database is a collection of inter-related data. Relational database stores
data in table or relations. The data stored in relation are arranged in tuple's or
records. Each record contains set of attributes or fields. The database description
describes the entire database used in the application to store all records.
4.3 Table relation
4.4 Description of table and fields

.
4.4.1 admin_reg
Description:(admin registration): This table stores Username and password as
administrations login form.
NAME
TYPE
SIZE
DESCRIPTION
admin_name
varchar
20
Admin name
user_name
varchar
20
User name
Password
varchar
20
Password
Gender
varchar
10
Gender
designation
varchar
20
Designation
Email
varchar
30
Email id
Phoneno
int
11
Phone number
4.4.2 book table:

Description:This table stores book details.
NAME
TYPE
SIZE
DESCRIPTION
bookid
bookcat_id
Int
Int
10
10
Book id
Book category id
bookname
varchar
20
Book name
isbn
Varchar
20
isbn number
title
Varchar
20
Title of the book
author
Varchar
20
Author
publisher
Varchar
20
Publisher
yr_of_publ
Varchar
20
Year of publications
edition
Varchar
20
Edition
book_code
varchar
20
Book code
course_id
Int
20
Course id
cost
Double
noofcopies
Int
dateofentry
Date
Status
varchar
Cost
11
Number of copies
Date of entry
10
Status
4.3.3 Book return Table:

Description: This table stores information about Returned book details.
NAME
TYPE
SIZE
DESCRIPTION
returnid
Int
10
Return id
issueid
Int
10
Issue id
userid
Int
10
User id
returndate
Date
status
varchar
Return date
10
status
4.3.4 book_category table:

Decription: This table stores information about Book Category.
NAME
TYPE
SIZE
DECRIPTION
bookcat_id
int
11
Book category id
bookcat_name
varchar
20
Book category name
Status
varchar
20
Status
4.3.5. book_issue table:

Description: This table includes book issue details
NAME
TYPE
SIZE
DESCRIPTION
Issueid
Int
10
Issue id
Bookid
Int
10
Book id
Userid
Int
10
User id
Issuedate
Date
Issue date
requestdate
Date
Request date
duedate
Date
Due date
Status
status
10
Status
4.3.6.course table:
Description:This table stores course details.
NAME
TYPE
SIZE
DESCRIPTION
course_id
int
11
Course id
course_name
varchar
20
Course name
call_no
varchar
20
Call number
Status
varchar
15
Status
4.3.7 penalty table:

Description: This table stores penalty details
NAME
TYPE
SIZE
DESCRIPTION
penaltyid
int
10
Penalty id
psid
int
10
Penalty setting id
penalty
float
userid
int
other
float
bookid
int
description
text
status
varchar
Penalty
10
User id
10
Book id
Description
10
status
4.3.8.penalty_setting:
Description:This table stores penalty setting details
NAME
TYPE
SIZE
DESCRIPTION
Psid
Int
10
Penalty setting id
penalty_type
varchar
20
Penalty type
Days
int
10
Days
penalty_cost
Float
Penalty cost
4.3.9 9.staff table:

Description:This table stores staff details.
NAME
TYPE
SIZE
DESCRIPTION
Staffid
varchar
10
Staff id
Name
varchar
10
Name
address
varchar
30
Address
contactno
varchar
10
Contact number
dateofjoin
date
login_id
varchar
Date of join
10
Log in id
password
varchar
30
Password
Design
varchar
10
Designation
4.3.9.10 student:
Description:This table stores student information.
NAME
TYPE
SIZE
DESCRIPTION
regno
varchar
10
Registration number
name
varchar
20
Name
Imag
varchar
30
Image
course_id
int
11
Course id
semester
varchar
20
Semester
contactno
varchar
20
Contact number
address
varchar
20
Address
Date
varchar
20
Date
password
varchar
20
password
4.5 E-R DIAGRAM

Entity Relationship Diagram:
An entity relation (ER) diagram is specialized graphics that illustrates the inter
relationship between entities in a database. ER diagrams often uses symbols to
represents three different types of information. Boxes are commonly used to represent
entities. Diamonds are normally used to represent relationship and ovals are used to
represent attributes.
An entity relationship model (ERM), in software engineering is an abstract and
conceptual representation of data. ERM is a relational schema database modelling
method, used to produce a type of conceptual schema or semantic data model of a
system, often a relation database, and its requirements in a top down fashion.
4.4.1 Entity:
Entity is the thing which we want to store information. It is an elementary basic
building block of storing information about business process. An entity represents an
object defined within the information system about which you want to store
information. Entities are distinct things in the enterprise.
4.4.2Relationships:
A relationship is a named collection or association between entities are used to
relate two or more entities with some common attributes or meaningful interaction
between the objects.
4.4.3 Attributes:
Attributes are the properties of the entities and relationship, descriptors of the entity.
Attributes are elementary pieces of information attached to entity.
E-R DIAGRAM
DETAILED
DESIGN
5. DETAILED DESIGN
5.1 Introduction:
Detailed design is the second level of the design process. During detailed design, we
specify how the module in the system interacts with each other and the internal logic
of each of the modules specified during system design is decided, hence it is also
called as logic design.
Detailed design essentially expands the system design and database design to contain
a more detailed description of the processing logic and data structures so that the
design is sufficiently complete for coding
5.2 Applicable Documents:

The detailed design refines the system document. Hence the first applicable document
here is system design. Also we are referring the data structure. Hence the second
applicable document here is database design.
5.3 Structure of software package:

The software package contains of following functional components.
1. Log in
2. Admin
staff
Student
Books
Penalty Setting
Reports
3. Student
Student Account
Student history
Search Book
Request Book
Change Password
5.4. Modular Decomposition of components

5.4.1 Log in Module
5.4.1.1 Design assumption, if any
This module is designed with an intension to provide security to the user.
5.4.1.2. Identification of modules
Log In module does not contain any sub modules
5.4.1.3. Structure chart
5.4.1.4 Data structure shared among modules

User name is stored as a session variable so that it is accessible throughout the
session.
5.4.1.5 Admin Module
5.4.1.6 Design assumptions
This module is designed with an intension to provide various features to the
administrator of the website
5.4.1.7 Identification of modules
It contains:
Staff
Student
Book Information
Requested Books
Issued Book
5.4.1.8 Structure chart
5.4.1.9 Data structure shared among modules
Penalty
settings
The Admin Id is shared among the modules
5.5 Module design of Admin

5.5.1 Staff Module
5.5.1.1 Inputs: Admin Enters the details like event code, event name etc.
5.5.1.2 Procedural details: Admin is provided with the event page where
admin could enter the required event information.
5.1.1.3 File I/O Interfaces: Provides an user friendly interface to enter the details.
5.5.1.4Output: Event details are stored into the database.
5.5.2. Student Module

5.5.2.1Input: Admin enters the menu details like code, name, description, price etc.
5.5.2.2 Procedural details: Admin will be provided with the menu page where admin
could enter required menu information.
Output: Menu details will be stored into the database.
5.5.3 Book Module
5.5.3.1 Input: Admin enters the supplier payment details like supplier name, date, total
amount to be paid, paid amount.
5.5.3.2 Procedural details: Admin will be provided with the payment page where admin
could enter required supplier payment information.
Output: Supplier payment details will be stored into the database.
5.6 User Module

Design Assumptions
This module is provided for registration of a new user.
5.6.1 Identification of modules

It contains: Search book
Request book
View History
Change Password
5.6.2 Structure chart
CODING
AND IMPLEMENTATION
6. CODING AND IMPLEMENTATION

6.1 Introduction
All the software engineering steps have been discussed so far are directed to words are
final objective of translating the module into the software form that could be understood by
the computer. Coding is an important aspect in system development and proper care has
been taken to ensure that the application is efficient and suits the requirement specified.
Coding id viewed as natural consequences of design.
Development guidelines
The coding is done with following characteristics in mind. They are:
Code efficiency
Response time
Maintainability
Security
Simple ease to understand code
Ease of design code translation
6.2 coding standards

The coding standards are necessary for a system because, people another than
programmers can easily understand the orderly convention of system. Standards facilitates
easy maintain of system as someone else other than developers, can later modify or
upgrade the system. The naming convention used here is similar to that window classes.
6.2.1 Code review and Walkthroughs

Review is "A process or meeting during which artifacts of software product are examined
by project stockholders, user representatives, or other interested parties for feedback or
approval. Software Review can be on Technical specifications, designs, source code, user
documentation, support and maintenance documentation, test plans, test specifications,
standards, and any other type of specific to work product, it can be conducted at any stage
of the software development life cycle.
Purpose of conducting review is to minimize the defect ratio as early as possible in
Software Development life cycle. As a general principle, the earlier a document is
reviewed, the greater will be the impact of its defects on any downstream activities and
their work products. Magnitude cost of defect fixing after the release of the product is
around 60-100x. Review can be formal or informal. Informal reviews are referred as
walkthrough and formal as Inspection.
Walkthrough Process: Author describes the artifact to be reviewed to reviewers during the
meeting. Reviewers present comments, possible defects, and improvement suggestions to
the author. Recorder records all defect, suggestion during walkthrough meeting. Based on
reviewer comments, author performs any necessary rework of the work product if required.
Recorder prepares minutes of meeting and sends the relevant stakeholders and leader is
normally to monitor overall walkthrough meeting activities as per the defined company
process or responsibilities for conducting the reviews, generally performs monitoring
activities, commitment against action items etc.
The Purpose of walkthrough is to:
Find problems
Discuss alternative solutions
Focusing on demonstrating how work product meets all requirements.IEEE 1028
recommends three specialist roles in a walkthrough leader
Adminreg.php
<?php
session_start();
include("sqlcon.php");
if(isset($_POST['token']) && ($_POST['token']==$_SESSION['token']))
{
if(isset($_POST["submit"]))
{
$result="insert into
admin_reg(admin_name,user_name,password,gender,designation,email,phoneno)
values('$_POST[name]','$_POST[uname]','$_POST[pw]','$_POST[gender]','$_POST[desig
n]','$_POST[email]','$_POST[phnno]')";
if(!mysql_query($result,$con))
{
die("error".mysql_error());
}
else
$msg="Registered Successfully...";
}
unset($_SESSION['token']);
}
$new_token = md5(time(). rand(0,100));
$_SESSION['token']=$new_token;
include("header.php");
?>
<html>
<head>
<title>
Registration Form</title>
<script language="javascript">
function validate()
{
var x=document.f1.email.value;
var atpos=x.indexOf("@");
var dotpos=x.lastIndexOf(".");
if(document.f1.name.value=="")
{
alert("Enter Admin Name");
document.f1.name.focus();
return false;
}
else if(document.f1.uname.value=="")
{
alert("Enter User Name");
document.f1.uname.focus();
return false;
}
else if(document.f1.pw.value=="")
{
alert("Enter Password");
document.f1.pw.focus();
return false;
}
else if(document.f1.pw.value.length<8 || document.f1.pw.value.length>15 )
{
alert("minimum charaters for password is 8 and maximum character is 15");
return false;
}
else if(document.f1.confirmpw.value=="")
{
alert("Enter Confirm Password");
document.f1.confirmpw.focus();
return false;
}
else if(document.f1.pw.value != document.reg.confirmpw.value)
{
alert("password and confirm password is not matching");
document.f1.confirmpw.value="";
return false;
}
else if(document.f1.gender.value=="")
{
alert("Enter Gender");
document.f1.gender.focus();
return false;
}
else if(document.f1.design.value=="")
{
alert("Enter desination");
document.f1.design.focus();
return false;
}
else if(document.f1.email.value=="")
{
alert("Enter EmailId");
document.f1.email.focus();
return false;
}
else if (atpos<1 || dotpos<atpos+2 || dotpos+2>=x.length)
{
alert("Not a valid e-mail address");
return false;
}
else if(document.f1.phnno.value=="")
{
alert("Enter Student Phone Number");
document.f1.phnno.focus();
return false;
}
else if(document.f1.phnno.value.length<5 || document.f1.phnno.value.length>11 )
{
alert("Not valid number");
document.f1.phnno.focus();
return false;
}
else
return true;
}
function ValidateAlpha()
{
var keyCode = window.event.keyCode;
if ((keyCode < 65 || keyCode > 90) && (keyCode < 97 || keyCode > 123) && keyCode !=
32)
{
window.event.returnValue = false;
alert("Enter only letters");
}
}
function isNumberKey(evt)
{
var charCode = (evt.which) ? evt.which : event.keyCode
if (charCode > 31 && (charCode < 48 || charCode > 57))
{
alert("Enter only Numbers");
}
return true;
}
</script>
</head>
<body>
<div id="templatemo_content_container">
<div id="templatemo_content">
<div id="templatemo_content_left">
<div class="templatemo_post">
<div class="post_title">
ADMIN REGISTRATION
</div>
<div class="post_body">
<form method="post" action="">
<table border="1" width="50%">
<input type="hidden" name="token" value="<?= $new_token?>" />

<tr>
<th>Admin Name</th><td><input type="text" name="name"
onKeyPress="ValidateAlpha();"/></td>
</tr>
<tr>
<th>User Name</th><td><input type="text" name="uname"
</tr>
<tR>
<th>Password</th><td><input type="password" name="pw"/></td>
</tr>
<tr>
<th>Confirm Password</th><td><input type="password" name="Confirmpw"/></td>
</tr>
<tr>
<th>Gender</th><td><input type="radio" name="gender" value="male" checked/>MALE
<input type="radio" name="gender" value="female"/>FEMALE</td>
</tr>
<tr>
<th>Designation</th><td><input type="text" name="design"
</tr>
<tr>
<th>Email</th><td><input type="email" name="email"
onBlur="validateEmail(this);"/></td>
</tr>
<tr>
<th>Phone Number</th><td><input type="number" name="phnno" onKeyPress="return
isNumberKey(event)"/></td>
</tr>
<tr><td colspan="2" align="center"><input type="submit" name="submit"
value="Register" class="CSSButton" onClick="return validate()"/>
<input type="reset" value="Clear" /></td>
</tr>
</table>
</form>
<center><?php echo $msg;?></center>
</div>
</div>
</div> 

<?php
include("sidebar.php");
?>
</div> 

</div> 
<?php
include("footer.php");?>
</body>
</html>
book category.php
<?php
session_start();
{
$ins="insert into book_category(bookcat_name,status)
values('$_POST[bkcat]','$_POST[status]')";
if(!mysql_query($ins,$con))
{
}
else
$msg="Added Successfully...";
}
?>
<html>
<head>
function validate()
{
if(document.f1.bkcat.value=="")
{
alert("Enter Book Category");
document.f1.bkcat.focus();
return false;
}
else if(document.f1.status.value=="")
{
alert("Enter Book Category Status");
document.f1.status.focus();
return false;
}
else
return true;
}
{
32)
{
}
}
{
{
}
return true;
}
</script>
</head>
<body>
ADD BOOK CATEGORY
</div>
<table width="73%" height="108" border="1" align="center">
<tr>
<th width="53%">Book category:</th><td width="47%"><input type="text"
name="bkcat" onKeyPress="ValidateAlpha();" /></td>
</tr>
<tr>
<th>Status:</th><td><select name="status">
<option value="">--select--</option>
<option value="available">Available</option>
<option value="not available">Not Available</option>
</select>
</td>
<tr>
<th colspan="2">
<input type="submit" name="submit" class="CSSButton" onClick="return validate()">
</th>
</tr>
</table>
</form>
</div>
</div>

<?php
?>

<?php
</body>
</html>
Book.php
<?php
session_start();
$d1=date("Y/m/d");
$result=mysql_query("select * from book_category");
$res1=mysql_query("select * from course");

{
{
book(bookcat_id,bookname,isbn,title,author,publisher,yr_of_publ,edition,book_code,cours
e_id,cost,noofcopies,dateofentry,status)
values('$_POST[cid]','$_POST[bname]','$_POST[isbn]','$_POST[title]','$_POST[autr]','$_
POST[publish]','$_POST[yr]','$_POST[edit]','$_POST[bcode]','$_POST[courseid]','$_POS
T[cost]','$_POST[num]','$_POST[doe]','$_POST[status]')";
{
}
else
$msg="Book Added Successfully...";
}
}
if(isset($_GET["editid"]))
{
$res=mysql_query("select * from book where bookid='$_GET[editid]'");
while($row=mysql_fetch_array($res))
{
$a=$row[0];
$b=$row[1];
$c=$row[2];
$d=$row[3];
$e=$row[4];
$f=$row[5];
$g=$row[6];
$h=$row[7];
$i=$row[8];
$j=$row[9];
$k=$row[10];
$l=$row[11];
$m=$row[12];
$n=$row[13];
$o=$row[14];
}
}
if(isset($_POST["update"]))
{
$updt="update book set
bookcat_id='$_POST[cid]',bookname='$_POST[bname]',isbn='$_POST[isbn]',title='$_PO
ST[title]',author='$_POST[autr]',publisher='$_POST[publish]',yr_of_publ='$_POST[yr]',ed
ition='$_POST[edit]',book_code='$_POST[bcode]',course_id='$_POST[courseid]',cost='$_
POST[cost]',noofcopies='$_POST[num]',dateofentry='$_POST[doe]',status='$_POST[statu
s]' where bookid='$_POST[bkid]'";
if(mysql_query($updt))
{
header("Location: viewbook.php");
}
else
die(mysql_error());
}

?>
<html>
<head><title>book form</title>
function validate()
{
if(document.f1.cid.value=="")
{
alert("select Book Category");
document.f1.cid.focus();
return false;
}
else if(document.f1.bname.value=="")
{
alert("Enter Book Name");
document.f1.bname.focus();
return false;
}
else if(document.f1.isbn.value=="")
{
alert("Enter Book Isbn");
document.f1.isbn.focus();
return false;
}
else if(document.f1.title.value=="")
{
alert("Enter book Title");
document.f1.title.focus();
return false;
}
else if(document.f1.autr.value=="")
{
alert("Enter Book Author");
document.f1.autr.focus();
return false;
}
else if(document.f1.publish.value=="")
{
alert("Enter book Publisher");
document.f1.publish.focus();
return false;
}
else if(document.f1.yr.value=="")
{
alert("Enter Year Of Publication");
document.f1.yr.focus();
return false;
}
else if(document.f1.edit.value=="")
{
alert("Enter Book Edition");
document.f1.edit.focus();
return false;
}
else if(document.f1.bcode.value=="")
{
alert("Enter Book Code");
document.f1.bcode.focus();
return false;
}
else if(document.f1.course.value=="")
{
alert("Select Course");
document.f1.course.focus();
return false;
}
else if(document.f1.cost.value=="")
{
alert("Enter Book Cost");
document.f1.cost.focus();
return false;
}
else if(document.f1.num.value=="")
{
alert("Enter Number Of Copies");
document.f1.num.focus();
return false;
}
else if(document.f1.doe.value=="")
{
alert("Enter Date Of Entry");
document.f1.doe.focus();
return false;
}
else if(document.f1.status.value=="")
{
alert("Select Book Status");
document.f1.status.focus();
return false;
}
else
return true;
}
{
32)
{
}
}
{
{
}
return true;
}
</script>
</head>
<body>
ADD BOOK
</div>
<input type="hidden" name="bkid" value="<?php echo $a;?>" />
<tr>
<th>Book category:</th><td><select name="cid">
<option value="">--select--</option>
<?php
while($row=mysql_fetch_array($result))
{
if($b==$row[0])
{
echo "<option value='$row[0]' selected>$row[1]</option>";

}
else
echo "<option value='$row[0]'>$row[1]</option>";
}
?>
</select>
</td>
</tr>
<tr>
<th>Book name:</th><td><input type="text" name="bname" value="<?php echo $c;?>"
onKeyPress="ValidateAlpha();" /></td>
</tr>
<tr>
<th>Isbn:</th><td><input type="text" name="isbn" value="<?php echo $d;?>" /></td>
</tr>
<tr>
<th>Title:</th><td><input type="text" name="title" value="<?php echo $e;?>"
</tr>
<tr>
<th>Author:</th><td><input type="text" name="autr" value="<?php echo $f;?>"
</tr>
<tr>
<th>Publisher:</th><td><input type="text" name="publish" value="<?php echo $g;?>"

</tr>
<tr>
<th>Year of Publication:</th><td><input type="text" name="yr" value="<?php echo $h;?
>" onKeyPress="return isNumberKey(event)"/></td>
</tr>
<tr>
<th>Edition:</th><td><input type="text" name="edit" value="<?php echo $i;?>"
onKeyPress="return isNumberKey(event)"/></td>
</tr>
<tr>
<th>Book code:</th><td><input type="text" name="bcode" value="<?php echo $j;?>"
/></td>
</tr>
<tr>
<th>Course:</th><td>
<select name="courseid">
<option value="">--Select--</option>
<?php
while($row=mysql_fetch_array($res1))
{
if($k==$row['course_id'])
{
echo "<option value='$row[course_id]'

selected>$row[course_name]</option>";
}
else
echo "<option value='$row[course_id]'>$row[course_name]</option>";

}
?>
</select>
</td>
</tr>
<tr>
<th>Cost:</th><td><input type="text" name="cost" value="<?php echo $l;?>"
</tr>
<tr>
<th>Number of copies:</th><td><input type="number" name="num" value="<?php echo
$m;?>" onKeyPress="return isNumberKey(event)"/></td>
</tr>
<tr>
<th>Date of entry:</th><td><input type="date" name="doe" value="<?php echo $n;?>"
</tr>
<tr>
<th>Status:</th><td><select name="status">
<option value="Available"
<?php
if($o=="Available")
{
echo "selected";
}
?>
>Available</option>
<option value="Not Available"
<?php
if($o=="Not Available")
{
echo "selected";
}
?>
>Not Available</option>
</select>
</td>
</tr>
<?php
{
?>
<tr><td colspan="2" align="center"><input type="submit" name="update"

value="Update" class="CSSButton" onClick="return validate()"/>
<input type="reset" value="Clear" /></td>
</tr>
<?php
}
else
{
?>
<tr><td colspan="2" align="center"><input type="submit" name="submit" value="Add
Book" class="CSSButton" onClick="return validate()"/>
<input type="reset" value="Clear" class="CSSButton"/></td>
<?php
}
?>
</table>
</form>
</div>
</div>

<?php
?>
<?php
</body>
</html>
Staff.php
<?php
session_start();
{
{
$result="insert into staff(name,address,contactno,dateofjoin,login_id,password,design)
values('$_POST[name]','$_POST[addr]','$_POST[contno]','$_POST[doj]','$_POST[logid]','
$_POST[pwd]','$_POST[design]')";
{
}
else
$msg="Added Successfully...";
}
}
{
$res=mysql_query("select * from staff where staffid='$_GET[editid]'");
{
$a=$row[0];
$b=$row[1];
$c=$row[2];
$d=$row[3];
$d1=$row[4];
$e=$row[5];
$f=$row[6];
$log=$row[login_id];
}
?>
<html>
<head>
<title>Staff Form</title>
function validate()
{
if(document.f1.name.value=="")
{
alert("Enter Staff Name");
return false;
}
else if(document.f1.addr.value=="")
{
alert("Enter Staff Address");
document.f1.addr.focus();
return false;
}
else if(document.f1.contno.value=="")
{
alert("Enter Staff Contact no");
document.f1.contno.focus();
return false;
}
else if(document.f1.contno.value.length<5 || document.f1.contno.value.length>11 )
{
return false;
}
else if(document.f1.doj.value=="")
{
alert("Enter Staff Date Of Join");
document.f1.doj.focus();
return false;
}
else if(document.f1.logid.value=="")
{
alert("Enter Staff Login id");
document.f1.logid.focus();
return false;
}
else if(document.f1.pwd.value=="")
{
alert("Enter Staff Password");
document.f1.pwd.focus();
return false;
}
else if(document.f1.pwd.value.length<8 || document.f1.pwd.value.length>15 )
{
return false;
}
else if(document.f1.design.value=="")
{
alert("Enter Staff Designation");
document.f1.design.focus();
return false;
}
else
return true;
}
{
32)
{

}
}
{
{
}
return true;
}
</script>
</head>
<body>
ADD STAFF
</div>
<form method="post" action="" name="f1">
<tr>
<th>Name:</th><td><input type="text" name="name" value="<?php echo $b;?>"
</tr>
<tr>
<th>Address:</th><td><input type="text" name="addr" value="<?php echo $c;?>"
/></td>
</tr>
<tr>
<th>Contact No:</th><td><input type="text" name="contno" value="<?php echo $d;?>"
</tr>
<tr>
<th>Date Of Join:</th><td><input type="date" name="doj" value="<?php echo $d1;?>"
/></td>
</tr>
<tr>
<th>Login id:</th>
<td><input type="text" name="logid" value="<?php echo $log;?>" /></td></tr>
<tr>
<th>Password:</th><td><input type="password" name="pwd" value="<?php echo $e;?
>" /></td>
</tr>
<tr>
<th>Designation:</th><td><input type="text" name="design" value="<?php echo $f;?>"
</tr>
<?php
{
?>
<tr><td colspan="2" align="center"><input type="submit" name="submit" value="Update
Staff" onClick="return validate()" class="CSSButton"/>
</tr>
<?php
}
else
{
?>
Staff" onClick="return validate()" class="CSSButton"/>
</tr>
<?php
}
?>
</table>
</form>
</div>
</div>

<?php
</body>
</html>
Student.php
<?php
session_start();
$d1=date("Y/m/d");
$UPLOADER="images/";
{
{
$f1=rand().$_FILES["file"]["name"];
$imgpath="{$UPLOADER}{$_FILES['file']['name']}";
move_uploaded_file($_FILES["file"]["tmp_name"],$imgpath);
student(regno,name,imag,course_id,semester,contactno,address,date,password)
values('$_POST[no]','$_POST[name]','$imgpath','$_POST[course]','$_POST[sem]','$_POS
T[contno]','$_POST[addr]','$_POST[date]','$_POST[pwd]')";
{
}
else
$msg="Registered Successfully...";
}
}
{
$res=mysql_query("select * from student where regno='$_GET[editid]'");
{
$a=$row[regno];
$b=$row[name];
$c=$row[imag];
$d=$row[course_id];
$e=$row[semester];
$f=$row[contactno];
$g=$row[address];
$h=$row[date];
$i=$row[password];
}
}
if(isset($_POST["update"]))
{
if($_FILES["file"]["name"]=="")
{
$imgpath=$_POST[img];
$updt="update student set
regno='$_POST[no]',name='$_POST[name]',imag='$imgpath',course_id='$_POST[course]'
,semester='$_POST[sem]',contactno='$_POST[contno]',address='$_POST[addr]',date='$_P
OST[date]',password='$_POST[pwd]' where regno='$_POST[no]'";
{
header("Location: viewstudent.php");
}
}
else
{
$f1=rand().$_FILES["file"]["name"];
$imgpath="{$UPLOADER}{$_FILES['file']['name']}";
move_uploaded_file($_FILES["file"]["tmp_name"],$imgpath);
$updt="update student set
regno='$_POST[no]',name='$_POST[name]',imag='$imgpath',course_id='$_POST[course]'
,semester='$_POST[sem]',contactno='$_POST[contno]',address='$_POST[addr]',date='$_P
OST[date]',password='$_POST[pwd]' where regno='$_POST[no]'";
{
header("Location: viewstudent.php");
}
}
}
include("studentheader.php");
?>
<html>
<head><title>student form</title>
function validate()
{
if(document.f1.no.value=="")
{
alert("Enter Student Register Number");
document.f1.no.focus();
return false;
}
else if(document.f1.no.value.length<10)
{
alert("Register number should have 10 numbers");
return false;
}
else if(document.f1.name.value=="")
{
alert("Enter Student Name");
return false;
}
else if(document.f1.name.value.length<3 ||
document.f1.name.value.length>10 )
{
alert("Student name must be greater than 3 letters and less than 10 letters");
return false;
}
else if(document.f1.file.value=="")
{
alert("Choose Student Image");
document.f1.file.focus();
return false;
}
else if(document.f1.course.value=="")
{
alert("Enter Student Course");
document.f1.course.focus();
return false;
}
else if(document.f1.sem.value=="")
{
alert("Enter Student Semester");
document.f1.sem.focus();
return false;
}
else if(document.f1.contno.value=="")
{
alert("Enter Student Contact Number");
return false;
}
else if(document.f1.contno.value.length<5 || document.f1.contno.value.length>11 )
{
return false;
}
else if(document.f1.date.value=="")
{
alert("Enter date");
document.f1.date.focus();
return false;
}
else if(document.f1.addr.value=="")
{
alert("Enter Student Address");
document.f1.addr.focus();
return false;
}
else if(document.f1.pwd.value=="")
{
alert("Enter Student Password");
return false;
}
else if(document.f1.pwd.value.length<8 || document.f1.pwd.value.length>15 )
{
return false;
}
else
return true;
}
{
32)
{
}
}
{

{
}
return true;
}
</script>
</head>
<body>
ADD STUDENT
</div>
<?php echo $msg;?>
<form method="post" action="" enctype="multipart/form-data">
<table width="82%" height="321" border="1" align="center">

<input type="hidden" name="img" value="<?php echo $c;?>" />
<tr>
<th width="46%">Register no:</th><td width="54%"><input type="text" name="no"
value="<?php echo $a;?>" onKeyPress="return isNumberKey(event)"/></td>
</tr>
<tr>
<th>Name:</th><td><input type="text" name="name" value="<?php echo $b;?>"
</tr>
<tr>
<th>Image:</th><td><input type="file" name="file" /></td>
</tr>
<tr>
<th>Course:</th><td><select name="course">
<?php
while($row=mysql_fetch_array($res1))
{
if($d==$row['course_id'])
{
echo "<option value='$row[course_id]'
selected>$row[course_name]</option>";
}
else
echo "<option value='$row[course_id]'>$row[course_name]</option>";
}
?>
</select>
</td>
</tr>
<tr>
<th>Semester:</th><td><input type="text" name="sem" value="<?php echo $e;?>"
</tr>
<tr>
<th>Contact no:</th><td><input type="number" name="contno" value="<?php echo $f;?
>" onKeyPress="return isNumberKey(event)"/></td>
</tr>
<tr>
<th>Address:</th><td><input type="text" name="addr" value="<?php echo $g;?>"
</tr>
<tr>
<th>Date:</th><td><input type="text" name="date" value="<?php echo date('Y/m/d');?>"
readonly onKeyPress="return isNumberKey(event)"/></td>
</tr>
<tr>
<th>password:</th><td><input type="password" name="pwd" value="<?php echo $i;?

>" /></td>
</tr>
<?php
{
?>
<tr><td colspan="2" align="center"><input type="submit" name="update" value="Update
Student" onClick="return validate()" class="CSSButton"/>
</tr>
<?php
}
else
{
?>
Student" onClick="return validate()" class="CSSButton"/>
</tr>
<?php
}
?>
</table>
</form>
</div>
</div>

<?php
</body>
</html>
TESTING
7. TESTING
7.1 Introduction
Testing is vital to the success of the system. System testing makes a logical assumption that
if all the parts of the system are correct, the goal will be successively achieved. Testing is
running the program (or product) under various circumstances and condition to find errors
and bugs in it. It is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. The testing phase involves testing of a
system using various test data. Testing involves operation of system or application under
controlled conditions and evaluating the results. The controlled conditions should include
both normal and abnormal conditions.
7.2. Testing Objectives

Testing is a process of executing a program with the intent to finding an error
A good test case is one that has a high probability of finding yet undiscovered error
To discuss the distinction between validation and defect testing
A successful test is one that uncovers an yet undiscovered error
7.3 Unit Testing

The term unit testing refers to the individual testing of separate units of a software system.
The first test in the development process is the unit test. The source code is normally
divided into modules, which in turn are divided into smaller units called units. These units
have specific behaviour. The test done on these units of code is called unit test. Unit test
depends upon the language on which the project is developed.
7.4White Box Testing

White box testing, sometimes called glass-box testing, is a test case design philosophy
that uses the control structure described as part of component-level design to derive test
cases. Using White box testing methods it can be ensured that:
All independent paths within a module have been exercised at least once
Exercise all logical decisions.
Execute all loops at their boundaries and within their operational bounds.
Exercise internal data structures to ensure their validity.
7.5 Black Box Testing

Black Box Test is tes ting w ithout know ledge of the internal w orkings of the
item being tested. For example, when black box testing is applied to software
engineering, the tester would only know the "legal" inputs and what the expected outputs
should be, but not how the program actually arrives at those outputs. It is because
of this that black box testing can be considered testing with respect to the
specifications, no other knowledge of the program is necessary
7.6 UNIT TEST CASES

A test case has a component that describes an input, action or event and an expected
response, to determine if a feature of an application is working correctly. The basic
objective of writing test cases is to validate the testing coverage of the application. Unit
testing enables us to detect errors and correct it without affecting any other modules.
1. Test Cases for login details
SL.NO
TEST CONDITION
EXPECTED
TEST RESULT
On load of the Login
RESULT
No data should be
Pass
1.
form
supplied
2.
When the user does
Should display error
not enter any values
message Please
and clicks Login.
enter Username and
When the user enters
Password
an invalid username
message Invalid
and clicks Login
Username or
3.
pass
pass
Password
4.
5.
When the user enters
an invalid password
message Invalid
and clicks Login
Username or
When user enters
Password
Should load the
valid Username and
Home form
Password and clicks

Login
pass
Pass
2. Test Cases for Admin Registration details
SL.NO
TEST CONDITION
EXPECTED
TEST RESULT
On load of the
RESULT
No data should be
pass
1.
adminreg form
supplied
2.
When user does not
enter any values and
message Please
clicks Register
When user enters
enter all fields

numbers instead of
message Enter only
letters in the field
letters
admin name
When user enters
digits lesser than 8
message "Minimum
and greater than 15
characters for
3.
4.
pass
pass
pass
password is 8 and
maximum character
5.
When user enters all
is 15"
Should display
fields and clicks
message Added
Register
Successfully
pass
3. Test Cases for Book category details
SL.NO
TEST CONDITION
EXPECTED
TEST RESULT
On load of the Book
RESULT
No data should be
pass
category form
supplied
When user does not
message Please
clicks Submit
When user does not
enter the fields

enter book category
message Please
and clicks Submit
enter book category
2.
3.
field
pass
pass
4.
5.
6.
When user enters
numbers instead of
message Enter only
letters
book category
When user does not
selects status and
message Please
clicks Submit
When user enters
select status
Should display
book category and
message Book
status and clicks
Added Successfully
pass
Pass
pass
Submit
4. Test Cases for Book details
SL.NO
TEST CONDITION
EXPECTED
TEST RESULT
RESULT
1.
2.
3.
4.
6.
7.
8.
On load of the Book
No data should be
form
supplied
When user does not
message Please
clicks Add book

When user does not
enter the fields

selects book
message Please
category
When user does not
select book category

enter book name
message Please
When user enter
select book name

letters instead of
message Enter Only
numbers in the field
numbers
isbn
When user enter
numbers instead of
message Enter only
letters
book name
When user enter
numbers instead of
message Enter only
Pass
Pass
Pass
Pass
Pass
Pass
pass
9.
10.
11.
letters
title
When user enter
numbers instead of
message Enter only
letters
author
When user enter
numbers instead of
message Enter only
letters
publisher
When user enter
letters instead of
message Enter only
numbers
Pass
Pass
Pass
year of publications
12.
13.
14.
15.
When user enter
letters instead of
message Enter only
numbers
edition
When user enter
letters instead of
message Enter only
numbers
cost
When user enter
letters instead of
message Enter only
numbers
number of copies
Should display
the fields and clicks
message Book
Add book
Added Successfully
Pass
Pass
Pass
Pass
5. Test Cases for Course details
SL.NO
TEST CONDITION
EXPECTED
TEST RESULT
RESULT
1.
On load of the
No data should be
Course form
supplied
pass
2.
3.
4.
5.
6.
When user does not
pass
message Please enter
clicks Submit
the fields
When user does not
enter course_name
When user enter
course name
numbers instead of
message Enter only
letters
book name
When user enter
letters instead of
message Enter Only
numbers
call_no
Should display
message Course
Submit
Added Successfully
pass
pass
pass
pass
6. Test Cases for History details
SL.NO
TEST
EXPECTED
TEST RESULT
1.
CONDITION
On load of the
RESULT
No data should be
pass
History form
supplied
When user does not
message Please
clicks Submit
When user does not
enter the fields

select search by
message Please
When user selects
select search by
Should load
search by and
appropriate page
2.
3.
4.
clicks Submit
7. Test Cases for Penalty setting details
pass
pass
pass
SL.NO
TEST
EXPECTED
TEST RESULT
1.
CONDITION
On load of the
RESULT
No data should be
pass
Penalty setting form
supplied
When user does not
message Please
clicks Submit
When user does not
enter the fields

select penalty
message Please
type
When user enter
select penalty type

letters instead of
message Enter only
numbers
cost
When user enter all
Should display
message Added
Submit
successfully
2.
3.
4.
5.
pass
pass
pass
pass
8. Test Cases for Penalty settings details
SL.NO
TEST
EXPECTED
TEST RESULT
1.
CONDITION
On load of the
RESULT
No data should be
pass
Penalty settings form
supplied
When user does not
message Please
clicks Submit
When user does not
enter the fields

select penalty type
message Please
When user enter
select penalty type

letters instead of
message Enter only
numbers
2.
3.
4.
no of days
pass
pass
pass
5.
6.
When user enter
letters instead of
message Enter only
numbers
penalty_cost
When user enter all
Should display
message Added
Submit
successfully
pass
pass
9. Test Cases for Search by details
SL.NO
TEST CONDITION
EXPECTED
TEST RESULT
RESULT
1.
2.
3.
On load of the
No data should be
Search by form
supplied
When user does not
clicks Search
the fields
When user enter
numbers instead of
message Enter only
letters
pass
pass
pass
Search book by title

4.
When user enter
Should display
pass
Search book by title appropriate page

and clicks Search
10. Test Cases for Staff details
SL.NO
TEST CONDITION EXPECTED

RESULT
TEST RESULT
1.
2.
3.
4.
5.
6.
7.
On load of the Staff
No data should be
form
supplied
When user does not
message Please
clicks Add staff

When user enter
enter staff name

number instead of
message Enter only
letter in the field
letters
name
When user enter
letters instead of
message Enter only
numbers
contact no
When user enter
number instead of
message Enter only
letter in the field
letters
designation
When user enter all
Should display
message Added
Add staff
Successfully
When user enters
message "Minimum
and greater than 15
characters for
pass
pass
pass
pass
pass
pass
pass
password is 8 and
maximum character
is 15"
11. Test Cases for Staff history details
SL.NO
TEST
EXPECTED
TEST RESULT
1.
CONDITION
On load of the Staff
RESULT
No data should be
pass
history form
supplied
When user does not
enter the field and
message Please
clicks Search
enter staff name
2.
pass
3.
When user enter
number instead of
message Enter only
letters
pass
enter the staff

4.
name
When user enter the
Should move to
field and clicks
appropriate page
pass
Search
12. Test Cases for Student details
SL.NO
1.
2.
TEST
EXPECTED
CONDITION
RESULT
On load of the
No data should be
Student form
supplied
Clicking Add
student button
message Please
without selecting
enter name
TEST RESULT
pass
pass
name
3.
When user enter
letters instead of
message Enter only
numbers
pass
Register no
4.
5.
When user enter
number instead of
message Enter only
letter in the field
letters
name
When user enter
letters instead of
message Enter only
numbers
Semester
pass
pass
6.
7.
8.
When user enter all
message Added
Add student
Successfully
When user does not
enter @ while
message Not a valid
writing email id
email id
When user enters
message "Minimum
and greater than 15
characters for
pass
pass
pass
password is 8 and
maximum character
is 15"
13. Test Cases for Student history details
SL.NO
1.
2.
3.
TEST CONDITION
EXPECTED
TEST RESULT
On load of the
RESULT
No data should be
pass
Student history form
supplied
Clicking Search
button without
message Please
selecting Student
enter Student no
no
When user enter letter Should display error
instead of number in
message Enter only
the field enter the
numbers
Student no
pass
pass
4.
When user enter the
Should move to
field and clicks
appropriate page
pass
Search
14. Test Cases for add fine details
SL.NO
1.
2.
3.
4.
TEST CONDITION
EXPECTED
TEST RESULT
On load of the Add
RESULT
No data should be
pass
fine form
supplied
Clicking Add fine
button without
message Please
selecting days and
enter all fields
cost
When user enter
letter instead of
message Enter only
numbers
cost
When user enter all
Should display
message Fine
Add fine
added
pass
pass
pass
15. Test Cases for Admin profile details
SL.NO.
TEST CONDITION
EXPECTED
TEST RESULT
1.
On load of the
RESULT
No data should be
pass
Admin profile form
supplied
Clicking Update
button without
message Please
giving Admin
enter Admin name
name
When user enter
number instead of
message Enter only
letters
2.
3.
pass
pass
4.
user name
Should store the
information in the
Update
database
pass
16. Test Cases for penalty details
SL.NO.
1.
2.
3.
TEST CONDITION
EXPECTED
TEST RESULT
On load of the
RESULT
No data should be
pass
penalty form
supplied
Clicking Add fine
button without
message Select all
selecting any fields

Clicking Add fine
fields
button without
message Select
selecting
registration number
pass
pass
Registration
4.
number
When user enter all
Should display
fields and click Add
message Penalty
fine
added
pass
SCREEN
SHOTS
8. Screenshots
1.Index form: this will display index information where user can search the books.
2. Admin login from:this page will allow admin to login to the page.
3.Admin Home form: when admin click in to the login button it will move to the home
page.
4.Student form:this page will contain the details of the student and this information
will be store in database and can retrieve for further use.
5.Staff form: this page will contain the details of the staff and this information will be
store in database and can retrieve for further use.
6.Book form:the details of the book will be added by admin and stored in database.
7.Search book form:here the user can search for a book on the base of title
8.Search book form:When we search for a particular book and the details of that
book will be displayed and if that book is available we can request for the book.
9.Member login page:when user request for book the member login page will be
displayed.
10.View request form:this page will view requested books.
11.View Request form:in this page all the requested books will be displayed by
admin.if that book is available admin can issue that book.
12.Issue book form:here book will be issued by admin to the members.
13.View issued book: in this form the issued books will displayed and the member can
also return the books.
14.Add fine form:here the fine will be added if the return date is exceeded.
15.Add fine form: here the fine will be displayed.
16.Add book form:if the user does not enter any fields and clicks Add book error
message will be displayed.
17.book form:when user enter letters instead of numbers then the error message will
be displayed.
18.Book form: when user enter numbers instead of letters the error message will be
displayed.
CONCLUSION
9. CONCLUSION
This Software is user friendly so there is no confusion for a new user to use this Software.
It is designed to minimize the time and increase the efficiency.
The package intends to provide a way to collect, maintain and analyze data of business
transaction carried out at CAMPCO. The Software will provide a graphical environment in
which the various users of the system will be able to accomplish individual operations that
are essential to the effective functioning of the organization.
SQL Server 2005 is used as the database. The main idea was to develop an Easy to use
simple front end using the concept of forms and reports in Visual Basic. All the possible
user requirements are accomplished using buttons. Up-to-date Reports can be generated
based on the user requests.
FUTURE
ENHANCEMENT
10. Future scope of the project
This project plays a vital role in the development of fund management system as the
fund requests from various branches will be taken up telephonically is faster and hence
it can be used in networking
User friendly screen dialogues for the definition and maintenance of the database
BIBLIOGRAPY
11. BIBLIOGRAPHY
References:
An integrated approach to software engineering by Pankaj Jalote
Websites referred:
http://www.templateMo.com
http://www.w3schools.com
http://www.wikipedia.com

E Library

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

E Library

Hochgeladen von

Copyright:

Verfügbare Formate

www.freestudentprojects.comwww.sourcecodefiles.

Title of the project

Chapter 2: System Requirement and Specifications

2.3.3.1 Performance Requirements

Chapter 3: System Design

Chapter 4: Database Design

Chapter 5: Detailed Design

5.2 Applicable Documents

Chapter 6: Coding and Implementation

Chapter 10: Future Enhancement

Chapter 11: Bibliography

1.3Objective of the project

will deal in all the requirements

needed for managing libraries.

every time they want to find some item in the library.

user need not visit the library every time to find

an item; instead, he/she can search items from his/her own

1.5 Problem statement

1.7 Languages used

XAMPP is a free and open source cross-platform server solution package,

The purpose of a web browser is to read HTML documents and compose

1.7.2 Back end

MySQL works on many different system platforms, including BSDi, FreeBSD,

1.7 Hardware and Software requirements

Technology Implemented : Apache Server

User Interface Design

: Mozilla, Google Chrome, IE8

1.7.2 Hardware requirements:

40 GB hard disk and above

: Windows XP/Windows 7 or above

1.8 Methodology (including a summary of the project)

1.9 Module Description

Renewal of books: This module is used by the admin to renew

1.10 What contribution would the project make?

Reduce the manual work and time consumption

2. SOFTWARE REQUIREMENTS SPECIFICATION

Electronic Library Management

Software Requirements specifications

Data Flow Diagram

Software Engineering Book- Ian Sommerville

An Integrated Approach to Software Engineering by Pankaj Jalote

The primary purpose of this application is to implement the above stated

2.2 overall descriptions

E-Library Management System is a online application that supports multi user. It is

2.2.2 Product Features

Keeps the track of the book details.

Status of the book.

Up-to-date Reports are generated.

Reduces manual work and time consumption

Provides Data security

No Data loss and Misuse of data is avoided.

2.2.3 User classes and Characteristics

Very easy to use and understand

Trained to use the software

2. 2.4 Assumption and dependencies

Processor: Intel dual core or above

Processor Speed: 1.0 GHZ or above

RAM: 1 GB RAM or above

Hard Disk: 20 GB hard disk or above

2.3.1.3 Software Interface

User Interface Design

:Windows xp /windows 7 and above

2.3.2 Functional Requirements: