Software Engineering (UML Diagrams)

This report discusses the use case, sequence, class and state machine diagrams in software engineering for library management system. It also includes a use case description, actors, stakeholders, flow of activities and exception conditions. The report concludes with a bibliography.

Running head: SOFTWARE ENGINEERING
Software Engineering (UML Diagrams)
Name of the Student:
Name of the University:
Author Note

1
SOFTWARE ENGINEERING
Use Case Description
The Use case description which is provided below is considered for the case where
the Books are to be checked out and only has a single exception.
Use Case Name: Check out books
Scenario: The books would be checked out by the patron
Triggering Event: The book is to be selected.
Brief Description: The books are to be checked out by the patron once the selection
of the book is done
Actors: Librarian, Students, Teachers
Related Use Case: Select Books
Stakeholders: Students, Teachers
Precondition: Selection of Book by the Patron
Post Condition: Return Books
Flow of Activities: Actor System
1. Search the book
2. Select the Book
3. Checkout the
Book
1. The list of books would be
displayed by the system.
2. The system would allocate
the books to the patron
3. The system would loan
out the books to the patron
Exception
Conditions:
The desired book is not in the inventory of the library

2
SOFTWARE ENGINEERING
Use Case Diagram
Figure 1: Use Case Diagram of the Library Management system
Source: (created by author)
The use case diagram for the Library management system has been used for the
description of the cases that can occur for the case study and the main actors of the use which
has been identified in the diagram are the system, librarian, teacher and students.

3
SOFTWARE ENGINEERING
Sequence Diagram
Figure 2: Sequence Diagram of the Library Management system
Source: (created by author)
The sequence diagram of the library management system provides the sequence in
which the tasks by the patron would take place and also the alternative flow of messages has
been shown in the diagram and this would help the illustration of the interaction of the patron
with the system.

4
SOFTWARE ENGINEERING
Class Diagram
Figure 3: Class Diagram of the Library Management system
Source: (created by author)
The class diagram has been used to display all the classes that are associated with the
library of the library management system. These classes would help the Patron object in
realising all the main methods and the return book method which is the main point of
discussion in this report.

5
SOFTWARE ENGINEERING
State Machine Diagram
Figure 4: State Machine Diagram of the Library Management system
Source: (created by author)
The state machine diagram is basically based on the object book in the library
management system. The state machine diagram has been used for displaying all the states of
the books and the all the process ends with the book returning to the Library management
system.

6
SOFTWARE ENGINEERING
Bibliography
Arcuri, A., & Briand, L. (2014). A Hitchhiker's guide to statistical tests for assessing
randomized algorithms in software engineering. Software Testing, Verification and
Reliability, 24(3), 219-250.
Fitzgerald, B., & Stol, K. J. (2017). Continuous software engineering: A roadmap and
agenda. Journal of Systems and Software, 123, 176-189.
Tahir, M., Khan, F., Babar, M., Arif, F., & Khan, F. (2016). Framework for Better
Reusability in Component Based Software Engineering. the Journal of Applied
Environmental and Biological Sciences (JAEBS), 6, 77-81.
Wohlin, C. (2014, May). Guidelines for snowballing in systematic literature studies and a
replication in software engineering. In Proceedings of the 18th international
conference on evaluation and assessment in software engineering (p. 38). ACM.