University Software Engineering Assignment: NIT2213 Solution

This document presents a comprehensive solution to a Software Engineering assignment, focusing on the design and analysis of a library management system. The solution includes detailed use case descriptions for actions such as checking out books, along with a corresponding use case diagram. It outlines the actors, stakeholders, preconditions, post-conditions, and alternative flows. Furthermore, the document provides explanations of various use cases, including registering users, borrowing books, and managing book returns. Class diagrams are used to model the system's classes, their relationships, and properties, while sequence diagrams illustrate interactions between objects in sequential order. Finally, a state machine diagram is included to represent the different states of the system. The assignment covers diagrams in Lucidchart and textual responses in Microsoft Word. This solution provides a valuable resource for students studying software engineering, offering insights into system design and analysis.

Running head: NIT2213 SOFTWARE ENGINEERING
NIT2213 Software Engineering
Name of the Student
Name of the University
Authors note

1NIT2213 SOFTWARE ENGINEERING
1.Use case Description for checking out books with one any exceptional
case
Use Case name Checking out books
Level Sub functional Level
Primary actor Faculty patrons, Graduate student patrons,
Undergraduate student patrons
Stakeholders and interest Graduate student patrons: The students
wants to loan a book from the library.
Library staff: The administrator needs to
register the details of the loaned book into
the system and update the loan details.
Administrator: The administrator of the
system responsible for management of
different transaction of the loaned books,
fine for late returns, login and registration of
the patron’s details.
Pre-condition 1. All the patrons are registered to the
prosed library management system.
2. The required books are available on the
shelf.
3. No other patrons have claimed reserve on
the required books.
Post-condition Record for a book loan against the student
account has been added.

2NIT2213 SOFTWARE ENGINEERING
Main success scenario 1 Student or the Library staff opens the
account of the patron in order to check if
there is any remaining due against his/her
account
2. If there is any outstanding fine the the
student/faculty will be asked to clear the
fine to get new loan of books
3 The patron without any fine will be
issued with the book loan after registering
the correct information about the book and
due date. 4 The patron gets the book loan.
Alternative flow 1. The patron opens the application and
searches for a book from the
database.
2. The patron finds out that the book is
not in the shelf.
3. Patron creates a reserve request is
helpful in getting the book first after
it is returned by the patron.
4. The Reserve request will be created
without any error and if any the
patron needs to inform the
administrator who will be rectifying
the issue as soon as possible.
Specific requirement The registered users to the system can only

3NIT2213 SOFTWARE ENGINEERING
borrow a book.
2.Use case diagram for the case study
Explanation of the use cases

4NIT2213 SOFTWARE ENGINEERING
U.1: Register a user
Use case Description: The user/Patron have to register/sign up. The administrator will
be able to add two different type of users to the system.
The library administrator/staff: The staff or the patrons have to provide details about
their name, address, and telephone number and other details.
Under graduate /post graduate student, faculty staff : The student have to provide
their course details along with name, address, phone number, email id, and department,
office phone number.
U.1.1: Sign up
Input: Details of the patrons (student/faculty) about users as mentioned above.
Output: Confirmation about the registration process for a member with a user id and
password will be provided to the user.
Processing: Details of the users will be checked and validated for any error. If any
error found then concerned error message will be displayed.
U.1.2: Login
Input: The users have to enter use rid and password to login to the system.
Output: logged in user will be able to use functionalities of the system.
U.2: Borrowing the books by the user (by students/faculty).
U.2.1: Issuing Books.
Description: The List of books will be displayed against the searches by the user.

5NIT2213 SOFTWARE ENGINEERING
U.2.2: Search for a Book
Input: The user have to enter the author name/ publisher/ ISBN of a required book
that needs to be issued.
Output: The system will display the list of books that matches with the related
keyword.
U.2.3: Issue book to a user (student/faculty)
State: The Book is on the shelf and which is required by the user wants to issues.
Input: Ask the library staff to issue the book against the users account.
Output: conformation message/screen for issuing the book.
U.2.4: Renew last issued book
State: The due date is checked and validated that the account does not have any fine
and the renewal is issued.
Input: Select and notify the library staff which book is to be renewed for the next
period.
Output: Renewal conformation message for the successful renewal.
Processing: In case the required book is having reserve request by other user then
error message will be prompted otherwise conformation for the renewal message will be
depicted.
U.2.5: Return a book
Input: The user will request the library staff to return loaned book back to the
library.

6NIT2213 SOFTWARE ENGINEERING
Output: The library staff will open the user account and find out the issued list of
books and will be update the list removing the books which are returned by the patron.
U.2.6: Request for Reserve a book
Input: search for a book by entering the details of required books.
Output: successfully reserve request is placed.
U.2.7 calculate and collect Fine
Input: The staff will check for additional days after the predetermined due date in
order to calculate the fines.
Output: Detail is displayed on the screen about the additional days and fines on
different books.
Processing: Fine will be calculated depending on the predefined structure, In case the
user has crossed the date of return and loan is not renewed.
U.3.1.2 Remove details of books
Input: Enter the details in order to find out the book and quantity of books which are
to be deleted.
Output: Updated list of books will be available and displayed.

7NIT2213 SOFTWARE ENGINEERING
Functionalities for the library staff
The Library staff will have username and password in order to access the developed
system. After logging in to the system the staff has to add details of the books and users to
system and then check the book stock. In the university library management system librarian
will be able to create the members whether student or faculty patron.
Librarian or the staff will be able to issue books to only to the registered patrons and
get return from those users. Calculation of fines/penalty for late return of the book to the
library.
Only administrator will be able to access as well as add particulars of a book to the
library shelf. The other user have no access to this functionality. Information about the
users/patrons like user name, required password, contact, department of the faculty patterns
and office contacts are required by the admin in order to
3. Class diagram for the case study
In modelling a proposed information system Class diagrams are considered as the
main building blocks of development using the object oriented languages. The UML class
diagram is very useful in depicting the show potential classes, relationships among the
classes, different interfaces that may work as collaborators, association among the classes and
finally the collaboration.
As in the OOP based system development methods classes are considered as building
block of the proposed application. Due to the fact that class diagram can appropriately
represent the required classes, inheritance and other properties along with everything that
OOPs is based on. In addition to that , the class diagrams are helpful in describing the
various kind of objects of the classes and static relationship among the classes of the

8NIT2213 SOFTWARE ENGINEERING
application. In this way the class diagrams are helpful in proper designing as well as analysis
of proposed application in a faster and efficient way.

9NIT2213 SOFTWARE ENGINEERING

10NIT2213 SOFTWARE ENGINEERING
5. Sequence diagram for the checking out books
In developing an application sequence diagram is useful in depicting the interactions
among the objects in sequential order. The sequence of the interaction will be same as
they may take place in the proposed system. Sequence diagrams also helpful in
describing how as well as the order interaction among the class objects in a system.

11NIT2213 SOFTWARE ENGINEERING
5. SMD for the case study