library Management Systems

8/22/2019 library Management Systems

1/67


2/67

CONTENTS

ABSTRACT

INTRODUCTION

HARDWARE & SOFTWARE REQUIREMENTS

PROBLEM ANALYSISMODULES DESCRIPTION

TABLE DESIGN

ER DIAGRAM

SCREEN SHOTS

TEST CASES

CONCLUSION


3/67

ABSTRACT

This project is aimed at developing an Library

Management System for the college library.

This system can be used to search for books,Issue/Renewal books, Fine generation etc..,

This is one integrated system that contains studentand administrator modules.


4/67

INTRODUCTION The mission of the Library Management System Project is to

create an integrated information about the books for membersand administration.

There are registered people in the system (students,Administrator et al). Each one of them may have some exclusiveprivileges.

The Home page is provided with links to connect

ADMINISTRATOR/STUDENT modules in the system.

The cost of the System is economical and it is developed withinthe required time.


5/67

HARDWARE REQUIREMENTS

Processor: Intel Pentium 4 or equivalent

RAM: Minimum of 256 MB or higher

HDD: 20 GB or higher

Monitor: 15 or 17 color monitor


6/67

SOFTWAREREQUIREMENTS

Front-end:J2EE (JSP, HTML, JavaScript)

Back-end: Oracle 9i or higher

Server: Apache Tomcat 5.5

Operating system: Microsoft Windows 2000 or XP

Browser: Microsoft Internet Explorer or any other


7/67


8/67

EXISTING SYSTEM

By using present system, work is done manually. So all

transactions takes lot of time to complete.

If the information is maintained manually the process becomes

much complicated and difficult for understanding and retrieval

of information.

Student cannot interact directly with system. He can onlyinteract with administrator.


9/67

PROPOSED SYSTEMThis system is a completely computerized one.

Books Information can be retrieved easily by using searchoperations, Which is not possible in a manual system.

Student can directly interact with system and can check the statusof the books borrowed by him and the respective due dates andother relevant details by entering his/her Register no.


10/67

MODULES:

MODULES OPERATIONAL

RIGHTS

ADMINISTRATOR

Add/Remove books

Add/Remove members Issue/Renewal books Return books Search

STUDENTSearchDisplay status of thebooks borrowed by him and otherrelevant details.


11/67

DATABASE TABLESALOGIN

FIELD NAME KEY TYPE DATA TYPE----------------- --------------- -----------------

UNAME VARCHAR2(30)

PWD PRIMARY KEY VARCHAR2(15)


12/67

DATABASE TABLESBOOKS

FIELD NAME KEY TYPE DATA TYPE

----------------- --------------- -----------------BOOKID PRIMARY KEY VARCHAR2(5)

TITLE VARCHAR2(50)

SUBJECT VARCHAR2(50)

STATUS VARCHAR2(20)

PRICE VARCHAR2(10)

AUTHOR VARCHAR2(15)

SHELF NO VARCHAR2(15)


13/67

DATABASE TABLESSTUDENT


----------------- --------------- -----------------SID PRIMARY KEY VARCHAR2(5)

FNAME VARCHAR2(50)

LNAME VARCHAR2(50)

MID VARCHAR2(20)

RES VARCHAR2(10)

MOB VARCHAR2(15)

DOB VARCHAR2(15)


14/67

DATABASE TABLESISSUE


----------------- --------------- -----------------BOOKID FOREIGN KEY VARCHAR2(5)

SID FOREIGN KEY VARCHAR2(5)

ISSUEDATE DATE

RETURNDATE DATE

STATUS VARCHAR2(12)

FINE NUMBER(6)


15/67


16/67


17/67


18/67


19/67


20/67


21/67


22/67


23/67


24/67


25/67


26/67


27/67


28/67


29/67


30/67


31/67


32/67


33/67


34/67


35/67


36/67


37/67


38/67


39/67


40/67


41/67


42/67


43/67


44/67


45/67


46/67


47/67


48/67


49/67


50/67


51/67


52/67


53/67


54/67


55/67


56/67


57/67


58/67


59/67


60/67


61/67


62/67

TESTING

Testing is process of executing program with the intent of

finding an error

Testing is the phase where errors remaining from the earlierphase are also detected.

In this the program to be tested is executed with a set of test

cases and the output of the program for the test case isevaluated to determine whether the program is performing as it

is expected to do.


63/67

TEST CASEWhen invalid characters are included in any of thefields while entering details.

Expected Result

System should not accept the details entered anddisplay an appropriate error message.

Observed Result

The system displayed the message and the user isprompted to reenter the details.


64/67

Test CaseWhen an invalid UserID or Password are given

Expected Result

System should display an error message followed by ascreen to re-enter the id or password

Observed Result

The system displayed the message and the screen to re-

enter the details.


65/67

Test Case

When required fields are not entered.

Expected Result

System should identify the fields and display anappropriate error message

Observed Result

The system displayed the appropriate error message.


66/67

The entire implemented system mainly demonstrates the

concept of a library management system.

The developed system perfectly met all the objectivesconceived at the design phase of the system.

This project helps the user from avoiding the manual stress in

maintaining the records.

No system is always perfect or complete and there is scope for

further development.


67/67

Documents

library Management Systems