Library Management System Software Development Stages

1. Analysis

Analysis involves a systematic evaluation of the different activities conducted inside and

outside of a system and its relationships. This includes knowledge collection and the use of

formal research methods. One feature of research is the definition of scheme borders and the

consideration of other similar schemes by the applicant system. The details on open files,

decision points and transactions processed by the current system are being obtained during

research. The researcher has a clear idea of what can be done after the research is complete. The

next move is how to fix the dilemma.

The Library management system has the system administrator, students’ users and

visitors who are the unregistered users. The system admin performs the user’s password

verification login, register a new book to the system and also delete the borrowed old book from

the system.

For the student users, they can verify their login especially after inputting wrong login

details. Students can also borrow the books, return the borrowed books and also look for their

borrowed books and circumstances like fines and late book returns.

Visitors can check out all the information about books but however do not have the

ability to borrow books.

The Library Management System has master library document like book descriptions,

information about the library, inserting and updating of records. The new books will be

automatically by activities like book issue and return. The system would care for the particular

1
specifics of the most recent books at the moment. Book holding and return will automatically be

automatically updated to offer the latest book details to the users.

User features

1. User model

Verify the book availability and book return

2. Administration module

a. User registration

b. Book details entry

c. Book issuance

General constraints

To provide an accurate and most updated values. All changes about books are

instantly updated.

Specific requirement

External interface requirement

Has to be so simple and easier for consumers to understand and have ease of use.

Should have an immersive interface where the user and the system admin should have

the system prompt the login and make corrections on the constraints.

User interface

It has a nice gui which can be run in performing and handling specific tasks like

design, review, display and book details. Users can access faster reports in real time.

Stock verification and search services basing on various needs.

2
 Hardware interface

1. Windows operating system

2. 4.0 Gb hard disk

3. Dual core CPU Processor

4. 257MB RAM

Software interface

1. Java programming language

2. NetBeans IDE 7.0.6

3. MS SQL server 2008

Windows communication interface

Functional requirements

1. Book entry where we can store information about books.

2. Register student where new student’s data is stored

3. Book issue where we keep records of books issued

4. Book return where we keep track of books returned.

Performance constraints

The library management system relies on the computers capability and efficiency When

database is large enough the system will allow storage of huge inputs. This is entirely reliant on

the availability of the memory.

Nonfunctional requirements

3
 1. Maintainability. The library management system will need update and

servicing. Database is built by the end user and therefore must be retained

by the same end user.

2. Portability. This system is stable and so can be installed in any device

making it portable.

3. Availability. The system will be able to operate on the system in which its

built on.

4. Scalability. The system is scalable according to user system requirements.

3. Design

The Library Management System consists of 3 main flow charts

1. The administration flow chart where, the administrator can inquire book number, add

new book to the system or delete old book from the system.

2. The user flow chart where, users can borrow books from the library, return borrowed

books to the library, inquire about books or sign out of the library management

system.

3. The system login flow chart where, you can inquire the book number, get to the

student flow chart or the administrator flow chart.

Detailed focus on the technological and additional requirements for operation of a new

system are discussed in the system architecture. The configuration of inputs and the conception

of output reports in a manner suitable to the consumer is a significant step. The system

4
architecture offers the requisite insight and procedural information to execute the System as the

feasibility study recommends

Library management state machine diagram

5
Library management state machine diagram

6
 The state machine begins by a student inquiring about a book they would wish to borrow

from the library management system. The system then checks for the book availability. If the

book happens to be available then the system proceeds to verify the member (student) else, the

system halts. The system then checks if the member is registered, if no the member is notified to

register before proceeding to the book borrowing. If the member is registered, the system checks

the number of books borrowed by the member, if the maximum number required is exceeded

then the system halts else the member is issued with the book. After registering the member, the

book, member and issue details are updated then the system halts.

4. Implementation

The system is composed of three different parts: admin, student users and non-registered

users (visitors).

Password Authentication Login: only the manager enters the right account with a correct

password, the admin interface can be entered. Administrators have the following features. If the

error is entered, the system will indicate the account error and the administrator system gui

cannot be entered. Likewise, the code displays a login error if you type an incorrect password,

and you cannot access the system interface of the administrator. Register a new book: the

manager will enter simple book data while he is active in the book system and add a new book.

Register a new book. Uninstall the old book: the book number (unique identity book) can be

entered by the administrator to remove books.

The following features are available to student users: 1) Checking of passwords Login:

The administrator interface will only enter the right account and password for the user. The code

shows the account error and cannot type the user system interface if you access an incorrect

account. Likewise, the code will display password errors if you type the incorrect password, and

7
you will still not be able to enter the user system interface. 2) Borrow books: the borrower

successfully enters the book number and his proper book borrowing account and password. 3)

Return books: only the customer can enter the number of books bought and their valid account

and password to successfully return the book. If the author did not buck this book, "never

borrowed the book" would be output from the device. If the username or password is incorrect,

"account mistake" or "password error" are output by the machine. 4) Look up the books and

personal conditions you borrowed: the customer is able to see the general facts and the books

you borrowed.

The role of unsuccessful users (visitors) is to search any book detail, but they are not able

to borrow books. You may also register new users by completing the basic details of the student.

5. Testing

In the system lifecycle, software testing plays a vital part. Computer monitoring is only in

operating and servicing of standard waterfall models and is a vital way of ensuring that the

software is quality before the software items are supplied to the customer. The class of software

engineers recently seems to believe that each phase of the evaluation involves the lifecycle of the

software such that the effects of the phase are tested as they are closest to the goal to be reached,

to identify defects and modifications as quickly as possible. Unless early testing is carried out,

the misrepresentation of the interval leads sometimes to a considerable challenge in the final

product evaluation.

The framework entirely uses code blocks programming methods, so the demanding

software runtime environment is more popular and easier to work. System testing: using manual

8
testing methods for system testing and starting from the application debugging for the purpose

that software architecture has to compile a lot of code. However, it's most much inaccurate. Test

each module if no error is found. Then attach it to other modules after passing the test to see if

the overall architecture is fair. At the start of the evaluation, data in the actual case cannot be

performed and well-designed data could be used as a test case. This reduces the processing

overhead and also makes it possible to assess the error and the scope of the error. The test object

functional test should be focused on all test criteria specifically linked to case use or business

functions. Use a black box evaluation approach mostly to test such device modules:

The login page is red for the administrator, and the login page is blue sky for the user.

When there are errors more than three times in the username account and password, it is

suggested to join again.

New stock of books Inputting the right password, entering the add books feature modules

on the administrator page and displays whether books can be added after the latest book

information has been entered.

Delete old books, you must pick the book delete feature in the administrator page and

enter the book details. If the book isn't available, the book should not exist promptly. When you

successfully find the book and validate the deletion of it, you will successfully remove the book

and see if it was successfully removed in the question module.

User Management Administration will handle user records, change user privileges, log

users out and even initialize passwords for user logins, but managers cannot add users at the will.

9
 Borrowing books Upon the user successfully logs in, select the loan feature, enter the

appropriate book details, the borrowing books operation is accomplished. And before confirming

user information you can't borrow books; the machine changes the book borrowing information

simultaneously.

Books Return. You will return the book after the student has borrowed the book. When

you return the non-loaned copy, it would be suggested if you have lent or returned the book. And

framework changes the details for the book borrowing simultaneously.

Investigation of the library the book query feature for viewing books may be selected by

users. The question number, bible query and fuzzy query can be selected. The related book

details will be shown in the system. The resulting book may be accessed if the user selects a

flashy question and inserts a keyword such as part of the title.

Register of Users On the guest page visitors will register the user. After you enter the

legal user number and user details you will register as a user. You can now set up your own

password and log in to the login page.

10