FDRE TECHNICAL AND VOCATIONAL TRAINING INSTITUTE

ETHIO-ITALY POLY TECHNIC COLLEGE SATTELLITE DEGREE CAMPUS

INFORMATION COMMUNICATION TECHNOLOGY

PROJECT TITLE
WEB BASED LIBRARY MANAGEMENT SYSTEM FOR ETHIO_ITALY
POLY TECHNIC COLLEGE

Name ID
Degife Seifu ETUSR/031/2013
Fate Abdi ETUSR/037/2013
Motuma Abera ETUSR/044/2013
Alemayehu Mulat ETUSR/027/2013

A Project Submitted to Ethio-Italy Poly Technic College, in Partial Fulfillment for

Bachelor of Science Degree at Department of Information Communication
Technology
Advisor: Mr. Eyasu D. (Msc)

Dire-Dawa, Ethiopia
April, 2024

FDRE TECHNICAL AND VOCATIONAL TRAINING INSTITUTE ETHIO-

ITALY POLY TECHNIC COLLEGE SATTELLITE DEGREE CAMPUS
INFORMATION COMMUNICATION TECHNOLOGY
i
 1. Degife Seifu
2. Fate Abdi
3. Motuma Abera
4. Alemayehu Mulat

Advisor: Inst. Eyasu D.

This is to clarify that the project prepared by, Degife Seifu, Fate Abdi, Motuma
Abera, Alemayehu Mulat, titled: LIBRARY MANAGEMENT SYSTEM and
submitted in partial fulfillments for Bachelor of Science Degree in Information
Communication Technology complies with the regulations of the Institute and
meets theaccepted standards with respect to originality and quality.

Advisor Approval:

Advisor Name Signature Date

Approved by the Examining committee:

Name Signature Date

Examiner:

Examiner:

Examiner:

ii
Contents

Acknowledgment ....................................................................................................................... vi

Abbreviation and Acronyms ......................................................................................................... vii

List of Tables ............................................................................................................................... viii

List of Figures ................................................................................................................................ ix

Abstract ....................................................................................................................................... x

CHAPTER ONE ........................................................................................................................... 11

1. INTRODUCTION ................................................................................................................ 11

1.1. Background of Project .................................................................................................... 12

1.2. Statement of the problem ............................................................................................... 12

1.3. Objectives of the Project ................................................................................................ 13

1.3.1. General Objectives. .................................................................................................... 13

1.3.2. Specific Objectives ..................................................................................................... 13

1.4. Scope of the Project........................................................................................................ 13

1.5. Significance of the project.............................................................................................. 13

1.6. Beneficiaries of the Project ............................................................................................ 14

1.7. Methodology .................................................................................................................. 14

1.7.1. Data Gathering Methodology ..................................................................................... 14

1.7.2. Development Methodology ........................................................................................ 15

1.7.3. Development Tools..................................................................................................... 16

1.8. Feasibility Study ............................................................................................................. 17

1.8.1. Economic Feasibility .................................................................................................. 18

1.8.2. Technical Feasibility................................................................................................... 18

1.8.3. Operational Feasibility ............................................................................................... 19

iii
1.9. Project Plan .................................................................................................................... 19

1.9.1. Project Time Scheduling ............................................................................................ 19

1.9.2. Budget plan estimation ............................................................................................... 20

CHAPTER TWO .......................................................................................................................... 21

1. REQUIREMENT ELICITATION ........................................................................................ 21

2.1. Overview of Existing System ......................................................................................... 21

2.2. Proposed Solutions ......................................................................................................... 22

2.3. Preferred Solutions ......................................................................................................... 22

2.4. Domain Modeling with CRC Card................................................................................. 23

2.5. Essential use case diagram ............................................................................................. 24

2.6. Essential use case documentation .................................................................................. 25

2.7. Essential user interface prototype .................................................................................. 31

Chapter Three ................................................................................................................................ 32

3. System Analysis .................................................................................................................... 32

3.1. Overview of the new system .......................................................................................... 32

3.2. System Requirements ..................................................................................................... 32

3.2.1. Functional Requirements ........................................................................................ 32

3.2.2. Non-functional Requirements ................................................................................. 33

3.3. System modeling ............................................................................................................ 34

3.3.1. System use case diagram ........................................................................................ 35

3.3.2. System Use Case Diagram Documentation ............................................................ 36

3.3.3. Sequence Diagram .................................................................................................. 54

3.3.4. Activities Diagram .................................................................................................. 55

3.3.5. Class Diagram ......................................................................................................... 58

Chapter Four ................................................................................................................................. 59

iv
4. System Design ...................................................................................................................... 59

4.1. Design Goals .................................................................................................................. 59

4.2. System Architectural ...................................................................................................... 60

4.3. Sub-System Decomposition ........................................................................................... 61

4.4. Hardware/Software Mapping ......................................................................................... 62

4.5. State Chart Diagram ....................................................................................................... 64

4.6. Collaboration diagram .................................................................................................... 65

4.7. Deployment Diagram ..................................................................................................... 66

4.8. Persistent Data Storage and Management ...................................................................... 67

4.9. Graphical User Interface Design .................................................................................... 71

CHAPTER FIVE........................................................................................................................... 72

5. CONCLUSIONS AND RECOMMENDATION ................................................................. 72

5.1. Conclusions .................................................................................................................... 72

5.2. Recommendations .......................................................................................................... 73

References ..................................................................................................................................... 74

v
Acknowledgment
First of all , we would like to express our heartfelt gratitude to "The Almighty God" for providing
us with this opportunity and providing us with the physical strength and a pleasant mind to
complete this proposal work, as well as to those who encourage and satisfy our needs to complete
this project work. We are grateful to our lab helpers for allowing us to create our proposal in a
well-equipped lab. We would also like to express our heartfelt gratitude to our advisor, MR.
Eyasu D. for his input on everything from planning our proposal to the completion of all of our
operations. We would also like to outspread our salutation to the Department of ICT for their
logistic support for proper working conditions and smooth running of the study.

vi
Abbreviation and Acronyms

EIPTC ............................................................. Ethio_Italy Polly Technic College

FDRE ............................................................. Federal Democratic Republic of Ethiopia

TVETI ............................................................. Technical and Vocational Training Institute

CD ............................................................ Compact Disk

DVD ............................................................. Digital Versatile Disk

PC............................................................ Personal Computer

HTML ............................................................ Hypertext Markup Language

CSS ............................................................ Cascading style sheet

PHP ............................................................. Hypertext preprocessing

UML............................................................ Unified Modeling Language

MySQL ............................................................ My Structural Query Language

vii
List of Tables
Table 1: Project Time Scheduling ................................................................................................. 19
Table 2: Budget plan estimation ................................................................................................... 20
Table 3:CRC Card for Users ......................................................................................................... 23
Table 4:CRC Card for Librarians .................................................................................................. 24
Table 5:Use case description for Generate report ......................................................................... 25
Table 6:Use case description for Add Books. ............................................................................... 26
Table 7:Use case description for Delete books ............................................................................. 27
Table 8:Use case description for Remove books .......................................................................... 28
Table 9:Use case description for Borrow book ............................................................................. 29
Table 10:Use case description for Return book ............................................................................ 30
Table 11:Use case description to validate admin login ................................................................. 36
Table 12:Use case description for add librarian (member) ........................................................... 47
Table 13:Use case description for creating an account. ................................................................ 47
Table 14:Use case description for removing the account. ............................................................ 48
Table 15:Use case description for removing librarian. ................................................................. 49
Table 16:Use case description for adding a new book. ................................................................. 50
Table 17:Use case description for removing outdated books. ...................................................... 50
Table 18:Use case description for changing password. ................................................................ 51
Table 19:Use case description for Borrow books ......................................................................... 52
Table 20:Use case description for return books ............................................................................ 53
Table 21:Activity diagram description.......................................................................................... 55
Table 22:persistent data management for Admin ........................................................................ 67
Table 23:persistent data management for labrarian ...................................................................... 67
Table 24:persistent data management for user .............................................................................. 67
Table 25:Access control and security ........................................................................................... 70

viii
List of Figures
Figure 1:Essential use case diagram ............................................................................................. 24
Figure 2:Essential user interface prototype ................................................................................... 31
Figure 3:Use case diagram ............................................................................................................ 35
Figure 4 Sequence diagram for login......................................................................................... 54
Figure 5 Sequence diagram for adding book ............................................................................ 54
Figure 6 Sequence diagram for removing librarian ................................................................ 55
Figure 7 Activity diagram for admin login ............................................................................... 56
Figure 8 Activity diagram for adding librarian ....................................................................... 56
Figure 9 Activity diagram for removing librarian ................................................................... 57
Figure 10 Activity diagram for removing the book ................................................................. 57
Figure 11 Activity diagram for changing password................................................................. 57
Figure 12 class diagram .............................................................................................................. 58
Figure 13 Architectural design of system ..................................................................................... 60
Figure 14 Subsystem decomposition diagram .......................................................................... 61
Figure 15 Create account state diagram ................................................................................... 64
Figure 16 Login state diagram ................................................................................................... 64
Figure 17 Collaboration diagram for admin login ................................................................... 65
Figure 18 Collaboration diagram for registration ................................................................... 65
Figure 19 Deployment Diagram................................................................................................. 66
Figure 20 Entity-relationship diagram/database design ......................................................... 68
Figure 21 User interface prototyping for login page................................................................ 71

ix
 Abstract
A web based library system is used to handle book information and students who borrows books.
It helps to grant information on any book present in the library to the user as well as the staff
members. It keeps a track of book issued, returned and added to the library.
The administrators have the capability to open all sectors of the program and edit librarian’s
information while the librarian is limited to adding book and student records but is not allowed to
update or delete any recorded detail and transactions that had been recorded in the system. The
purpose of the library borrowing system is to provide quality services. It aims to provide a good
library borrowing system. The system provides a feature that can easily manage student’s
information, book details and manage borrowing transactions.

The project was designed with the use of PHP, CSS and Java script which is an integrated
development environment made by MYSQL database server. It can be used to develop web
based system and graphical user interface applications along with windows form application
websites.

x
 CHAPTER ONE
1. INTRODUCTION
Ethio_Italy Poly Technic College is a governmental college found in Dire Dawa city, Ethiopia
country. EIPTC provide governmental higher education opportunities for students. It is one of
the growing new governmental colleges in the country. The EIPTC as a 'Center for Excellence'
was born out of the dynamic ideas and the desire to assist the national and regional endeavors to
provide an adequate number of total quality higher education institutions.
A library system is software that had been developed to handle basic housekeeping functions of a
library. It helps to grant information on any book present in the library to the user as well as the
staff members. It keeps a track of book issued, returned and added to the library.
Currently EIPTC is using a library system which operates manually. Forms are given to the
Librarian and they fill them of using pens. The manual library system is very time consuming
and a tiresome task. The primary complaint of some Librarians with this manual system is the
tiresome task of searching records. The fast changed of technology describe a lot to the
development of the library system. The computerized library system may help the academe.

11 | P a g e
1.1. Background of Project
Web base library management system is a software application that refers to small or medium-
sized library systems. Librarians manage the library using a computerized system, in which they
may record various transactions such as book issues, returns, new book additions, new student
additions, and so on, use it. This system also includes books and student maintenance modules,
which maintain track of the students who use the library as well as a complete description of the
books in the library. There will be no loss of book or member records with this computerized
method, which is common when a no computerized approach is employed. The Library
Management System also has a report module. If the user is an administrator, he or she can
generate several reports, such as a list of enrolled students, a list of books, an issue report, and a
return report. When compared to non-computerized library systems, all of these modules can
assist librarians in managing the library with greater ease and efficiency.

1.2. Statement of the problem

In EIPTC library management system is operated manually due to that the college is facing a lot
of problems. Currently EIPTC library system is passing through all those mentioned problems.
Since the records and provides services are paper-based there is the challenge of retrieval. The
system was timed, not secured, lack of efficiency and effectiveness. In general, the current
EIPTC College library management system has many problems. These are -

 The current system is bulky, It is inefficient because it follows manual system service,
 Documentation is not easy to retrieve and record,
 Redundancy of books. In the documentation system,
 Borrowing to instructors is allowed by preparing a form to accept some input from them
such as Name, code, signature, Telephone, department, ID, the title of book, date, charge
date, difference symbol, and signature by using a manual system.
 It wastes much time searching the books
 It makes the work bulky
 When we went to borrow the book for the user it that done by using a name, ID,
department, telephone, book code data taking the book by using a manual system.

12 | P a g e
1.3. Objectives of the Project
There are two types of objectives the first one is general objective and the second is specific
objectives.

1.3.1. General Objectives.

The general objective of this project is to design and develop a web based library management
system.

1.3.2. Specific Objectives

Our specific objective is to develop a user-friendly user interface for our system that:
 Requirement gathering and analyzing that requirement of the system.
 To Design friendly user interface for the proposed system.
 Implementing and testing the new system
 To develop an appropriate database that is easily manageable.
 Test and Maintenance of the Proposed system

1.4. Scope of the Project

The scope of our project plans and targets in developing and implementing web based Library
Management system to replace and solve the problems of the existing system within the current
manual system.

Our scope is to develop system that:-

 Book management (Inserting , updating, searching, and others)
 Borrowing and returning of books
 Manage account (means create, deactivate and update account).
 Search item information.
 Generating reports
1.5. Significance of the project
The goal of this system is to make library functionality more independent of human effort by
making it simple to comprehend and use. This project is useful for keeping track of all book and
library information as well as automating the maximum number of books that visitors want to
read.

13 | P a g e
The software will be able to manage all of the required data.
In general, the system makes a significant contribution, such as:
 Improve user satisfaction
 Decrease loss of data
 Increase time management
 Decrease human power
 To give timely and accurate reports (daily, weekly, monthly, etc.),
 Make it simple for employees to communicate.
 Enable workers to get all information easily and fully
 Decrease the loss of necessary data
1.6. Beneficiaries of the Project
Following the development of the system, it provides a excess of functions for users, employees,
managers, college, and the country as a whole, among other things.

Users: -to access everything easily. This means that if someone wants to read in the library he/she knows
whether the book exists reading and for reading different books easily.

Administrators - The system will lighten the paper works of the school as requirement reports.
Librarian - The Librarian can monitor well the students who borrow books in the library
through reliable and correct reports.
Students - The students can easily borrow book without spending so much time.
Teachers - The students can be provided quick access for the library items so the teachers won’t
worry enough if the students can manage to make a library research task given by them.
Future Researchers - The future researchers can use the study as their guide of reference for
their future researches also that is related to database management system.

1.7. Methodology
1.7.1. Data Gathering Methodology
To gather data from the different users and managers of the existing system project team used the
following techniques.
 Interview: Different users of the existing system along with workers were involved to
have an understanding of how the system works, what are its and different features,

14 | P a g e
 factors, and advantages as well as advantages so we obtain detailed information from
them.
 Direct Observation: We will observe some Library Management systems on the
internet. We will have also observed the existing Library Management systems to know
how the process is going and to understand the management features it provides.
 Document Analysis: To get information about the background of the system project
team will review necessary documents and books that support this project.
1.7.2. Development Methodology
We decided to use the object-oriented system analysis and design (OOSAD) method for system
analysis and design because use object-oriented approach has the features like inheritance, which
enables the reuse of code, encapsulation, and polymorphism.
The object-oriented methodology is used because of the following reason:
 It implements the concept of object orientation like inheritance, encapsulation, and
polymorphism.
 The ability to challenge the problem domains.
 To make simple communication among user analyses is Entity-relationship programmers.
 Use case diagram, Activity diagram, sequence diagram, class diagram, data modeling,
and deployment diagram.

As a result, we selected to use Incremental Model. Because our project has need to the
following will be used to design the system.
 A project has a lengthy development schedule.
 When Software team are not very well skilled or trained.
 When the customer demands a quick release of the product.
 You can develop prioritized requirements first.
 The LMS can be built incrementally, starting with basic features and gradually
adding more functionality.
 It makes backward and forwards for error correction, it is suitable for developing a good
and efficient system.
1. Requirement Analysis
2. Analysis
3. Design

15 | P a g e
 4. Implementation
5. Test
6. Maintenance
1.7.3. Development Tools

Hardware and Software Tools

Hardware and software tools required for successful completion of the projects are listed below
with their respective significance. Hardware tools required are:-
Personal computer (PC): Almost all tasks of our project are performed on computer
Flash: Required for data movement
Disks (CD, DVD): Necessary for the movement of relevant data and for backup and recovery
mechanism.
Printer: To print documentations
Software development tools: are computer programs used by software development tools to
create, debug, manage and support applications, frameworks, systems, and other programs.
There are several tools that can be used for developing a Web-based Library Management
System. Here are some of the commonly used tools:

 HTML: is used for creating the structure of the web pages in the system.
 CSS: is used for styling the web pages in the system.
 JavaScript: is used for adding interactivity to the web pages in the system.
 JQuery: is a fast, small, and feature-rich JavaScript library that can be used for
simplifying the client-side scripting of HTML in the system.

 Bootstrap: is a popular front-end framework that can be used for developing

responsive and mobile-first web pages in the system.
 PHP: is a server-side scripting language that can be used for developing dynamic
web pages in the system
 MySQL: is a popular open-source relational database management system that can be
used for storing and managing data in the system.
 Sublime: is a text editor that is used for writing and editing code, markup, and
prose.

16 | P a g e
  XAMPP: stands for Cross-Platform (X), Apache (A), MySQL (M), PHP (P) and Perl
(P). It is a simple, lightweight Apache distribution that makes it extremely easy for
developers to create a local web server for testing purposes.
 Mozilla Firefox: is a vast and powerful tool. Over the course of a few decades, the
internet has changed the way we work, the way we play and the way we interact with
one another. Depending on how it’s used, it bridges nations, drives commerce,
nurtures relationships, drives the innovation engine of the future and is responsible
for more memes than we know what to do with.
 MS word: allows you to create professional-quality documents, reports, letters, and
resumes. Unlike a plain text editor, Microsoft Word has features including spell
check, grammar Check, text and font formatting, HTML support, image support,
advanced page layout, and more.
 StarUML: to draw diagrams such as use cases diagrams, class diagrams, sequence
diagrams, collaboration diagrams, activity diagrams and state charts
 Adobe Photoshop and Picasso: to edit images and texts:

Other Requirements for our System Development

 Internet Connection: Since our system is web based, it is very necessary requirement. It
is also help us to extract relevant information about our project from internet.
 Stationeries (pen, paper): For writing all necessary documentations associated with the
project
 Note book: To take notes during data collection and for other documentations

1.8. Feasibility Study

Feasibility study is the test of the system proposal made to identify whether the user needs may
be satisfied using the current software and hardware technologies, whether the system will be
cost effective from a business point of view and whether it can be developed with the given
budgetary constraints.

17 | P a g e
 1.8.1. Economic Feasibility
Our systems to be developed are economically feasible and the benefit is outweighing the cost.
Since this project computerizes the existing Manual system, by now the reduction of cost for
materials used in manual operation becomes beneficiary to the organization. Generally the
system that we will develop, Web based Library Management System brought a number of
tangible and intangible benefits.
 Tangible benefit In the project going to be computerized there will be reduction of cost
for materials used for manual operation.
 The intangible benefit that the system will give is listed as following: -
 Reduce Resource Consumption
 Increase security
 Increase speed of activity.

1.8.2. Technical Feasibility

Technical feasibility is the measure of the practicality of a specific technical solution and the
availability of technical resources. In technical feasibility we should notify that our new system
can implement with current technology and also the customer has enough experience using that
technology. Technical feasibility addresses three main things:
 Is the technology practical
 Do we currently passes the necessary technology
 The ability to do on the technologies
We are using currently available technologies such as:
 MySQL
 XAMPP
 Mozilla Firefox
 StarUML

 Window 10
 Sublime

Generally we can say that the new system is technically feasible.

18 | P a g e
 1.8.3. Operational Feasibility
Operation feasibility is used to check whether the project is operationally feasible or not. Our
system requires very less human power. It provides simple user interface in which the employee
of office can access easily, and more accurately. Maintenance is less and easy. The system will
have GUI interface and very less user-training is required to learn it. The system is so simple to
use, so no any special skills will be required to use the system.
So the system is operationally feasible
1.9. Project Plan
1.9.1. Project Time Scheduling
We will arrange activities because completing the project is not a one-person job, according to
the department's timeline, the project will be submitted. The following table contains the project
timetable.
The table below represents the main activities of the project together with their respective start
and end date.

No Activity Start Date End Date Duratio Compl 2024

ete
n

De Jan Feb Mar April

c

1 Requirement Dec Jan 20/2024 30 days

Gathering 20/20233

2 Requirement Jan 21/2024 Jan 29/2024 8days

Analysis

3 System design Jan 30/2024 Feb 30/2024 30 days

4 Implementation Mar 1/2024 Mar 30/2024 30 days

5 System Testing April April 21 days

1/2024 21/2024

6 Submission and
defense

Table 1: Project Time Scheduling

19 | P a g e
 1.9.2. Budget plan estimation
The following table lists budget required for the successful development of the proposed system
Types of costs Tool name Quantity Unit price (in Birr) Total price (in
Birr)
PC 1 8000 24000.00
Flash(32 GB) 1 400 500.00
Hard ware costs CD DVD 2 100 300.00
Printing document 85 page 5 1500.00
Pen 5 20 100.00
Paper 2 packet 650 1300.00
Note book 3 50 150.00
XAMPP server 1 Free Free

Microsoft office 2007 1 Free Free

Software costs
Notepad++ 1 Free Free

Microsoft Visio 2010 1 Free Free

Adobe Photoshop 1 Free Free

Windows 7 OS 1 Free Free

Other costs Transportation cost - -

Meal cost - - 500.00

Miscellaneous cost - - 200.00

Total cost - - - 28550.00

Table 2: Budget Plan Estimation

20 | P a g e
 CHAPTER TWO
1. REQUIREMENT ELICITATION
2.1. Overview of Existing System
In this chapter, we identified major functions of the existing system and its advantages and
drawbacks, provide alternative proposed solutions for the problem identified, and some
supplementary specifications about the system like, domain modeling with CRC cards, essential
use case diagram and essential use case documentation and finally the essential user interface
prototype.

Currently Ethio_Italy Polly Technical College library provide service for different users like
students, instructors and other Member of the community but Library management system is
manual system for managing the various activities and services provided. Its main features of the
current system are support large amount of books and members data can maintain in manual
way. The basic operations on the system are like adding new books and members, searching and
updating information’s, deleting books and members in traditional way (i.e. paper based). It take
a lot of time to get particular books and members (i.e. searching is difficult and time consuming),
no proper record of data, replication of records occur and retrieve of particular data is very slow
and time consuming.

Main disadvantages of manual system are the following:

 Wastage of resource like time, human power, equipment during issuing and returning books.

 It is not reliable and efficient service for library users.

 It is difficult to search books using pockets.

 The information transaction is very late with other class of the library like store and
classification.

Main Advantage of manual system is the following:

 Since its manual method no additional knowledge about technology is required to use it.
 It’s inclusive and doesn’t require internet.

21 | P a g e
 2.2. Proposed Solutions
As described above in the above section (2.1 overview of existing system) manual system has
many drawbacks, which can be easily solved by providing:

Our Proposed system is a web based system. Through our system user can add books, search
books, update information, borrow and return books in quick time. System has User friendly
interface, Fast access to database, less error, Quick transaction.

1. Standards Application: This solution involves using a software application that is designed
to meet industry standards for library management. The software would be installed on a
computer and would allow librarians to manage the library’s collection, track circulation, and
generate reports.

2. Web-based Application: This solution involves using a web-based application that can be
accessed from any device with an internet connection. The application would allow librarians to
manage the library’s collection, which mainly focuses on basic operations in a library like
adding new books, updating new books, searching new books and deleting books facility to
borrow and return books.

3. Integrated Application: This solution involves using an integrated library system that
combines multiple library functions into a single software package. The software would be
installed on a computer and would allow librarians to manage the library’s collection, track
circulation, generate reports, and perform other library functions.

4. Mobile Applications: This solution involves using a mobile application that can be installed
on a smartphone or tablet. The application would allow librarians to manage the library’s
collection, track circulation, and generate reports.

2.3. Preferred Solutions

Web based Library management system: is an application program that is stored on a
remote server and delivered over the internet through a browser interface. Provides access to
a software system using a computer and internet connection.
The project Library Management System is developed in PHP and other programming
language which mainly focuses on basic operations in a library like adding new books,
searching new books, and updating new books, and deleting books, facility to borrow and
return books. Our system is easy to use for both beginners and advanced users.

22 | P a g e
 So we preferred to develop web based library management system for Ethio-Italy
Polytechnic College for the advantages of:-
 Accessibility across devices for users: can be accessed by using laptops, computers and
mobile devices with internet access.
 Increased flexibility and scalability. Just as upgrades are simple to implement, it is also
simple to increase the application's capacity to grow with your library management
system. As you require more processes to happen simultaneously, your web-based
software can facilitate it.
 It is easy to implement: we find web-based system easier to implement than others.
 Doesn’t require any additional hardware devices than the college already has.
 Protecting your data: Web-based applications offer a good way of accessing centralized
data securely.

2.4. Domain Modeling with CRC Card

A class responsibility collaborator (CRC) model is a collection of standard index cards that have
been divided into three sections, class, responsibility and collaborator. A class represents a
collection of similar objects, a responsibility is something that a class knows and a collaborator is
another class that a class interacts with to fulfill its responsibilities.

Class Users
Responsibility Collaborator
 Borrow books Librarians

 Return books

Table 3: CRC Card for Users

23 | P a g e
Class Librarians
Responsibility Collaborator
 Add book Users

 Drop books
 Search books
 Update books

Table 4: CRC Card for Librarians

2.5. Essential use case diagram

24 | P a g e
Figure 1: Essential use case diagram

25 | P a g e
 2.6. Essential use case documentation
Use case number 1
Use case name Generate report
Actors  Librarian
Description  Allow librarians to generate report
Pre-condition  the librarian must be an authorized to perform this activity
Flow of action  Librarian want to generate report

 Librarian enter username and password to the system

 The system verifies the librarian is legal to generate report

 The librarian selects the place for report

 The librarian selects operation for which report to be generated
Alternative Flow of  If the librarian username and password is incorrect system displays
Action incorrect username or password and displays try again
Post-condition  report will be generated

Table 5: Use case description for Generate report

Use case number 2

Use case name Add Books
Actor  librarian
Description Allow librarians to add items in to the database
Pre-condition the librarian must be an authorized to perform this
activity

26 | P a g e
Flow of action  Authorized librarian want to add item in to database
Librarian enter username and password to the system
 The system verifies the librarian is legal or not to enter
to this operation

 The librarian selects the place for the item to be inserted

 The librarian inserts the item in to the system

 The system checks the validity of the item inserted

 The system add the item in to the database

Alternative Flow of If the librarian username and password is incorrect
Action system displays incorrect username or password and
displays try again

Post condition  the item will be inserted in to the database

Table 6: Use case description for Add Books.

27 | P a g e
Use case number 3
Use case name Delete books
Actor  librarian
Description  Allow librarians to delete items from the database
Pre-condition  the librarian must be an authorized to perform this activity

 Authorized librarian want to delete item from the database

Flow of action
 Librarian enter username and password to the system

 The system verifies the librarian is legal or not to enter to this

operation

 The librarian selects the place of the item to be deleted

 The librarian selects the type of the item to be deleted

 The librarian types the item to be deleted

The alternative flow of action  If the librarian username and password is incorrect
system displays incorrect username or password and
Post-condition  the item will be deleted from the database

Table 7: Use case description for Delete books

28 | P a g e
.

Use case number 4

Use case name Remove books
Actor(s)  librarian
Description  The administrator and librarian login into the system to
remove outdated books.
Pre-condition  Book information is not deleted
Flow of action  Include validate admin librarian login use case)
 Librarian selects the book transaction.
 Librarian select the book, whose book information is
about to be removed.
 Librarian select the book delete book transaction.
 The system prompts a confirmation dialog. If she/he
sure permanently deletes the book information,
Alternative flow of  If librarian cancels the delete transaction the remains in
Action the system
Post-condition  The book information has been removed.

Table 8: Use case description for Remove books.

29 | P a g e
Use case number 5
Use case name Borrow book
Actors  user
Description  Allow users to borrow book

Pre-condition  the user should have to be a renewed College ID

Flow of action  User want to borrow book

 The librarian request ID of the user and verify its validity

 The librarian verifies the ID of the user

 The user requests the book he/she wants to borrow

 The librarian enters the users request to the system

 The system check for the availability of the requested book

 The librarian enter both the details of the book and the borrower in to
the system
Alternative Flow of  If the user ID is not valid the librarian rejects the user
Action  If the requested book is not available the system displays book not
found

Post-condition  The user borrow the book

Table 9: Use case description for Borrow book

30 | P a g e
Use case number 6
Use case name return book
Actors  user
Description  Allow users to return book

Pre-condition  the user should have to be a renewed College ID

Flow of action  User want to return book

 User go to the return counter

 The librarian request the ID of the borrower

 The librarian enter both the detail of the borrower and the book in to
the system

 The system check the detail

 The user return the book to the librarian

 The librarian order the system to delete the user from

the borrowed list of the users
 The system delete the book from borrowed list of books

 The use case ends The librarian inform the system to generate a
report
Alternative Flow of  If the detail of that book is not the same as the recorded
Action detail the librarian cannot accept it.

Post-condition  The user returns the book

Table 10: Use case description for Return book

31 | P a g e
 2.7. Essential user interface prototype

Figure 2: Essential user interface prototype

32 | P a g e
Chapter Three
3. System Analysis
3.1. Overview of the new system
The analysis is the process of studying a procedure to identify its goal and purposes and create
systems and procedures that will achieve efficiently. To achieve them this chapter will see, the
analysis phase of the project that contains a detailed description of the operation of the existing
system, an overview of the new system, requirement analysis of the new system, and system
analysis to simplify the design and implementation of complex programs. The project with
Ethio_Italy Polly Technic College Library Management System is a web based system for
monitoring, controlling transactions, and reading or uploading the books, pdf, and ppt for us
online. Library Management System is a collection of information that is stored and accessed
electronically. This digital Library system is available for two tasks. The first is Management
System: which mainl y focuses on basic operations in the library like adding members, adding
new books, updating new information, and searching for books. The second is online access to
reference books. The library manager and the librarians are high-level users of’ the EIPTC
Library Management System. The purpose of the system is as follows:-
 To make the services fast and easy to use.
 To save time and cost wad to searching available books all over book shelves.
 To search resources easily.
 Online service on the users.
3.2. System Requirements
3.2.1. Functional Requirements

A functional requirement describes what a software system should do. The

functional requirements focus on requirements of the proposed system. It deals
with what the system should do or provide for users. The major functional
requirement of the proposed system includes

 Login
 Admin
 Add Librarians
 Create account

33 | P a g e
  Add books
 Remove Librarians
 Get book list
 Remove books
 Change password
 Search books
 Logout
 Liberians
 Add Books
 Remove Books
 Get book list
 Search books
 Logout
 User
 Search books
 Get book list
 Borrow books
 Return Books
 Logout

3.2.2. Non-functional Requirements

A non-functional requirement is a requirement that specifies criteria that can be used to judge
the operation of a system, rather than specific behaviors. The following are non-functional
requirements.
 Reliability: - the system should not fail more than once a month.
 Usability: - the system that have we developed should be easy to learn and operate. It
will need only two days of training to use the system.
 Availability: - this system is available everywhere and at all times for those who have
access to use the system.
 Performance: - the system will have good performance i.e. fast response time and

34 | P a g e
 optimal workload.
 Adaptability: - this software is adaptable by any organization.
 Correctness: - the results of the function are pure and accurate.
 Flexibility: - the operation may be flexible and reports can be presented in many
ways.
 Maintainability: - after the deployment of the project if any occurs then it can be
easily maintained by the software developer.
 Portability: - the software can be deployed on any machine.
 Reusability: - the data that are saved in the database can be reused if needed.
 Robustness: - if there is an error in any window or module then it does not affect the
remaining part of the software.

3.3. System modeling

Analysis Model
Here, for the analysis of our project, we have selected the unstructured one which we call object-
oriented methodology system analysis and design method specifically UML (Unified Modeling
Language) model. We have selected this because of the following reasons: -
 To simplify the design and implementation of a complex program.
 To make it easier for teams of designers and programmers to work on a single software
project.
 To enable a high degree of reusability of designs.
 To decrease the cost of software maintenance.
As we mentioned in the above section, in this project, we have used an object-oriented system
development methodology. To develop this project, we have used an object-oriented system and
analysis models. From the object-oriented system analysis method, we have used the following
design diagrams listed below.
 Use case diagram
 Activity diagram
 Sequential diagram
 Class diagram

35 | P a g e
Use case modeling
In its simplest form, a use case can be described as a specific way of using the system from a
user’s (actor’s) perspective and describes what the system does from that point of view. Use
cases provide a means to capture system requirements, communicate with the end users’ domain
experts, and test the system. Use cases are best discovered by examining the actors and defining
what the actor will be able to do with the system. The actors in the system are the following:
 User
 Librarian
 Administrator
3.3.1. System use case diagram

Figure 3: Use case diagram

36 | P a g e
 3.3.2. System Use Case Diagram Documentation

A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. A use case is a collection of conceivable sequences of interactions between
systems and users in a specific environment, all of which are tied to a specific purpose. The use
cases of the system are the following:

Table 11: Use case description to validate admin login

Use case number 1

Use case name Validate Login
Actors  Admin, librarians, users.
Description  The actors must be login with the administration to modify the system
 The users and librarians login into the system for searching books
downloads books and get a book list.
Pre-condition  Administrator, user, and librarian must have user name and password.
Flow of action  They are on the home page to log in to the system.
 The system promotes them to enter a username and, password.
 They enter their username and password and click the login on.
 The system verifies that all the filled have been filled out and
validates the system successfully logged in the system.
Alternative Flow  If the system determines that the entered user name and password
of action are invalid, the system admin displays an error message and prompts
 Administrator adds books, adds librarians, and creates accounts for
Post-condition users, librarians, and others.
 Users see a list o f books, s e a r c h for books, download books, and
get information.

37 | P a g e
Table 12: Use case description for add librarian (member)

Use case number 2

Use case name Add librarian (member).
Actors  Admin
Description  The administrator login into the system to register the librarian
(member).
Pre-condition  The administrator must have a user name and password and the
admin wants to add a new librarian.
Flow of action  Include validating login (this is admin must login in before adding
Librarian (member) added.
 Admin select add librarian in transaction menu.
 System displays a form
 Admin and new librarian fill the form and select add librarian.
 System validates librarian information.
Alternative Flow of  If librarian information is not valid, t h e system displays an Error
Action message until the admin or librarian entered valid information.
Post-condition  New librarian is added.

47 | P a g e
 Table 15: Use case description for removing librarian.

Use case number 3

Use case name Remove librarian.
Actor  Admin
Description  The administrator login into the system to remove librarians
Pre-condition  Administrator must have user name and password and librarians
and librarian information is not deleted
 Include validate login use case.
Flow of action  The admin selects display user list.
 System displays user list table.
 The admin selects the librarian and selects delete librarian.
 The system prompts the admin that she or he is sure to
permanently delete the librarian information
 The admin confirms that she or he is sure to remove
librarian information, the system removes all the information
that the librarian has.
The alternative flow of action  If the admin cancels the delete information transaction with the
librarian, information remains maintained on the system.
Post-condition  The librarian information has been removed.

48 | P a g e
Table 16:Use case description for adding a new book.

Use case number 4

Use case name Add a new book.
Actor  Admin librarian
Description  The administrator login into the system to add books.
Pre-condition  Administrator must have a user name,
password, and librarians, and the book is not
 registered or, no more number of books.
Flow of action Include validate admin login use case
 The admin selects book transaction
 The admin selects add book publisher, copyright, and other
information.
 The system validates if the entered values are correct

Alternative flow of  If the entered values are incorrect, the system asks the user to
Action enter valid information.
Post-condition  The books have been added.

Table 17: Use case description for removing outdated books.

Use case number 5

Use case name Remove books
Actor(s)  Admin, librarian
Description  The administrator and librarian login into the system to
remove outdated books.
Pre-condition  Book information is not deleted
Flow of action  Include validate admin librarian login use case)
 Admin/librarian selects the book transaction.
 Admin/librarian select the book, whose book
information is about to be removed.
 Admin/librarian select the book delete book
transaction.
 The system prompts a confirmation dialog. If she/he
Alternative flow of  If Admin/librarian cancels the delete transaction the
Action remains in the system

49 | P a g e
Post-condition  The book information has been removed.

50 | P a g e
Table 19:Use case description for Borrow books

Use case number 6

Use case name Borrow book
Actors  user
Description  Allow users to borrow book

Pre-condition  the user should have to be a renewed College ID

Flow of action  User want to borrow book

 The librarian request ID of the user and verify its validity

 The librarian verifies the ID of the user

 The user requests the book he/she wants to borrow

 The librarian enters the users request to the system

 The system check for the availability of the requested book

 The librarian enter both the details of the book and the borrower in to
the system
Alternative Flow of  If the user ID is not valid the librarian rejects the user
Action  If the requested book is not available the system displays book not
found

Post-condition  The user borrow the book

51 | P a g e
Table 20:Use case description for return books

Use case number 7

Use case name return book
Actors  user
Description  Allow users to return book

Pre-condition  the user should have to be a renewed College ID

Flow of action  User want to return book

 User go to the return counter

 The librarian request the ID of the borrower

 The librarian enter both the detail of the borrower and the book in to
the system

 The system check the detail

 The user return the book to the librarian

 The librarian order the system to delete the user from

the borrowed list of the users
 The system delete the book from borrowed list of books

 The use case ends The librarian inform the system to generate a
report
Alternative Flow of  If the detail of that book is not the same as the recorded
Action detail the librarian cannot accept it.

Post-condition  The user returns the book

52 | P a g e
 3.3.3. Sequence Diagram

The sequence diagram of our proposed system is used primarily to show the interactions
between objects in the sequential order. The main purpose of a sequence diagram our system
is to define event sequences that result in some desired outcome.

Figure 4 Sequence diagram for login

Figure 5 Sequence diagram for adding book

53 | P a g e
 Figure 6 Sequence diagram for removing librarian
3.3.4. Activities Diagram

Active diagrams are used to model the flow of an object as it moves from state to state at
different points in the flow of control. It is essentially a flow chart that emphasizes the
activity that takes place over time. Activity diagrams can be used to model higher-level
business process at the business unit level, or to model low-level internal class actions. It is
"Less technical" in appearance, compared to sequence diagrams, and business-minded people
tend them more quickly.
Table 21:Activity diagram description

No Symbol Name Function

1. Initial state To start the activity.

2. Decision activity To make validation.

3. Final state To terminate from the activity.

4. Arrow To show the flow of activity between two

activity.

54 | P a g e
 5. Activity Set of activities that the user and system
performing.

Figure 7 Activity diagram for admin login

Figure 8 Activity diagram for adding librarian

55 | P a g e
Figure 9 Activity diagram for removing librarian

Figure 10 Activity diagram for removing the book

Figure 11 Activity diagram for changing password

56 | P a g e
 3.3.5. Class Diagram

A class diagram describes the types of objects in the system and the various kinds of static
relationships that exist among them. The class diagram of our project can show the classes
and the relationships among classes. The class diagram of our project can store and manages
information in the system. In the phase of conceptual class modeling, we just create classes
and their relation.

Figure 12 class diagram

57 | P a g e
 Chapter Four
4. System Design

Introduction

System Design phase is process of describing, organizing, and structuring system

components at architectural design level and detailed design level. Build a system Design
converts functional models from analysis into models that helps to represent the
solution for the problem. In system Designing process we can use structured or object
oriented approaches.

In the case of online job portal system our system design modeling, will fill the gap between
the system specification produced during requirement elicitation and analysis which is
concentrated on the purpose and the functionality of the job portal system.
Library Management System design is the process of defining its components, its modules its
interfaces, and data for a system to satisfy specified requirements. It is intermediate language
between requirements and code and also it is the first step in moving from problem domain to
solution domain proceeding from abstract to more concrete representations. It is a
creative activity. It determines the major characteristics of a system. In this chapter we will
use different type of diagrams that are useful to design the proposed system.
4.1. Design Goals
The goal of design is to model the system with high quality. The design goals are derived
from non-functional requirements which means the non-functional requirement is the
description of the feature characteristics and attributes of the system as well as any
constraints that may limit the boundary of the solution. Design goals describe the qualities of
the system that the developers should consider.
 Reliability:- Wed based Library Management system should be reliable.
 Security: - Wed based library Management system should be secured, i.e., not allow
other users or unauthorized users to access data that has no the right to access it.
 Performance: - The system should respond fast with high throughput, i.e. it should
perform the task quickly.

58 | P a g e
 4.2. System Architectural
The current system doesn’t use any computerized system to provide service. Hence there is
no system architecture, so we are going to develop the proposed system architecture to
determine the type of interactions that the components are going to have.

The following figure shows the architecture of the system

Figure 13 Architectural design of system

59 | P a g e
 4.3. Sub-System Decomposition
System decomposition means a high-level function, process, and organization broken down
into lower-level components that are more detailed. It provides a logical hierarchical
decomposition of a system. In addition, is breaking a complex problem or system into parts
that are easier to conceive, understand, program, and maintain. The Library system has its
system function for these functions decompose into a sub-function of the system. That
contains the admin page, user page, the admin page is used for the administrator, and any
users use the user page in that system. Library management system decomposition diagram
put as follows:-

Figure 14 Subsystem decomposition diagram

60 | P a g e
 4.4. Hardware/Software Mapping

Hardware/Software mapping refers to the process of identifying and

establishing the relationship between the hardware components and the
corresponding software tasks in a computer system or application. It
involves determining how software functions, algorithms, or processes are
assigned to specific hardware resources for execution.

The Hardware Software mapping is described to indicate the various

hardware devices and equipment’s used in the system and its interaction
with the software components.

Key components of a web-based car rental and tracking system:

1. Client Machine

 Hardware: The client machines are the devices used by users to

access the web- based car rental and tracking system.
These can include:

 Desktop computers
 laptops
 Smartphones or tablets.
 Software: The client machines should have a web browser installed,
such as Google Chrome, Mozilla Firefox, Microsoft Edge, or Safari,
to access and interact with the web-based application. The client
machines also need an operating system (e.g., Windows, macOS,
Linux, iOS, Android) to run the web browser and communicate with
the server-side components.
2. Web Server
 Hardware: Dell PowerEdge R-Series: a rack-mounted servers
designed for data center environments. They offer a balance of
performance, storage capacity, and scalability.
 Software: Apache HTTP Server
3. Database Server
 Hardware: Oracle Exadata Database Machine. Designed to deliver
optimal performance, reliability, and manageability for MySQL

61 | P a g e
deployments

62 | P a g e
 4.5. State Chart Diagram
State chart diagram describes the flow of control from one state to another state
Create account state diagram

Figure 15 Create account state diagram

Login state diagram

Figure 16 Login state diagram

63 | P a g e
4.6. Collaboration diagram

Figure 17 Collaboration diagram for admin login

Figure 18 Collaboration diagram for registration

64 | P a g e
 4.7. Deployment Diagram
Deployment diagrams of Library Management system are used for describing the hardware components
where software components are deployed.
The software going to be developed is allowed by the UML model. UML deployment diagram shows a
physical view of the system, taking software into the real world by showing how software is assigned to
hardware and how communicates. Deployment diagrams show the configuration of run-time processing
elements and the software components, processes, and objects that live on them. Software component
instances represent run-time manifestations of code units. The purpose of deployment diagrams can be
described as:
 Visualize the hardware topology of a system.
 Describe the hardware components used to deploy software components.
 Describe runtime processing node

Figure 19 Deployment Diagram

65 | P a g e
 4.8. Persistent Data Storage and Management

Persistent data storage refers to the long-term storage and retrieval of data in a computer
system or application. It involves storing data in a way that allows it to persist even after the
system or application is shut down or restarted.

Persistent data storage is essential in various domains, including web applications, databases,
file systems, and cloud storage. It enables the preservation of critical information, facilitates
data sharing, supports data analysis and reporting, and ensures the integrity and availability of
important data over time.

Admin
Attribute Data type Null Key Relationship
Id Int Not Null Primary
Username Varchar(70) Not Null
Password Varchar(70) Not Null
Table 22: persistent data management for Admin

Librarian
Attribute Data type Null Key Relationship
ID Int Not Null Primary
Username Varchar(70) Not Null Foreign Authentication
Password Varchar(70) Not Null
Table 23:persistent data management for librarian

User
Attribute Data type Null Key Relationship
ID Int Not Null Primary
Username Varchar(70) Not Null Foreign Authentication
Password Varchar(70) Not Null
Table 24:persistent data management for user

66 | P a g e
Figure 20 Entity-relationship diagram/database design

67 | P a g e
Access control and Security

Access control refers to security features that control who can access resources in the operating
system. Applications call access control functions to set who can access specific resources. This
overview describes the security model for controlling access to Windows objects, such as files,
and for controlling access to administrative functions, such as setting the system time or auditing
user actions. The Access Control Model topic provides a high-level description of the parts of
access control and how they interact with each other. Access Control is any mechanism by which
a system grants or revokes the right to access some data or perform some action. Normally, a
user must first log in to a system, using some Authentication system. Next, the Access Control
mechanism controls what operations the user may or may not make by comparing the User ID to
an Access Control database.

Access Control systems include:

 File permissions, such as create, read, edit or delete on a file server.
 Program permissions, such as the right to execute a program on an application server.
 Data rights, such as the right to retrieve or update information in a database

68 | P a g e
 Table 25:Access control and security

Function Actors

Admin Librarian User

Login   

Add librarians 

Upload books 

Remove books   

Get booklist   

Remove outdated book  

Change password  

Download books   

Search Books   

Comment 

Logout   

69 | P a g e
 4.9. Graphical User Interface Design

Home page

Login page

70 | P a g e
Admin page

Figure 21 User interface prototyping for login page

User page

71 | P a g e
 CHAPTER FIVE
5. CONCLUSIONS AND RECOMMENDATION
5.1. Conclusions
The Project culminated in the design and implementation of a library management system
application, meant to ease the processing of library . It is capable of storing and processing book
information with high speed and accuracy, and presenting output in certain required forms. It has
some qualities such as reduction in the cost of processing; reduction in time spent in computing
book’s information and elimination of duplication of effort which makes it overshadow the
manual system of book’s record keeping. The new system is flexible and can be modified to
suite any kind of record keeping and data processing. It uses graphical user interface (GUI)
rather than commandline approach, hence is easy to use, reasonably secure, and enforces data
integrity resulting from the use of a relational database management system. With this
application, the processing of Trainee’s’ results can be system to a large extent, thereby reducing
processing time and increasing accuracy.

72 | P a g e
 5.2. Recommendations
According to the scope of our project the team develops web application. Because of the time
constraint we could not do beyond to our scopes, but in the future others developed included the
application futures like Attendance control system, seclude or timetable, able to download books
and reference, online payment, grad report. Also:-
 Used for additional library system to select core literature in other disciplines.
 Examine the expectations of academic libraries’ service to the broad public: what are the
roles of municipal, state, and federally supported institutions for public access and those
of private institutions?
 Conduct analysis of how digitized collections, both special and general, are used and by
whom.
 Foster the development of a registry of digitized collections that includes capture
information, metadata standards, and disposition of original source materials.
 Foster the development of service bureaus that would offer scanning and archiving
services.
 Foster the development of shared print repositories.

73 | P a g e
 References

[1] J. o. L. Administration, "Journal of Library Administration," Retrieved 7 November, Vols.

no-1, no. Retrieved 7 November, 2020.

[2] https://asu.edu.et/index.php, "asu.edu.et," 2. [Online]. Available:

https://asu.edu.et/index.php. [Accessed 2022 4 24].

[3] ". M. Mukherjee, "Feasibility studies and important aspect of project management.,"
International Journal of Advanced, , Vols. no. 4,, pp. 98-100, , 2017.

[4] I. F. M. T. A. I. Z. M. Akar, "International Journal of Information Systems and

Engineering," International Journal of Information Systems and Engineering, Vols. no-1,
no. 2015, pp. 85-97, 2015.

[5] ". D. &. S. Rosenberg, "Use case driven object modeling with UML," Addison-Wesley," Use
case driven object modeling with UML," Addison-Wesley .

[6] ". ,. v. i. .. D. Bell, "UML basics:," The sequence diagram, pp. pp. 89-103,, 2015.

[7] .. ,. v. i. A. S. Evans, ""Reasoning with UML class diagrams," in Formal Specification

Techniques.

[8] J. R. 0. 1. JEFFERY A.HOFFER, " Modern system analysis and design," in (2004).(third
edition ed.)., 2022, pp. 137-150.

[9] A. Bahrami, Object Oriented Analysis and Design, 2009.

[10] ". M. Y. Waykar, Importance of UML Diagrams in Software Development.,.

[11] ". J. Heumann, "Introduction to business modeling using the Unified Modeling Language,"
vol. 2.

[12] ". ,. D. Bell, "Uml basics:," The component diagram," IBM Global Services., , pp. 50-61,
2004..

74 | P a g e