REG NO: BIT/03007/2021

NAME: ISAIAH KIPKOECH

UNIT: OBJECT ORIENTED ANALYSIS AND DESIGN
CODE: BIT 223
1.Analysis and Design of a Library Management Information System Using Object-Oriented
Methodology
1. Introduction
The objective of this analysis is to design a Library Management Information System (LMIS)
using object-oriented methodology. This system will facilitate the management of library
resources, including books, members, and transactions. The use of object-oriented principles will
enhance modularity, reusability, and maintainability.
2. Requirements Gathering
Before designing the system, it is essential to gather requirements from stakeholders such as
librarians, library staff, and users. Key functionalities identified include:
 Book Management: Adding, updating, deleting book records.
 Member Management: Registering new members, updating member information.
 Transaction Management: Borrowing and returning books.
 Search Functionality: Searching for books by title, author, or ISBN.
 Reporting: Generating reports on borrowed books and member activity.

Function and non-functionals of library system

When designing a library system, it’s essential to outline both functional and non-functional
requirements. Here’s a breakdown of each:
Functional Requirements
These describe what the system should do:
1. User Management
o Register new members.
o Update member information.
o View member details.
2. Book Management
o Add new books to the catalog.
o Update book details (title, author, ISBN, etc.).
o Remove books from the catalog.
o Search for books by various criteria (title, author, ISBN).
3. Borrowing and Returning
o Check out books to members.
o Record the return of books.
o Track due dates and late returns.
4. Reservations
o Allow members to reserve books that are currently checked out.
o Notify members when reserved books become available.
5. Librarian Functions
o Manage member accounts (approve, suspend).
o Generate reports on book inventory, member activity, and overdue items.
6. Notifications
o Send reminders for due dates.
o Notify members of new arrivals or available reservations.
Non-Functional Requirements
These describe how the system performs its functions:
1. Performance
o The system should handle up to X concurrent users without significant delays.
 o Response time for searches should be under Y seconds.
2. Scalability
o The system should support an increasing number of users and books without
performance degradation.
3. Reliability
o The system should have an uptime of 99.9%.
o Data backups should occur daily to prevent loss.
4. Usability
o The user interface should be intuitive and easy to navigate for both members and
librarians.
o Provide help documentation and tutorials.
5. Security
o Implement user authentication and authorization.
o Protect sensitive member information through encryption.
6. Compatibility
o The system should be compatible with various devices (desktops, tablets,
smartphones).
o Ensure integration with other systems (e.g., payment gateways, inventory
systems).
7. Maintainability
o The codebase should be modular and well-documented to facilitate updates and
maintenance.
These requirements provide a solid foundation for developing a comprehensive library system
that meets the needs of users while ensuring optimal performance and usability. If you need
further details or specific examples, feel free to ask!
3. Use Case Identification
Based on the requirements gathered, we can identify several use cases:

 Use Case 1: Add Book

  Actor: Librarian
 Description: The librarian adds a new book to the system.
 Use Case 2: Register Member
 Actor: Librarian
 Description: The librarian registers a new member in the system.
 Use Case 3: Borrow Book
 Actor: Member
 Description: A member borrows a book from the library.
 Use Case 4: Return Book
 Actor: Member
 Description: A member returns a borrowed book.
4. Class Diagram Design
Using object-oriented principles, we can define classes that represent entities in the LMIS:
 Class Book
 Attributes:
 ISBN (String)
 Title (String)
 Author (String)
 Publisher (String)
 YearPublished (Integer)
  Status (Boolean) // Available or Borrowed
 Class Member
 Attributes:
 MemberID (String)
 Name (String)
 Email (String)
 PhoneNumber (String)
 Class Transaction
 Attributes:
 TransactionalID (String)
 MemberID (String)
 ISBN (String)
 DateBorrowed (DateTime)
 DateReturned (DateTime)

5. Sequence Diagrams
To illustrate interactions between objects during specific scenarios, sequence diagrams can be
created for key use cases:
 

 For “Borrow Book”:

Librarian -> Book : Check Availability()
Member -> Transaction : Create Transaction()
Transaction -> Book : Update Status(Borrowed)
This sequence shows how the librarian checks if a book is available before allowing a member to
borrow it.
Activity diagram
State diagram
6. Implementation Considerations
When implementing the LMIS using an object-oriented programming language such as Java or
Python:
 Use encapsulation to protect data within classes.
 Implement inheritance for specialized classes if needed; for example, different types of
members could inherit from a base Member class.
 Utilize polymorphism for methods that may behave differently based on the object type
calling them.
7. Testing Strategy
A comprehensive testing strategy should be employed to ensure all functionalities work as
intended:
 Unit Testing: Test individual classes and methods.
 Integration Testing: Test interactions between classes.
 User Acceptance Testing: Validate that the system meets user requirements through real-
world scenarios.
8. Conclusion
The design of a Library Management Information System using object-oriented methodology
provides a structured approach to managing library operations efficiently. By focusing on key
functionalities and employing best practices in software design, this system can significantly
improve resource management in libraries.