0% found this document useful (0 votes)
88 views4 pages

Use Case and Use Case Specification Template

The document provides use case specifications for the log in, return book, and transaction summary generation processes of a library management system. It includes tables that describe the actor, description, main and alternative sequences of steps, preconditions, and postconditions for each use case. An incomplete use case diagram is also shown to provide context for the specifications.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
88 views4 pages

Use Case and Use Case Specification Template

The document provides use case specifications for the log in, return book, and transaction summary generation processes of a library management system. It includes tables that describe the actor, description, main and alternative sequences of steps, preconditions, and postconditions for each use case. An incomplete use case diagram is also shown to provide context for the specifications.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Figure 1(continue figure numbering) [Arial 11, bold]

Use Case Diagram for XYZ System [Arial 11]

Note:
The figure shown above is an incomplete version of a library system.
Use Case Specification [Arial 12]
Table 1 [Arial 11, bold]
Use Case Specification for Log In [Arial 11]

Use Case Name Log In


Actor(s) Librarian, Admin
Description The Log In process
Main Sequence Actor Action System Response
Step 1: The actor initiates the
system.
Step 2: The system displays
the log in dialog.
Step 3: The actor inputs log
in credentials
Step 4: The actor clicks the
“Log in” button.
Step 5: The system validates
the log in request.
Step 6: System displays the
main form.

Alternative Sequence Step 6: [for failed log in


validation] System displays
error message.
Step 7: Actor closes the error
dialog
Step 8: System redirects the
actor to step 3.
Step 3: The actor clicks the
“Cancel” Button.
Step 4: System Terminates
itself
Step 4: The actor clicks the
“Cancel” button.
Step 5: System Terminates
itself
Precondition System is initiated, Actor have valid log in credentials
Postcondition The actor successfully logged on
Table 2
Use Case Specification for Return Book

Use Case Name Return Book


Actor(s) Librarian
Description Actor returns a book/material
Main Sequence Actor Action System Response
Step 1: The actor initiates the
“Return Book” module.
Step 2: The system displays
the “Return Book” dialog.
Step 3: The actor
inputs/scans the book
accession number.
Step 4: Include “Transaction
Summary Generation”
Step 5: Include “Penalty
Generation”
Step 6: Include “Update
Material Availability”
Step 7: System Displays
Success Message Dialog.

Step 8: Actor Closes the


message dialog
Step 9: System redirects the
actor to the main form.

Alternative Sequence Step 3: Actor Closes the


“Return Book Module”
Step 4: System redirects the
actor to the main form.

Precondition User is logged in; Material has a valid accession number.


Postcondition Book/ Material Returned; Is available for other loan
transaction
Table 3
Use Case Specification for Transaction Summary Generation inclusion

Use Case Name Transaction Summary Generation


Actor(s) Librarian
Description System generates the transaction summary. This includes
loan date, duration, reference/material type, purpose, and
borrower data.
Main Sequence Actor Action System Response
Step 1: The actor
inputs/scans the book
accession number.
Step 2: The system retrieves
related data such as loan
date, duration,
reference/material type,
purpose, and borrower data.

Step 3: System appends the


transaction summary into one
of the main panels of the
system UI.
Alternative Sequence Step 2: The system is not
able to retrieve related data.

Step 3: Displays Error


Message Dialog
Step 4: Actor Closes the
message dialog
Step 5: System redirects the
actor to the main form.

Precondition User is logged in; The actor initiates the “Return Book”
module.
Postcondition Generated Transaction Summary

Note:
You need to create specifications for every use case found in our diagram.
Please be consistent in the usage of terms/keywords

You might also like