LIBRARY MANAGEMENT SYSTEM

like link:

Uid: yasir.jaseem@gmail.com

Pwd: admin

Download Complete Source Code:

LMS

Database

Plateform:

PHP Codeigniter Platform

Table of Contents

Table of Contents.......................................................................................................................... iii

Revision History............................................................................................................................ iii

1. Introduction.............................................................................................................................. 1

1.1 Purpose............................................................................................................................. 1

2. Overall Description.................................................................................................................. 1

2.1 Product Perspective.......................................................................................................... 1

2.2 Product Functions............................................................................................................. 2

2.3 User Classes and Characteristics....................................................................................... 2

2.4 Operating Environment..................................................................................................... 2

2.5 Assumptions and Dependencies....................................................................................... 3

3. External Interface Requirements........................................................................................... 3

3.1 Hardware Interfaces......................................................................................................... 3

3.2 Software Interfaces........................................................................................................... 3

3.3 Communications Interfaces.............................................................................................. 3

4. System Design........................................................................................................................... 4

4.1 Application Architecture................................................................................................... 4

4.2 Database Modeling and Design......................................................................................... 4

5. System Testing.......................................................................................................................... 4

5.1 Functional Testing............................................................................................................ 4

5.2 User Acceptance Testing.................................................................................................. 4

6. UML Diagrams........................................................................................................................ 5

6.1 ERD.................................................................................................................................. 5

1. Introduction

Library Management System is an online project where manager issue the books to registered students. This is a web based application where admin can add user, delete user, add book, delete book, issue book to the student, and make duplicate of the book.

1.1 Purpose

The purpose of this project is to keep track even a single book of library and record the history of books whenever is issued to students.

2. Overall Description

2.1 Product Perspective

Library Management System is a real time application. Through this project all manual record of the library can be computerized and minimize the chances of errors. This is a web based project where manager issue the books to registered students. In this application admin can add user, delete user, add book, delete book, issue book to the student, and make duplicate of the book.

2.2 Product Functions

The functions of the system include

The admin can create users.
The admin can delete users.
The admin can edit users.
The admin can add students.
The admin can delete students.
The manager can add book in the system.
The manager can edit book.
The manager can delete book when it is lost.
The manager can issue book to the student.

2.3 User Classes and Characteristics

There are three types of user for the Help Desk Software:

Administrator: Admin of the system. He is responsible to add, update, delete users and student.
Manager: Manager of the library. He is responsible to add, update, delete book in the library and issue to the student.
Student: Student of the campus. He will issue books from library and responsible to return the book on time.

2.4 Operating Environment

This application is compatible with any browser that supports HTML5.

2.4.1 PHP

PHP is a server-side scripting language that provides database access, form processing, user authentication. In short, it has the capabilities for developing the Library Management System with all of the functionality described in the requirements’ analysis. It is used in conjunction with the Apache web server. It will also run on both Microsoft Windows and on the Linux platform.

2.4.2 My SQL Database

There are many different relational database management systems (RDBMSs) from a number of software manufacturers. Library Management System’s Analysis, design and implementation of a system decision to use My SQL is consistent with the choices made with the rest of the infrastructure.

2.5 Assumptions and Dependencies

· The user should have sufficient knowledge about computer.

· The computer should have internet connection and web browser.

· The users know the English language, as the interface will be provided in English.

3. External Interface Requirements

3.1 Hardware Interfaces

-|- Client Side: PC

-|- Server Side: PC

3.2 Software Interfaces

-|- Front End Client: CSS, HTML5

-|- Data Base Server: My SQL

-|- Back End: PHP

3.3 Communications Interfaces

· Web Browser (Internet Explore, Firefox, Chrome)

· Internet connection

4. System Design

4.1 Application Architecture

The architecture of the application is designed to fit into the infrastructure at Library Management System which leads to a distributed n-tier application. This is defined as a model that helps developers to create flexible and reusable applications by breaking it up into different tiers. As a result, it is likely that if changes are made to a single tier, it is possible that the entire application will not need updating when those changes are made.

4.2 Database Modeling and Design

A sound database design will be the key to the success of this system. By ensuring that, at this stage, all the relevant information is incorporated into the system, the rest of the system design will fall easily around the database. Database design is generally thought to involve the modeling of different Entities, Relationships and Attributes. the design of the database is broken down into different stages:

Conceptual database design

Logical database design

Physical database design

5. System Testing

5.1 Functional Testing

The sole aim of the functional testing carried out is to ensure that the user cannot ‘break’ the system by entering erroneous data, where certain functionality has not been implemented. Library Management System has agreed that future developments will address this absence. Because of the prototyping approach, coupled with the fact that a second iteration now needs to be developed, it is felt that the tests provide some very positive feedback about the system. One of the most significant outcomes of the functional testing is the uncovering of the fact that field validation needs to be implemented on each of the forms.

5.2 User Acceptance Testing

At the beginning of this project, after all the requirements capture and analysis had been undertaken, it was necessary for Library Management System to sign-off the requirements list and for them to have an understanding of what would be included in the first prototype. More important than the validation testing is the acceptance from the Users that it works as they expect it to.