Library Management System

Supervised By:
Submitted By:
Dr. Zaw Tun
4CS 364 Ma Naw Zin Mar Myint
Associate Professor
4CS 370 Ma Hsu Hnin Wai
4CS 374 Mg Kyaw Soe Win
4CS 395 Ma
Moe Thu Khaing
4CS 413 Ma Lin Lin Thu
4CS 428 Ma Ei Lwin Ko

Objective
To handle the entire activity of a library.
To provide easy system circulation using computers rather

than writing system.

To modernize library database, where data was stored in a

card-based catalog.
To optimize the system users work and time.

Introduction
System has 2 users: Admin & Receptionist.
System allows Admin to:

- add/remove books to/form the library database.

- order books alongside the requests of the members
- maintain the system run operationally.
System allows Receptionist to:

- search librarys books

- move books physically and update the location in system.
- receive the notifications of the system.
- check the availability of the requests manually
3

Functional Requirements
Store necessary information about items in the library database.
Store information about the library members.
Allows search of item by author, title or keywords.
Notify the members automatically by e-mail.
Generate reports like overdue notification, requested items

availability and so on.

Store information about each shelf in the library.
4

Non-Functional Requirements
A book cant be hold for a member for more than 7 days.
As an exception, the books can be hold up to 14 days if the

members occupation is master or higher.

If the member is under-graduate and wants to reference thesis

books, the books have to be returned before 2:30 PM on day.

A member has to be fined 5 Ks per day for overdue items.
A member can borrow at most 2 books once.
The capacity of a shelf is average 50 books depending on the

thickness of books.
5

User Requirements
Users should have the basic knowledge about the internet and

web related applications, and the basic computer using.

Legal Requirements
- All personal information should be protected.

Usability Requirements
Systems interface has to be easy to understand.
The interface should contain prompts and helps to avoid

making mistakes.
The product should be used by people with not further training

about the system.

Performance Requirements
Any interface between a user and system should have a

maximum response time of 5 seconds.

The response should be fast enough to avoid users response
collisions.

Operational Requirements
- The system should be correctly implemented in different

Internet browsers.

Mandatory Constraints for Client PC

Hardware
- IBM-compatible PC with Pentium I processor and higher.
- 50 MB free space on HDD
- 32 MB RAM
- Internet connection

Software
- MS Windows XP/Vista/7
- Any browser which supports PHP

Mandatory Constraints for Server

Hardware
- IBM-compatible PC with Pentium III processor and higher.
- 80 GB free space on HDD
- 256 MB RAM or higher

Software
- MS SQL server an MS Access (Database server)
- MS Internet Information Server (Web server)

10