ONLINE LIBRARY MANAGEMENT SYSTEM FOR JJU

2015

Table of Contents
List of Figures.............................................................................................................................................IV
List of Tables................................................................................................................................................V
Abstract.....................................................................................................................................................VII
Acknowledgment......................................................................................................................................VII
CHAPTER ONE..............................................................................................................................................2
1 .Introduction.............................................................................................................................................2
1.1 Background............................................................................................................................................3
1.2. Statement of the Problem....................................................................................................................3
1.2.1 Justification of the current system.................................................................................................3
1.3. Objectives.............................................................................................................................................4
1.3.1. General objectives.........................................................................................................................4
1.3.2. Specific objectives..........................................................................................................................4
1.4. Scope of the Project.............................................................................................................................4
1.5. Methodology........................................................................................................................................5
1.5.1. Data gathering tools......................................................................................................................5
1.5.2. Analysis and design........................................................................................................................6
1.5.3. System implementation method...................................................................................................7
1.5.4. Development tools and techniques...............................................................................................7
1.6. Significance of the Project....................................................................................................................8
1.7. Risk Assessment and Management......................................................................................................8
1.8. Operating Environment........................................................................................................................9
1.8.1. Hardware requirements................................................................................................................9
1.8.2. Software requirements..................................................................................................................9
1.9 Project Plan and Time Table..................................................................................................................9
1.10 Cost Estimation..................................................................................................................................11
1.10.1. Software development cost.......................................................................................................11
1.10. Project organization..........................................................................................................................12
CHAPTER TWO...........................................................................................................................................13
2.1 Introduction.........................................................................................................................................13

JJU Page I
2.2 The main activities...............................................................................................................................13
2.3 Functions of the Existing System.........................................................................................................14
2.4 Players of the Existing System.............................................................................................................15
2.5 Report Generating in the Existing System...........................................................................................15
2.6 Documents Used in the Existing System..............................................................................................16
2.7 Weakness of the Existing System.........................................................................................................16
2.8 Strength of the Existing System...........................................................................................................16
2.9 Alternative Solution.............................................................................................................................17
3.1 Introduction.........................................................................................................................................18
3.1.1 Purpose.........................................................................................................................................18
3.1.2 Intended Audience and Reading Suggestions...............................................................................18
3.1.3. Document Convention.................................................................................................................20
3.2 Objective.............................................................................................................................................21
3.3 Functional Requirements.....................................................................................................................21
3.4 Product Perspective.............................................................................................................................22
3.5 Product Functions................................................................................................................................22
3.6 Principal Actors....................................................................................................................................23
3.7 User Characteristics.............................................................................................................................23
3.8 General Constraints.............................................................................................................................23
3.9 Assumptions and Dependencies..........................................................................................................24
3.10 Non Functional Requirements...........................................................................................................24
3.11 System Models..................................................................................................................................26
3.11.1 Use Case Models.........................................................................................................................27
3.11.2 Use Case Descriptions.................................................................................................................28
3.11.3 Sequence Diagram......................................................................................................................38
3.11.4 Class Diagram/UML....................................................................................................................45
Diagram.................................................................................................................................................45
CHAPTER FOUR..........................................................................................................................................46
4.2 Design Goals........................................................................................................................................46
4.2.1 Performance Criteria....................................................................................................................46
4.2.2 Maintenance Criteria....................................................................................................................46
 4.2.3 End User Criteria...........................................................................................................................47
4.3 System Architecture............................................................................................................................47
4.4 Subsystem Decomposition..................................................................................................................48
4.4.1 Login subsystem...........................................................................................................................49
4.4.2 Member management..................................................................................................................49
4.4.3 Book management.......................................................................................................................50
4.4.4 View report...................................................................................................................................50
4.4.5 Class Modeling..............................................................................................................................50
4.4.6 Documenting the Classes..............................................................................................................52
4.5 Deployment Diagram (Hardware/Software Mapping).........................................................................57
4.6 Persistent Data Management..............................................................................................................58
CHAPTER FIVE............................................................................................................................................60
IMPLEMENTATION AND TESTING..............................................................................................................60
5.1. INTRODUCTION..................................................................................................................................60
5.2. Algorithm Design / Coding..................................................................................................................60
5.3. Testing................................................................................................................................................62
5.3.1. Unit testing..................................................................................................................................62
5.3.2. Integration testing.......................................................................................................................62
5.3.3. System testing.............................................................................................................................62
5.4. Hardware and Software Requirements..........................................................................................64
5.4.1. Hardware Requirements..............................................................................................................64
5.4.2. Software Requirements...............................................................................................................64
5.6. User Manual.......................................................................................................................................65
5.9. Installation..........................................................................................................................................67
CHAPTER SIX..............................................................................................................................................68
6. CONCLUSION AND RECOMMENDATION...............................................................................................68
6.1. CONCLUSION......................................................................................................................................68
6.2. Recommendation...............................................................................................................................68
References.................................................................................................................................................69
Appendex..................................................................................................................................................70
List of Figures
Figure1. 1 Pictures that show the future aim of the project----------------------------------------------
Error! Bookmark not defined.

Figure3. 1 Use case Diagram for Library system--------------------------------------------------------

Error! Bookmark not defined.

Figure3. 2 Sequence diagram for login 38

Figure3. 3 Sequence diagram for return book 39

Figure3. 4 Sequence diagram for search book 39

Figure3. 5 Sequence diagram for Issue 40

Figure3. 6 Sequence diagram for Register member----------------------------------------------------40

Figure3. 7 Sequence diagram for Add new book------------------------------------------------------41

Figure3. 8 Sequence diagram for Delete book---------------------------------------------------------41

Figure3. 9 Sequence diagram for Update book--------------------------------------------------------42

Figure3. 10 Sequence diagram for Update member---------------------------------------------------43

Figure3. 11 Sequence diagram for Generate Report--------------------------------------------------44

Figure3. 12 Class Diagram 45

Figure4. 1 System architectures 47

Figure4. 2 Subsystem decomposition 48

Figure4. 3 Class Modeling Diagram 50

Figure4. 4 Deployment modeling 57

Figure4. 5 Persistence modeling 58

List of Tables
Table1Project plan activity......................................................................................................10

Table1.1cost estimation.............................................................................................................11

Table1.2Soft ware cost.............................................................................................................11

Table3. 1 Login description 28 Table3. 2 Register description

28 Table3. 3 Search description

29 Table3. 4 Issue book description

30 Table3. 5 Return book description

31 Table3. 6 Update book description

32 Table3. 7 Update member description

33 Table3. 8 Remove book description

34 Table3. 9 Record book description

35 Table3. 10 Generate report description

36 Table3. 11 Check account description

36 Table4. 1 description of Librarian’s class attributes------------------------------------------------51

Table4. 2 description of member class attributes------------------------------------------------------52

Table4. 3 description of Book class attributes 53

Table4. 4 description of Issue book class attributes--------------------------------------------------53

Table4. 5 description of Return book class attributes------------------------------------------------55

Table4. 6 description of search class attributes-------------------------------------------------------56

List of Acronomys and Abrevations

CDs: Compact Discs

ID: Identification

LMS: Library Management System

ISBN: International Standard Book Number

JJULMS: Jigjiga University Library Management System

JJU: Jigjiga University

Mid: member id

UI: user interface

Btitle: Book title

Bcode: Book code

addB: add book

uname: user name

Fname: First name

Lname: Last name

Abstract
This application software of Online Library Management System developed for JJU Library
system. The activity of this university library system depended on manual way of processing so
that this is the way the system changed into computerized by this application software. It can
keep track of data related to library books, members of the library and related activity of the
system. To develop this software the team members (Graduate students of Computer science)
collected reliable data about the college and conducted the procedures starting from planning and
justification of the system. Based on the studying and recognizing about the problems of the
existing system, the team members as a designer specified and analyzed the requirements and
then developed the designing of the proposed system as a solution to the problems of existing
system. The system would provide basic set of features to add or update members, books, and
manage in specifications for the systems based on the client’s need. The system includes all
possible available books found in the book store so that one can check what is available inside
the book store without manually search. Addition to this it enables the university library
managers and workers to control daily attendance and easily submit work report.
Acknowledgment
First and foremost and above all our biggest thanks would be to Almighty God because nothing
could be possible without his free will and the completion of this project is supported by him.
Secondly, our deepest thanks goes to our Advisor Ahmad M. and co-advisor Michael for guiding
and correcting various documents of ours with attention and care. They have taken pain to go
through the project and made necessary correction as and when needed.

In addition, we would like to forward our special words of gratitude to Jigjiga University library
system librarian who helped us by providing information and by giving useful documents and
materials that are useful for our project.

We would also thank our Department and Our project coordinator without whom this project
would have been a distant reality.
 ONLINE LIBRARY MANAGEMENT SYSTEM FOR JJU
2015
CHAPTER ONE

1 .Introduction
Library is one of the basic requirements that enable the functionality of all educational institutes.
In the university and college level the main criteria is also adjusted in library system. To obtain
enough amount and specified book without any restriction, online library management system is
obligatory [1]. We mean online library system, it is supported with automation system and its
work process should be based on computer aided. Library Management System is mainly focuses
on basic operations in a library like adding new member, new books, and updating new
information, searching books and members and facility to borrow and return books. It features a
familiar and well thought-out, an attractive user interface, combined with strong searching
Insertion and reporting capabilities.
The report generation facility of library system helps to get a good idea of which is the books
borrowed by the members,

Library Management System has four main modules.

 Insertion to Database Module –User friendly input screen

 Extracting from Database module – Attractive Output Screen
 Report Generation module – borrowed book list & Available book list
 Search Facility system – search for books and members

JJU Page 2
 1.1 Background
Jigjiga University is one of the higher institution established in eastern part of Ethiopia in Somali
region Jigjiga town. Jigjiga University was founded in 1999 E.C. It has no enough facility to
develop online Library management system at that time. From foundation, still now, the library
system uses manual system. So we have decided to develop online Library management system
for Jigjiga University that overcomes the problems of the existing manual system like academic
case, food, wastage of time, dormitory problem etc. Our new system will eliminate the problems
in the manual system and increase the speed of whole process.

1.2. Statement of the Problem

Currently, the process and the services that Jigjiga university library system carries out are based
mostly on manual system [2]. With this manual system there is some limitation based on
different aspects. In the following lines we had tried to justify some of such limitations in the
system.

Some of the problems in the current system includes:

 Problems or weakness of the existing system is its manual operation that kills
much amount of time to complete a simple work.
 In this, it also needs man powers for a long period of time.
 The way of stack is almost with a manual check.
 Insufficiencies of reference resources for some course users.

1.2.1 Justification of the current system

Our new system will help the office by providing support method to complete their tasks with a
simple difficulty and with few workers with little period of time.
This new system need to fulfill the automation plan of the office. Therefore we as developer or
as designer going to complete their plan by providing designed supportable website as much as
possible in our standard.
 1.3. Objectives
1.3.1. General objectives

The general objective of this project is to develop interactive online library Management system
for Jigjiga University.

1.3.2. Specific objectives

Here are some specific objectives that would together help us to achieve the overall the project as
follows: .

 Find the solution for the problem found in existing system.

 Design and build a particular model of this proposed system.
 Deploy the system and maintain it till it fits to the needs of the system.
 Implementing the model with the flexible user interface.

1.4. Scope of the Project

The scope of this project is developing online library Management System for Jigjiga University

This project helps the workers to work without barrier of bad actions during their daily activity.
On the completion of this project we expect the system will have:

 Presence of centralized and organized material (book) records.

 Accurate way of recording and storing information in to database.
 Create an account for Administrator.
 The staff members will be registered using this website.
 Some reports like book borrow, book return and etc will be
generated.
 Major Functionality
Books borrow: enables user in order to use the books outside of library for a short period of time
with recorded agreement as necessary.

Search for specified book: using book’s unique information (i.e., book code, book title) to
check the availability of a given book.

Generate report, Add, delete and update

The library manager who is responsible for this process can do the following with help of our
interface: -

1. Add new book in book’s database.

2. Update already stored book’s information from database when necessary.
3. Delete the user information after the book is returned to clean database.

Our project scope does not cover:

 Cannot support all languages.

 Cannot relate with financial cost of the book.

1.5. Methodology
Method is the process and way we will use to develop this project. The project we proposed
will be started using requirements elicitation technique. The software process that we will be
using is iterative SOFTWARE development approach type since we will discuss and correct our
errors with our advisor frequently.

Generally we used the following methodologies for our data collection.

1.5.1. Data gathering tools

Data collection is a way of collecting information for improving or changing the existing system
by the new system. Data collection is a base for better solution. Without a requirement or without
collecting information about the existing system, it is difficult to establish the new system.
Requirement is use full for solving problem that was existed in the current system by collecting
information or by gathering data.
Data collection is a process in which we collect the necessary information in order to understand
the existing system and user requirements. To gather the information we will use interviewing
and reviewing document (forms, reports). During interviewing we will interview the university
library system about the existing system’s working activity. So the data collection methods that
will be used to achieve the development of this project based on the fact that must be applied to
overcome the manual library system. We want to apply or use three types of data gathering
methodologies. These methodologies are observation, Interview and document analysis.

This method has been the primary base for the project. Therefore using the current and
background knowledge and experience of the team, the team will be able to identify and list out
the common functionalities and requirements for the project.

Observation: as our team member will detect in the university about the system. These will help
the team (us) to precede some data gathering stages. Furthermore, it creates a bridge or cause for
other methodology to conduct them in proper method.

Interview: This methodology encapsulates two types of methods. These methods are closed and
open interview. So the team has selected an open interview for interviewing the manager and
employees for recognizing the existing working procedure of the system. So the team will be
able to gather more information about the library system and requirements.
Document analysis: Besides the interviewing we also use the library general work document.
This document available in the office, that gives the directions for total activities. It is the paper
hard copy that gives the general function that the system currently handling.

1.5.2. Analysis and design

After the requirement is fully elicited, the next step to be done is analysis model. This model is a
bridge to design model. Analysis model focus on requirement that is visible within the problem.
Each element we analysis will add to an overall understanding of software requirements and
provide insight into the information domain, function and behavior of the system. The preceding
step after analysis model is design model. In this step we will plan a solution. To work on those
models we use the following tools. Visio 2010 will be used on models. In analysis model we will
be using it to draw use case diagram, Sequence diagram and activity diagram. In design
modeling we will be using it to draw class and other diagrams. In designing model to draw the
graphical interface we will be using pencil prototyping.
After the document is completed the work that will follow is creating the system. This
programming language php will be used for the application development that communicates with
the database. The database will be created using MS-Access. Generally in our design and
analysis we use object oriented concept rather than structural system analysis since object-
oriented model enable us to thoroughly respect complex relationship and represent data and
processing with a consistent notation, which allow an evolutionary process. Thus it improves
system quality and productivity of system analysis and design.
Data are analyzed through Use case Diagram, Activity Diagram, sequence diagram and class
diagram. After analysis the design models conducted by deployment, and component. According
to the time schedule, all the process will be carried on. Data collection is being first as already
we started some part and the other process is also continuing sequentially. The documentation
part partially completed with the following three months and the remaining documentation part
and coding will be conducted next four months.

1.5.3. System implementation method

After completing the development of the system, the testing process will be take place. This part
recognizes that the system works correctly or not, accurate or not, updates the features if
necessary. It will be carried out after all coding process completed. If this process realizes the
functionalities of the system and is ok, the product CD will be submitted to the Jigjiga university
library system that they can use this web technology for their further work process.

1.5.4. Development tools and techniques

We will also use the following tools

 Windows – as a development environment

 php-for coding
 MS-Access – for storing the data that are going to be retrieved later.
 Microsoft office Visio 2010- in order to model the system requirement in UML (unified
modeling language).
 1.6. Significance of the Project
Developing this project has much significance for the university and the students. After the
completion of the total process, the system give web based application for Jigjiga university
library workers as well as users. As we explained above section, the current system that based on
manual system will be changed when they apply this strategic product.

The users also use the library resources with safely and complete security without any time restriction.
Some of the significant for the project.

 Time consuming
 Reduce man power & budget
 Avoid document or reference misplacing.
 It ensuring the availability of library books in their proper place.
 With less effort and cost, the system will be able to
maintain and store information.

1.7. Risk Assessment and Management

Some of the risks might face during our further work is assumed as the following points.

 Unexpected man power failure:

 Virus attack on computer:

 Failure of electric power:

 Time limitation
 Resource related problems:
To manage the above risks we take the following as a solution
 We will manage the problem of man power failure by covering the tasks of the
victim with the remaining team members that they should take alternative period.
 For virus infection, duplicate files more than two computers, copy files on CD-
RW and external devices in order to resist problem.
  To manage power problem we will use personal resources like laptop. However,
since all the team members do not have laptop computer, the group members will
be forced to get through any way during the time of for longed power cut.
 We will use the night period up to 11:00pm (local time) to cover the total process
in order to manage time limitation.
 Our target source is through Google search, unless we seek our advisors help and
other colleagues’ cooperation.

1.8. Operating Environment

1.8.1. Hardware requirements
The hardware this system needs to be operated is:

 Desk top computer for over all operation

 Laptop computer as alternative use
 CD for data backup (hold setup)
 Printer to print report by hard copy

1.8.2. Software requirements

The software requirements are no more for these operations. It needs windows operating system
with MS-Office installed in the computer.

1.9 Project Plan and Time Table

Scheduling is used to perform the works in appropriate time that helps to reach the goal
effectively and efficiently.

Giant chart: for scheduling our project

 Chart1 Project plan activity diagram

Table 1: Project Plan Activity Table

NO Task Name Start Finish

1 Gathering Information 11/11/2014 11/20/2014

2 Proposal 11/11/2014 11/ 25/2014

3 Existing System 11/25/2014 12/25/2014

4 Requirement 12/25/2014 1/23/2015

Specification

5 Designing 1/23/2015 2/23/2015

6 Coding 2/23/2015 3/23/2015

7 Implementation and 3/23/2015 4/23/2015

Testing

8 Conclusion And 4/23/2015 5/22/2015

Recommendation
1.10 Cost Estimation
The following table lists the different cost estimation that we spent in the process of the
development of the system.

Table 1.1 Cost estimation

Material Amount Price

Printing 100 pages 100 Birr

Pen 5 15 Birr

Paper ONE DESTA 90 Birr

Flash disk 1 150 Birr

CD 11 44 Birr

Total ------------ 399 Birr

1.10.1. Software development cost

For this particular project we will be using different software but the software is provided by the
university. Table 1.2 Software costs

Software Description Price

Microsoft office by the university

Wampserver Free down load

Microsoft Visio by the university

Total 0.00birr
 1.10. Project organization
The project content: The project contains generally two phases: Phase І and Phase ІІ. Phase І
contains four chapters, introduction, Description of current system, Requirement Analysis and
Specification and system modeling using object oriented paradigm (oop). Phase II contains two
chapters. System Implementation and Testing and Conclusion.

Project Proposal: Before being starting a project we submit the proposal of the project to the
advisor that contain the aim of the project and discuss the methodology intended to use in
achieving those aims.

Progress report: We submit to our advisor periodically written progress of the project that
contain project title and full content of each chapter to be submitted. After carefully review our
work on the given chapter and the advisor comment which is correct and which need correction
again and give back for us.

Interim report: We submit the first phase of the project that contains four chapters at the end of
this semester and we give detail presentation of each chapter.

Final report: At the end of second semester we submit the second phase of the project that
contain System Implementation and Testing of the first phase and present it.
 CHAPTER TWO

DESCRIPTION OF THE EXSITING SYSTEM

2.1 Introduction
This library management system contains the description of the existing system and the problem
that we are going to solve. This phase is pointing what the system needs and contains many
diverse activities and tasks that are extremely important to the overall success of the learning
solution. It also includes weakness, strengthens, documents used in the system, players of the
system and description (current system description), function of the existing system, alternative
solution currently the system use.

2.2 The main activities

The library management system is now using manual system to manage their working process.
The main activities of the library management system are as listed below:

 Registering new books

 Registering new member
 Generating report
 Add books to data base
 Search books
 Updating books
 Delete the user information

All of this activity is very complex and time loosing .The main reason for these problems is the
absence of any computer technology or web based system, which will bring a best solution by
reducing a time consumed by performing each activity
 2.3 Functions of the Existing System
The existing system has major functionalities namely protection of total books, recording newly
entered books, supplies books to users, and controls the book security. Prepares the general
reports. Reports problems and the shortage of books to the target or responsible body and obtains
solution.

Generally the library system performs the following activities: -

 Member Management
Input: Name, Age, Id No, year, number of books taken.

Process: Clerk should check the detail information of the user.

Output: Members is recorded in the database.

 Book Management
Input: Author, Title, Call number.

Process: Librarian checks the type and the number of books.

Output: Registered in the cabinet.

When they receive new books, they record the essential information with prepared form
[Appendix].
Feature of Existing System
 Borrowing
Input: Pocket, Member Id No.

Process: Librarian should check pocket and member Id No.

Output: Members should get the book.

 Returning
Input: Member Id No, Book code, Date of issue and Date of expiry.

Process: Librarian should check the issue book and pocket of the members.

Output: Documentation and Member details should be updated.

  Search
Input: Title, Subject Author.

Process: Librarian and user check the availability of the books.

Output: Get the search result by the librarian

Mostly the operations are based on forms of hard copy; this is not secured for wise protection of
books. The use of computer is rarely and the used software is also not comfortable to handle
easily. It is difficult to handle with this method so it needs rapid automation.

2.4 Players of the Existing System

In the existing system there are different players namely:

Administrator/ manager: is the responsible person in the library for managing and
coordinating the whole system. This service called as backline service which means that he/she
doesn’t contact with members.

Librarian/clerk: They provide front line service for the user/members and always have direct
contact with members.

Student and Teacher: are registered members who are authorized to issue articles from library.

2.5 Report Generating in the Existing System

In the existing system the report is generated as the requirement of the library. As we observed
and also interviewed the library managements the report generating mechanism is manual.
Mainly the system reports include book related information, member related information, staff
related information, users related information and other side problems of the library management
system reports are written on paper by clerk and then it will be transformed to the manager.
 2.6 Documents Used in the Existing System
The document used in existing system is the mostly manual materials like printed paper forms
and rarely computer with the MS-Office applications used for some basic documentations.
When the reports are preparing, the computer system is used.

2.7 Weakness of the Existing System

Weakness of the existing system is its manual operation that kills much amount of time to
complete a simple work. In this, it also needs man powers for a long period of time [2].
The way of stack is almost with a manual check.
Due to the manual means being used, in giving treatment for students, a lot of problems are
encountered which includes:

Time wastage problem

 Some students waste their time by waiting to turn for limited amount of text
resources which arranged by time record.
 First of all the works are processed manually.
 Takes a lot of time to retrieve a particular task.
 The low treatment leads the student being less effective and less result.
Complexity problem
 Students are overloaded for shelf workers.

 Searching for a given reference is very difficult and rarely unable to get.

 Tiredness or exhaustiveness problems

2.8 Strength of the Existing System

Its strength is that the prepared files do not infect with simple phenomena’s in contrast to
computer system, since much files held with paper copy not with computer and no virus there to
infect it.
It does not need electric power to see files automatically.
It does not need more computer skill and not require specialized software.
The technological aspects like internet connections are not matter for the users as well as for the
operators (workers) since most of its operations based on manual system [2].

2.9 Alternative Solution

The office takes more employers or support workers when there is a load of work emerged. They
use other shelve workers to handle the current activities with a given period of time [2].In order
to provide the desired treatment for the users, the system uses different methods such as time
restriction; with the recorded treatment; arranged time table for certain applications like less
amounted books and internet service. This enables the system to manage the seasonal problems.
 CHAPTER THREE

REQUIREMENTS SPECIFICATION AND ANALYSIS

3.1 Introduction
Requirement gathering is a way of collecting information to improve or change the existing
system by the new system. Requirement is a major base for better solution or for solving
problem which exists in the current system by gathering requirement [3].The new system is
based on the interest and understanding of users. The sequences of activities which are
performed in the current system also affect the new developing system. To work in accordance
with interest of users and working process of current system there must be a clear understanding
of the way how activities are performed, what current system requires, what are the problems
that the current system faces, and what improvement should be done to make it a better system.
Having such kind of understanding helped us to distinguish parts which are going to be changed
in the new system and to determine how our system can solve the current problems and also able
to design other new features which are user interactive. To gather the information we used
interviewing and reviewing document (forms, reports). In addition to the above two methods we
observed how they perform their activities in the current system.

3.1.1 Purpose
Analyzing the current system and making requirement determination helped us to develop a
system which includes necessary information and source for different activities. Some of the
purposes of analyzing manual system are:-

 To distinguish current problems in different categories based on the case and to find
solution to each. In case of finding solution we analyzed which parts of the existing
manual system has to be converted into new computerized system.
 To design and develop different type of files, forms and report generating system based on
manual activity.

3.1.2 Intended Audience and Reading Suggestions

In the system the intended audiences are the library system managers (workers) that have
permission to access the system by system. Instructors and other users will get the application
based on the system’s rule and regulations. When we implement this system we prepare essential
reading manuals that are used to simplify the use of the system by the user. We hope the system
handled easily according our manual. So they should read the manual that we provide.

Process model approach

Possible use of a process model approach is to prescribe how things should be done in contrast to
the process itself which is really what happens. A process model is roughly an anticipation of
what the process will look like. What the process shall be will be determined during actual
system development

Spiral model

We use spiral model to work out our project because of the following reason.

 High amount of risk analysis hence, avoidance of Risk is enhanced.

 Good for large and mission-critical projects.
 Strong approval and documentation control.
 Additional Functionality can be added at a later date.
 Software is produced early in the software life cycle.
 3.1.3. Document Convention
The following are the list of convensions and acronyms in this document and the project as well:

User: intended users for the software

MYSQL: structured query language, used to retrieve information from a database

Layer: represents a section of the project

User interface layer: the section of the assignment referring to what the user interacts with
directory

Use case: a broad level diagram of the project showing a basic overview

Interface: something used to communicate a cross different mediums

PHP:hypertext preprocessor and server side scripting language

RAM: random access memory.

 3.2 Objective
The objective of this phase is to develop the requirement specification and analysis as it started
from last section by using the information planned. The requirement specification is the phase
that leads to the designing and implementation; that the correct and accurate designing has a
great role to the system implementation. Based on this designing our target, providing the
automated system to the library system, be attained with the rapidly developing technologies.
The system is to be beneficiary of this by applying the possible technology results as much as
possible.

3.3 Functional Requirements

Management of user/book: User must fill all relevant information in the registration form like,
name, Id No, department, edu/year, etc with librarians. And add the book details by the book
title, author, edition etc.

Search book: users can search for the book where necessary by the searching that can be done
according to title and Author.

Book Return Procedure: Student/user is required to return the book within the due date.

View book/member: users can also see the list of member/user who have not returned their
books even after due day from the date of issuing, in which system prints a detailed report of
the member who have not returned their books and their relevant information include the
book details.

Update: Any changes in the database either details information of books or members should be
updated

Delete member or book: Wrong or not allowed data entry to the system must be removed from
the database.

Issuing Procedure: Member/user can issue the respective book he/she needs .The procedure
checks for the case when the book is already issued by some other borrower or the book is not
present in the library and thus it is not available for issuing. The user is required to enter the
issuing date and then the validations for the date are performed .Also the procedure incorporates
automatic return date generations system as discussed previously. The return date must be
calculated with in specified time constraints.

Generate report: The system incorporates report generation and data filtering mechanisms.
Reports can be built on the following various criterions:

 List different books present in the library with the columns separated under different
files. Author name, Edition number, ISBN and status of the book whether the book is
issued or not.
 View the details of books currently issued.
 View the books present in the library that is the books which have not been issued by any
of the borrowers.
 Member detail who have issued the books with the details of the books and the respective
member’s details.
 List of books which are requested by the members.

3.4 Product Perspective

The proposed library management system which will be developed by the project team member
is web based application. This system will provide the mechanism for the new book and already
existed book is to register by the manager and the students reserve online. The systems user can
also retrieve and search for books.

The authorized person (Manager) can perform update, delete, and insert operations on the books
as needed.

3.5 Product Functions

Based on our plan and scope our end product performs the following activities: -

 Enables the managers to handle its operations easily

 The system registers the staff members of the library system.
 Easily searches for the desired information’s
 Records the newly entered books with easiest way.
 Searches the required book from book database easily.
  Deletes the list whose book is not available or wrongly recorded in the book database.

3.6 Principal Actors

Administrator/ manager: is the responsible person in the library for managing and coordinating
the whole system. This service called as backline service which means that he/she doesn’t
contact with members.

Librarian/clerk: They provide front line service for the user/members and always have direct
contact with members.

Student and Teacher: are registered members who are authorized to view and issue articles
from library.

3.7 User Characteristics

The main users of this system are library operators and members who are expected to perform
circulation operation and book issue.

 Student information based on demands of books.

 Each department course information.
 Instructor information.
 Building safety an arranged room.
 Staff member user procedures directed by head manager.

Since the instructors or the other registered members of the college are the users of this software
system, they can provide their demands to the operators to view and use available resources for
their need.

3.8 General Constraints

When developing this system, we as a developer justify the following constraints for the accurate
use of the developed system [4].

 Administer or head manager take over all control for this application in case of security,
checking and others.
  Librarians perform by following the correct way as a system leads and respect the
manager instruction that related with time.
 Book recorded in the book table with correct book ISBN as it entered into college and
functionally available for view.
 Registered member can see the book detail by using correct username and password with
the permission of manager.
 The application will used within any windows form.

3.9 Assumptions and Dependencies

The system assumes that the user has enough knowledge about the essential part of the computer.
It is assumed the maintenance of the database will be assigned to the authorized person only, i.e.,
only authorized persons will be allowed inside the systems update and check.
The system does not depend on the software components and operating system like windows
version and windows flat form.
This application is used to convert the manual application to the computerized application.
Customized data will be used in this application.
External users and guest does not have right to enter information about books’ and other entire
application system.

3.10 Non Functional Requirements

Performance: The system will be accessed by many users or members inside the college by
using centralized operating system with the help of technology that connect one CPU with the
multiple monitor. So it should be given more emphasis for the speed to access the system.

User Interface: The developed system provides desktop application user interfaces that are
compatible for any windows operating system. For this reason the user of the system especially
the librarians who develop the collections is expected to know at least how to interact with this
application. The users or who navigate the other interface of the system to retrieve the collections
of the system is also expected to know basic understanding on how to navigate.

Software Interface: A firewall will be used with the application to prevent unauthorized access
to the system.
Security and Access permissions: We are going to develop a secured database for the College.
There are different categories of users namely administrator, library and member. Depending
upon the category of user the access rights are decided. It means if the user is an administrator
then he can be able to modify the entire data, delete, append etc., all other users other than library
staff only have the rights to retrieve the information about database. In another way
authentication is provided to all the users, only authenticated users can use.

No Redundancy: In the proposed system can be avoided reputation of data anywhere in the
database but there may reputation is case of data backup. This would assure economic use of
storage space and consistency of the data stored in the database.

Availability: All data in the system will be available at any time.

Error handling: When the users of the system interact with the system errors may appear. To
control these inaccuracies the system will generate different messages. Data errors which are
entered in to the system may not be completely avoided but they can be minimized. To do this,
most of the system execution buttons will be controlled according to the sequence which the user
is expected to follow. Or this can be done by generating different system responses to the input
of the users.

System modification: Through time there are always changes when the user’s needs another
additional functionality, when the system administrator identifies the system need to be
modified, while the organizations work style is changed and depending on different reasons.
Some of the user interface and basic modification can be performed by the collection developers
but the system developers are the right persons to update the system
 3.11 System Models
Analysis approach

The analysis approach that we used object oriented paradigm because of the following reason.

Reduced Maintenance: The primary goal of object-oriented development is the assurance that
the system will enjoy a longer life while having far smaller maintenance costs

Real-World Modeling: Object-oriented system tend to model the real world in a more complete
fashion than do traditional methods.

Improved Reliability and Flexibility: Object-oriented system promise to be far more reliable
than traditional systems, primarily because new behaviors can be "built" from existing objects.

High Code Reusability: When a new object is created, it will automatically inherit the data
attributes and characteristics of the class from which it was spawned.
 3.11.1 Use Case Models

Figure 3.1 use case diagram for library system.

3.11.2 Use Case Descriptions

Table3. 1 Login description

Use case ID JJU #1

Use case name Login

Primary Actor Librarian, Members, Manager, Administrator (Commonly called as users)

Description To interact with the system, LMS will validate its registration with this
system. It also defines the actions a user can perform in LMS.

Pre condition Any user must have user name and password.

Basic flow 1. System show login screen. A1

action
2. User filling required information enters user name and password.

3. System acknowledges entry.

Post condition System transfer control to user main screen to precede actions.

Alternative If users found the system display invalid user name and password error
condition: message. Then go to step 1.

A1

Table3. 2 Register description

Use case id JJU #2

Use case name Register member

Primary actors Librarian

Description Registered new members in the database of the library system.

Precondition The member should have a valid college membership document which
contains his name, department, ID number to obtain library membership.
1. To register the member the administrator or librarian has to first
Basic flow of action
login.A1
2. After login the administrator or librarian searches for the existing
member.A2
3. The system displays registration form.
4. The Librarian to fill full his name, ID number and any information
about the user.
5. The system sends successfully message for the user to be
registered.

Post condition The user account, the system generates and sends user information to the
user.

Alternative action : The administrator or Librarian fails for login.

A1 Administrator or librarian can try again by entering username and

password.
A2

Table3. 3 Search description

Use case ID JJU #4

Use case name Search book

Primary actor Librarian, Member (Commonly called as users)

Description The books in the library can be searched through parameters like title
(book name), Author.

Pre condition The book to be searched should have been registered in the database of
the library management system.
Basic flow of action 1. The staff or Librarian login to the system. A1

2. The Staff or Librarian request search for book.A2

3. The librarian forward to database.

4. Verify the availability the book.

5. The system is displayed search result

Post condition Display search result

Alternative action:

A1 If the login is fail. The staff/member can enter user name and password
again.
A2
If the search is unsuccessful, then the Librarian should add that book.

Table3. 4 Issue book description

Use case ID JJU #5

Use case name Issue Book

Primary actor Librarian

Description End user can issue the respective book he/she needs.

Pre condition To borrow any book it is important that the member or other user;
member is registered with the library and the book to be borrowed is
available with the library.

Basic flow of action 1. The librarian should login to the system.A1

2. The system displays main page.

3. The member request to the librarian.

 5. The librarian should enter the call number of the book (title, author
and subject).A2

6. The system displays the book is available.

7. The librarian response message to the member.

Post condition Book can be borrowed.

Alternative action: If the login fails the librarian or administrator should enter user name and
password again.
A1
If the member search is unsuccessful and no data is found then the
A2
administrator should re-register the member.

Table3. 5 Return book description

Use case ID JJU #6

Use case name Return book

Primary actor Librarian

Description The end user can return the books. Fine is charged if he/she submits the
book after the due date.

Pre condition The member and the staff member are registered and that book

Data is available with the library.

Basic flow of action 1. The Librarian should login to the system.A1

2. The librarian should enter the member id to be search.A2

3. The system displays search result.

4. The librarian should enter the call number of the book (title, author and
 subject).A2

5. The system displays search result about the book.

4. The librarian should check the report data for any pending fine.

5. The system display message no fine pending the book can be returned.

Post condition Book can be returned.

Alternative action : If the login fails the librarian or administrator should enter user name and
password.
A1
If the member search is unsuccessful and book data is not found then an
A2
administrator must enter the book and member ID in database.

Table3. 6 Update book description

Use case ID JJU#7

Use case name Update Book

Primary actor Librarian, Administrator (commonly called as user)

Description It allows to modifying (changing) the details information of the book from
data base.

Pre condition Detail information the user must be recorded in the database.

Basic flow of action 1. The librarian logs to his account from the home page of the
JJULMS.A1

2. The librarian clicks on the Search button.

3. The System displays search options (title, Id, subject).A2

4. The librarian search using one search method.

 5. The system displays the searched result.

6. The librarian clicks on the update button.

7. The system displays new data.

Post condition The user record is modified successfully.

Alternative action: If the login fails the librarian should enter user name and password.

A1 If the data there is a mistake in the data entry the system displays error
message and allow making correction.
A2

Table3. 7 Update member description

Use case ID JJU #8

Use case name Update user

Primary actor Librarian

Description It allows to modifying (changing) the details information of the user

from data base.

Pre condition Detail information the user must be recorded in the database.

Basic flow of action 1. The librarian logs to his account from the home page of the
JJULMS.A1

2. The librarian clicks on the Search button.

3. The System displays search options (name, ID).A2

4. The librarian search using one search method.

5. The system displays the searched result.

 6. The librarian clicks on the update button.

7. The system displays new data.

Post condition The user record is modified successfully.

Alternative action If the login fails the librarian should enter user name and password.

A1 If the data there is a mistake in the data entry the system displays
error message and allow making correction.
A2
Table3. 8 Remove book description

User case ID JJU#9

Use case name Remove Book

Primary Actors librarian

Description Wrong or not allowed data entry to the system must be removed from the
database. Or The old and damaged books are removed from the library.

Pre condition To delete the book must be part of the database or registered in the database
for the LMS.

Basic flow action 1.The Librarian logs to his account from the main page of the

JJULMS.A1

2. The Librarian clicks on the Search new user button

3. The System displays search options (title, subject and author) .A2

4. The Librarian search using one search method.

5. The system displays the searched result.

6. The Book record are automatically removed

Post condition The book result is removed from the database.

Alternative If the login is unsuccessful the librarian should enter user name and password
action: again.

A1 If a book search is not found in the database then librarian or admin

shouldn’t be removed the book.
A2

Table3. 9 Record book description

User case ID JJU #3

Use case name Add Book

Primary Actors Librarian

Description Add new books to the library with all the details of the book.

Pre condition To add any book that book should have parameters like book name,
ISBN, printed date etc.

Basic flow action 1.The librarian logs to his account from the main page of the JJULMS.A1

2. The librarian clicks on the Search new user button

3. The System displays search options (author, title, and subject).

4. The librarian search using one search method.

A2
5. The system displays the searched result.

6. The librarian clicks on the Add button to add the new book.A3

Post condition The book result is added to the database.

Alternative action: If the login is unsuccessful the librarian should enter user name and
password again.
A1
If a book is to be added on search is already exists it should not added.
A2
If the registered record exists in the database, the system displays the file
A3
already exist message and if the input data has errors the system display
error message.
Table3. 10 Generate report description

Use case id JJU #12

Use case name Generate report

Primary actor Librarian ,manager

Description The system incorporates report generation and generated filtering

mechanisms. Or allow librarian to generate reports through parameters
like daily, weekly and monthly.

Pre condition The librarian must be an authorized to perform this activity.

Basic flow 1. The librarian login to the system.A1

2. The system verifies the librarian is legal to generate report.

3. The librarian selects the parameters for which report to be

generated.A2

4. The system displays the needed information.

5. The librarian informs the system to generate a report.

6. The system generates the report.

Post condition Report will be generated.

Alternative action: If login system is failed librarian should be enter user name and password
again.
A1
If the parameter is failed the system display message.
A2

Table3. 11 Check account description

Use case JJU #14

Use case name Check accounts

Primary action Administrator

Description System will show member current issue articles, transaction history.

Pre condition User must have user name and password.

Basic flow of 1. The user login to the system.A1

action
2. The system displays successfully message.A2

Post condition Successful the account result.

Alternative action: If the users account not correct the system display error message and users try
again.
A1
If the user can not part of the library the system display error massage and
A2
users registered by administrator.
 3.11.3 Sequence Diagram

Figure3. 1 Sequence diagram for login

Figure3. 2 Sequence diagram for return book

Figure3. 3 Sequence diagram for search book

Figure3. 4 Sequence diagram for Issue

Figure3. 5 Sequence diagram for Register member.

Figure3. 6 Sequence diagram for Add new book.

Figure3. 7 Sequence diagram for Delete book.

Figure3. 8 Sequence diagram for Update book.
Figure3. 9 Sequence diagram for Update member
Figure3. 10 Sequence diagram for Generate Report.
 3.11.4 Class Diagram/UML

Search Admin
Book
Title
BTitle Fname
Diagram
BCode
Code Lname
Author
Author User name
Mid Password
Published
Search () Login ()
Add B ()
Delete () Create
Update () account ()
Display () Update ()
Delete ()
Logout ()
Teacher/Stu
dent
Librarian
Issue Book Fname
* Lname Fname Lname Role type
BTitle Mcatagory
BCode
s Phone
Mid
E_mail
Category
Login () Role
Issue date Add ()
()
Delete ()
Issue () GenerateReport(
Update ()
Update () ) Logout()
Display ()
Display ()

Return Book

Mid
Due date
BCode

Return ()
Update ()
Display ()

Figure 3.12 class diagram

 CHAPTER FOUR

SYSTEM DESIGN

4.1 Introduction
This chapter contains different tools and techniques to model the design of the project these are
deployment diagrams and decomposition diagrams which comes from different models of the
analyses model [3].
Our purpose of designing is to show the direction how this system built and to provide clear and
enough information needed to drive the actual implementation of the system. It is based on
understanding of the model the software built on. Our objective is to model the system with high
quality since the implementations of high quality system depend on the nature of design created
by the designing phase. If one wants to change the system after it has been put in to operation, it
depends on the quality of the system design [3].

4.2 Design Goals

The goal of our system design according to the proposed project is to manage complexity by
dividing the system into smaller, manageable pieces and to increase the system based on
efficiency, reliability and flexibility [3].

4.2.1 Performance Criteria

The system performs all desired application efficiently and thoroughly without waste of money
and time. It will be reliable, perform every work area should use it with a good performance. The
choice of windows form is not matter for this system; through applicable by every windows flat
form.

4.2.2 Maintenance Criteria

The system able to change to suite new condition or situation flexibly. When needed, it is
possible to take maintenance easily. By using the same development environment, it can be
easily maintained.
 4.2.3 End User Criteria
The system should be secured, i.e. not allow unauthorized users to access the system since it is
inner office application. To enter into the application area the operator should use a correct
username and password unless it is not possible to take any single operation. Staff member
attendance form is controlled by administrator or manager privilege that it is open for a given
period of time and then it will be closed by the manager as necessarily.

4.3 System Architecture

The various layers are represented by the rectangles and collaboration between layers by the
parenthesis. A common architectural strategy is to layer the architecture of a system into several
layers.

The purpose of system architecture is the static structure of how our software will be built. The
only difference with that of analysis class architecture is that it focuses on domain solution rather
than problem domain and it introduce changes to our class model based on implementation
technologies in the project.
Figure4. 1 System architectures

4.4 Subsystem Decomposition

In this part we can see the sub systems in the entire system. These are the working area of the
project after the completion of total process. In the sub system decomposition we can see the
different components emanated from system architecture that collaborate to handle single
application at a time.
When the operator runs the application software, the user interface appears by preceding login
screen. Next to login screen is the main page that supports other operational directories. The
different subsystems have a coupling to complete entire process. The subsystems namely book
management; member management, report generation and other simple operations are the major
sub system of this project.
Figure4. 2 Subsystem decomposition

4.4.1 Login subsystem

This subsystem keeps the security of the system and gives privilege. It checks whether the user is
valid or not controls unauthorized users from entrance of the system. So that it consists of the
authentication, authorization, and security of the system.

4.4.2 Member management

The registration subsystem consists of the functionalities of registering legal members in to the
system, updating member information, view and delete unnecessary information from member
database. The members may include staff members, instructors and other necessary part those
who essence registration in the database. So by using the part prepared for member registration,
the responsible body easily can register the members.
 4.4.3 Book management
This subsystem enables the end user to record newly entered books into database, manage
book issue, update, delete, view book detail and manage other book related information.
With the help of this section it is easy to handle the correct book information and store it
with in database.

4.4.4 View report

This is the subsystem whose main operation is to generate weekly or monthly report.

The report subsystem consists of all functionalities of the system that produce report concerning
book operation and member operation. The reports might be in a paper form or data grid
depending on the type of report

4.4.5 Class Modeling

The following sh ows the class modeling diagram
 Search Admin
Book
+Title: varchar(50)
+BTitle:varchar(50)
+Fname: varchar(50)
+Code: varchar(50) +Lname: varchar(50)
+BCode: varchar(50) +Author: varchar(50)
+Author: varchar(50) +Uname: varchar(50)
+Mid: varchar(50) +Password: varchar(50)
+Published: varchar(50)
Search () Login()
Add B()
Create account()
Delete()
Update()
Update()
Delete()
Display()
Logout()

Teacher/Student

+Fname: varchar(20)
+Lname: varchar(20)
Issue Book +Mcatagory: varchar(20)
Librarian
+Phone: varchar(20)
+BTitle: varchar(50) +E_mail: varchar(20) +Fname: varchar(50)
+BCode: varchar(20)
+Lname: varchar(50)
+Mid: varchar(20) AddM() +Role type: varchar(50)
+MCategory: varchar(20) Delete()
+Issue date:Date Update() Login() Role()
Display() GenerateReport() Logout()
Issue() Update() Display()

Return Book

+Mid: varchar(20)
+Duedate:Date
+BCode: varchar(20)

Return()
Updte()
Display()

Figure4. 3 Class Modeling Diagram

 4.4.6 Documenting the Classes
Documenting class model is used to document the detail about a class as well as the reasoning
behind any system; the following are the documentation of the class model for the database
system for library management system.

Librarian’s class

Librarian’s class is a persistence class that is used to contain Librarian’s (circulator, clerk and
others) information and also called client it has the following attributes and methods.

Attributes

Table4. 1 description of Librarian’s class attributes

Attributes Description Data type

Fname Name of employee String

Lname Fathers name of employee String

Roletype Occupation of an individual in the library system String

Methods

Boolean is used to check the availability of record.

Pre-condition: Librarians should be registered.

Post condition: the Librarians availability should be checked.

BEGIN

ACCEPT Librarians

VALIDAT profession

IF professional register and submit to the database

ELSE
AVOID unprofessional

END IF

END

Member CLASS

Member class is a user class that uses the systems application with registered authentication that
they have their user name and password. It has the following attributes.

ATTRIBUTES

Table4. 2 description of member class attributes

Attributes Purpose Type

F name Name of member String

Lname Father name of member String

category Category of member String

Mid ID of member Number

Phone Phone number of member String

e-mail E-mail address of member String

METHODS

Boolean is used to eligibility of registering members.

Pre condition: the member should provide full information to be registered.

Post condition: the member should be registered and available in data base.

Book class

This class performs the recording or adding process of the new entrance books to the library
database system.
ATTRIBUTES

Table4. 3 description of Book class attr0butes

Attributes Purpose Type

Btitle Title of the particular book String

Bcode code for the particular book Number

Author Author of the book was written String

Published Year of the book published at Integer

METHODS

Pre condition: the book should have been entered to the college library store and qualified.

Post condition: the books should be registered and available in book database.

 Issue book

This is a sub class in book class that is used for Librarian’s to manage members those need for
this application. The members’ detail or information stored in database by using this part of
website.

Attributes

Table4. 4 description of Issue book class attributes

Attributes Description Data type

Mid ID of member Number

Phone Phone number of member String

category Category of member String

Issue date Date of the book issued Date

Due date The date when the book should be Date
returned

Btitle Title of the particular book String

Bcode code for the particular book String

Methods

Boolean is used to check the availability of books in the store.

Pre condition: the full information should be recorded and stored.

Post condition: member obtains the book of his/her seek.

BEGIN

ACCEPT detail

VALIDAT complete

If it is complete submitted to the database

ELSE

AVOID incomplete information

END IF

END

 Return book

This is also other sub class of book class which enables the Librarian’s to manage issued book in
order to replace the book in to book store accurately.
Attributes

Table4. 5 description of Return book class attributes

Attributes Description Data type

Mid ID of member String

Due date The date when the book should be returned Date

Bcode code for the particular book String

Methods

Boolean is used to check the originality of books as it issued.

Pre condition: member should provide the on desired date.

Post condition: the book returned to the book store as it’s.

BEGIN

ACCEPT book

VALIDAT check database

If it is valid submitted to the database

ELSE

AVOID ask for validity

END IF

END
  Search

This class enables the users of the systems’ application to see the book details that exist in the
book database. It has the following attributes.

ATTRIBUTES

The attribute used her is either the book title or author for one user at a time.

Table4. 6 description of search class attributes

Attributes Purpose Type

Btitle Title of the particular book String

Author Author of the book was written String

METHODS

Boolean is used to the availability of information entered.

Pre condition: the book should be recorded available in the database.

Post condition: the user should get the searched book.

4.5 Deployment Diagram (Hardware/Software Mapping)

UML deployment diagrams show the physical view of our system, bringing our software into the
real world by showing how software gets assigned to hardware and how the pieces communicate.
It is also used to show a collection of nodes and also dependencies of associations among them.
The associations between nodes Represents a physical connection. The physical deployment
model provides a detailed model of the way components will be deployed across the system
infrastructure. It details network capabilities, server specifications, hardware requirements and
other information related to deploying the proposed system.
Figure4. 4 Deployment modeling

4.6 Persistent Data Management

Persistent data management is a modeling that we used to communicate the design of the
database, usually the database of the different tables communicate with each other through
foreign key. In this system, ISBN and Mid mainly used to describe the persistence data aspect of
the library management system. The following diagram indicates the persistence diagram of the
library management system.
Figure4. 5 Persistence modeling
 CHAPTER FIVE

IMPLEMENTATION AND TESTING

5.1. INTRODUCTION
The Implementation phase in the software life-cycle is where the actual software is implemented.
The result of this phase consists of source code, together with documentation to make the code
more readable. This is what we call software implementation. The purpose of these activities is
to convert the final physical system specification into working model with reliable software and
hardware, document the work that has been done, and provide help for current and future users
and take care of the system.

5.2. Algorithm Design / Coding

The following sample used algorithm design way of our system. It is just similar with our code
functionality and validity. There are so many different classes in our system, but we selected
very few of them to justify the way of algorithm the system follows.

Class Login class

Login class is a user interface class that is used to validate the authorization of the users to the
system with the help of account information.

Method

Is Valid (account): checks the validity of the user account and password.

Precondition: account information should be entered by the user or Administrator.

Post condition: account information will be valid.

BEGIN

ACCEPT user account and password

VALIDATE user account and password

IF VALID submit to the database

ELSE

DISPLAY error message

ENDIF
END

Class Operation on Book

Class Book record is a persistence class that is used to record book data in database.

Methods

Record (Save): is used to record the book record.

Precondition: Book entry, book qualification should be completed.

Post condition: book information should be created (recorded) in database.

BEGIN

ACCEPT book data

VALIDATE book data

IFVALID submit to the database

ELSE

DISPLAY error message

ENDIF

END

END

Delete record (): is used to delete invigilator book information.

Precondition: book data should be selected.

Post condition: book data will be deleted.

BEGIN

CONNECT to the database

SELECT the authorization table

DISPLAY the book data

DELETE the book data

END
 5.3. Testing
The test plan is designed to analyze the logic used in the implementation of the Library
Management System. The tests will allow us to ensure correct program flow, and to determine
the error-handling capability of the system [6].

Once coding has begun, the testing process can be begin and proceed in parallel. As each
program module is produced, it can be tested individually, as a part of larger program, and then
as a part of larger system.

5.3.1.Unit testing
Unit test is a way of testing each of the system functionality independently. Accordingly the
team has tested each one of the three major activities and the rest accompanying activities
independently using different user input, different login mechanisms and any technique of fault
finding so that an incorrect functioning of the activities was corrected at the right time

5.3.2.Integration testing
By combining each individual form and report with their concerned database we had tested by
giving general data. From this we had understood and realized that how the system works using
separate module.

5.3.3.System testing
It is the final step of testing. In this system tested the entire system as a whole with all forms,
code, modules. In this we tested all the functionalities in the System. All errors in the forms,
functions, modules have been tested. Finally by the system testing we had ensured that the entire
integrated software system meets the desired requirements.

Test Case 1 – User Authentication

Test Case ID = user

Unit to Test = Authentication of Login Users

Assumptions = Redirects to user.php

Test Data = Username (valid username, invalid username, empty)

Password (invalid password, valid password, empty)

Category(valid type, empty)

Steps to be Executed Data Expected Results

Enter valid Username and Empty Display an alert “Please Enter your
Username=admin,
Password and Click Login button. password correctly"

Should display an alert “Please

Enter Valid Password and Empty
Password=123 enter Your valid Username
user name and Click Login button
correctly...!"

Enter valid Username, Password Username=admin, Should display an alert “Please

and Empty type and Click Login select the catagory”
button Password=123

Should display an alert “Incorrect

Enter Invalid Password and Invalid Username =werr
username or password, Please enter
user name Click Login button Password = asd again correctly to be Logged in...!”

Username=admin, Redirects to Form2 (Administrator

Enter Username, Password,
page)
SELECT ROLE and Click Login Password=123
button
Type=admin

Table5. 1 Test Case 1 – User Authentication

Test Case 2 – Librarian Registration

Test Case ID = JCTELMS – TestCase02

Unit to Test = Registration of Librarian

Assumptions =SUCCESSFULLY REGISTERED!

Test Data = First Name(invalid name, valid name, empty)

Last Name(invalid name, valid name, empty)

Password(Valid Password, empty)

Phone number(invalid Phone number, Valid number)

Id(Valid Item Number, empty)

Username(valid username, empty)

Select Role (selected librarian, empty)

Steps to be Executed Data Expected Results

Empty First name and all
“PLease provide your first
others filled and Click Any valid data for the other fields
name”
register button

Invalid First name and Click “Frist Name must be string”

First name =kenya
register button

Empty Member ID and Click “PLease provide your correct

Any valid data for the other fields
register button ID number”

Enter Invalid phone number “phone numbur must be

Phone number=092116etf integer value”
And all others filled and
Click register button

First name kenya Successfully completes the

librarian registration
Last Name lammi

Password admin
Enter all valid filled and
Phone number 0920974103
Click Register button
Id 2090

User name admin

Role librarian

Table5. 2 Test Case 2 – Librarian Registration

5.4. Hardware and Software Requirements

The most possible way of the acquisition of the software and hardware for this system is
purchasing from the market. If they exist in this organization, it can be used as necessary.

5.4.1.Hardware Requirements
Computer

Printer

LAN network connector equipments for distributed operating system

5.4.2. Software Requirements

Installation MS-Office
 5.6. User Manual
We as a software developer had developed the following user manual to lead our custom users
easily get the way of the applications of this application software. See fig. below
 5.9. Installation
After installing both Macromedia Dreamweaver and vertigo server software do the following
steps

Step1

 Get the folder “hrm “from the Developing Team.

Step 2

 Copy the folder to WWW folder in the c:\programfiles\vertrigo

After doing these steps again, copy the folder “HRMData” from the Developing Team then,

Step3

 Paste into the folder ”data “in the C:\programfiles\vertrigo\Mysql\Data

Step4

Installation is finished.
 CHAPTER SIX

6. CONCLUSION AND RECOMMENDATION

6.1. CONCLUSION
After we have completed the project we are sure the problems in the existing system would
overcome. The “LIBRARY MANAGEMENT SYSTEM” process made computerized to
reduce human errors and to increase the efficiency. The main focus of this project is to lessen
human efforts. The maintenance of the records is made efficient, as all the records are stored in
the ACCESS database, through which data can be retrieved easily. If the numbers of records are
very large then user has to just type in the search string and user gets the results immediately.
The editing is also made simpler. The user has to just type in the required field and press the
update button to update the desired field.

Our main aim of the project is to get the correct information about a particular student and books
available in the library.

The problems, which existed in the earlier system, have been removed to a large extent. And it is
expected that this project will go a long way in satisfying user’s requirements. The
computerization of the Library Management will not only improves the efficiency but will also
reduce human stress thereby indirectly improving human recourses.

6.2. Recommendation
This application software was developed for better use for the library management system of
Jigjiga University. The system handles major of the operations that carried out in the college like
registering new book entrance and manages the librarian daily attendance with specified period
of time. For this, we strongly recommend for the system users to use our new product to handle
their daily operations easily and secured report generation by printing the daily or weekly
activities.
 References
For our further work, we used different necessary materials as references. Major of the
references we used were as follows.

1. Online library system [pdf document]. Available at:

http://www.ibm.com/developerworks/rational/library/3101.html.

2. Jigjiga College of Teacher Education library system work process printed materials.

3. Library Management System (BACHELOR’S THESIS OF TURKU UNIVERSITY OF

APPLIED SCIENCES | Jin Jiawei); through Google search.

4. Katipo Communications Ltd. [PDF document]. Available at:

http://www.parliaments.info/downloads/16%20KOHA%20-%20Presentation.pdf.

5. Software Engineering course materials.

6. Library Management System available at: http://www.answers.com/topic/ library.

Appendex

Questions asked during requirement gathering using interview

Q1. What are the objectives of your System?

Q2. What is the mission of your System?
Q3. How many employees do you have?
Q4. How does your current system work?
A. Is it manual?
B. is it computerized?
C. is it semi automated?