logo

NIT2213 Software Engineering - Use Case Description, Use Case Diagram, Class Diagram, Sequence Diagram, and SMD

Answer a set of questions about material of the unit related to use cases, sequence diagrams, class diagrams, and state machine diagrams.

12 Pages1395 Words184 Views
   

Added on  2022-10-19

About This Document

This document provides a detailed understanding of NIT2213 Software Engineering with a use case description for checking out books, a use case diagram, a class diagram, a sequence diagram, and an SMD. It also includes functionalities for library staff, stakeholders, and interests, pre- and post-conditions, and specific requirements. The document is relevant for students studying software engineering at the university level.

NIT2213 Software Engineering - Use Case Description, Use Case Diagram, Class Diagram, Sequence Diagram, and SMD

Answer a set of questions about material of the unit related to use cases, sequence diagrams, class diagrams, and state machine diagrams.

   Added on 2022-10-19

ShareRelated Documents
Running head: NIT2213 SOFTWARE ENGINEERING
NIT2213 Software Engineering
Name of the Student
Name of the University
Authors note
NIT2213 Software Engineering - Use Case Description, Use Case Diagram, Class Diagram, Sequence Diagram, and SMD_1
NIT2213 SOFTWARE ENGINEERING
1
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.
NIT2213 Software Engineering - Use Case Description, Use Case Diagram, Class Diagram, Sequence Diagram, and SMD_2
NIT2213 SOFTWARE ENGINEERING
2
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
NIT2213 Software Engineering - Use Case Description, Use Case Diagram, Class Diagram, Sequence Diagram, and SMD_3
NIT2213 SOFTWARE ENGINEERING
3
borrow a book.
2.Use case diagram for the case study
Explanation of the use cases
NIT2213 Software Engineering - Use Case Description, Use Case Diagram, Class Diagram, Sequence Diagram, and SMD_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Use Case Description for Checking Out Books in University Library System
|10
|1237
|384

UML Diagrams for University Library System Case Study
|8
|595
|271

Library Service System for University | Desklib
|4
|985
|498

Use Cases for Accommodation Booking System - Desklib
|17
|2703
|284

Analyzing the System: Use Case, Activity, Sequence, State Machine, and Domain Model Diagrams
|16
|1924
|34

System Analysis Report for World Tour Company
|12
|2327
|1