DAMBI DOLLO UNIVERSITY
COLLEGE OF ENGINEERING AND TECHNOLOGY
DEPARTMENT OF ELECTRICAL AND COMPUTER
ENGINEERING
(COMPUTER ENGINEERING)
TITLE:OLINE LIBRARY MANAGEMENT SYSTEM PROJECT
DAMBI DOLLO UNIVERSITY
Name …………………………………………………………ID
1 Abdisa Tashoma……………………………………NSR/033/21
2 Abera Bekele………………………………………..
3 Fikru Tefera…………………………………………
4 Firo Kebede…………………………………………
I
Catalog
Abstract........................................................................................................................III
Acknowledgment.........................................................................................................IV
CHAPTER ONE............................................................................................................1
[Link].................................................................................................................1
1.1 Background..............................................................................................................2
[Link] of the problem.........................................................................................2
1.2.1 Justification of the current system.........................................................................2
[Link]..................................................................................................................3
[Link] objective...................................................................................................3
[Link] objective..................................................................................................3
[Link]..............................................................................................................3
[Link] gathering tools..................................................................................................3
[Link] and design...............................................................................................5
[Link] implementation method............................................................................5
[Link] tools and techniques........................................................................6
[Link] of the project..................................................................................................6
[Link] of the Project.......................................................................................7
1.8. Feasibility Study......................................................................................................8
1.9. Risk Assessment and Management.........................................................................8
[Link] Breakdown...................................................................................................9
I II
Abstract
This application software of Online Library Management System developed for
Dambi dollo Library system. The activity of this university library system depended
on manual way of processing so that this is the way the system changed into
computerized by this application software. It can keep track of data related to library
books, members of the library and related activity of the system. To develop this
software the team members (Graduate students of Computer science)collected reliable
data about the college and conducted the procedures starting from planning
and justification of the system. Based on the studying and recognizing about the
problems of the existing system, the team members as a designer specified and
analyzed the requirements and then developed the designing of the proposed system
as a solution to the problems of existing system. The system would provide basic set
of features to add or update members, books, and manage in specifications for the
systems based on the client’s need. The system includes all possible available books
found in the book store so that one can check what is available inside the book store
without manually search. Addition to this it enables the university library managers
and workers to control daily attendance and easily submit work report
I III
Acknowledgment
First and foremost and above all our biggest thanks would be to Almighty God
because nothing could be possible without his free will and the completion of this
project is supported by [Link], our deepest thanks goes to our Advisor Mr
Belay E and co-advisor ……… for guiding and correcting various documents of ours
with attention and care. They have taken pain to go through the project and made
necessary correction as and when needed.
In addition, we would like to forward our special words of gratitude to DaDu
University library system librarian who helped us by providing information and by
giving useful documents and materials that are useful for our project.
We would also thank our Department and Our project coordinator without whom this
project would have been a distant reality.
II IV
CHAPTER ONE
[Link]
Library is one of the basic requirements that enable the functionality of all educational
[Link] the university and college level the main criteria is also adjusted in library
system. To obtain enough amount and specified book without any restriction, online
library management system is obligatory [1]. We mean online library system, it is
supported with automation system and its work process should be based on computer
aided. Library Management System is mainly focuses on basic operations in a library
like adding new member, new books, and updating new information, searching books
and members and facility to borrow and return books. It features a familiar and well
thought-out, an attractive user interface, combined with strong searching Insertion and
reporting capabilities.
The report generation facility of library system helps to get a good idea of which is
the books borrowed by the members,
Library Management System has four main modules.
Insertion to Database Module –User friendly input screen
Extracting from Database module – Attractive Output Screen
Report Generation module – borrowed book list & Available book list
Search Facility system – search for books and members
1
1.1 Background
Dambi Dollo University is one of the higher institution established in eastern part of
Ethiopia in kelam welega near to Dambi Dollo town . Dambi Dollo University was
founded in 2007 E.C. It has no enough facility to develop online Library management
system at that time. From foundation, still now, the library system uses manual
system. So we have decided to develop online Library management system for Dambi
Dollo University that overcomes the problems of the existing manual system like
academic case, food, wastage of time, dormitory problem etc. Our new system will
eliminate the problems in the manual system and increase the speed of whole process.
[Link] of the problem
Currently, the process and the services that Dambi Dollo university library system
carries out are based mostly on manual system [2]. With this manual system there is
some limitation based on different aspects. In the following lines we had tried to
justify some of such limitations in the system.
Some of the problems in the current system includes:
Problems or weakness of the existing system is its manual operation that
kills much amount of time to complete a simple work.
In this, it also needs man powers for a long period of time.
The way of stack is almost with a manual check.
Insufficiencies of reference resources for some course users.
1.2.1 Justification of the current system
Our new system will help the office by providing support method to complete their
tasks with a simple difficulty and with few workers with little period of [Link] new
system need to fulfill the automation plan of the office. Therefore we as developer
oras designer going to complete their plan by providing designed supportable website
as much as possible in our standard
2
[Link]
[Link] objective
The general objective of this project is to develop interactive online library
Management system for Dambidollo Universit
[Link] objective
Here are some specific objectives that would together help us to achieve the overall
the project as follows: .
Find the solution for the problem found in existing system.
Design and build a particular model of this proposed system.
Deploy the system and maintain it till it fits to the needs of the system.
Implementing the model with the flexible user interface
[Link]
Method is the process and way we will use to develop this project. The project we
proposed will be started using requirements elicitation technique. The software
process that we will be using is iterative SOFTWARE development approach type
since we will discuss and correct our errors with our advisor frequently.
Generally we used the following methodologies for our data collection
[Link] gathering tools
Data collection is a way of collecting information for improving or changing the
existing system by the new system. Data collection is a base for better solution.
3
Without a requirement or with out collecting information about the existing system, it
is difficult to establish the new [Link] is use full for solving problem
that was existed in the current system by collecting information or by gathering data
Data collection is a process in which we collect the necessary information in order to
under stand the existing system and user requirements. To gather the information we
will use inter viewing and reviewing document (forms, reports). During interviewing
we will interview the university library system about the existing system’s working
activity. So the data collection methods that will be used to achieve the development
of this project based on the fact that must be applied to overcome the manual library
system. We want to apply or use three types of data gathering methodologies. These
methodologies are observation, Interview and document analysis.
This method has been the primary base for the project. Therefore using the current
and background knowledge and experience of the team, the team will be able to
identify and list out the common functionalities and requirements for the project
Observation:as our team member will detect in the university about the system.
These will help the team (us) to precede some data gathering stages. Furthermore, it
creates a bridge or cause for other methodology to conduct them in proper method.
Interview:This methodology encapsulates two types of methods. These methods are
closed and open interview. So the team has selected an open interview for
interviewing the manager and employees for recognizing the existing working
procedure of the system. So the team will be able to gather more information about
the library system and requirements.
Document analysis:Besides the interviewing we also use the library general work
[Link] document available in the office, that gives the directions for total
activities. It is the paper hard copy that gives the general function that the system
currently handling.
4
[Link] and design
After the requirement is fully elicited, the next step to be done is analysis model. This
model is a bridge to design model. Analysis model focus on requirement that is
visible within the [Link] element we analysis will add to an overall
understanding of software requirements and provide insight into the information
domain, function and behavior of the system. The preceding step after analysis model
is design model. In this step we will plan a solution. To work on those models we use
the following tools. Visio 2010 will be used on models. In analysis model we will be
using it to draw use case diagram, Sequence diagram and activity diagram. In design
modeling we will be using it to draw class and other diagrams. In designing model to
draw the graphical interface we will be using pencil [Link] the document is
completed the work that will follow is creating the system. This programming
language php will be used for the application development that communicates with
the database. The database will be created using MS-Access. Generally in our design
and analysis we use object oriented concept rather than structural system analysis
since object-oriented model enable us to thoroughly respect complex relationship and
represent data and processing with a consistent notation, which allow an evolutionary
process. Thus it improves system quality and productivity of system analysis and
design
Data are analyzed through Use case Diagram, Activity Diagram, sequence diagram
and class diagram. After analysis the design models conducted by deployment, and
component. According to the time schedule, all the process will be carried on. Data
collection is being first as already we started some part and the other process is also
continuing sequentially. The documentation part partially completed with the
following three months and the remaining documentation part and coding will be
conducted next four months.
[Link] implementation method
After completing the development of the system, the testing process will be take
place. This part recognizes that the system works correctly or not, accurate or not,
updates the features if necessary. It will be carried out after all coding process
5
completed. If this process realizes the functionalities of the system and is ok, the
product CD will be submitted to the Dambi Dollo university library system that they
can use this web technology for their further work process
[Link] tools and techniques
We will also use the following tools
Windows – as a development environment
php-for coding
MS-Access – for storing the data that are going to be retrieved later.
Microsoft office Visio 2010- in order to model the system requirement in UML
(unified modeling language)
[Link] of the project
The scope of this project is developing online library Management System for Dambi
Dollo University This project helps the workers to work without barrier of bad actions
during their daily [Link] the completion of this project we expect the system will
have:
Presence of centralized and organized material (book) records.
Accurate way of recording and storing information in to database.
Create an account for Administrator.
The staff members will be registered using this website.
Some reports like book borrow, book return and etc will be generated.
Major Functionality
Books borrow: enables user in order to use the books outside of library for a short
period of time with recorded agreement as necessary.
Search for specified book:using book’s unique information (i.e., book code, book
title) to check the availability of a given book.
Generate report, Add, delete and update
6
The library manager who is responsible for this process can do the following with
help of our interface:
1. Add new book in book’s database.
2. Update already stored book’s information from database when
necessary.
3. Delete the user information after the book is returned to clean
database
Our project scope does not cover:
Cannot support all languages.
Cannot relate with financial cost of the book
[Link] of the Project
Developing this project has much significance for the university and the students.
After the completion of the total process, the system give web based application for
Dambi Dollo university library workers as well as users. As we explained above
section, the current system that based on manual system will be changed when they
apply this strategic product.
The users also use the library resources with safely and complete security without any
time restriction.
Some of the significant for the project.
Time consuming
Reduce man power & budget
Avoid document or reference misplacing.
It ensuring the availability of library books in their proper place.
With less effort and cost, the system will be able to maintain and store
information.
7
1.8. Feasibility Study
A feasibility study: is an analysis conducted to determine the viability of a project or
system. It evaluates whether the project is technically, economically, legally, and
operationally feasible. The goal is to assess the potential for success before
committing significant resources. In the context of an
Online Library Management System, a feasibility study would address:
- Technical Feasibility: Can the system be developed with the available technology?
Are the required hardware, software, and expertise accessible?
- Economic Feasibility: Is the project financially viable? What are the costs
(development, maintenance, infrastructure) versus the benefits
(efficiency, user satisfaction)?
- Legal Feasibility: Does the system comply with legal requirements, such as data
protection laws (e.g., GDPR) and copyright regulations?
-Operational Feasibility: Can the system be integrated into the existing workflow?
Will users (librarians, students, etc.) adopt it effectively?
- Schedule Feasibility: Can the project be completed within the desired time frame?
The feasibility study helps stakeholders decide whether to proceed with the project.
1.9. Risk Assessment and Management
Some of the risks might face during our further work is assumed as the following
points.
Unexpected man power failure:
Virus attack on computer:
Failure of electric power:
Time limitation
Resource related problems:
To manage the above risks we take the following as a solution
8
We will manage the problem of man power failure by covering the tasks of
thevictim with the remaining team members that they should take alternative
period.
For virus infection, duplicate files more than two computers, copy files on CD-
RW and external devices in order to resist problem.
To manage power problem we will use personal resources like laptop.
However,since all the team members do not have laptop computer, the group
members will be forced to get through any way during the time of for longed
power cut.
We will use the night period up to 11:00pm (local time) to cover the total process
in order to manage time limitation.
Our target source is through Google search, unless we seek our advisors help and
other colleagues’ cooperation
[Link] Breakdown
Work Breakdown Structure (WBS) is a hierarchical decomposition of a project into
smaller, manageable components or tasks. It organizes the project into phases,
deliverables, and work packages, making it easier to plan, execute, and monitor
progress.
For an Online Library Management System, the WBS might look like this:
Level 1: Project
- Online Library Management System
Level 2: Major Phases
1. Project Planning
- Define project scope
- Create project schedule
- Allocate resources
2. Requirement Analysis
- Gather user requirements
- Analyze functional and non-functional
9
requirements
3. System Design
- Design database schema
- Create UI/UX prototypes
- Define system architecture
4. Development
- Frontend development (user interface)
- Backend development (server, database)
- Integration of modules
5. Testing
- Unit testing
- Integration testing
- User acceptance testing (UAT)
6. Deployment
- Set up server and hosting
- Migrate data
- Launch the system
7. Maintenance and Support
- Bug fixes
- System updates
- User training and support
Level 3: Sub-Tasks (Example for Development Phase)
- Frontend Development
- Design homepage
- Implement search functionality
- Create user login/registration pages
- Backend Development
- Develop database for book records
- Implement user authentication
- Create APIs for book search and borrowing
10
The WBS ensures that all tasks are clearly defined, assigned, and tracked, reducing
the risk of missing critical components.
11
12
13