ABSTRACT LIBRARY MANAGEMENT SYSTEM would be used by members who may be students or professors of the college to check the

availability of the books and borrow the books, and by the librarian to update the databases. The purpose of the system is to focuses on the capabilities and facilities provided by a Library. Library Management System have following features: The system provides logon facility to the users. The system provides the members with the option to check their account and/or edit their account.. The system allows the Librarian to create the books catalog, add/delete books and maintain the books catalog. The system allows the Librarian to issue/return books and collect dues. The users of the system are members, librarian of the college and the administrators who maintain the system

TABLE OF CONTENTS

Page | 1

CHAPTER NO.

TITLE

PAGE NO.

ABSTRACT LIST OF TABLE LIST OF FIGURES 3 3

1. INTRODUCTION

1.1. SDLC FOR PROJECT

1.2. OVERVIEW OF PROJECT 1.3. REQURIMENT 2. PROJECT ENVIRONMENT 2.1. TECHNOLOGY USED 2.2. SCREENSHOTS 2.3. TESTING 3. CONCLUSION
4. FUTURE ENHANCEMENT

5. REFERENCES

Page | 2

LIST OF TABLES Sr. No. 1. 2. Page No. 16 16

Name HARDWARE REQUIREMENTS SOFTWARE REQUIREMENTS

LIST OF FIGURES Sr. No. 1. 2. Name Waterfall Model User Interface Page No. 16 16

1. INTRODUCTION

Page | 3

1.1 SDLC OF PROJECT:

The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project from an initial feasibility study through maintenance of the completed application. Various SDLC methodologies have been developed to guide the processes involved including the waterfall model (the original SDLC method), rapid application development (RAD), joint application development (JAD), the fountain model and the spiral model. Mostly, several models are combined into some sort of hybrid methodology. Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely particular plan was followed. Phases of SDLC are: Feasibility The feasibility study is used to determine if the project should get the go-ahead. If the project is to proceed, the feasibility study will produce a project plan and budget estimates for the future stages of development.

Requirement Analysis and Design Analysis gathers the requirements for the system. This stage includes a detailed study of the business needs of the organization. Options for changing the business process may be considered. Design focuses on high level design like, what programs are needed and how are they going to interact, low-level design Page | 4

(how the individual programs are going to work), interface design (what are the interfaces going to look like) and data design (what data will be required). During these phases, the software's overall structure is defined. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this Implementation In this phase the designs are translated into code. Computer programs are written using a conventional programming language or an application generator. Programming tools like Compilers, Interpreters, Debuggers are used to generate the code. Different high level programming languages like C, C++, Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen. Testing In this phase the system is tested. Normally programs are written as a series of individual modules, these subject to separate and detailed test. The system is then tested as a whole. The separate modules are brought together and tested as a complete system. The system is tested to ensure that interfaces between modules work (integration testing), the system works on the intended platform and with the expected volume of data (volume testing) and that the system does what the user requires (acceptance/beta testing). Maintenance Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period. Page | 5

Review At the end a review is conducted to check whether the initial requirements are achieved or not. The designed system meets the user requirements or not. Steps are taken if any problem occurs. Review can be of two types: Formal Technical Review Informal Technical Review

Showing SDLC Phases With The Help Of Waterfall Models Methodlogy Page | 6

1.2 OVERVIEW OF PROJECT: Existing System Borrowing books, returning books or viewing the available books at the Library of the college is generally done manually where in the student has to go to the Library and check the available books at the Library. Students check for books available and borrow the books if they are available otherwise it is of waste for the student to come to the library to come to check for the books if the student doesnt get the book. Then the librarian checks the student id and issue/return the book and the librarian then updates the member database and also the books database. This takes much time so Library Management System is created. Proposed System The Library Management System is a package to be used by Libraries to improve the efficiency of Librarians, Library employees and Users. The Library Management System to be developed benefits greatly the members and the Librarian. The system provides books catalog and information to members and helps them decide on the books to borrow from the library. The Librarian can Page | 7

keep the books catalog updated all the time so that the members (students and the professors) get the updated information all the time. This system has the following functional divisions: Librarian

Member(Faculty/Student)

User Functionality is as follows: Librarian : Can maintain Catalog of library Can Add/Delete book Can Issue/Submit book Can Add new user Can view/update catolg Can Generate Fine

Faculty: Can see his/her account status Can is available books Student: Can see his/her account status Can is available books Can see fine status. The members and the librarian are assumed to have basic knowledge of the computers and internet. Page | 8

1.3 REQUIREMENTS:

Operating System: - Microsoft Windows 2000 or Higher Data Base Server: My SQL Server Clients Tools : Microsoft Internet Explorer, Mozilla Firefox : My Eclipse 6.5, Macromedia Dreamweaver 8

User Interface: JSP, HTML Code Behind : JSP

Software requirements: Number 1 2. 3. 4. Description Windows 2000/ XP/ or Higher MY-SQL Macromedia, My Eclipse Enterprise Workbench 6.5 Ms-Internet Explorer, Mozilla Firefox Apache Tomcat server 6.0.10

5. Hardware requirements: Number 1

Description PC with 2 GB hard-disk and 256 MB RAM

Page | 9

2 .PROJECT ENVIRONMENT 2.1 TECHNOLOGY USED: JSP TECHNOLOGY

JSP stands for JAVA SERVER PAGES. applications that are platform independent

JSP technology enables rapid development of web based JSP technology separates the user interface from content generation enabling designers to change the overall page layout without altering the underlying dynamic content JSP technology lets you mix regular, static HTML with dynamically-generated HTML Java Server Pages technology is an extension of the Java Servlet technology.

Understanding JSP Life Cycle JSP never outputs the content directly to the browser. Instead, JSP relies on initial server-side processing process which translates JSP page into the JSP Page class. The page class then will handle all the requests made of JSP. JSP life cycle can be divided into four phases: Translation, Initialization, execution and finalization.

Page | 10

Translation: In the translation phase, JSP engine checks for the JSP syntax and translate JSP page into its page implementation class if the syntax is correct. This class is actually a standard Java servlet. After that, JSP engine compiles the source file into class file and ready for use. If the container receives the request, it checks for the changes of the JSP page since it was last translated. If no changes was made, It just loads the servlet otherwise the process of check, translate and compile occurs again. Because the compilation process takes time so JSP engine wants to minimize it to increase the performance of the page processing.

Initialization: After the translation phase, JSP engine loads the class file and create an instance of of the servlet to handle processing of the initial request. JSP engines will call a method jspInit() to initialize the a servlet. jspInit method is generated during the translation phase which is normally used for initializing application-level parameters and resources. You can also overide this method by using declaration. <%! public void jspInit(){ // put your custom code here } %>

Execution: After the initialization phase, the web container calls the method jspService() to handle the request and returning a response to the client. Each request is Page | 11

handled is a separated thread. Be noted that all the scriptlets and expressions end up inside this method. The JSP directives and declaration are applied to the entire page so the are outside of this method. Finalization: In the finalization phase, the web container calls the method jspDestroy(). This method is used to clean up memory and resources. Like jspInit() method, you can override the jspDestroy() method also to do your all clean up such as release the resources you loaded in the initialization phase.... <%! public void jspDestroy(){ // put your custom code here // to clean up resources } %> JSP Scripting Elements JSP Scripting allows you to insert Java code into the servlet which is generated from JSP page. These are the forms of scripting elements such as: comment expression scriptlet declaration

JSP Implicit Objects JSP container provides a list of instantiated objects for you to access different kind of data in a web application. Those objects are called implicit object Page | 12

because it is automatically available to access. These are some main implicit objects in JSP which you use most: request object response object session object out object pageContext object application object config object page object excpetion object JSP Directives JSP directives instruct the JSP container on how to work with JSPs. The directive form usualy follows the following form: <%@ directive attribute1 = "value 1" attribute2 = "value 2" ... %>

There are three directives in the JSP specification: page include taglib.

Page | 13

JSP Standard Actions JSP actions are special XML tags which control the behavior of servlet engine. JSP actions allow you to insert a file dynamically, reuse external JavaBean components, forward the request to the other page and generate HTML for Java Applet plugin. Some actions are: jsp:include Action jsp:useBean Action jsp:forward Action jsp:plugin Action

2.2 SCRENSHOTS: HOME PAGE:

Page | 14

LIBRARIAN LOGIN:

Page | 15

LIBRARIAN SECTION:

LIBRARIAN ADDING NEW BOOK:

Page | 16

LIBRARIAN DELETING BOOK:

Page | 17

LIBRARIAN UPDATING BOOK:

LIBRARIAN ISSUING BOOK:

Page | 18

LIBRARIAN SUBMITING BOOK:

LIBRARIAN GENRATING FINE:

Page | 19

MEMBER SECTION: FACULTY:

FACULTY VIEWING BOOK:

STUDENT SECTION:

Page | 20

2.3 TESTING APPROACH TO SOFTWARE TESTING The software engineering process can be viewed as a spiral. Initially system engineering defines the role of software and leads to software requirement analysis where the information domain, functions, behaviour, performance, constraints and validation criteria for software are established. Moving inward along the spiral, we come to design and finally to coding. To develop computer software we spiral in along streamlines that decrease the level of abstraction on each turn. A strategy for software testing may also be viewed in the context of the spiral. Unit testing begins at the vertex of the spiral and concentrates on each unit of the software as implemented in source code. Testing progress by moving outward along the spiral to integration testing, where the focus is on the design and the construction of the software architecture. Talking another turn on outward on the spiral we encounter validation testing where requirements established as part of software requirements analysis are validated against the software that has been constructed. Finally we arrive at system testing, where the software and other system elements are tested as a whole.

UNIT TESTING Unit testing focuses verification effort on the smallest unit of software design, the module. The unit testing we have is white box oriented and some modules the steps are conducted in parallel.

Page | 21

WHITE BOX TESTING This type of testing ensures that All independent paths have been exercised at least once All logical decisions have been exercised on their true and false sides All loops are executed at their boundaries and within their operational bounds All internal data structures have been exercised to assure their validity. To follow the concept of white box testing we have tested each form .we have created independently to verify that Data flow is correct, All conditions are exercised to check their validity, All loops are executed on their boundaries. BASIC PATH TESTING Established technique of flow graph with Cyclomatic complexity was used to derive test cases for all the functions. The main steps in deriving test cases were: Use the design of the code and draw correspondent flow graph. Determine the Cyclomatic complexity of resultant flow graph, using formula: V(G)=E-N+2 or V(G)=P+1 or V(G)=Number Of Regions Where V(G) is Cyclomatic complexity, E is the number of edges, N is the number of flow graph nodes, P is the number of predicate nodes. Determine the basis of set of linearly independent paths.

Page | 22

CONDITIONAL TESTING In this part of the testing each of the conditions were tested to both true and false aspects. And all the resulting paths were tested. So that each path that may be generate on particular condition is traced to uncover any possible errors. DATA FLOW TESTING This type of testing selects the path of the program according to the location of definition and use of variables. This kind of testing was used only when some local variable were declared. The definition-use chain method was used in this type of testing. These were particularly useful in nested statements. LOOP TESTING In this type of testing all the loops are tested to all the limits possible. The following exercise was adopted for all loops: All the loops were tested at their limits, just above them and just below them. All the loops were skipped at least once. For nested loops test the inner most loop first and then work outwards. For concatenated loops the values of dependent loops were set with the help of connected loop. Unstructured loops were resolved into nested loops or concatenated loops and tested as above. Each unit has been separately tested by the development team itself and all the input have been validated.

3.CONCLUSION

Page | 23

This project proved good for me as it provided practical knowledge of not only programming in JAVA and HTML web based application and MYSQL , but also about all handling procedure related with library. It also provides knowledge about the latest technology used in developing web enabled application and client server technology that will be great demand in future. This will provide better opportunities and guidance in future in developing projects independently. BENEFITS: Its a web-enabled project. The user is mainly more concerned about the validity of the data, whatever he is entering. There are checks on every stages of any new creation, data entry or updation so that the user cannot enter the invalid data, which can create problems at later date. User is provided the option of monitoring the records he entered earlier. He can see the desired records with the variety of options provided by him. From every part of the project the user is provided with the links through framing so that he can go from one option of the project to other as per the requirement. This is bound to be simple and very friendly as per the user is concerned. That is, we can say that the project is user friendly which is one of the primary concerns of any good project. Data storage and retrieval will become faster and easier to maintain because data is stored in a systematic manner and in a single database. Decision making process would be greatly enhanced because of faster processing of information since data collection from information available on computer takes much less time then manual system. Allocating of sample results becomes much faster because at a time the user can see the records of last years. Easier and faster data transfer through latest technology associated with the computer and communication.

Page | 24

 Through these features it will increase the efficiency, accuracy and transparency. LIMITATIONS: The size of the database increases day-by-day, increasing the load on the database back up and data maintenance activity. Training for simple computer operations is necessary for the users working on the system.

4. FUTURE IMPROVEMENT:

Automatic fine generation facility can be added.

Bidding for the books by members can be there Section for user uploads should be added. This System being web-based and an undertaking of Cyber Security Division, needs to be thoroughly tested to find out any security gaps.

5.REFERENCE:

www.google.com www.wikipedia.org www.msdn.microsoft.com Page | 25

 The following books were referred during the analysis and execution phase of the project Sql the compleate reference By Sql Press Software engineering By Roger.S.Pressman

Page | 26