Figure is a fully developed use case description for the use case Receive new book in the university library system. Do the following:

a. Develop a first-cut sequence diagram, which only includes the actor and problem domain classes.
b. Add the view layer classes and the data access classes to your diagram from part a.
c. Develop a design class diagram based on the domain class diagram and the results of parts a and b.
d. Develop a package diagram showing a three layer solution with view layer, domain layer, and data access layerpackages.

Transcribed Image Text:

Use Case Name: Receive new book Scenario Triggering Event: Newly purchased book arrives Receive new book Brief Description:The librarian decides on purchases of new books and places order (prior to this use case) Shipments of new books arrive. Each new book is assigned a library catalog number. Some books are simply additional copies of existing titles. Some books are new editions of existing titles. Some books are new titles and new physical books. The new book information is added to the system. Em Stakeholders: Preconditions Postconditions Flow of Activities: Book Title exists ical Book exists System 1. Collect new books from receipt of shipment. 2. For each book, research book category and catalog numbers. Assign tentative number. 3a. If new copy of existing title, enter book information3a.1 Update catalog with new and catalog number into system. 3b. If new edition of existing title, enter book information, 3b.1 Update catalog with new number.Verify that not duplicate. number. Verity that not duplicate. not duplicate. edition information, and catalog number 3c. If new title, assign general catalog number. Assign3c.1 Verify that catalog number book copy number 4. Mark book with number. 5. Place book on shelving cart. 6. Repeat for each book (back to step 2). Exception Duplicate numbers require further research and reassignment of catalog numbers.