***

JAVA LIBRARY MANAGEMENT SYSTEM

A PROJECT REPORT

Submitted by

URVASHI SRIVASTAVA

in partial fulfillment for the award of the

degree

of

MASTER OF COMPUTER APPLICATION

in

MCA DEPARTMENT

OF

GRAPHIC ERA UNIVERSITY

DEHRADUN 24800

***

College Roll No : 49 Examination Roll No : 1101250

DIVISION OF MASTERS OF COMPUTER APPLICATION OF

GRAPHIC ERA DEEMED UNIVERSITY (DEHRADUN)

CERTIFICATE

Certified that this is a bonafide record of the project work titled JAVA LIBRARY MANAGEMENT SYSTEM

DONE BY

URVASHI SRIVASTAVA

of 4th semester of Masters of Computer Application(L) in the year 2014-16 in partial fulfillment of the requirements for the award of Degree of Masters of

Computer Application of

Graphic Era Deemed University (Dehradun)

Dr. Sushil Chandra Dimri Department of Computer Application Head of Department & Professor

Mr. Sanjiv Chauhan Department of Computer Application Assistant Professor Project Guide

***

Acknowledgement We are made up of thousands of others as we are shaped by people their thoughts, opinion, presence and energy. I would like to take this opportunity to first and foremost thank the Almighty for being my strength and my parents Shri A.C. Srivastava & Smt Saroj Srivastava for bringing me up and making me the person I am. Their sacrifice and everlasting love for me always encouraged me to propel myself in all endeavors. No word can document my torchbearer for mentoring and educating me with great patience, from the core of my heart I thank esteemed Asstt. Prof. of our Computer Application Department, Mr.Sanjiv Chauhan (Project Guide) without his help this work would have not have seen the light of the day. His wide knowledge and logical way of thinking reflects true embodiment of a mentor which is of great value for me. I cant forget my hard times in which he stood by me to support me in my carrier and showed confidence in me. I would like to express the deepest appreciation The Head of Department and Professor of Computer Application Dr. Sushil Chandra Dimri who have the attitude and substance of a genius and continuously and convincingly conveyed a spirit of adventure and excitement in regard to this Project.

I wish to express my heartfelt regards with deep sense of reverence and gratitude to Mr Sushil Chamoli, Asstt. Prof Ramesh Rawat Asstt. Prof., Mr. Umesh Tiwari Asstt. Prof.,Mr. Kamlesh Purohit Asstt. Prof.,of (Computer Application Department), for their constant guidance and encouragement during my course of studies. My sincere appreciation and thanks to one and all who have worked tirelessly to support me in my work and helped me to complete well in time. Your names may have not found place here but I believe few things are to be felt rather than being documented.

Urvashi Srivastava MCA(L) Section-B 4th Sem Roll No-1101250 Batch: 2014-16 Under the Guidance of [Assistant Professor Mr. Sanjiv Chauhan Specialization in JAVA Tech. Department of Computer ApplicationIn Graphic Era Deemed University]

***

Discipline of Masters in Computer Application

Project on Java Library Management System

Student Declaration

I URVASHI SRIVASTAVA with student roll no. number 1101250 of IVth

semester, declare that this report contains only work completed by myself

except for information obtained in a legitimate way from literature, company or

university sources. All information from these other sources has been duly

referenced and acknowledged in accordance with the Graphic Era University

in Dehradun.

***

Table of Contents

Sno. Description Page No.

1. TITLE OF THE PROJECT 7 2. PROBLEM DEFINITION 8 3. OBJECTIVE 9 4. ABSTRACT 10 5. PURPOSE 11 6. TECHNOLOGY USED : JAVA 12 6.1 The Key Features of Java 13 7. SWINGS 15 7.1 The origin of Swing 15 7.2 Swing is Built on AWT 15 7.3 Two key Swing Features 15 7.3.1 Swing Components are Lightweight 16 7.3.2 Swing Supports Pluggable Look and Feel 16 7.4 The MVC Connection 17 7.5 Components and Containers 18 7.5.1 Components 18 7.5.2 Containers 19 7.6 The top level container Panes 19 7.7 The Swing Packages 20 7.8 Some important Architectural Diagrams and Facts related

To Swings 20-21

8. INTRODUCTION OF LIBRARY MANAGEMENT SYSTEM 26 9. SCOPE AND FEATURES 27 10. REQUIREMENTS SUMMARY 28 10.1 Business Requirements 28 10.2 User Requirements 28 . 10.2.1 System Users 28 10.2.2 Supervisor 28 10.3 Operational Requirements 28 11. DEVELOPMENT TOOLS AND TECHNIQUES 29 11.1 Front End 29 11.2 Back End 29

***

12. SYSTEM ANALYSIS 30 12.1. Existing System 30 12.2. Proposed System 31 13. FEASIBILITY ANALYSIS 32 13.1. Technical Feasibility 32 13.2. Economic Feasibility 32 14. MINIMAL HARDWARE REQUIREMENTS 33 15. MINIMAL SOFTWARE REQUIREMENTS 33 16. SYSTEM REQUIREMENTS 34 17. SYSTEM DESIGN 35 17.1. Input Design 35 17.2. Output Design 36 18. DATABASE DESIGN 37 19. TABLE USED 38 20. DFD: DATA FLOW DIAGRAM 40 21. GUI INTERFACE: OUTPUT OF THE PROJECT 42 22. SYSTEM IMPLEMENTATION 52 22.1 End User Training 52 22.2 End User Education 52 22.3 Training of Application Software 52 22.4 Post Implementation 52 23. SOFTWARE TESTING 53 23.1. White Box Testing 53 23.2. Black Box Testing 54 23.3. Testing Approach 54 23.4. Testing Scope 54 24. ADVANTAGES OF THE PRESENT SYSTEM 55 25. DISADVANTAGES OF THE PRESENT SYSTEM 55 26. FUTURE SCOPE OF THE PRESENT SYSTEM 56 27. CONCLUSION 57 28. BIBLIOGRAPHY 58 29. VITA 59

Signature of the PROJECT GUIDE:

***

1.TITLE OF THE PROJECT:

LIBRARY MANAGEMENT SYSTEM is a software application to

maintain the records related to Add Books, Listing of All Books,

Book Information, Borrow Books , Book Returns, Add members, and

all necessary requirements for the Library to manage day to day

operations.

***

2.PROBLEM DEFINITION:

The transactions related to Add Book, Remove Book, Book Information, Book

Returns, Borrow Books, Add Members, Listing of all members are maintained

manually at present along with maintaining the accounts of the Students and

the Lecturers.

All these are to be automated and an application is required to relate all of

them relatively and logically so that the current system can be replaced and

accepted without major changes and problems.

The application should provide quick access to the records maintained and

must reveal the important reviews about the business so that the growth can

be easily compared and should provide with the various reports showing the

related details so that the important decisions could be taken easily.

***

3.OBJECTIVE:

The main objective of the application is to automate the existing system of

manually maintain the records of the Add Book, Remove Book, Book

Information, Book Returns, Borrow Books, Add Members, Listing of all members

etc all to be computerized. So the Book Borrow, Return, Searching will be

faster.

***

4.ABSTARCT

Today most of the library is using either manual system for tracking the day to

day activity or they are using desktop, spread sheet like MS Excel application to

manage the day to day activity. In this proposed Library Management

System it will run in client server mode and user can check the book

availability, they can search the books, library staff can issue, receive book,

and management can check the report. System will store historical data.

Management can anytime view the total book status, library card status.

eLibrary is a complete library solution make this complicated function look

much easier. The software is user-friendly, with user-definable preferences like

Book category and extensive and search facilities, huge library of periodical

data to analyze the trend of issue and receive of books.

***

5.Purpose:

The purpose of this project is to provide a friendly environment to maintain the

details of books and library members.

The main purpose of this project is to maintain the circulation system using

computers and to provide different reports.

Improved customers and services through greater access to accurate

information.

Greater accountability and Transparency in operations.

***

6. Technology used : JAVA

Java was conceived by James Gosling, Patrick Naughton, Chris Warth, Ed Frank, and Mike Sheridan at Sun Microsystems, Inc. in 1991. It took 18 months to develop the first working version. This language was initially called Oak, but was renamed Java in 1995. Between the initial implementation of Oak in the fall of 1992 and the public announcement of Java in the spring of 1995, many more people contributed to the design and evolution of the language. Bill Joy, Arthur van Hoff, Jonathan Payne, Frank Yellin, and Tim Lindholm were key contributors to the maturing of the original prototype. Somewhat surprisingly, the original impetus for Java was not the Internet! Instead, the primary motivation was the need for a platform-independent (that is, architecture-neutral) language that could be used to create software to be embedded in various consumer electronic devices, such as microwave ovens and remote controls. As you can probably guess, many different types of CPUs are used as controllers. The trouble with C and C++ (and most other languages) is that they are designed to be compiled for a specific target. Although it is possible to compile a C++ program for just about any type of CPU, to do so requires a full C++ compiler targeted for that CPU. The problem is that compilers are expensive and time-consuming to create. An easierand more cost-efficientsolution was needed. In an attempt to find such a solution, Gosling and others began work on a portable, platform-independent language that could be used to produce code that would run on a variety of CPUs under differing environments. This effort ultimately led to the creation of Java. The second force was, of course, the World Wide Web. Had the Web not taken shape at about the same time that Java was being implemented, Java might have remained a useful but obscure language for programming consumer electronics. However, with the emergence of the World Wide Web, Java was propelled to the forefront of computer language design, because the Web, too, demanded portable programs. The Internet helped catapult Java to the forefront of programming, and Java, in turn, had a profound effect on the Internet. In addition to simplifying web programming in general, Java innovated a new type of networked program called the applet that changed the way the online world thought about content. Java also addressed some of the thorniest issues associated with the Internet: portability and security.

***

6.1 The Key Features of JAVA are :

Simple Java was designed to be easy for the professional programmer to learn and use effectively. Assuming that you have some programming experience, you will not find Java hard to master. If you already understand the basic concepts of object-oriented programming, learning Java will be even easier. Best of all, if you are an experienced C++ programmer, moving to Java will require very little effort. Because Java inherits the C/C++ syntax and many of the object-oriented features of C++, most programmers have little trouble learning Java. Object-Oriented Although influenced by its predecessors, Java was not designed to be source-code compatible with any other language. This allowed the Java team the freedom to design with a blank slate. One outcome of this was a clean, usable, pragmatic approach to objects. Borrowing liberally from many seminal object-software environments of the last few decades, Java manages to strike a balance between the purists everything is an object paradigm and the pragmatists stay out of my way model. The object model in Java is simple and easy to extend, while primitive types, such as integers, are kept as high-performance non objects. Robust The multiplatform environment of the Web places extraordinary demands on a program, because the program must execute reliably in a variety of systems. Thus, the ability to create robust programs was given a high priority in the design of Java. To gain reliability, Java restricts you in a few key areas to force you to find your mistakes early in program development. At the same time, Java frees you from having to worry about many of the most common causes of programming errors. Because Java is a strictly typed language, it checks your code at compile time. However, it also checks your code at run time. Many hard-to-track-down bugs that often turn up in hard-to-reproduce run-time situations are simply impossible to create in Java. Knowing that what you have written will behave in a predictable way under diverse conditions is a key feature of Java. Multithreaded Java was designed to meet the real-world requirement of creating interactive, networked programs. To accomplish this, Java supports multithreaded programming, which allows you to write programs that do many things simultaneously. The Java run-time system comes with an elegant yet sophisticated solution for multiprocess synchronization that

***

enables you to construct smoothly running interactive systems. Javas easy-to-use approach to multithreading allows you to think about the specific behavior of your program, not the multitasking subsystem.

Architecture-Neutral: Acentral issue for the Java designers was that of code longevity and portability. One of the main problems facing programmers is that no guarantee exists that if you write a program today, it will run tomorroweven on the same machine. Operating system upgrades, processor upgrades, and changes in core system resources can all combine to make a program malfunction. The Java designers made several hard decisions in the Java language and the Java Virtual Machine in an attempt to alter this situation. Their goal was write once; run anywhere, any time, forever. To a great extent, this goal was accomplished.

Interpreted and High Performance As described earlier, Java enables the creation of cross-platform programs by compiling into an intermediate representation called Java bytecode. This code can be executed on any system that implements the Java Virtual Machine. Most previous attempts at cross-platform solutions have done so at the expense of performance. As explained earlier, the Java bytecode was carefully designed so that it would be easy to translate directly into native machine code for very high performance by using a just-in-time compiler. Java run-time systems that provide this feature lose none of the benefits of the platform-independent code. Distributed Java is designed for the distributed environment of the Internet because it handles TCP/IP protocols. In fact, accessing a resource using a URL is not much different from accessing a file. Java also supports Remote Method Invocation (RMI). This feature enables a program to invoke methods across a network.

Dynamic Java programs carry with them substantial amounts of run-time type information that is used to verify and resolve accesses to objects at run time. This makes it possible to dynamically link code in a safe and expedient manner. This is crucial to the robustness of the Java environment, in which small fragments of bytecode may be dynamically updated on a running system.

Object-oriented programming (OOP) is at the core of Java. In fact, all Java programs are to at least some extent object-oriented. OOP is so integral to Java that it is best to understand its basic principles before you begin writing even simple Java programs.

***

7.SWINGS

7.1The Origins of Swing

Swing did not exist in the early days of Java. Rather, it was a response to deficiencies present in Javas original GUI subsystem: the Abstract Window Toolkit. The AWT defines a basic set of controls, windows, and dialog boxes that support a usable, but limited graphical interface. One reason for the limited nature of the AWT is that it translates its various visual components into their corresponding, platform-specific equivalents, or peers. This means that the look and feel of a component is defined by the platform, not by Java. Because the AWT components use native code resources, they are referred to as heavyweight. The use of native peers led to several problems. First, because of variations between operating systems, a component might look, or even act, differently on different platforms. This potential variability threatened the overarching philosophy of Java: write once, run anywhere. Second, the look and feel of each component was fixed (because it is defined by the platform) and could not be (easily) changed. Third, the use of heavyweight components caused some frustrating restrictions. For example, a heavyweight component is always rectangular and opaque. Not long after Javas original release, it became apparent that the limitations and restrictions present in the AWT were sufficiently serious that a better approach was needed. The solution was Swing. Introduced in 1997, Swing was included as part of the Java Foundation Classes (JFC). Swing was initially available for use with Java 1.1 as a separate library. However, beginning with Java 1.2, Swing (and the rest of the JFC) was fully integrated into Java. 7.2 Swing Is Built on the AWT Before moving on, it is necessary to make one important point: although Swing eliminates a number of the limitations inherent in the AWT, Swing does not replace it. Instead, Swing is built on the foundation of the AWT. This is why the AWT is still a crucial part of Java. Swing also uses the same event handling mechanism as the AWT. Therefore, a basic understanding of the AWT and of event handling is required to use Swing. (The AWT is covered in Chapters 23 and 24. Event handling is described in Chapter 22.) 7.3 Two Key Swing Features As just explained, Swing was created to address the limitations present in the AWT. It does this through two key features: lightweight components and a pluggable look and feel. Together they provide an elegant, yet easy-to-use solution to the problems of the AWT. More than anything else, it is these two features that define the essence of Swing. Each is examined here. 7.3.1.Swing Components Are Lightweight

***

With very few exceptions, Swing components are lightweight. This means that they are written entirely in Java and do not map directly to platform-specific peers. Because lightweight components are rendered using graphics primitives, they can be transparent, which enables nonrectangular shapes. Thus, lightweight components are more efficient and more flexible. Furthermore, because lightweight components do not translate into native peers, the look and feel of each component is determined by Swing, not by the underlying operating system. This means that each component will work in a consistent manner across all platforms. 7.3.2.Swing Supports a Pluggable Look and Feel Swing supports a pluggable look and feel (PLAF). Because each Swing component is rendered by Java code rather than by native peers, the look and feel of a component is under the control of Swing. This fact means that it is possible to separate the look and feel of a component from the logic of the component, and this is what Swing does. Separating out the look and feel provides a significant advantage: it becomes possible to change the way That a component is rendered without affecting any of its other aspects. In other words, it is possible to plug in a new look and feel for any given component without creating any side effects in the code that uses that component. Moreover, it becomes possible to define entire sets of look-and-feels that represent different GUI styles. To use a specific style, its look and feel is simply plugged in. Once this is done, all components are automatically rendered using that style. Pluggable look-and-feels offer several important advantages. It is possible to define a look and feel that is consistent across all platforms. Conversely, it is possible to create a look and feel that acts like a specific platform. For example, if you know that an application will be running only in a Windows environment, it is possible to specify the Windows look and feel. It is also possible to design a custom look and feel. Finally, the look and feel can be Changed dynamically at run time. and feel that acts like a specific platform. For example, if you know that an application will be running only in a Windows environment, it is possible to specify the Windows look and feel. It is also possible to design a custom look and feel. Finally, the look and feel can be changed dynamically at run time. Java SE 6 provides look-and-feels, such as metal and Motif, that are available to all Swing users. The metal look and feel is also called the Java look and feel. It is platform-independent and available in all Java execution environments. It is also the default look and feel. Windows environments also have access to the Windows and Windows Classic look and feel. This book uses the default Java look and feel (metal) because it is platform independent.

***

7.4 The MVC Connection

In general, a visual component is a composite of three distinct aspects: The way that the component looks when rendered on the screen The way that the component reacts to the user The state information associated with the component No matter what architecture is used to implement a component, it must implicitly contain these three parts. Over the years, one component architecture has proven itself to be exceptionally effective: Model-View-Controller, or MVC for short. The MVC architecture is successful because each piece of the design corresponds to an aspect of a component. In MVC terminology, the model corresponds to the state information associated with the component. For example, in the case of a check box, the model contains a field that indicates if the box is checked or unchecked. The view determines how the component is displayed on the screen, including any aspects of the view that are affected by the current state of the model. The controller determines how the component reacts to the user. For example, when the user clicks a check box, the controller reacts by changing the model to reflect the users choice (checked or unchecked). This then results in the view being updated. By separating a component into a model, a view, and a controller, the specific implementation of each can be changed without affecting the other two. For instance, different view implementations can render the same component in different ways without affecting the model or the controller. Although the MVC architecture and the principles behind it are conceptually sound, the high level of separation between the view and the controller is not beneficial for Swing components. Instead, Swing uses a modified version of MVC that combines the view and the controller into a single logical entity called the UI delegate. For this reason, Swings approach is called either the Model-Delegate architecture or the Separable Model architecture. Therefore, although Swings component architecture is based on MVC, it does not use a classical implementation of it. Swings pluggable look and feel is made possible by its Model-Delegate architecture. Because the view (look) and controller (feel) are separate from the model, the look and feel can be changed without affecting how the component is used within a program. Conversely, it is possible to customize the model without affecting the way that the component appears on the screen or responds to user input. To support the Model-Delegate architecture, most Swing components contain two objects. The first represents the model. The second represents the UI delegate. Models are defined by interfaces. For example, the model for a button is defined by the

***

ButtonModel interface. UI delegates are classes that inherit ComponentUI. For example, the UI delegate for a button is ButtonUI. Normally, your programs will not interact directly with the UI delegate. 7.5 Components and Containers A Swing GUI consists of two key items: components and containers. However, this distinction is mostly conceptual because all containers are also components. The difference between the two is found in their intended purpose: As the term is commonly used, a component is an independent visual control, such as a push button or slider. A container holds a group of Components. Thus, a container is a special type of component that is designed to hold other components. Furthermore, in order for a component to be displayed, it must be held within a container. Thus, all Swing GUIs will have at least one container. Because containers are components, a container can also hold other containers. This enables Swing to define what is called a containment hierarchy, at the top of which must be a top-level container. Lets look a bit more closely at components and containers. 7.5.1 Components In general, Swing components are derived from the JComponent class. (The only exceptions to this are the four top-level containers, described in the next section.) JComponent provides the functionality that is common to all components. For example, JComponent supports the pluggable look and feel. JComponent inherits the AWT classes Container and Component. Thus, a Swing component is built on and compatible with an AWT component. All of Swings components are represented by classes defined within the package javax.swing. The following table shows the class names for Swing components (including those used as containers).

***

Notice that all component classes begin with the letter J. For example, the class for a label is JLabel; the class for a push button is JButton; and the class for a scroll bar is JScrollBar.

7.5.2 Containers Swing defines two types of containers. The first are top-level containers: JFrame, JApplet, JWindow, and JDialog. These containers do not inherit JComponent. They do, however, inherit the AWT classes Component and Container. Unlike Swings other components, which are lightweight, the top-level containers are heavyweight. This makes the top-level containers a special case in the Swing component library. As the name implies, a top-level container must be at the top of a containment hierarchy. Atop-level container is not contained within any other container. Furthermore, every containment hierarchy must begin with a top-level container. The one most commonly used for applications is JFrame. The one used for applets is JApplet. The second types of containers supported by Swing are lightweight containers. Lightweight containers do inherit JComponent. An example of a lightweight container is JPanel, which is a general-purpose container. Lightweight containers are often used to organize and manage groups of related components because a lightweight container can be contained within another container. Thus, you can use lightweight containers such as JPanel to create subgroups of related controls that are contained within an outer container. 7.6 The Top-Level Container Panes Each top-level container defines a set of panes. At the top of the hierarchy is an instance of JRootPane. JRootPane is a lightweight container whose purpose is to manage the other panes. It also helps manage the optional menu bar. The panes that comprise the root pane are called the glass pane, the content pane, and the layered pane. The glass pane is the top-level pane. It sits above and completely covers all other panes. By default, it is a transparent instance of JPanel. The glass pane enables you to manage mouse events that affect the entire container (rather than an individual control) or to paint over any other component, for example. In most cases, you wont need to use the glass pane directly, but it is there if you need it. The layered pane is an instance of JLayeredPane. The layered pane allows components to be given a depth value. This value determines which component overlays another. (Thus, the layered pane lets you specify a Z-order for a component, although this is not something that you will usually need to do.) The layered pane holds the content pane and the (optional) menu bar.

***

Although the glass pane and the layered panes are integral to the operation of a top-level container and serve important purposes, much of what they provide occurs behind the scene. The pane with which your application will interact the most is the content pane, because this is the pane to which you will add visual components. In other words, when you add a component, such as a button, to a top-level container, you will add it to the content pane. By default, the content pane is an opaque instance of JPanel. 7.7 The Swing Packages Swing is a very large subsystem and makes use of many packages. These are the packages used by Swing that are defined by Java SE 6.

The main package is javax.swing. This package must be imported into any program that uses Swing. It contains the classes that implement the basic Swing components, such as push buttons, labels, and check boxes.

7.8 Some Important Architectural diagrams and facts related to Swings

***

***

***

***

***

***

8. INTRODUCTION of Library Management System

The project titled Library Management System is Library management software for monitoring and controlling the transactions in a library .The project Library Management System is developed in java, which mainly focuses on basic operations in a library like adding new member, new books, and updating new information, searching books and members and facility to borrow and return books. Library Management System is a windows application written for 32-bit Windows operating systems, designed to help users maintain and organize library. Our software is easy to use for both beginners and advanced users. It features a familiar and well thought-out, an attractive user interface, combined with strong searching Insertion and reporting capabilities. The report generation facility of library system helps to get a good idea of which are the books borrowed by the members, makes users possible to generate reports hard copy. The software Library Management System has four main modules. Insertion to Database Module User friendly input screen Extracting from Database module Attractive Output Screen Report Generation module borrowed book list & Available book list Search Facility system search for books and members

***

9.Scope and Features

The Library Management System is designed & developed for a receipt and

issuance of books in the library along with the students details. The books

received in the library are entered in Books Entry form and the new student is

entered in the student entry form. When the student wants to get the desired

book the same is issued on the availability basis to the student. The issuance

and due date for the returning of the book is also entered into the Book Issue

form under third menu Book Issue. The student has to pay the fine if any on

the basis of no. of days delayed deposit of the book in the library.

Any education institute can make use of it for providing information about

author, content of the available books. It can be used in offices and

modifications can be easily done according to requirements

From an end-user perspective, the Library Management System Project consists

of two functional elements: Master and Transaction Module.

***

10.Requirements Summary The following preliminary lists are based on initial interviews

10.1. Business Requirements The business goal for the application is to support an increase the productivity and complete automation of existing manual or semi-automatic library management process. Business requirements are discussed in the Scope section, with the following additional detail:

10.2. User Requirements User requirements are categorized by user type.

10.2.1. System Users

Able to search and view the member details. Able to find all the information like book details, book and library card

transaction details in one screen to give answer to member query.

10.2.2. Supervisor

Update book and member details. Modify library card details if required.

10.3. Operational Requirements The following requirements provide a high-level view of how the system will run:

Processor usage should not exceed 80 percent during concurrent uses. Backups will occur incrementally throughout the day. A full weekly backup is required to WORM drives. Ensure that information is easy to access either, and meaningful for the

system users and the company. Minimize the technical knowledge that systems users need to access the

***

11. Development Tools and Technologies

11.1 Front End JAVA , Netbeans 11.2 Back End MS ACCESS

***

12.SYSTEM ANALYSIS

12.1 EXISTING SYSTEM: System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system? What must be done to solve the problem? Analysis begins when a user or manager begins a study of the program using existing system. During analysis, data collected on the various files, decision points and transactions handled by the present system. Training, experience and common sense are required for collection of relevant information needed to develop the system. The success of the system depends largely on how clearly the problem is defined, thoroughly investigated and properly carried out through the choice of solution. A good analysis model should provide not only the mechanisms of problem understanding but also the frame work of the solution. Thus, it should be studied thoroughly by collecting data about the system. Then the proposed system should be analyzed thoroughly in accordance with the needs. System analysis can be categorized into four parts: System planning and initial investigation Information Gathering Applying analysis tools for structured analysis Feasibility study Cost/ Benefit analysis.

In our existing system, all the transaction of books are done manually, so taking more time for a transaction like borrowing a book or returning a book and also for searching of members and books. Another major disadvantage is that preparing the list of books borrowed and the available books in the library will take more time, currently a one day process for verifying all records. So after conducting the feasibility study we decided to make a computerized library management system.

***

12.2 PROPOSED SYSTEM Proposed system is an automated Library Management System. Through our software user can add members, add books, search members, search books, update information, edit information, borrow and return books in quick time. Our proposed system has the following advantages. User friendly interface Fast access to database Less error More Storage Capacity Search facility Look and Feel Environment Quick transaction

All the manual difficulties in managing the Library have been rectified by implementing computerization.

***

13.FEASIBILITY ANALYSIS

Whatever we think need not be feasible .It is wise to think about the feasibility of any problem we undertake. Feasibility is the study of impact, which happens in the organization by the development of a system. The impact can be either positive or negative. When the positives nominate the negatives, then the system is considered feasible. Here the feasibility study can be performed in two ways such as technical feasibility and Economical Feasibility. 13.1 Technical Feasibility:

We can strongly say that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All the resources needed for the development of the software as well as the maintenance of the same is available in the organization here we are utilizing the resources which are available already. 13.2 Economical Feasibility:

Development of this application is highly economically feasible .The organization needed not spend much m one for the development of t he system already available. The only thing is to be done is making an environment for the development with an effective supervision. If we are doing so, we can attain the maximum usability of the corresponding resources .Even after the development, the organization will not be in a condition to invest more in the organization .Therefore, the system is economically feasible.

***

14.MINIMAL HARDWARE REQUIREMENTS Processor : Pentium IV RAM : 2GB Hard Disk : 20GB Monitor : Any Key Board : 122 Keys

15.MINIMAL SOFTWARE REQUIREMENTS Operating System : Windows 8 Language : Java 7 Runtime Environment or better Front End : Netbeans 8.0.2 Back End : Database: MS Access 2010 Notepad++ or Notepad

***

16. SYSTEM REQUIREMENTS

This management system can be used in windows 98, Windows2000, Windows XP and Windows NT, supported for other platform such as Applet, Macintosh and UNIX.

The system must be running Windows 98 or Windows NT4.0 operating system and must meet the following hardware requirements. For Windows 95 based computers, a 486 / 66 MHz or higher Processor with 8MB For Windows 98 based computers, a 500/88MHz or higher Processor with 32 Mb of RAM For Windows NT based computers, a 488 / 66 MHz or higher Processor with 16 MB of RAM For Windows 200 based computers, a 700/850 MHz or higher Processor with 512 MB of Ram

***

17.SYSTEM DESIGN

17.1. Input Design: Input design is the process of converting user-oriented input to a computer based format. Input design is a part of overall system design, which requires very careful attention .Often the collection of input data is the most expensive part of the system. The main objectives of the input design are: 1. Produce cost effective method of input 2. Achieve highest possible level of accuracy 3. Ensure that the input is acceptable to and understood by the staff. Input Data: The goal of designing input data is to make enter easy, logical and free from errors as possible. The entering data entry operators need to know the allocated space for each field; field sequence and which must match with that in the source document. The format in which the data fields are entered should be given in the input form .Here data entry is online; it makes use of processor that accepts commands and data from the operator through a key board. The input required is analyzed by the processor. It is then accepted or rejected. Input stages include the following processes: Data Recording Data Transcription Data Conversion Data Verification Data Control Data Transmission Data Correction

One of the aims of the system analyst must be to select data capture method and devices, which reduce the number of stages so as to reduce both the changes of errors and the cost .Input types, can be characterized as.

External Internal Operational Computerized Interactive

Input files can exist in document form before being input to the computer. Input design is rather complex since it involves procedures for capturing data as well as inputting it to the computer.

***

17.2. Output Design: Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of these result for latter consultation .Computer output is the most important and direct source of information to the users. Designing computer output should proceed in an organized well throughout the manner. The right output must be available for the people who find the system easy to use. The outputs have been defined during the logical design stage. If not, they should defined at the beginning of the output designing terms of types of output connect, format, response etc. Various types of outputs are: External outputs Internal outputs Operational outputs Interactive outputs Turn around outputs All screens are informative and interactive in such a way that the user can full fill his requirements through asking queries.

***

18. DATABASE DESIGN

The general theme behind a database is to handle information as an integrated whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and effectively. After designing input and output, the analyst must concentrate on database design or how data should be organized around user requirements. The general objective is to make information access, easy quick, inexpensive and flexible for other users. During database design the following objectives are concerned:-

Controlled Redundancy Data independence Accurate and integrating More information at low cost Recovery from failure Privacy and security Performance Ease of learning and use

***

19. TABLES USED

***

***

20.

***

***

21.GUI Interface: Output of the Project

***

***

1. ADD BOOKS 2. LISTING OF ALL BOOKS 3. ADD MEMBERS 4. LISTING OF ALL MEMBERS 5. SEARCH OF A BOOK 6. LIST OF SEARCHED BOOK 7. SEARCH OF MEMBER 8. LIST OF SEARCHED MEMBER 9. BORROW BOOKS 10. RETURN BOOKS

When we creates its Data base then its output like this :

***

1. ADD BOOKS

2. LISTING OF ALL BOOKS

***

3. ADD MEMBERS

4. LISTING OF ALL MEMBERS

***

5. SEARCH OF A BOOK

6. LIST OF SEARCHED BOOK

***

7. SEARCH OF MEMBER

8. LIST OF SEARCHED MEMBER

***

9. BOOK INFORMATION AND BORROW BOOKS

***

10. RETURN BOOKS

***

***

22. SYSTEM IMPLEMENTATION Implementation is the stage in the project where the theoretical design is turned into a working system. The implementation phase constructs, installs and operates the new system. The most crucial stage in achieving a new successful system is that it will work efficiently and effectively. There are several activities involved while implementing a new project they are

End user training End user Education Training on the application software System Design Parallel Run And To New System Post implementation Review 22.1. End user Training: The successful implementation of the new system will purely upon the involvement of the officers working in that department. The officers will be imparted the necessary training on the new technology. 22.2. End User Education: The education of the end user start after the implementation and testing is over. When the system is found to be more difficult to understand and complex, more effort is put to educate the end used to make them aware of the system, giving them lectures about the new system and providing them necessary documents and materials about how the system can do this. 22.3. Training of application software: After providing the necessary basic training on the computer awareness, the users will have to be trained upon the new system such as the screen flows and screen design type of help on the screen, type of errors while entering the data , the corresponding validation check at each entry and the way to correct the data entered. It should then cover information needed by the specific user or group to use the system.

22.4. Post Implementation

The department is planning a method to know the states of the past implementation process. For that regular meeting will be arranged by the concerned officers about the implementation problem and success

***

23. SOFTWARE TESTING

Is the menu bar displayed in the appropriate contested some system related features included either in menus or tools? Do pull Down menu operation and Tool-bars work properly? Are all menu function and pull down sub function properly listed ?; Is it possible to invoke each menu function using a logical assumptions that if all parts of the system are correct, the goal will be successfully achieved .? In adequate testing or non-testing will leads to errors that may appear few months later. This create two problem 1. Time delay between the cause and appearance of the problem. 2. The effect of the system errors on files and records within the system The purpose of the system testing is to consider all the likely variations to which it will be suggested and push the systems to limits. The testing process focuses on the logical intervals of the software ensuring that all statements have been tested and on functional interval is conducting tests to uncover errors and ensure that defined input will produce actual results that agree with the required results. Program level testing, modules level testing integrated and carried out. There are two major type of testing they are 1) White Box Testing. 2) Black Box Testing. 23.1. White Box Testing White box sometimes called Glass box testing is a test case design uses the control structure of the procedural design to drive test case. Using white box testing methods, the following tests were made on the system

A) All independent paths within a module have been exercised once. In our system, ensuring that case was selected and executed checked all case structures. The bugs that were prevailing in some part of the code where fixed b) All logical decisions were checked for the truth and falsity of the values.

***

23.2. Black box Testing Black box testing focuses on the functional requirements of the software. This is black box testing enables the software engineering to derive a set of input conditions that will fully exercise all functional requirements for a program. Black box testing is not an alternative to white box testing rather it is complementary approach that is likely to uncover a different class of errors that white box methods like.. 1) Interface errors 2) Performance in data structure 3) Performance errors 4) Initializing and termination errors 23.3 TESTING APPROACH Functional Specifications are thoroughly reviewed for correctness,

coverage and completeness. Study of Design specification and Review for Requirement coverage. Review the design of system components and their integration to give

business solution. Identification of units of application for testing Preparation of database scripts for testing

23.4 TESTING SCOPE The system has different type of forms that were used for input,

manipulation and output of data. The System will be tested for the usability, functionality, reliability and

performance of the application as whole and in parts.

***

24. Advantages of the Present System

This project can be used for any company, for infinite number of products, and for infinite number of categories as it is totally generic.

The data of the member would be entered in the database.

There would be a safe storage of information of the member in the database.

Quick, easy, flexible generation of the member reports.

There would be a dynamic and fully computerized system would be developed.

With the database any data can be added, modified, deleted very quickly.

Security features are very much provided in the system.

User friendly environment

25. Disadvantages of Present System

Some of the problems being faced in manual system are as follows:

1. Fast report generation is not possible.

2. Without MS Access it is not executed.

***

26. Future Scope of Present System

To make the Software Platform Independent. To make the Software general accessibility to the users. Giving inner topics highlights of the book searched. Providing space for online suggestions. To add more features and graphics making it User- Friendly. In any system there is always chance for its enhancement and extension. This system can also be enhanced with the change facilities. Also with the

progress of the Fashion Design system can also be enhance in future.

More facilities can be added to the system for its growth. There is always scope for enhancements in any system, especially in the

ever changing world of computers.

The Fashion design System can also be modified according to the feature requirements the advancement of the technology.

***

27. CONCLUSION

Our project is only a humble venture to satisfy the needs in a library. Several user friendly coding have also adopted. This package shall prove to be a powerful package in satisfying all the requirements of the organization. The objective of software planning is to provide a frame work that enables the Manger to make reasonable estimates made within a limited time frame at the beginning of the software project and should be updated regularly as the project progresses. Last but not least it is no the work that played the ways to success but ALMIGHTY This project was developed to fulfill user and business requirement; however

there are lots of scopes to improve the performance of the Library Management

System in the area of user interface, database performance, and query

processing time. Etc.

So there are many things for future enhancement of this project. The future

enhancements that are possible in the project are as follows.

Connection to third-party OLAP applications

Implement Bar code reader

Web interface for members

In the area of data security and system security.

Provide more online tips and help.

To optimize the query this is embedded in the system.

Linking and integration of any legacy system for accounting.

Integration with bank database through Web Services

***

28. BIBLIOGRAPHY

1. http://www.java2s.com/

2. http://www.javaworld.com/javaworld/jw-01-1998/jw-01- bookreview.html 3. Database Programming with JDBC and Java by O'Reilly 4. Head First Java 2nd Edition 5. http://java.sun.com/javase/technologies/desktop/

6. Java Book : The Complete Refrence

7. http://www.google.com

8. http://www.microsoft.com

9. http://www.programmer2programmer.net

10. http://www.codeproject.com

11. http://www.msdn.com.

***

Vita : Self Introduction Urvashi srivastava, the MCA student of GEU was born on 16th Oct, 1993 in Lucknow, Uttar Pradesh. She passed her High School and Intermediate Examination conducted by C.B.S.E Board in the year 2009 and 2011, respectively. She obtained her graduate degree from BNPG College Affiliated to MohanLal Sukhadia University of Udaipur, in 2014. She was admitted for the MCA(L). Program in the department of Computer Application, Graphic Era Deemed University, Uttrakhand in 2014-15. Address Urvashi Srivastava D/O Sh. A.C Srivastava Qtr.No. 260/8 CR Camp IMA Premnagar Dehradun Uttarakhand Email- urvashisrivastava234s@gmail.com

***

***