ISY2001 Case Study: Analysis and Design of Library Management System

This case study report details the design and analysis of a library management system. It begins with an introduction and justification for the system's development, emphasizing the need for efficient data management within an institution. The report outlines the business background, project scope, and the system's functionalities, including user roles (lecturers, staff, and students). It incorporates essential diagrams such as use case, sequence, data flow (context), and entity-relationship diagrams to visualize the system's architecture and data flow. The report also presents screen interfaces for the main menu, input, and report sections, along with a Gantt chart illustrating the project's timeline and cost analysis. The conclusion summarizes the processes followed, ensuring smooth system operation and efficient transaction handling, making it a valuable resource for understanding system analysis and design principles.

LIBRARY MANAGEMENT SYSTEM
Research Document

Contents
Introduction................................................................................................................................2
Justification of the system.........................................................................................................2
Background of the business.......................................................................................................2
Project scope...............................................................................................................................3
Use case diagram and sequence diagram.................................................................................5
Dfd level 0/ context diagram.....................................................................................................7
Entity relation diagram.............................................................................................................8
Screen interfaces........................................................................................................................9
Main menu screen......................................................................................................................9
The input screen is as represented below...............................................................................10
Report screen............................................................................................................................11
Conclusion.................................................................................................................................12

Introduction
In the current world that we are living in, there are many advancements when it comes to the
field of IT. Since a lot of data are being exposed over the internet and many of which are useful
depending on what one is searching or looking over the internet in order to satisfy the person's
needs. At the end of this what it means is that as an institution, it's good to have equipment that is
able to handle and store those data in a safe way that will make it easily accessible to those in
need. For this to be possible a system needs to be built, and companies or institutions with this
system normally benefit most of the time.
Justification of the system
Libraries within institutions are among the most effective places where people tend to do their
research and gather proper evidence or result depending on the research that one is conducting.
In most cases, it is taken that all the required information and appropriate research materials are
easily available in the library (Sula, 2013). This means that for an institution to be of help and
provide good quality it requires a proper library that will make research work and learning
process smooth to those in need of the library.
Still when building the library what is mostly taken into consideration is how it is managed.
Proper management will make the transactions taking place in the library to be smoother and
without congestion or overload due to many activities that normally occur in the library like
arranging and borrowing of books, verification of students during the entrance and many others
that we'll see in the system. Due to this, a suitable library management system will be required,
which is able to store huge amount of data and carry out most of the functions which are
automated in the system. And these enable the users to get services that are of high quality.
Background of the business
The library in this case is accessed by lecturers, staff and students or other users depending with
how the institution interacts to the society around it. For this to be possible, the system requires
users to use their identification for verification and to provide easy access to the system. At the
start the students and staffs are required to fill their details such as name, registration, department
and user type.
Functions of the student in this system are as follows:
 Borrow book.
 Register.

 Make booking.
Staffs also are able to perform the following action:
 Make reservation.
 Lease books.
.
Project scope
The system involves deals mainly with the staff, students and lecturers and may be other users
apart from those mentioned. The system is designed in such a way that it enables user to such for
books using keywords that can be from the book title or the author’s name. The system is also
able to generate the bills and records that may arise when transaction are taking place in this
library system. The system also handles verification of users when using it.
Below is the schedule analysis for the project
TASK Critical
path
Start day Finish Duration Slack Milestone
Analysis Yes 1 10 10 0
Design Yes 10 20 11 0
Developmen
t
Yes 20 48 29 0 Day 29
Testing Yes 31 36 6 0
Maintenance Yes 36 40 5 0
The brief cost of the project is as below:
Analysis phase- 10day * 3analyst *50 $ =1,500$
Design phase- 11days * 8 designers *45$=3,960$
Development- 29days * 5developers * 100$=14,500$
Testing – 5days * 250=1,250 $
Maintenance- 5days * 70 $=350$
The total budget will be= 21,560$

Use case diagram and sequence diagram (Gemino and Parker, 2009)
The use case scenarios for the lecturer or student include are registering, borrowing books,
booking a book and returning a borrowed book. The library staff use case includes leasing a
book, making a reservation for booking and receiving a book. The system can also generate
reports, calculate the overdue payment and send reminders; it also generates a report that is
viewed by the manager. The manager can delete system information.

Below is the system’s sequence diagram (Swain, Mohapatra and Mall, 2010)
The sequence diagram show the librarian as a staff logs in the system and access information that
he/she is authorized to see, and updates them as required. Among this is also adding members to
the system and generating records of the existing catalog from the system.

DFD level 0/ context diagram
The data flow diagram level 0 is also the context diagram below is the context diagram (Ibrahim,
2010).

Entity relation diagram
Below is the entity diagram of the library information system (Bagui and Earp, 2011).
In the above diagram maximum number of books borrowed will be two and they must be put in a
category that satisfies what the student will need in the process. The students and staff are using

similar approach in acquiring resource from the library the only difference comes when they are
being identified where staffs use employee number as their identification.
Screen interfaces
Below is the
Main menu screen
This option is what is expected to be seen by the users when and before logging in. This is the
outlook of the main page and it directs uses on option and choices of what the user can access
when logged in. The main page should be presentable and easy to access not complicated.

The input screen is as represented below
This page allows the user to access the system itself, this depends with whether you have
forgotten your password, sign up or login into the system. This interface allows one to enter
his/her credentials for verification with what is on the system before access is given.

Report screen
This screen can only be viewed by the manager who will be in charge of the system after its
completion. The manager sees the overview of what is required and gives his/her conclusion
depending with the overall result or objective. And this interface is only accessed with the
manager which happens because of his rank.

Below is an image representation of the Gantt chart
The above Gantt chart has been used to show all the procedures that will occur when developing
the system from scratch. It starts from the first stage which is analysis stage to last part which is
the maintenance stage. From this chart both the owners of the project and the developers are able
to know the maximum or minimum time that the project will take for it to be complete.
Conclusion
From the given report, all the procedures being followed in the process ensures that the system
runs smoothly without interference or break down. The analysis phase ensures that all the system
functional requirements are met as required.
The sequence diagram ensures that all the process within a transaction is showed as required. In
case an issue arises it will be easy to pinpoint provide the required solution. And the entity
system diagram enables the designers to find ways in which the entities will be related to each
when designing the UX in order for the three interfaces to coordinate well. The proposed library
system will ensure that all the transactions within the library are done in the appropriate way
while taking the minimum time possible.

References
Bagui, S. and Earp, R., 2011. Database design using entity-relationship diagrams. Auerbach
Publications.
Fulton, C., 2011. Web accessibility, libraries, and the law. Information Technology and
Libraries, 30(1), pp.34-43.
Gemino, A. and Parker, D., 2009. Use case diagrams in support of use case modeling: Deriving
understanding from the picture. Journal of Database Management (JDM), 20(1), pp.1-24.
Ibrahim, R., 2010. Formalization of the data flow diagram rules for consistency check. arXiv
preprint arXiv:1011.0278.
Sula, C.A., 2013. Digital humanities and libraries: A conceptual model. Journal of Library
Administration, 53(1), pp.10-26.
Swain, S.K., Mohapatra, D.P. and Mall, R., 2010. Test case generation based on use case and
sequence diagram. International Journal of Software Engineering, 3(2), pp.21-52.