The document outlines the development of a Library Management System (LMS) designed to enhance library operations by replacing manual processes and providing electronic access to library materials. It includes objectives for user registration, advanced search capabilities, and distinct interfaces for administrators and users. The document details system diagrams, application modules, and testing methods employed to ensure software functionality and performance.

1. A Medical Research Council’s Library
Management System
Martins Jr. Divine Okoi

2. CONTENT
1. Introduction
2. Project Objectives
3. Application Modules
• User Modules
• Admin Modules
4. System Diagrams
1. ER Diagram
2. Flowchart
3. Add Module Flowchart
4. Check In/Check Out Process
5. Design
• Design Freelance
• Design User
• Design Admin: Function & Process Walkthrough
6. Testing
7. Thank You

3. INTRODUCTION (definition)
According to Stephen, Maeve & Philips (2007), in a traditional sense, a Library is a large collection of
books, and can refer to the place in which the collection is housed. Today, the term can refer to any
collection, including digital sources, resources, and services. The collections can be of print, audio, and
visual materials in numerous formats, including maps, prints, and documents, microform, CDs, cassettes,
videotapes, DVDs, video games, e-books, audio books and many other electronic resources. The places
where this material is stored can range from public libraries, subscription libraries, private libraries, and
can also be in digital form, stored on computers or accessible over the internet.

4. INTRODUCTION (definition cont.)
A library management system (LMS) is a software that is developed to handle at least the most basic
housekeeping functions of a library.
It’s a well organized software solution for a library which helps to provide information on any registered
materials present in the library to the user as well as staff.
The LMS facilitates technical functions of a library and one such function is electronic cataloguing. With
an LMS, library users can trace desired items electronically without going through shelves. An LMS also
facilitates the lending process by keeping records of items lent and the borrower’s information. LMS
supports other administrative tasks such as inventory and data processing.

5. Project Objectives
 Develop a system that can replace the manual library managing system.
 Develop a database which stores user & items details.
 Build an advanced search that can help for the best handling of user queries, this search should
handle different search types like searching by author, title, year of publication, *barcode.
 The search result should contain information about the exact location of the book.
 The Administrator, Librarian & Users should have separate logins.
 Create an easy to understand user friendly environment.

6. Project Objectives (cont.)
 Create an attractive user interfaces to navigate through the system for the users.
 Create a module to produce technical reports and/or logs of the LMS events.
 Develop a system that will record the items borrowed.
 Provide security (i.e. only the administrator can update any information to the database).

7. APPLICATION MODULES
User Modules
• Log In/Out – (Security Module)
• Book, Journal, Magazine & Thesis Search (OPAC Access)
• Change Password
• Reset Password
• Request for Books
• Contact Admin

8. APPLICATION MODULES (cont.)
Admin Modules
• Log In/Out – (Security Module)
• Add/Remove Members
• Update/Delete Member Information
• Book, Journal, Magazine & Thesis Search (OPAC Access)

9. APPLICATION MODULES (cont.)
Admin Modules (cont.)
• Add and/or Delete Books, Journals, Magazines & Thesis
• Update Books’, Journals’, Magazines’ & Thesis’ Details
• Authenticate the Check Out of Books, Journals, Magazine & Thesis
• Check In Returned Materials using a Barcode Scanner

10. System Diagrams (ER Diagram)

11. System Diagrams (Flowchart)

12. System Diagrams (Add Module Process)

13. System Diagrams (Check Out - Check In Process)

14. Freelance (Home)

15. Freelance (Landing page)

16. Freelance (Login pages)

17. Freelance (Contact page)

18. User (Index page)

19. User (Search & Search_result pages)

20. User (See Request Status and Change Password)

21. Admin (Home)

22. Function & Process Walkthrough
(Admin Home : Contents)

23. Function & Process Walkthrough
(“On Loan” Items)

24. Function & Process Walkthrough
(Admin Registration Request From Freelancer)

25. Function & Process Walkthrough
(Admin : Add New Member)

26. Function & Process Walkthrough
(Admin : Add New Member; Visitor)

27. Function & Process Walkthrough
(Admin : Change Password)

28. Function & Process Walkthrough
(Cataloging : Search Module – Member (f_name) Search)

29. Function & Process Walkthrough
(Cataloging : Search Module – Member (f_name) Search
Result)

30. Function & Process Walkthrough
(Circulation: Check In Item {Using a Barcode Scanner})

31. Function & Process Walkthrough
(Circulation: Check In Item Detail Verification)

32. Function & Process Walkthrough
(Circulation : Change Member’s Password on Request)

33. Function & Process Walkthrough
(Cataloging : Add New Book)

34. Function & Process Walkthrough
(Cataloguing : Requested Items)

35. Function & Process Walkthrough
(Cataloging : Search Module – Book Search & Search Results)

36. Function & Process Walkthrough
(Reports: Logged Data)

37. Function & Process Walkthrough
(Reports: Checked Out Listing)

38. TESTING
The testing process was focused on the logical intervals of the software ensuring that all statements
have been tested and on functional interval is conducting tests to uncover errors and ensure that
defined input will produce actual results that agree with the required results, thus program level
testing and modules level testing were integrated and carried out.
I used two types of testing; White Box Testing and Black Box Testing.
White box sometimes called “Glass box testing” is a test case design that uses the control structure of
the procedural design to drive test cases. Using white box testing methods, the following tests were
made on the system:
a. All independent paths within a module have been exercised once.
b. All logical decisions were checked for the truth and falsity of the values.

39. TESTING (cont.)
Black box testing focuses on the functional requirements of the software. This black box testing enables
the software engineer to derive a set of input conditions that will fully exercise all functional
requirements for a program.
a. Interface errors
b. Performance in data structure
c. Performance errors
d. Initializing and termination errors

40. MANY THANKS Martins Jr. Divine Okoi