Create Activity diagram for following: Use Case: Check Out Books Primary Actor: Worker Stakeholders and Interests: Worker: wants fast, and easy check out to books. Patron: wants fast checkout, and does not want to be charged for books they did not checkout. Library: wants fast checkout of books, and wants to make sure that all books that leave the library have been checked out. Wants to allocate books fairly. Government: wants to protect investment in books and keep costs down. Wants to promote learning and citizen happiness. Preconditions: The Worker has been authenticated. Success Guarantee (Post conditions): The System remembers that the Patron has checked out the books. Main Success Scenario (or Basic Flow): The Worker tells the System the identity of a patron who wishes to check out books. The System confirms that the patron is all owed to check out books, and remembers the patron's identity. The Worker tells the system the identity of a book this patron is checking out. The System confirms that the book can be circulated, calculates the due date based on whether the patron is a faculty member or a student, and records that the patron has checked out this book, which is due on the calculated due date, and makes that information available from the library catalogue. 5. The System tells the Worker the due date (which also confirms that the book has been checked 1. 2. 3. 4. out). The Worker repeats steps 3-5 until indicates done. Extensions (or Alternative Flows): 2a. If the patron is not allowed to check out books because they have violated some library policy (for example, if the patron has not paid their university bill or library fines): 1. The System tells the Worker that the patron is not allowed to check out books and the reason for this prohibition. 2. The use case ends. 4a. If the book that is being checked out is non-circulating: 1. The System tells the Worker why the book is non-circulating. 2. The use case continues from step 3 in the main success scenario. Special Requirements - There are different due dates depending on the kind of patron one is dealing with. For example, faculty can take out books for the whole academic year, whereas students can only take them out for a limited time. - The System must respond to the Worker, at least giving some progress indication, within 3 seconds, 95% of the time.
Create Activity diagram for following: Use Case: Check Out Books Primary Actor: Worker Stakeholders and Interests: Worker: wants fast, and easy check out to books. Patron: wants fast checkout, and does not want to be charged for books they did not checkout. Library: wants fast checkout of books, and wants to make sure that all books that leave the library have been checked out. Wants to allocate books fairly. Government: wants to protect investment in books and keep costs down. Wants to promote learning and citizen happiness. Preconditions: The Worker has been authenticated. Success Guarantee (Post conditions): The System remembers that the Patron has checked out the books. Main Success Scenario (or Basic Flow): The Worker tells the System the identity of a patron who wishes to check out books. The System confirms that the patron is all owed to check out books, and remembers the patron's identity. The Worker tells the system the identity of a book this patron is checking out. The System confirms that the book can be circulated, calculates the due date based on whether the patron is a faculty member or a student, and records that the patron has checked out this book, which is due on the calculated due date, and makes that information available from the library catalogue. 5. The System tells the Worker the due date (which also confirms that the book has been checked 1. 2. 3. 4. out). The Worker repeats steps 3-5 until indicates done. Extensions (or Alternative Flows): 2a. If the patron is not allowed to check out books because they have violated some library policy (for example, if the patron has not paid their university bill or library fines): 1. The System tells the Worker that the patron is not allowed to check out books and the reason for this prohibition. 2. The use case ends. 4a. If the book that is being checked out is non-circulating: 1. The System tells the Worker why the book is non-circulating. 2. The use case continues from step 3 in the main success scenario. Special Requirements - There are different due dates depending on the kind of patron one is dealing with. For example, faculty can take out books for the whole academic year, whereas students can only take them out for a limited time. - The System must respond to the Worker, at least giving some progress indication, within 3 seconds, 95% of the time.
Computer Networking: A Top-Down Approach (7th Edition)
7th Edition
ISBN:9780133594140
Author:James Kurose, Keith Ross
Publisher:James Kurose, Keith Ross
Chapter1: Computer Networks And The Internet
Section: Chapter Questions
Problem R1RQ: What is the difference between a host and an end system? List several different types of end...
Related questions
Question
Transcribed Image Text:Create Activity diagram for following:
Use Case: Check Out Books
Primary Actor: Worker Stakeholders and Interests:
Worker: wants fast, and easy check out to books.
Patron: wants fast checkout, and does not want to be charged for books they did not
checkout.
Library: wants fast checkout of books, and wants to make sure that all books that leave the
library have been checked out. Wants to allocate books fairly.
Government: wants to protect investment in books and keep costs down. Wants to
promote learning and citizen happiness.
Preconditions: The Worker has been authenticated.
Success Guarantee (Post conditions): The System remembers that the Patron has checked out the
books. Main Success Scenario (or Basic Flow):
The Worker tells the System the identity of a patron who wishes to check out books.
The System confirms that the patron is all owed to check out books, and remembers the
patron's identity.
The Worker tells the system the identity of a book this patron is checking out.
The System confirms that the book can be circulated, calculates the due date based on
whether the patron is a faculty member or a student, and records that the patron has checked
out this book, which is due on the calculated due date, and makes that information available
from the library catalogue.
5. The System tells the Worker the due date (which also confirms that the book has been checked
out).
The Worker repeats steps 3-5 until indicates done.
1.
2.
3.
4.
Extensions (or Alternative Flows):
2a. If the patron is not allowed to check out books because they have violated some library policy
(for example, if the patron has not paid their university bill or library fines):
1. The System tells the Worker that the patron is not allowed to check out books and the
reason for this prohibition.
2. The use case ends.
4a. If the book that is being checked out is non-circulating:
1. The System tells the Worker why the book is non-circulating.
2. The use case continues from step 3 in the main success scenario.
Special Requirements
- There are different due dates depending on the kind of patron one is dealing with. For example,
faculty can take out books for the whole academic year, whereas students can only take them out
for a limited time.
- The System must respond to the Worker, at least giving some progress indication, within 3
seconds, 95% of the time.
Expert Solution
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
This is a popular solution!
Trending now
This is a popular solution!
Step by step
Solved in 2 steps with 1 images
Recommended textbooks for you
Computer Networking: A Top-Down Approach (7th Edi…
Computer Engineering
ISBN:
9780133594140
Author:
James Kurose, Keith Ross
Publisher:
PEARSON
Computer Organization and Design MIPS Edition, Fi…
Computer Engineering
ISBN:
9780124077263
Author:
David A. Patterson, John L. Hennessy
Publisher:
Elsevier Science
Network+ Guide to Networks (MindTap Course List)
Computer Engineering
ISBN:
9781337569330
Author:
Jill West, Tamara Dean, Jean Andrews
Publisher:
Cengage Learning
Computer Networking: A Top-Down Approach (7th Edi…
Computer Engineering
ISBN:
9780133594140
Author:
James Kurose, Keith Ross
Publisher:
PEARSON
Computer Organization and Design MIPS Edition, Fi…
Computer Engineering
ISBN:
9780124077263
Author:
David A. Patterson, John L. Hennessy
Publisher:
Elsevier Science
Network+ Guide to Networks (MindTap Course List)
Computer Engineering
ISBN:
9781337569330
Author:
Jill West, Tamara Dean, Jean Andrews
Publisher:
Cengage Learning
Concepts of Database Management
Computer Engineering
ISBN:
9781337093422
Author:
Joy L. Starks, Philip J. Pratt, Mary Z. Last
Publisher:
Cengage Learning
Prelude to Programming
Computer Engineering
ISBN:
9780133750423
Author:
VENIT, Stewart
Publisher:
Pearson Education
Sc Business Data Communications and Networking, T…
Computer Engineering
ISBN:
9781119368830
Author:
FITZGERALD
Publisher:
WILEY