Вы находитесь на странице: 1из 9

Table of content

Content Page
Introduction
Project overview 1
Problem statement 1
Objective
Scope 1
2
Content
Methodology 3

Diagram 8
Reference 9
Gantt chart 10

1
Project Overview

The Library Management System will store all the books and members information that
consist book number, book title, author name and racks to the system database. The system
also provides search function to help students to find the book by book number, book title and
author name. The search function will search through the books database to look for the book
and view where the book is situated. The system also let the students to issue and return
book, update information, rate and recommend book, reserve book and pay their due online.
For the administrator user, only librarians have access to view or edit data from the system
databases. Administrator user will handle administrator functions such as create user account
and decide the number of days allowed for the borrowed books. Students need to enter
correct password and use student id card before students can access those functions.

Problem Statement

Since the amount of students and books is increasing, it is necessary to find a space to store
them. However, they will not last longer, the record book will be stockpiled. It need well
organized and it is hard to find the record in a short time. This will cost a lot of time and not
efficiency at all. Therefore, we decided to make the Library Management System more
computerized to improve the situation.

Objectives

1. To build a system that can receive input and generate automatically output in easy
way and short time.
2. To build a system that provide more convenience to user.

2
Scope

This system is built for Universiti Malaysia Sarawaks library, the system will store
information of all books and record of borrower. However, only the librarian who have
specified access such as administrator can handle administrator functions of this library
system. This can avoid unauthorized user to enter the restricted area of this system especially
system databases. There are some functions:

1. Provide the list of availability of the books.

2. Authenticate user identity by using matric card.

3. Ability to reserve books.

4. All the users are able to view the books reserved by them.

5. Ability to cancel their reservation of the books.

6. Ability to view the due date of the borrow books and the penalties of late returned.

7. Available to rate the system.

8. List of recommended books.

Methodology

The Library Management System is built up by the waterfall model. There are few reasons
why we choose the waterfall model.

Why waterfall model

1. Requirements were well known, clear and fixed.


2. Do not have particular customer, so the possibility of requirements changes is less.
3. Project is short as we have identified six features to include in the first release.
4. Once the product is ready then it can be customized and deployed in the user
environment to make it available to end users.
5. Once the product is developed, we can add few more features in future releases.

Requirement
Definition 3

System and Implementation and Integration and Operation and


Software Design Unit Testing System Testing Maintenance
Figure 1: Waterfall model

1. Requirement

A good system development practice starts with a good system analysis. Before
developing a system, the objectives of the system must be understood thoroughly and
the functional and non-functional requirement of the system must be elicited.
(Library Management System Waterfall Model, 2015)

Functional requirement

1. Barcode Scanning: We will be using an electronic device which will scan the
barcode to issue and return the books.
2. Rating and Recommendation: The users can provide a feedback while returning
the book. A user can provide ratings and recommendations to a particular book,
can write about their experience and also provide recommendations for any future
user.
3. Account Management: This feature will allow the users with many features like
update information, pay due, manage reserved book, view history.
4. Catalog Management: This feature will allow the users with many features like
search functionality, log off feature, reference book functionality, book
availability.
5. Self-check in/Self-check Out: Here user can issue the book by itself by scanning
the barcode of the book and swiping its Id card wherein no need of librarian is

4
required. User can also return the book by just swiping the barcode of the book
and can check out the book from his name.

Non-functional requirement

1. Performance
The system database shall accommodate high number of books and users
without any fault.
Responses to view information shall take no longer than 5 seconds to
appear on the screen.
The system should be able to support 300 users and 550 requests / minute
concurrently.
2. Availability
The software should be available 24 hours a day and specifically during
the working hours.
Database backup and recovery plan should be proper in order to avoid any
unexpected downtime of application.
3. Security
System will have different types of users and every user has access
constraints.
Software will be connected to secured database.
Normal users can just read information but they cannot edit or modify
anything except their personal and some other information.
Administrator will have full access to the system to resolve any issues.
Librarian will have access to application with restriction to database
access.

4. Error Handling
System shall handle expected and non-expected errors in ways that will
prevent loss in information and long downtime period. Prevention and
necessary downtime will be taken to prevent any impact on the system.

Minimum Software Requirement

Operating system: Windows XP, Windows 7 or better

Language: Java 7 Runtime Environment or better

Front End: Netbeans 7.3.1

5
Back End: MySQL server 5.0

Minimum Hardware Requirement

Processor: Pentium IV or better

RAM: 128 MB or more

Hard Disk: 20GB

Monitor: Any

Keyboard: 122 keys

2. System and software design

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.
(Shahaditya, 2014)

Output Design

Output from computer systems are required primarily to communicate the results of
processing to users. Computer output is most important and direct source of
information to the users. The right output must be available for the people who find
the system easy to use. (Shahaditya, 2014)

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. The general objective is to make
information access, easy quick, inexpensive and flexible for other user.

6
3. Implementation and Unit Testing

Implementation phase is the stage where the system unit is produced. Each unit is
tested to verify that it meets its specification. In the Library Management System
project, several subsystems are building simultaneously from individual components.
Each subsystem is tested as new components are coded and integrated into the
evolving software. Each unit is developed and tested for its functionality.

4. Integration and System Testing

After each unit is developed and tested for their functionality, these units are
integrated into a complete system during Integration phase and tested to check if all
the units coordinate between each other and the system as a whole behaves as per the
specifications. After successfully testing the software, it is delivered to the customer.

5. Operation and Maintenance

Generally, problems with the system developed which are not found during the
development life cycle come up after its practical use starts, so the issues related to
the system are solved after deployment of the system. Not all the problems will occur
directly but they will arise time to time and need to be solved.

Diagrams

Figure 2: Interface for Member Registration

7
Figure 3: Interface for Login

Figure 4: Interface for Main Page

Gantt Chart

8
References

Shahaditya. (2014, February 14). Library Management System. Retrieved from


http://www.slideshare.net/shahaditya/library-management-system-31197877

Library Management System Waterfall Model. (2015, April 5). Retrieved from
http://www.slideshare.net/mitwa1990/library-management-system-waterfall-model
https://ru.scribd.com/document/351530003/Library-Management-System
ru.scribd.com
crawl=CC-MAIN-2020-34
382429
application/http; msgtype=response
sha1:PYIYY7B2OIGJBXZRZSEPHTZMZBHSLPXU
<urn:uuid:69748f6c-73f4-4dda-923c-6f76a9ce77d4>
2020-08-08T12:44:55Z
199.232.66.152
application/xhtml+xml
sha1:UWQO7OGKYK2OXOUPZOOVSSICYYSF3NE5
<urn:uuid:497e1725-1d15-4c5d-82e8-9df1e76893a3>
https://ru.scribd.com/document/351530003/Library-Management-System
response
<urn:uuid:44c3b2b8-1552-4411-b93d-80be6947b6f3>
isPartOf: CC-MAIN-2020-34
publisher: Common Crawl
description: Wide crawl of the web for August 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-181.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/