DEBRETABORUNIVERSIT

COLLEGE Of BUSINESS AND ECONOMICS

Department Management
Project Title:- Library Management System

NAME ID No

1, Asregd Belete. ...........................................................02307

2, Azene Birye. ....,..........................................................02724

3, Asnake Getie. ...........................................................

4, Ayalnesh Assefa. .......................................................

5,Kalkidan Tesfaye ....................................................

6,Tomas Eyasu..........................................................

Submitted to: Abebaw Alem (ph D)

January. 2025

DebreTabor,Ethiopia
CHAPTERONE:-INTRODUCTION

The concept of our system is storing and generating all the data or records of the book contained
within the library. This can be known as a general database which stores the data of the book
details.Ithelpsinsearchingthedetailsbyreducingtimeconsumption.Not only protects the details of
the books in the library but also saves all the data up to date without missing any. This is the
major benefit of the Library Management System.

1.1. Background
A Library Management System (LMS) is a software application designed to manage and
streamlinetheoperationsoflibrariesandtheirresources.The primary goal of an LMS is to enhance
the efficiency, organization, and accessibility of library services, thereby supporting the
informational, educational, and research needs of patrons.

Debre Tabor University was established in 2004 E.C. and has provided library services since its
inception. Initially, the library had only four staff members; however, that number has now
increased to 127 to meet the growing demands of its users. The library currently houses
approximately 300 personal computers and features two rooms dedicated to its digital library.
Books are added to the library's collection as needed, and a manager oversees the overall
coordination of the system.

Debre Tabor University Library consists of three main categories: the Main Library, the Socials
Library, and the Technology Library.it serves only the university students and staff members.
The library plays a crucial role in providing access to information and resources, fostering
educational and research initiatives within the region. To facilitate resource management, the
library has implemented specific borrowing limits for staff members. Each Instructors is allowed
to borrow up to 4 books at a time and Each administrative staff member is allowed to borrow up
to 2 books at a time.

1
Books must be returned to the library manager by the due date. If a borrower fails to submit the
books on time a penalty.The penalty for late returns is50 cents per day for each overdue book.
Librarians manage the borrowing process by maintaining an attendance record, which helps track
who has borrowed which books and ensures that all borrowed items are returned promptly. This
policy aims to promote responsibility among staff members while ensuring the availability of
library resources for all users.
1.2. Statement of the problem
We have observed issues in the Debre Tabor University Library System while dealing with the
existing system.

 Some books may not exist when users want to use it.

 Student cannot get library service if he or she lost ID card.

 There is workload of librarians.

 Less retrieval of information about the desired book.

 There are a lot of problem regarding time,knowledge of the librarian,cost,space,accuracy

and tiredness.

 Time:Itlookalotoftimetosearchamateriallikebookwhenauserasksforthematerials even if
the materials are not available.

 Knowledge of the librarian:- Most of the librarians are not familiar with the materials
which will cause for user not to get a material they want.

 Cost:- when we come to cost all of these work is done by paper which is costly for the
library to afford those papers.

 Space:- all information of the members and the materials is documented in the library
which needs a large amount of space to keep it.

2
 1.3. Objectives

1.3.1. General Objectives

The main objectives of this project is design and develop library management system for
Debre Tabor University

1.3.2. Specific Objectives

The specific objectives of this projects are:-

 To design a functional and reliable program using PHP.

 To help manage the effective delivery of library service.

 To evaluate its performance and acceptability.

 To design and develop the system.

 Develop data base for the system.

1.4. Scope of the projects

The system will be able to handle many services to take care of all users in a quick manner. The
system should be user appropriate,easy to use,provide easy recovery of errors and have an
overall end user high subjective satisfaction.

The Scope of system includes the following feature for the library management system.

 Manage library books

 Upload student information

 Manage book borrowers

 Handling registration of resources

 The system will be able to upload, reading,display and delete resource.

The system accessed by user name and password.
The system work only for DTU campus.
3
 1.5. Significance of the projects
Implementingaprojectfocusedonlibrarymanagementsystemholdssignificantimportanceacross various
dimensions. Firstly, it enhances operational efficiency by automating tasks such as cataloging,
membership management, and inventory tracking, thereby saving time for librarians
andimprovingoverallorganizationaleffectiveness.Secondly,Itelevatesuserexperiencethrough
features like online catalogs, digital lending options, and reservation systems, making library
resources more accessible and user-friendly.

Thissystemprovidesmanyadvantagesforthestudentsandlibrarians. Such

advantages are:-

 Minimize errors

 Eliminate paper based on records

 Easy to use the system

 Minimize work load

1.6. Feasibility Study

Feasibility is the measure of how beneficial the development or enhancement of an information
system would be to the business. Feasibility analysis is the process by which feasibility is
measured. Itisanongoingprocessdonefrequentlyduringsystemsdevelopmentprojectsinorder
toachieveacreepingcommitmentfromtheuserandtocontinuallyassessthecurrentstatusofthe project.
The various feasibility studies are: Economic Feasibility, Operational Feasibility, and Technical
Feasibility.

4
1.6.1. Economic Feasibility

Economicallythesystemismorefunctionalinreducingcostsfrombothstudentsandtheusersas it helps
to many personnel need and standard journals producing with the standard set of guides found in
the server of the web site.

The hardware and software cost estimated for the development of the system will as below.

Hardware cost estimation

Table1.Hardware Cost Estimation

No. Material Total price

1 Hard disk Free

2 Flash disc Free

3 Pc Free

5 Pen 25

6 Paper 2

7 Print 5

Total 32

5
Software cost estimation

Table2.software Cost Estimation

No. Software cost

1 XAMP server to run PHP programs Free
2 Microsoftofficeword2010 to write documentation Free
3 Operatingsystemwindow10 Free
4 MicrosoftPowerPoint2010 Free
5 Visual studio code-to edit codes Free
6 E draw Max to draw diagram Free
MYSQL database Free
Total 0.00Br

1.6.2. Technical Feasibility

It is the process of evaluatingtheorganizationabilitytoconstructaproposed system.

We concern here with equipment and software that will satisfy the user requirement. The system
will developed by PHP so the system is technically feasible. Also our proposed system can be
integrated with other university information systems it is technically feasible.

1.6.3Operational Feasibility
Our system is should be easy to use for uneducated and educated students to access the system.

Operational feasibility is a measure of how well a proposed system solves the problems, of the
existing system. The library management system is operationally feasible and it doesn’t affect
the organization structure. The new system is operationally feasible in terms of reliability,
maintainability, supportability, usability and flexibility. The new system will be:-
 Operatedbyanyusers

 User friendly

 Easier for navigate the page

6
 1.7. Methodology
Toperformthisprojectoursystemrequirementwillfollowmethods,models and development of software
life cycle techniques.

1.7.1. Data collection method

Todeveloplibrarymanagementsystemtheprimarytaskiscollectingrequireddatafromdifferent sources to
perform further tasks. The data will be gathered by using the following techniques:-

Primary data sources:-

Observation:-Wehaveobservedsomedataphysicallybygoingtotheirofficedirectly.Weselect
observation to know the real world environment of the organization manual working. In the
observation part we observe how the manual library management system is working.

Interview: -The other method we have used to get information about the general view of the system
is by interviewing employee of library office. It is fact finding technique where by the system
analyst collects information from individual face to face interaction. It gives us an opportunity to
motivate the interviewee to respond freely and openly.

We have asked different questions:-

 What is the current problem of the manual system?

 How do you work currently?Or

 How to process the current system?

Document analysis:-wealsocollectedcertainrelevantinformationfromwrittendocumentsinthe DTU

library office.Notonlythatbutalsowetriedtoreviewotherrelevantdocumentstodevelop our project
proposal

Secondary data source:-

Internet:-internet aids us to see the available sample on the internet and to down load different types
of tutorials which help to do our project.
Software Process Model

7
Thesoftwareprocessmodelofalibrarymanagementsystemtypicallyfollowsastandardsoftware
development life cycle (SDLC) model. The SDLC model defines a series of phases for building,
testing,anddeployingsoftware.Eachphasehasitsownsetofdeliverablesandobjectives,andthe process
flows from one phase to the next in a logical sequence.

Here’sanoverviewofthesoftwareprocessmodelforlibrarymanagementsystem:

1. Requirements gathering – This phase involves identifying the functional and non-functional
requirements of the library management system. Here, the developer will interact with the
stakeholders, including the librarians, library users, and management, to define the scope of the
system.

2. Analysisanddesign–Thisphaseinvolvesanalyzingthecollectedrequirementsandcreatinga
Creating a high-level design involves conceptualizing the overall structure of the system. This
includes defining the software architecture, data models, and workflow diagrams

3. Development – The development phase involves building the software using the design
specifications. The developer will write the code, unit test it, and integrate it with the rest of the
system.

Here some Development Tools:-

1. Integrated Development Environments(ID Es):

 Visual Studio:A popular IDE for various programming languages.

 In telliJ IDEA:Widely used for Java development.
 Eclipse:An other versatile IDE for multiple programming languages.

2. Code Editors:

 Visual Studio Code:Lightweight,highly customizable,and supports a wide range of

languages.
 Sub lime Text:Known for its speed and ease of use
Tools andTechniques

We have used the following software and hardware tools to do our project:-

Software tools:-
8
 Microsoft Office Visio2010 – to design scheduling phase

Client side: JavaScript, CSS, HTML.

Server side:-PHP

Edraw max:- for UML modeling and diagram

Visual studio code:- to write implementation or code

Microsoft word 2010for documentation

Microsoft power point 2010 for presentation

Apache: web server

MYSQL database: - for storing data in the database.

PHP engine:-for running PHP scripts

Web browser :-to run our program or code from the server side

1.8. Roles and Responsibilities

DTU library management system that manages and stores books information electronically
according to student’s needs. The system helps both students and library manager to keep a
constant track of all the books available in the library. It allows both the admin and the student to
search for the desired book.

9
1.9. Work Break down Structur

1
Project Scheduling
Table4.ProjectScheduling

December Januar
y

TaskName Start Finish 1-3 4-9 10-18 19-30 1-4

N
o
1 Proposal Dece January
Preparation 2024 2025

2 Requiremen January January s

t Analysis 2025 2025

3 Design January January

2025 2025

1
CHAPTERTWO:-STUDYOFEXISTINGSYSTEM

2.1. Introduction
In this chapter we will deal with the Existing System, Organizational structure, Service Provide,
User, Business rule, and Existing Infrastructure. Then we will discussed Proposed System.

2.2. Existing System Of Project

Currently Debra Tabor University Library System completely manual run system. The burden of
controllingthelibraryentirelyliesintheshoulderoftheadmin.Moreovertheterm“userfriendly” doesn’t
have a place to stand in the existing library system, as the user have the heavy work of finding a
desired book from the library.

Some of the major drawbacks of Existing System faces is includes:-

 Wastage of Time.

 Man Power.

 Inconsistency.

 Absence of secure mechanism.

 Burden of record keeping and wastage of storage space.

2.3. Organizational Structure

Thelibrarymanagementsystemisanintegratedsystemofsoftwareandhardwarecomponentsthat is
designed to manage the resource of a library.

Theorganizationalstructureoflibrarymanagementsystemisacriticalfactorinthesuccessofthe system.

Components of organizational structures:-

 System Administration

 Technical Service

 Library Service
2.3 Services Provided
Alibrarymanagementsystemisdesignedtohelplibrariesautomatetheiroperations,manage their
1
resources, and provide efficient services to their users.

Here are some of the services providedby an LMS:-

1. Cataloging:TheLMSallowslibrarianstocreate,maintain,andmanagethelibrarycatalog.The
catalogcontainsinformationaboutthelibrary'scollectionofresources,includingbooks,journals,
newspapers and other materials.

2. Circulation:Thisservicemanagestheborrowingandreturningoflibrarymaterials.The LMS
maintainstheborrowingrecords,duedatecalculation,andoverduefinescalculation.Italsohelps users
to reserve or request a book from another branch of the library.

3. Membership management:TheLMSmanagesuseraccounts,includingregistration,renewals,
andsuspensions. Ithelpsuserstoaccessthelibrary'scollectionandtracktheirborrowinghistory.

4. Reporting: The LMS generates reports and statistics about the library's collection, usage, and
user behavior. These reports help librarians to optimize their operations and improve services.

5. Inter-library loan: This service allows the LMS to request resources from other libraries and
borrow them for users.

6. Automated notifications: The LMS sends automatic emails, SMS notifications, or notices to
remindusersofbookreturns,overduefines,orreservationsavailability.Theuserrequestsabook from
the library's catalog, the LMS checks availability and book location, the user borrows the book,
and the LMS updates the borrowing record. The LMS also manages users' accounts, generates
reports, and facilitates inter-library loans.

1
 2.4. Users
A library management system is software that is designed to manage all the functions of a library. It
helps librarian to maintain the database of new books and the books that are borrowed by
members along with their due dates. This system completely automates all libraries’ activities.

Users can see what materials they have checked out, when they are due, and whether they have
any overdue items. This helps users keep track of their borrowing habits and avoid late fees. In
addition to physical materials, library management systems also provide access to digital
resources.

Many libraries offer e-books, audio books, and other digital materials that can be borrowed and
downloaded from the library's website. Users can access these resources from anywhere with an
internet connection, making it easy to read or listen to books on the go.

Finally, library management systems provide a way for users to communicate with the library. Users
can use the system to ask questions, make suggestions, or report problems with library
materials.Thishelpslibrariansprovidebetterservicetotheirusersandimprovetheoveralllibrary
experience.Inconclusion,librarymanagementsystemsareavaluabletoolforusersofalltypesof
libraries.

They provide easy access to library resources,help users track their borrowing habits,and offer a way
to communicate with library staff. By using a library management system, users can get the most
out of their library experience.

1
2.5. Business Rule Identification
A business rule is effectively an operating principle or polices that we try to specify for both the
existing system and the new system must satisfy. The business rule is a principle or a policy in
which the proposed system operates accordingly.

The main business rules or principles of the existing system proposed system are:-

Name:-Manage Librarian

Identifier:-BR01- All librarian managed by Library manager.

Name:-Manage resource

Identifier:-BR02-ResourcemanagedbyAdmin,librarian.

Name:-Manage Account

Identifier:-BR03- Account managed by Admin.

Name:-Manage staff

Identifier:-BR04-Booksorderedby librarian.

Name:-generate report

Identifier:-BR05-librariangeneratereport.

Name:-login

Identifier: - BR06 - login is used for authentication the system, also it accept password and user
name

Name:-upload Recourse

Identifier:-BR07- Admin,librarian add resource

Name:-Search book

Identifier:-BR08-Usersreadbook

1
Name:-Manage librarian

Identifier:-BR09: -Library manager manag elibrarian

2.6. Existing Infrastructure

The existing infrastructure of the LMS in a library typically includes hardware, software, and
networking components. ThehardwareinfrastructureoftheLMSincludesthecomputersystems,
servers, printers, and other peripheral devices.

ThelibrarymayhaveadedicatedserverfortheLMSoruseacloud-basedsolution.The computers
usedinthelibraryaretypicallydesktopsorlaptopsthatareconnectedtothenetwork.The printers are
used to print circulation receipts, catalog cards, and other documents.

TheSoftwareinfrastructureofLMSincludestheoperatingsystem,database management system, and

the LMS application. The operating system is the software that manages the computer
hardwareandprovidesaplatformforothersoftwareapplicationstorun.The database management
system is used to store and manage the library's collection of books.

The system is designed to manage and automate the operations of the library and provides a
platformforlibrarianstoperformvarioustasksefficiently.TheintegrationoftheLMSwithother systems
enhances the functionality of the library and improves the user experience for students and staff.

1
2.7. Proposed System
Proposed system The system is designed to solve the problem that is faced to the existing DTU
librarysystem.Inthisprojectwecreatedatabaseforlibraryusers,managersandforonlinereading.
ThisSystemcanprovideallusualservicesforusersbystoringdatabasesuchasadding,uploading, online
reading or viewing, deleting and searching information. This project is to provide a user- friendly
environment to maintain the details of resources and library members, to maintain easy
circulation system and to provide different reports using computers.

The proposed system uses the functionality of existing system to advance speed, performance,
security and reliability of the system. Our proposed system will eliminate or improve the
weaknesses of the existing system by providing on line service.

The proposed system will performd if ferent tasks such as:

 Thesystemchangesexistingmanualsystemtowebbasedsystem

 The system minimizes data redundancy by using database.

 The system can minimize loose of data and loss of time.

 The system reduces workload of librarians.

 The system will reduce the cost.

 The system controls all the activities of the students.

 The system make more efficient, responsive and less time consuming with high level of
accuracy.

1
 CHAPTERTHREE:-SOFTWAREREQUIREMENTSPECIFICATION

3.1. Introduction
This chapter will discuss about general requirement, External interface requirement, Functional
requirement, use case design, sequential diagram, Activity diagram Class diagram and non
functional requirement.

3.2. External Interface Requirement

3.2.1. User Interfaces

Library management system is used by librarian and admin so it just simply designed and not
colorful. The interface is user friendly and easy to use.

Thiscanbeprovingwhenusercanknowthatbutton’sfunctioniswhenhe/she looks at the button. It is

because the buttons text is clear and easy to understand. For example when want to register the
student records, we use ‘register’ button.

3.2.2. Hardware Interfaces

For library management, the additional device needed is bar code scanner. Bar code scanner is
needed to scan the book bar code id and also scan the member id. This can be time because
librarians no need to type the bar code of the book or members.

3.2.3. Software Interfaces

LibrarymanagementsystemtoinstallSQLserver2008.SQLserver2008islatestversionofSQL server and

it has been enhanced compared to SQL server 2005. For operating system requires window XP
or never version.

1
3.2.4. Communications Interfaces

Although library system is not web Application. But some function required the internet
connection.Thus Hyper Text Transfer(HTTP)shall be used to provide the internet connection to
the system. HTTP is the standard Method of transferring data between web server and browser
web (client).

3.3. Functional Requirements

Functional requirement is concerned with actual performance of the system that is going to be
developed. Functional requirements describe the functionality or service provided by the new
system.Thefunctionalrequirementistheservicesthatareprovidedbythesystem.It also describes the
interactions between the system and the user.

The new system will perform the following actives:-

Create Account:thenewsystemasksusernameandpasswordandallowsonlyauthorized users

to access the database.

Add new resources:-the new system will allow add book information (soft copy).

Delete resources:-The new system will allow delete book information.

Delete Librarian:-The new system will allow delete librarian information.

Search resources:-the new system will allow search resources.

Change Password:-the new system will allow old password changes.

1
The new system is expected to provide the following functionality

Input Requirements:-

 The system should register books.

 The system should verify the requested information.

 The system should check store book item by book name.

 Allow the librarian to add and remove new members

 Allow the user to search for books based on title, publication date, author, etc., and find their
location in the library.

 User scan request,reserve,or renew a book.

 Librarian can add and manage the books.

 The system should notify the user and librarian about the over due books.

 The system calculates the fine for over due books on their return.

Output Requirements:-

 The system generates a report.

 The system should store all the data related with all the tasks performed in to a database.
 The system should display store book item that are reach to registered date.
 The system should display student information to the librarian and admin.

2
 3.4. Use Case Design
Usecasediagramisoneoftheunifiedmodelinglanguagewhichrepresentsuser’sinteractionwith the system
and depicting the specifications of a use case.

The purposes of use case diagrams can be as follows:-

 Used to gather requirements of a system

 Used to get an outside view of a system

 Identifyexternalandinternalfactorsinfluencingthesystem

3.4.1. Actor Identification

Admin

Librarian

Student

Teacher

User

3.4.2. Use Case Identification

Login View Borrower

Create Account Manage User

Borrow Book Delete Account

Add Book Search Book

Delete Book Change Password

Update Book Logout

Use is play Book

2
3.4.3aseDiagram

Figure1.Use Case Diagram

2
3.4.4. Use Case Description

Table5.Use case Description for Login

Name Login
Use case id UC#1
Brief description When the user enter user name,password and select user type,it checks
The input from database,if it is valid the user can access,if not it
displays invalid user name or password.
Actors Librarian,Student,and Teacher
Precondition User must be authorized user who has user name and password
Post condition Theuserisauthenticatedandthesystemdisplaysallfeaturesavailable
For the role for the user is associated.
Basic Course Of User action System response
Action 1. The student, Librarian, and Teacher 2. The system display login
are want to login to the system. form
4. The system verifies that
3. The Librarian, Student and Teacher
all the filled have been
Enter user name ,password and select
filled out and valid.
user type then request to login
5. The system successfully
logged in.

6. Use case ends.

2
Table6.Use Case Description for Create Account

Name Create Account

Use case id UC#2
Brief description The Librarian create account for their staff worker,for Student and for
Teacher
Actor(s) Librarian
Pre-condition they must be authorized
Post-condition Create account for users
Basic Course Of User action System response
Action
1.The Librarian request to create account 2. The system display
3. The Librarian fill information that create account Form
included id, full name, sex, phone, user 5. The system display
name and select user type message “account created
4.the Librarian officers request to create successfully”
6. Use case ends

2
Table7.Use case Description for Search Book

Name Search Book

Use case id UC#3

Brief Description The book in library can be searched through parameters like Book
name, Author and Subject name

Actor(s) Student,librarian and teacher

Pre-condition Thebookormembertobesearchedshouldhavebeenregisteredin the

database of the library management system.

Post-condition Display search result

BasicCourseOfAction User action System action

1. The librarian and 2.The system verify the

student available book.

requestsearch book.

2
Table8.Use Case description for Logout

Name Log out

Use case id UC#4

Brief Description Help user wants to leave from the page.

Actor(s) Librarian,student and teacher

Pre-condition Librarian,student and teacher should be log in

Post-condition Librarian,student and teacher may logout from the page

BasicCourseOfAction User Action System Action

1: this use case starts 2:system returns back to login screen

when user clicks log out
3:use case ends.
button on current page.

2
Table9.Use Case description for Borrow Book

Name Borrow Book

Use case id UC#5

Brief Description Borrow Book is used to refer an action performed by the user
in order to borrow book from the book store.

Actor(s) Student, Teacher.

Pre-condition Student,Teacher are must fill the system requirement like First
name, last name, sex, address and phone number .

Post-condition Get the requested book.

BasicCourseOfAction User Action System Action

1. User requested 2. The system check the

book from the whether the user is
book store. registered.
3. Use case ends.

2
Table10.Use Case Description for Add book

Name Add Book

Use case id UC#6

Brief Description
Adding book is the process of Adding new book to the library store

Actor(s) Librarian

Pre-condition Thelibrarianhasthenecessaryinformationaboutthebook,such as book

tittle, book author, ISBN, publisher and publication date.

Post-condition The book is Added to the library store.

BasicCourseOfAction User Action System Action

1.The librarian click 2.The system is display the form for entering
Add Book button. the book information

3.The librarian enter the 4. The system valid a test the book
book information in the information and checks if the book already
form and click the exists in the store.
submit button.
5. if the book is already exists, the system
display an error message to the user.

6.if the book does not exists,the system Add

the book to the library store.

7.use case ends.

2
Table11.Use Case description for issued Book

Name Issued Book

Use case id UC#7

Brief Description This issued book is the process of issuing the book to library user.

Actor(s) Librarian,user

Pre-condition Thelibraryuserhasregisteredforanaccountandloggedintothe system.

Theuserhassearchedforandselectedthedesiredbookfromthelibrary store.

Post-condition The book is checked out to the library user and the book inventory is
updated.

The librarian has updated the book circulation log and user account
information.

Basic Course Of User Action System Action

Action
1.the user select the 2. the system form for the user to enter the
borrow book option the borrowing detail.
desired book from the
4. The system validates the borrowing
library store.
details and checks if the book available for
3.the user enters the the borrowing.
borrowing details in the
5, if the books is available the system
form and clicks the
updates .
submits button
6.use case ends.

2
3.5 Sequential Diagram
ASequencediagramisaninteractiondiagramthatshowshowobjectsoperatewithoneanother and in
what order. A sequence diagram shows object interactions arranged in time sequence.
Sequence diagrams are sometimes called event diagrams or event scenarios.

Figure2.Sequence Diagram for login form

3
Figure3.Sequence diagram for logout form

3
Figure4.Sequence diagram for Create Account form

3
Figure5.sequenceDiagramforIssuedBookform

3
3.6 Activity Diagram
Activity diagram is another important behavioral diagram in UMLdiagram to describe dynamic
aspects of the system. Activity diagram is essentially an advanced version of flow chart that
modeling the flow from one activity to another activity.

Figure6.Activity Diagram for login form

3
Figure7.Activitydiagramforlogoutform

3
Figure8.ActivitydiagramforCreateAccountform

3
Figure9.Activity Diagram for Borrow Book form

3
3.7 Class Diagram
Class diagrams are the blueprints of your system or subsystem. You can use class diagrams to
model the objects that make up the system, to display the relationships between the objects, and
to describe what those objects do and the services that they provide. Class diagrams are useful in
many stages of system design.

Figure10.Class Diagram

3
3.8.Non-Functional Requirements
Non-functional requirements describe how the system works, while functional requirements
describe what the system should do. They specify criteria that judge the operation of system
qualities to capture the required properties of the system. Then the team is going to develop its
own non- functional requirements, such as:-

Security:-Accesstothevarioussubsystemswillbeprotectedbyauserloginscreenthat requires a
user name and password.

Binary compatibility:the system is accessible for many computers.

Accessibility:system can be accessed from anywhere.

Flexibility:the system intends to increase or the functionality after its deployment.

Efficiency:thesystemutilizesresourcesandtakeslesstimetoperformactivitiesandmean time to
repair . Even if the system fails, the system will be recovered back up with in an hour or
less.

Reliability: capability of the system to maintain its performance over time.

Availability: the amount of time that it is operational and available for use.

Accuracy:Thesystemshouldaccuratelyproviderealtimeinformationtakinginto
consideration various concurrency issues.

Performance: The information is refreshed at regular intervals depending upon whether

some updates have occurred or not. The system shall respond to the member within few
seconds from the time of the request submitter. The system shall be allowed to take more
time when doing large processing jobs.

Maintain ability and Portability:Changes(addition of information, password changes,

and database changes) must be verified. The system should provide automatically
notification to users

3
 CHAPTER4:SYSTEMDESIGN

4.1. Design Overview

Thesystemdesignisacomprehensiveplanthatoutlinesthestructureandfunctionalityofasystem. It is
essential to ensure that the system is efficient,reliable ,and meets the requirements of the end-
users.

4.2. Chosen System Architecture

Figure11.SystemArchitecture

4
4.3. User Interface Design

User interface design is the process of designing the visual and functional aspects of a software
application or website that users interact with. It involves creating an interface that is easy to use,
intuitive, and visually appealing.

Thegoalofuserinterfacedesignistocreateapositiveuserexperiencebymakingiteasyforusers to
accomplish their tasks and achieve their goals within the application or website. This includes
designing elements such as buttons, menus, forms, icons, and other visual components that users
interact with to navigate through the system.

4.3.1. Description of the User Interface

Description for login form:-

Aloginformforlibrarymanagementsysteminterfaceisthatallowsuserstoentertheircredentials, such
as a user name and password ,to gain access to a secure area of a system .It typically consists of
two input fields for the user's login information and a button to submit the form.

The purpose of the login form is to authenticate the user's identity and grant them access to
restricted content or functionality.

Description for homepage:-

Thehomepageforoursystemisthefirstpagethatusersseewhentheyaccessthesystem.It serves
asagatewaytoallthefeaturesandfunctionalitiesofthesystem.The homepage typically includes a
student registration, teacher registration and links to important sections of our system.

The top menu provides users with easy access to different sections of the library, such as login,
contact us and other social media. The login bar allows the legal users to enter or to get in the
libraries for see different information.

Descriptionfordashboard:-

4
Thedashboardforthissystemwouldlikelyhaveseveralimportantfeatures.First and fore most,it would
provide an overview of available books, including how many members, books, how many issued
book and requested book. The dashboard might also allow librarians to view detailed information
about each book in the system.They may also be able to view the status of each book, such as
whether it is damaged, lost ,or currently being repaired .Additionally,the dash board might
include tools for managing patron accounts ,such as adding new user or up dating user
information.

Description for create account:-

The Create Account page should include input fields for the user to enter their personal
information, such as:- first name, Last name, Email Address, password and confirm their
passwords, then click create button.

4.4 Database Design

Databasedesignistheprocessofstructuringandorganizingdatainalogicalandefficientmanner. It
involves creating a blueprint for storing,managing,and accessing data with in a database system.
Themaingoalofdatabasedesignistoensurethatdataisaccurate,consistent,and easily accessible.

The term database design can be used to describe many different parts of the design of an

overalldatabasesystem.Principally,and most correctly,it can be though to fas the logical design of

the data base structures used to store the data. In the relational model these are the tables and

views. In an object database the entities and relationships map directly to object classes and

named relationships.

Database name:Library

Table name:Student,Teacher,Book,Librarian

Table12.Database Design

4
No Table name Attribute Datatype Primary Foreign
key key

1 Student table  Id Int(34)

 Full_name Var char(35) ID

 User type Var char(55)

 Email Var char(23)

 Phone number Varc har(23)

 Password Var char(23)

 Status Int(23)

 Registration date Var char(23)

Var char(23)

Librarian  Employee id Var char(30)

table
 F_name Var char(35)

 L_name Var char(15)

 Email Var char(55)

 Phone number Var char(15)

 Password Var char(55)

 Sex Var char(23

 User type Var char(23

4
No Table name Attribute Data type Primary Foreign
key key

3 Book list table  name Var char(50) Book_Code

 type Var char(30)

 download Var char(44)

 delete Var char(33)

 File size Int(11)

4 Teacher table  Id Int(34)

 Full_name Varchar(35) ID

 Usertype Varchar(55)

 Email Varchar(23)

 Phonenumber Varchar(23)

 Password Varchar(23)

 Status Int(23)

 Registrationdate Varchar(23)

Varchar(23)

4
Entity-Relationship(ER)Diagram

Figure12. ER Diagram

4
4.4.2RelationalDataModel

Figure13.RelationalDatamodel

4
4.4.3. Normalization

Normalization is a database design technique that reduces data redundancy and eliminates

undesirable characteristics like Insertion, Update and Deletion Anomalies. Normalization rules

divides larger tables into smaller tables and links them using relationships. The purpose of

Normalization in SQL is to eliminate redundant(repetitive)data and ensure data is stored

logically.

Librarian

ID fname lname email Phone password sex User

number type

User

id UID fname Lname Username Password Email Phone Address Sex User Status
type

Student

id SID fname Lname Username Password Email Phone Address Sex

Teacher
Id SID fname Lname Username Password Email Phone Address Sex

4
Reference
Andrews,D.C and N.S Leven thal.1993.

Hanna,M.1992“using Documentation as life-Cycle tools”softwareMagazine6(Dec):4146.

Advanced Database

System Analysis and Design

https://books.google.com.et/books?
id=XluhCgAAQBAJ&pg=PA1&dq=existing+infrastructure+library+management+system&hl=en&newbks=1&
newbks_redir=1&sa=X&ved=2ahUKEwj2jd
_tu9yJAxVgVqQEHXejDAUQ6AF6BAgMEAI

librarymanagement systemin PHPand mysqli