BAHIR DAR UNIVERSITY SCHOOL OF

COMPUTING AND ELECTRICAL ENGINEERING

OBJECT ORIENTER SYSTEM ANALYSIS AND
DESIGN
Title: Library management system project
Department computer science
NAME ID
1. Endalk Meku ia ……………………………………………………

2. Endeshaw Ma def o ………………………………………………

3.E d is Ja al………………………………………………………………

4.Erkihun Bele …………………………………………………………...

5.E ua e Assefa ………………………………………………………..

6.Ede Da iel…………………………………………………………......

Submitted to: - Asegahegn

Submitted on date:-22/09/2006

0|Page
Table of content page
ACKNOWLEDGEMENT............................................................................................................4

1. Introduction...........................................................................................................................4

2. Background of the organization…………………………………………………………………………………………….4

3. Background of FBE library management system ..................................................................5

4. VISION ..................................................................................................................................6

5. MISSION .............................................................................................................................. 6

6. PURPOSE OF THE PROJECT...................................................................................................6

7. SCOPE OF THE PROJECT ......................................................................................................7

8. OBJECTIVE OF THE PROJECT: ..............................................................................................7

8.1. “pe ifi o je ti e of the p oje t………………………………………………………………………………..

8.2.General objective of the project………………………………………………………………………………………………….8

9. PROBLEM OF THE MANUAL SYSTEM ....................................................................................8

9.1. Existing syste …………………………………………………………………………………………………………8

10. PROPOSED SYSTEM ......................................................................................................8

10.1. Advantages of proposed system................................................................................9

11. Methodology ...............................................................................................................9

11.1. Nonfunctional e ui e e t………………………………………………………………………………..10

11.2. Business ule…………………………………………………………………………………………………………

12.1. List of a to s…………………………………………………………………………………………………………10

12.2. List of use ase……………………………………………………………………………………………….……

. . use ase diag a ……………………………………………………………………………………………....12

1|Page
12.4. Use ase details…………………………………………………………………………………………………

13. CRC odeli g………………………………………………………………………………………………………20

14. Class diag a ………………………………………………………………………………………………..……

15. Sequence diag a ………………………………………………………………………………………………

15. Activity diag a …………………………………………………………………………………………………

. Co lusio ……………………………………………………………………………………………………..…..33

19. Reference……………………………………………………………………………………………………..……

2|Page
ACKNOWLEDGEMENT

We would like to thanks all those who helped us by giving

information and constructive suggestions that helps us in the
preparation of this project. We would like to express our deepest
gratitude to our librarians including the library manager who
gives support for the success of the project
We are grateful to our project guide instructor asegahegne
1. Introduction
This project describes the sections those included within it, that means, the sections
those we have included in our project. Library is regarded as the brain of any
institute; many institutes understand the importance of the library to the growth of
the institute and their esteem users (students). LMS support the general
requirement of the library like acquisition, cataloguing, circulation.

Our Library project system that offers many flexible and convenient features,
allowing librarians and library users to maximize time and efficiency. Library
System gives the all detailed information about students, staff and books. It will
track on the how many books available in library and books issued to the students.
It can reserve a book. It will provide book lost in library. It generates MIS reports
for management. Our software is customizable for any library requirement.

3. Background of FBE library management system

Faculty of business and economics library is one of the libraries found in the Bahir
Dar University. It serves of Computing and Electrical Engineering, Accounting,
management, economics, logistics and truism. Internet service was provided above
third year graduating students only.

Basically, the students learning in this university are using different materials and
requirement. Such as library and internet. In order to that we focus on the library
system to be automated rather than the manual system. The purpose to having a
computer based system.

3|Page
4. VISION

The vision of Bahir dar university FBE library is to give successful way of service
to the university students and other members of the university in order to develop
skillful and knowledgeable citizens, this library management system offering to
customers to improve their efficiency and becoming one of the top ten research
university from Africa.

5. MISSION

The mission of Bihar Dar University FBE library is omitted to exceed its customer
expectation for quality education, agility, research, community service and
professional excellence.

6. PURPOSE OF THE PROJECT

The purposes of this project are as follows:

Improved efficiency and effectiveness in administration and management of the

library.

More reliable security for sensitive and confidential information

Appropriate knowledge-based action and intervention can now take place in a

timelier

The software is for automation of library

Can enter details related to a particular book.

4|Page
Can reserve, borrow, return book in easy and understandable way

Can provide membership to members.

Can read and write information about a member

Can update, create, and delete the record of membership as per requirement and

implementation plants
.

7. SCOPE OF THE PROJECT

The different areas where we can use this project are:

Any education institute can make use of it for providing information about author, content of the
available books.

It can be used in offices and modifications can be easily done according to requirements.

8. OBJECTIVE OF THE PROJECT:

The main objective of our project is:

To identify the actors/users who use books and other reading materials in the library and to
enhance the productivity and efficiency of the library processes.

To describe use case of the system and identifying the job concerned to those workers of the
library.

To know about other systems interacting with the system.

Our project is specified in order to solve the problem that listed in business and economics
library management system.

The general objectives of our project is that all branched libraries’ in bahir dar university provide
effective management system by using automated system and connecting to gather by computer
network in order to get information.

9. PROBLEM OF THE MANUAL SYSTEM

5|Page
Some of the problems being faced in manual system are as follows:

1. Fast report generation is not possible.

2. Tracing a book is difficult.

3. Information about issue/return of the books is not properly maintained.

4. No central database can be created as information is not available in database.

9.1. Existing system

Business and economics library management system there are two types of
services are available. This is circular disk and reserve disk. Both of these two
services in business and economics library management system are implemented
by manual system .This system works by power to find the required book from
different book shelf. These systems are advantageous in order to create the
opportunity job to jobless human being. On the other hand this system has a
disadvantage in case of time and energy and also it may happen lossing
information when the student ID is losing from the id box. Generally, we would
conclude that the system has its own limitation.

10. PROPOSED SYSTEM

 Login to the system through the first page of the application.
 See the status of the books borrowed / reserved.
 Search for the particular book.
 Cancel the reservation made earlier for a particular book.
 Notification should be given to the librarian about the expiry of due dates for
the books.

10.1. Advantages of proposed system

 It provides "better and efficient" service to members.
 Students according to their needs get the books issued and in case they are
unable to
 Return the book; they can extend the date of return.

6|Page
  Maintenance of the books becomes easy for the librarian.
 All the transactions are maintained by computer easily by just little
understanding.
 Provide facility for proper monitoring reduces paper work and provide data
security.

11. Methodology
1. Users Requirement
1.2 Functional requirement
List of service:

The Manager

 The system should allow for Manager to add new book to the database.
 The Manager should able to update a book from database
 The system should allow add the user as a member to the database

The librarian

 The system should allow modifying the details of books

 The system should allow modifying the details of members
 The system should allow storing reserve book in the database
 The system should allow displaying the list of books according to various
criteria.
 Such criteria are title, author name, publisher, published date
 The system
 The system should generate the report of the student who have issued or not
issued the books

The users

 The system should allow for the user to return book

 The system should allow for the user to search book by title
 The system should allow for the user to search book by author

7|Page
  The system should allow for the user to search book by title

Business Rule
1. The user must be registered to get the service

2. The user must have his own password to get the service

3. If the user doesn’t return the book on the date he will punished.

4. The librarians must be punctual.

11.1. Non-functional requirement

The system should give a response to the user with in 5 second

The system should not fail more than 2 days in a month The system should
managing operation means (register, delete, and update) can be used by only
library clerk.

The system product requires at most 10GB for installing software and storing
database.

12.1. List of Actors

In our system the main actors are User (student and instructor):-represent a person
that use the system

Librarian:- those who organize the information services or materials for those who
need information.

Library manager:-represent a person that manages all activity

Registrar system:-the organization that check the user registered or not.

8|Page
12.2. List of use case
Search book

Login

Check reservation

Borrow book

Remove book

Add book

Reserve book

Return book

Fig 1.Use case diagram (designed by Eden

danial)

9|Page
 Library management System

search book by
author
login
«extends»
search book by
«extends» title

search book

librarian
borrow book
users

returen book

Registrar system

reserve book

check resevation
of book

add book manager

remove book

10 | P a g e
 12.3. Use case details(designed by Endalk mekuria)
Use case 1: login

Actor: User, Registrar, Manager

Description: Entering in to the system

Precondition: User must have an ID

Post condition: Getting the user interface

Basic course of action:

1. Users wants to login open browser

2. The system display the login page

3. User enters password and name

4. The user clicks on login button

5. The system checks validity of the password and name

6. the system display the main page

6. End of use case

11 | P a g e
Use case 2

Search book by title

Name: Search book by title

Actors: user
Description: allow the user to search book by title.
Precondition: users are logged on the system.
Post condition: user search book by title
Basic course of Action
1. User wants to search book by title
2. The user enters book title.
5. the user clicks on “search book” button
6. The system display available book list
7. Use case end.
Alternate course of action:
3.if the enter book title incorrectly
4. The system displays the result can’t found.

12 | P a g e
Use case 3: search book by author

Name: Search book by author

Actors: user

Description: allow the user to search book by author

Precondition: users are logged on the system.

Post condition: allows the user to search book by author

Basic course of action

1. User wants to search book by author from the system

2. User enters author name
3. The user clicks on search book by author button

4. The system display list of the book will appear

5. Use case end

Alternate course of action

3. If the user enters author name incorrectly

4. The system display the result is not found

13 | P a g e
Use case 4: Borrow book

Name: borrow book

Actors: (user, librarian).

Description: allow the user to borrow book

Precondition: users must be registered.

Post condition: the user borrows the book

Basic course of Action

1. The user wants to borrow book

2. The librarian searches book by title

3. The system will display two choices a. borrow book b. reserve book

4. The librarian clicks on borrow book

5. The system will display list of available book and a form

7. The user filled out the form

8. The system display the deadline date and the book will delivered

9. The user borrowed book

10. Use case end

Alternative course of Action

6.If the book is on reserved state

The librarian clicks on the cancel reservation

14 | P a g e
The user borrow book

Use case 5: Reserve books

Name: reserve book

Actors: librarian

Description: allow librarian to reserves book

Precondition: the book is available in the database

Post condition: the book is reserved

Basic course of Action

1. The user enters the book title

2. The system display list of books

3. Clicks on the reserve button

4. The system will reserve the book

5. use case end

15 | P a g e
Use-case 6: Check reservation

Name: checks reservation of books

Actor: librarian

Description: checking whether the book is reserved or not

Precondition: The user must login in to the system

Post condition: checking book reservation

Basic course of an action

1. The librarian is in the logged page

2. The librarian wants to check reservation of books

3. The librarian clicks on check reservation button

4. The system will display information of the book whether it is reserved or

borrowed

5. End of use case

16 | P a g e
Use case 7: delete book

Name: delete book

Actors: library manager

Description: allow the manager to delete book.

Precondition: The store (database) should have books

Post condition: deleting book from the database

Basic the course of Action

1. Library manager wants to delete book from the database

2. Library manager enters the book title that has to be deleted

3. The library manager clicks delete button

4. The book is deleted from the database

5. Use case end

17 | P a g e
Use case 8: Add book

Name: Add book

Actors: library manager

Description: allow the manager to add book.

Precondition: the database should have books

Post condition: adding book to the data base

Basic the course of Action

1. Library manager wants to add book into catalogue

5. The library manager clicks Register new book button

6. The system displays asks the accession and call number

7. The library manager enters the accession and call number

8-the book is added to the database

9. Use case end

18 | P a g e
13. CRC MODELING (DESIGENDE BY ENDESHAW MANDEFRO)

CRC (Class-Responsibility-Collaborator)
CRC modeling often includes the users, analysts, and developers in a modeling
and design.

Process, bringing together the entire development team to form a common

understanding of an OO development project. It is one of many tools that should be
used in the collaborative design of a system .The technique has since been refined
to become valuable beyond the education curriculum. A CRC Model is a collection
of cards (usually standard index cards or larger) that are divided into three sections.

1. Class

2. Responsibility

3. Collaborator

13.1. Class

A Class represents a collection of similar objects. They can be a person, place,

thing, or any other concept important to the system at hand. The Class name
appears. Across the top of the CRC card.

13.2. Responsibility

A Responsibility is anything that the class knows or does. These responsibilities

are things that the class has knowledge about itself, or things the class can do with
the knowledge it has.

19 | P a g e
 13.3. Collaborator: Collaborator is another class
Librarian that is used to get information for, or perform
Name actions for the class at hand. The Collaborators of
Password Book
Sex Library manager
a class appear along the right side of the CRC
Address user card.
Job experience
Search book()
Search by title
Search by author
Reserve book()
Send report()

Library manager
Name
Password User
Sex
Address Librarian
Job experience
Delete book
Add book

User
Name Librarian
id
Sex
Phone number
Return book
Search book
Borrow book

20 | P a g e
 Book

Title User
Author Librarian
Registrar
Name Manager Edition
Address
Level Borrowed by user()
Cheek the student register Reserved by
librarian()
Searched by user()
Searched by
librarian()
Returned by the
user()

21 | P a g e
14. Class Diagram
library manager
Users
1..*
1 --name -1

--id number
--job exprience *
--name --address
--id numeber --sex
-phone number
+add user()
--sex
+delete user()
+search book() +receive report() * -1..*
+ borrow book() 1
+give response()
+return book()
book
* -1 --author
--tittle
--eddition
--ISBN
-End1
-End2 +borrrowing by user()
+returned by user()
*
* +arrenged by librarian()
+searched by liberarian and user()
*
-End2 *

registrar
* -1 1..*
-name
1 -level
librarian
-address
--name
-
--id
+checking student registration()
--address
--sex
--job exprience
+search book()
-End1
+reserve book()
+send report()
*
-1..*

(DESIGEND BY ERKIHUN BELEW)

22 | P a g e
Fig 2.class diagram

Sequence diagram (DESIGEN BY ENQUANHONE ASSEFA)

search book by
title

user User interface control<<UI>>

database
enters the book title

clicks on search book by title

checks

the rseult is not found

Display the available book list

23 | P a g e
 search book by
author

user User interface

control<<UI>>

database

enters the book title

clicks on search book by title checks

The result is not found

display avalaible book list

24 | P a g e
 borrow book

user User interface control<<UI>> database

enter the book title

clicks on borrow book

the system display a form

The user filled out the form

the user borrowed book

25 | P a g e
 Remove book

Library manager User interface Controller

<<UI>> database

enters the book title

checks

no book found

clicks on remove button

The book removed

26 | P a g e
 Add book

Controller
Library manager user interface <<UI>> database

enters the book title

clicks on register new book

asks accession & call number

enters the accession & call number

the book is added to the database

27 | P a g e
15. ACTIVITY DIAGRAM:
Activity diagram is the object oriented equivalent of flow chart and data follow diagrams (DFDS)
from the structured development.

Activity diagrams are diagram technique showing workflows of stepwise activities and

Actions,

Activity Diagrams are also useful for: analyzing a

Use case by describing what actions needs to take place and when they should occur;
describing a

Complicated sequential algorithm; and modeling applications with parallel processes.

28 | P a g e
 Users are in the home page

The user enters password and name

incorect

corect

The user clicks on login

The system display the main page

Login activity diagram (design by endris Jamal)

29 | P a g e
Search book by title activity diagram

The user wants to borrow book

The librarian search the book by title

Display two choices reserveand borrow book

The librarian clicks on borrow books

Displays a form

the user filled out the form

User borrow book

Borrow book activity diagram

30 | P a g e
 Enters the book title

display the book list

Clicks on the remove book

The book removed from the database

Remove book activity diagram

31 | P a g e
 Add book to the catalogue

Clicks on the register new books

Asks accession and call number

Enters accession and call number

The book is added in to the database

Add book activity diagram

32 | P a g e
 Login

User name

Password Login

Ok cancel

Search book by title

Book title

Search book

Ok Cancel

33 | P a g e
 Borow book

Enter Book titel Fundamenta c++

Acce no 1234

borow reserv

18. CONCLUSION
We have conclude that this project overcome the problems in the existing systems. The
LIBRARY MANAGEMENT “Y“TEM p o ess ade o pute ized to

Reduce human errors and to increase the efficiency.

The problems, which existed in the earlier system, have been removed to a large extent.

And itisexpected that this project will go a long way in satisfying users requirements. The

computerization of the Library Management will not only improves the efficiency but will also

reduce human stress thereby indirectly improving human recourses

34 | P a g e
 REFERENCE
1. INTERNET

2. OBJECT ORIENTED SOFTWARE ENGINEERING USING UML

3. HANDOUTS OF OOAD

4. Object oriented primer

5. Interview with librarian

35 | P a g e