Sunteți pe pagina 1din 18

ONLINE LIBRARY MANAGEMENT SYSTEM

Tayyab Anwar BM-09226 Utkarsh Verma BM-09239

1. PROJECT MANAGEMENT PLANNING


Objectives: This software is for automation of library. Design and implement a library database based on a standard library classification system. Build an advanced search that can help for the best handling of user queries, this search should handle different search types like searching by author, title, subject, format or any combination of them, or searching by ISBN, or Publisher and Publication date. The search result should contain information about the exact location of the book. Build the interface between the online screens and the library database system.

Operator Can enter details related to a particular book. Can provide membership to members. Admin Can read and write information about any member. Can update, create, and delete the record of membership as per requirement and implementation plants.

SCOPE The different areas where we can use this application are: 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. Reception activities. Sales transactions. Accounting system. Book store follow up. Using Internet facilities to connect all branches together.

2. Establish Project Infrastructures


1. Requirements Specification Complete specification of the system (with appropriate assumptions) including the database design (for storing the books/journals details). A document detailing the same should be written and a presentation on that be made. 2. Technology familiarization Understanding of the technology needed to implement the project. 3. High-level and Detailed Design Listing down all possible scenarios (like searching for book/ journal, reserving a book/ journal, cancelling the reservation, submitting a purchase application for new books etc) and then coming up with flowcharts or pseudo code to handle the scenario. 4. Implementation of the front-end of the system Implementation of the main screen giving the login, screen that follows the login giving various options, screens for students/faculty and librarian for the various functions etc.

5. Integrating the front-end with the database The front-end developed in the earlier milestone will now be able to update the books/journal database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing. 6. Testing The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). 7. Final Review Issues found during the previous milestone are fixed and the system is ready for the final review.

3. Analysis of project characteristics


ASSUMPTIONS This application is used to convert the manual application to the online application. Customized data will be used in this application. User does not have right to enter information about books. OVERVIEW Project is related to library management, which provides reading services to its members. Any person can become a member of the library by filling a prescribed form. They can get the book issued, so that they cab take home and return the

4. Identify project products and activities


PROPOSED SYSTEM There will be three major components: 1. Stock maintenance. 2. Transaction entry. 3. Reports. Proposed system provides with following solutions: 1. It provides "better and efficient" service to members. 2. Reduce the workload of employee. 3. Faster retrieval of information about the desired book. 4. Provide facilities for proper monitoring reduce paper work and provide data security. 5. All details will be available on a click.

5. Estimate efforts for each activity

6. Risks Associated with Activity


RISKS Requirement specification is not clear. Loss of Transactions due to movement from manual to automated system in data integration process. Deterioration of data during manual conversion. Planning goes absurd Require a lot training Missing Deadlines Defects in the end product due to Problems during integration. Difference in standards followed like naming Convention

ACTION PLAN (To avoid risk) Proper communication between development team and user. Regular discussions between the teams. Provide professional trainers. Planning day to day activities keeping in mind slacks and float. Continuous database up gradation and checking.

7. Allocate resources
Hardware requirements PC with 2 GB hard-disk and 256 MB RAM

Software requirements Windows 95/98/XP with MS-office Oracle ASP.NET Java

8. REVIEW OF PROJECT PLAN


Evaluating the performance of project development stages ,and comparing against the set milestones , alternatives actions like rescheduling the plan or project deliverables are validated and a modified set of action plan is being created so as to keep project on tine and also the tradeoff between resources available and requires is being found so as to allocate the resources during the implementation of modified developed plan .

PROJECT SIMULATION The developed software is being tested through simulations before real implementation. The software is tested for integration of different modules and the cohesion and coupling of modules so as to ensure proper functioning of the system. The system is installed and test cases and input are given to test the validity of system so as to find any inconsistency or functional errors by cross checking the produced outputs against the output desired in test cases.

PROJECT DOCUMENTATION Starting from the planning stage through requirement analysis, feasibility study, design of library management system all the report/Outputs of each stage of software development process are recorded in Project documentation. For library management system the documentation will contain

1) Business case for library management System. 2) Requirement Specification report. 3) Detailed Design Report
Logical Design Physical Design

4) Business Process Report for Library Management System 5) Implementation Plan Documentation including the methodology and constraints specifications.

Project Simulation
The developed software is being tested through simulations before real implementation. The software is tested for integration of different modules and the cohesion and coupling of modules so as to ensure proper functioning of the system. The system is installed and test cases and input are given to test the validity of system so as to find any inconsistency or functional errors by cross checking the produced outputs against the output desired in test cases.

9&10 Execute Plan