Software Engineering for Library Management System

Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the student
Name of the university
Author note

Table of Contents
Introduction:...............................................................................................................................3
Requirements:............................................................................................................................3
a) classes.................................................................................................................................4
a) Class Diagram.....................................................................................................................4
b) Object diagram....................................................................................................................5
c) OCL....................................................................................................................................6
e) State Machine Diagram......................................................................................................8
f) Sequence Diagram..............................................................................................................9
g) Communication diagram...................................................................................................10
Question 2:...............................................................................................................................10
Question 3: Sequence Diagram................................................................................................12

Introduction:
A library system must include some basic functionality in order to maintain the
transaction and ease the librarians work efforts. In a library, there are several operations
needs to be conducted for a single transaction. A web application can assist to automate most
of the work and as result it could provide optimal support and operation with less effort. In
this paper, the fundamentals of such application is discussed along with the UML diagrams
which will assist to understand and define the operations of the library management
application. A library must consist of librarians who manage the transactions, items which
can be borrowed, borrower who borrow the items. Similarly, the web application will involve
these to be more productive and improve their library services to library users. This approach
will not only assist them to automate the processes, it will also reduce the amount of time
spent looking for library items and speed up the delivery of library items to borrowers.
Requirements:
In order to define the functionalities of the new web application, requirements of the
application needs to be defined clearly. This application is associated with the library, hence
there must be functionalities such as checked out, returned, put on reserve and renewed. Even
though, the rules differ from one library to another. For this application, the items stored in
the library is categorized in the three sections such as books, DVDs and magazines.
Librarians will be the principal user of the application. The system should automate their
daily functions, which include: checkout, return, placing items on reserve, and renewing
items. The system should also allow a borrower or librarian to search for an item based on
title, author, or keywords.

a) Classes
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type
of static structure diagram that describes the structure of a system by showing the system's
classes, their attributes, operations (or methods), and the relationships among objects.
Borrower, item, librarian, transaction, reservation are the candidate classes along with books,
DVD and magazine.
a) Class Diagram