2. CONTENTS  ABSTRACT  INTRODUCTION  HARDWARE & SOFTWARE REQUIREMENTS  PROBLEM ANALYSIS  MODULES DESCRIPTION  TABLE DESIGN  ER DIAGRAM  SCREEN SHOTS  TEST CASES  CONCLUSION

3. 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 student and administrator modules.

4. INTRODUCTION  The mission of the Library Management System Project is to create an integrated information about the books for members and administration.  There are registered people in the system (students, Administrator et al). Each one of them may have some exclusive privileges.  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 within the required time.

5. 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. SOFTWARE REQUIREMENTS  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

8. 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 only interact with administrator.

9. PROPOSED SYSTEM  This system is a completely computerized one.  Books Information can be retrieved easily by using search operations, Which is not possible in a manual system.  Student can directly interact with system and can check the status of the books borrowed by him and the respective due dates and other relevant details by entering his/her Register no.

10. MODULES: MODULES OPERATIONAL RIGHTS ADMINISTRATOR  Add/Remove books  Add/Remove members  Issue/Renewal books  Return books  Search STUDENT  Search  Display status of the books borrowed by him and other relevant details.

11. DATABASE TABLES DATABASE TABLES ALOGIN FIELD NAME KEY TYPE DATA TYPE ----------------- --------------- ----------------- UNAME VARCHAR2(30) PWD PRIMARY KEY VARCHAR2(15)

12. DATABASE TABLES DATABASE TABLES BOOKS 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. DATABASE TABLES DATABASE TABLES STUDENT FIELD NAME KEY TYPE DATA TYPE ----------------- --------------- ----------------- SID PRIMARY KEY VARCHAR2(5) FNAME VARCHAR2(50) LNAME VARCHAR2(50) MID VARCHAR2(20) RES VARCHAR2(10) MOB VARCHAR2(15) DOB VARCHAR2(15)

14. DATABASE TABLES DATABASE TABLES ISSUE FIELD NAME KEY TYPE DATA TYPE ----------------- --------------- ----------------- BOOKID FOREIGN KEY VARCHAR2(5) SID FOREIGN KEY VARCHAR2(5) ISSUEDATE DATE RETURNDATE DATE STATUS VARCHAR2(12) FINE NUMBER(6)

62. TESTING Testing is process of executing program with the intent of finding an error Testing is the phase where errors remaining from the earlier phase 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 is evaluated to determine whether the program is performing as it is expected to do.

63. TEST CASE When invalid characters are included in any of the fields while entering details. Expected Result System should not accept the details entered and display an appropriate error message. Observed Result The system displayed the message and the user is prompted to reenter the details.

64. Test Case When an invalid UserID or Password are given Expected Result System should display an error message followed by a screen to re-enter the id or password Observed Result The system displayed the message and the screen to re- enter the details.

65. Test Case When required fields are not entered. Expected Result System should identify the fields and display an appropriate error message Observed Result The system displayed the appropriate error message.

66. The entire implemented system mainly demonstrates the concept of a library management system. The developed system perfectly met all the objectives conceived 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.