Build a Use Case Diagram for a Book Details API
The use case diagram communicates how an actor interacts with your feature and which systems the user interacts with.
- Must contain a business actor (2 pts)
- Must contain a use case/business case name with flow (2 pts)
- Must identify a system boundary (2 pts)
![student submitted image, transcription available below](https://media.cheggcdn.com/media/495/49560969-de7d-49de-90f5-ba59a2598103/php9KRNXE)
An administrator must be able to create a book with the book ISBN, book name, book description, price, author, genre, publisher, year published and copies sold. Logic: Given a Book's info, add it to the system. HTTP Request Type: POST Parameters Sent: Book Object Response Data: None Must be able retrieve a book's details by the ISBN Logic: Given a book id, retrieve the book information HTTP Request Type: GET Parameters Sent: Book Id Response Data: Book object JSON An administrator must be able to create an author with first name, last name, biography and publisher Logic: Given an Author's Info, add it to the system. HTTP Request Type: POST Parameters Sent: Author Object - Response Data: None Must be able to retrieve a list of books associated with an author Logic: Given an Author's Id, return the list of books for that author. HTTP Request Type: GET Parameters Sent: Author Id Response Data: JSON list of Book Objects