01-11-2016, 02:08 PM
1462986315-LibraryManagementSystem.docx (Size: 223.58 KB / Downloads: 5)
ABSTRACT
The Library Management System is designed & developed for a receipt and issuance of books in the library along with the student’s 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.
Introduction :
A development process consist of various phases, each phase ending with a defined output. The main reason for having a phased process is that it breaks the problem of developing software into successfully performing a set of phases, each handling a different concern of software development. This ensures that the cost of development is lower than what it would have been if the whole problem was tackled together. Furthermore, a phased process allows proper checking for quality and progress at some defined points during the development (end of process).Without this one would have to wait until the end to see what software has been produced.
Benefits:
Accurate Information around the clock
Information about the library database is accurate at any given point of time since its all automatic and updated after every transaction.
Maintenance is easy
Managing the database is easy and so is its maintenance. It does not require much of care and goes on until it isn’t affected due to heavy trafficking.
Sorting of data
Data is stored in different databases and sorted into different tables to differentiate content and it can easily converted into reports for presentations.
TOOL & languages:
• Java language
• Net beans IDE 7.0.1
• SQLITE manager
METHODOLOGY & SOFTWARE LIFECYCLE FOR THIS PROJECT:
• Login
• Books
• Borrower detail
• Issue books
• Return books
• Logout
Feasibility Study
Feasibility is a determination of whether or not a project is worth doing. Feasibility Study is performed for determining the feasibility of a project. The content and recommendations of such a study will be used as a sound basis for deciding to proceed, postpone, or cancel the project. In the conduct of feasibility study, we will usually consider following inter-related type of feasibility. They are:
Technical feasibility
We concern here with specifying Equipment and software that will satisfy the user requirement. It will run on any platform (machine), since the C# is considered platform independent. It will run with minimum system requirements and with minimum system resources acquired during run. It will need a web server, to which it gets from the internet, at run time. Expandability will be maintained in the new system. New modules can be added later on the application, if required in the future.
Operational feasibility
The system will be easy to use as user interface is GUI based. The system is easy to use so no any special skills will be required to use the system. New user will find it easy to use. So the project will be operationally feasible.
3. Economic feasibility
The procedure is to determine the benefit and savings that are expected from the project and compare them with the cost. As internet is the cheapest way of communication, we can perform communication using web. The cost is just the cost of using the internet based on the channel allocation. So the project will be economically feasible.
4. Social feasibility
The project will be socially feasible as today’s user want quick services in everywhere.With the help of web based shopping we can make business with others instantaneously in just seconds, in a large geographical area.
In feasibility study phase we had undergone through various steps which are describe asunder:
1. Identify the origin of the information at different level.
2. Identify the expectation of user from computerized system.
3. Analyze the drawback of existing system (manual) system
Software and hardware requirements
Functional requirements:
• Book entry: In this module we can store the details of the books.
• Register student: in this module we can keep the details of the new student.
• Book issue: This module is used to keep a track of book issue details.
• Book return: This module enables to keep a track of return the books.
3.3 Performance requirements: The capability of the computer depends on the performance of the software. The software can take any number of inputs provided the database size is larger enough. This would depend on the available memory space.
1. Design constraints :Each member will be having a identity card which can be used for the library book issue, fine payment etc. whenever library member wish to take a book, the book issued by the library authority will be check both the book details as well as the student details and store it in library database. In case of retrieval of book much of human intervention can be eliminated.
2. System attributes :
• Maintainability: There will be no maintained requirement for the software. The database is provided by the end user and therefore is maintained by this user.
• Portability: The system is developed for secured purpose, so it is can’t be portable.
• Availability: This system will available only until the system on which it is install, is running.
• Scalability: Applicable.
Hardware requirements:
• Operating system : window
• Hard disk :40 GB
• RAM : 256 MB
• Processor : Pentium®Dual-core CPU
Future Scope
FUTURE SCOPE
This application can be easily implemented under various situations. We can add new features as and when we require. Reusability is possible as and when require in this application. There is flexibility in all the modules.
SOFTWARE SCOPE: Extensibility
This software is extendable in ways that its original developers may not expect. The following principles enhance extensibility like hide data structure, avoid traversing multiple links or methods, avoid case statements on object type and distinguish public and private operations.
Reusability:
Reusability is possible as and when require in this application. We can update it next version. Reusable software reduces design, coding and testing cost by amortizing effort over several designs. Reducing the amount of code also simplifies understanding, which increases the likelihood that the code is correct. We follow up both types of reusability: Sharing of newly written code within a project and reuse of previously written code on new projects.
Understandability:
A method is understandable if someone other than the creator of the method can understand the code (as well as the creator after a time lapse). We use the method, which small and coherent helps to accomplish this.
Cost-effectiveness:
Its cost is under the budget and make within given time period. It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy the entire requirement. Scope of this document is to put down the requirements, clearly identifying the information needed by the user, the source of the information and outputs expected from the system.
Conclusion
From a proper analysis of positive points and constraints on the component, it can be safely concluded that the product is a highly efficient GUI based component. This application is working properly and meeting to all user requirements. This component can be easily plugged in many other systems.