2. Project Title
Introduction
Feasibility
Specific Requirements
Tools and Platform
Resources Used
Design Specification
Entity Relationship
Diagram
Data Flow Diagram
Data Base Structure
Snapshot
Modular Description
Process Logic
Reports
Future Scope
3.
4.
5. 1. Purpose:-
The purpose of this application is as follows:
The software is for automation of library.
It provides following facilities to
1.1 Operator:
Can enter details related to a particular book.
Can provide membership to members.
1.2 Admin:
Can read and write information about any member.
Can update, create, and delete the record of membership as per requirement and implementation.
6. 2. 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.
3. 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.
4. 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 them.
5. Functionality :
Online membership.
Keeps the track of issues and submission of books.
8. Feasibility
In feasibility study phase we had undergone through various steps which are describe as under:
1. Identify the origin of the information at different level.
2. Identify the expectation of user from computerized system.
3. Analyze the draw back of existing system (manual) system.
Working of present manual system:-
The staffs of library are involved in the following tasks.
1. Membership process : person have to fill membership form and they are provided with member id.
Drawbacks of present system:-
Some of the problems being faced in manual system are as follows:
1. Fast report generation is not possible.
2. Tracing a book is difficult.
3. Information about issue/return of the books are not properly maintained.
4. No central database can be created as information is not available in database.
9. 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 facility for proper monitoring reduce paper work and provide data
security.
5. All details will be available on a click.
10. Specific Requirements
This section describes in detail all the functional requirements.
Functionality
• Logon Capabilities
The system shall provide the users with logon capabilities.
• Mobile Devices
The Online Library System is also supported on mobile devices such as cell phones.
• Alerts
The system can alert the Librarian or the administrator in case of any problems.
Usability
• The system shall allow the users to access the system from the Internet using HTML or it’s derivative
technologies. The system uses a web browser as an interface.
• Since all users are familiar with the general usage of browsers, no specific training is required.
• The system is user friendly and self-explanatory.
11. Reliability
The system has to be very reliable due to the importance of
data and the damages incorrect or incomplete data can do.
Availability
The system is available 100% for the user and is used 24 hrs
a day and 365 days a year. The system shall be operational
24 hours a day and 7 days a week.
Accuracy
The accuracy of the system is limited by the accuracy of the
speed at which the employees of the library and users of the
library use the system.
12. Tools & Platform
My Project uses and works following tools and platforms respectively:
Front end:- asp.net 3.5(c#):-
ASP.NET is Microsoft’s new version of ASP for the managed environment. ASP.NET brings about
significant changes from its predecessor, most notably by supporting strongly typed and
precompiled languages such as C# and VB. With ASP.NET you can also design web application GUIs
using the drag-and-drop form design approach that made Visual Basic popular. ASP.NET is a
server-side technology that requires the installation of Microsoft Internet Information Server (IIS).
Some features of ASP.NET are as follows:-
Separation of code from content.
Support for compiled languages
Greater support for different browsers via server-side
Intuitive GUI design.
A quick and easy way to develop applications.
Native code compilation.
A common programming platform across all Microsoft applications.
13. Back end:-SQL server 2000:-
Microsoft SQL Server 2000 is a full-featured relational database management system (RDBMS) that offers a variety of
administrative tools to ease the burdens of database development, maintenance and administration.
Features of SQL server 2000:-
Plenty of features are available in SQL Server that makes it stand out from all its competitors. Some of the important
features describe bellow-
The graphical management tools make it extremely easy to manage the server. Major GUI is SQL enterprise manager.
This tool allows you to manage window NT, Internet information server and many other products from single
application.
Centralized management help in managing multiple servers from one place that is only one administrator is needed for
all servers.
SQL Server 2000 supports multiple client application.
SQL Server 2000 enterprise edition can support database larger than several terabytes with more than 32 processors.
For large-scale production purpose SQL Server 2000 runs on window NT & Window 97/98.
Development cost by SQL Server 2000 is less expensive than any other RDBMS.
SQL Server 2000 is perfect for managing large data warehouses. Data warehouses are usually extremely large database
that contain data from transactional oriented databases.
14. Resources Used
Hardware Recourse
PROCESSOR : P4
RAM : 512 MB recommended
HDD : 20 GB (min 10 MB virtual Space)
MONITOR : 17 CRT
KB : Normal GB
MOUSE : 3 Button Normal Mouse
Software Resource
O/S : Microsoft Windows XP/2000 Server
For Coding : Visual Studio 2008(C#)
For Database : SQL Server 2000
For Reporting : Crystal Report
For Documentation : MS Word, MS PowerPoint
15. Design Specification
ERD (Entity Relationship Diagram)
It is clear that the physical objects from the previous section – the
member, books, library – correspond to entities in the Entity-
Relationship model, and the operations to be done on
those entities – holds, checkouts, and so on – correspond to
relationships. However, a good design will minimize redundancy and
attempt to store all the required information
in as small a space as possible.
16.
17.
18. Database Structure
Id_no Number 50 Unique identification
of the members
Name Text 70 Name of members
Address Text 100 Location of Members
Date of
Issue
Text 25 Date of Registration
Date of
Expiry
Date/Time 10
Registration expiry
date
Status Date/Time 50 Permanent/Temporary
FIELD NAME DATA TYPE SIZE Description
19. Book_name Text 10 Title of the book
Book_code Text 15 Book identification
number
Author Text 10 Author of books
Date of
arrival
Date/time 10 Date on which book
was
received
Price Text 10 Cost of books
Rack_no Text Almirah no
No_of_books Text Quantity of books
Subject_code Text Unique identification
no of
particular subject
TABLE NAME: Add Books
20. Id_no Text 10 User identification
number
Book_name Text 10 Title of books
Issue_date Date/time 10
Date on which book
is
issued
Due_date Date/time 10
Due date on which
book is
to be returned
TABLE NAME: issue
FIELD NAME DATA TYPE SIZE Description
21. Id_no Text 10 User identification
number
Category_id Text 10 id of category
Isbn Text 10 Isbn of book
Category_Name Text 10 Category name
TABLE NAME: Book By Category
FIELD NAME DATA TYPE SIZE Description
Id_no Text 10 identification number
Author_Name Text 10 Author Name
Isbn Text 10 Isbn of book
TABLE NAME: Book By Author
FIELD NAME DATA TYPE SIZE Description
22.
23.
24.
25.
26.
27. Module Description
Type of user
Administrator (librarian)
HOD of all Department
Student
Faculty
Staff
Administrator module:
Budget (for all department)
Stock verification
Create user
Accept/Reject user
Change password
Book inventory
User information
Report generation
Search Book
28. Complaint All user can send their complaint
User module
Change password
Book Search
See account information
Fine information
All user check their fine
Fine by date & Month
Book inventory
Purchasing book information
Maintain book inventory
29. Book search
Normal search by alphabet
Quick search by type(Book id, Author, ISBN,Publication)
Other charges
Book Binding, chair , Rack
Journals
News paper
32. Reports
Reports provide information about metrics that are collected while a team
project is in progress. The information is used by project managers and leads to
monitor the health of the team project and to make decisions. As we create new
reports or modify existing reports, we can provide documentation in the process
guidance to help team members understand the purpose of the reports and how to
interpret the reports. If we add new reports or queries to our process template, we
should also add them to our process guidance, along with description of how they
should be used in our software development process.
33. Type of Reports: -
ID Wise:
Book Detail
Author Detail
Issue Detail
Stock Detail
Bill Detail
Employee Detail
Salary Detail
Date Wise:
Book Registration
Bill Payment
Author Detail
Stock Detail
34. Future Scope
We are developing our project Library Management System for the college or any Institute.
But this project can be deployed in any organization.
The Online Library System that is to be developed provides the members of the Library and
employees of the library with books information, online blocking of books and many other
facilities