In Chapter 12, you developed a first-cut design class diagram and CRC card solutions for two use cases: Request a package pickup and Pickup a package. Let us extend your solution from that chapter by developing the following:

1. A sequence diagram for each use case (domain classes and controller classes only).

2. A separate multilayer sequence diagram for each use case that includes the domain classes and the view layer classes. (We won’t combine view and data access layers on the same drawing. It makes the drawing too complex.)

3. A final design class diagram that includes the classes from both use cases. Include elaborated attributes, navigation arrows, and all the method signatures from both use cases.

4. In Chapter 11, we defined four subsystems:

Customer account (like customer account)

Pickup request (like sales)

Package delivery (like order fulfillment)

Routing and scheduling

Even though these subsystems are somewhat arbitrary, we can treat each one as a separate package. Develop a package diagram for each of the four subsystems by assigning domain model classes to each package. A domain model class should belong to only one subsystem package. Normally, it is the subsystem that instantiates objects from that class. Also, show dependency relationships among the various packages and classes.