In chapter 10, you developed a first-cut design class diagram and CRC card solutions for two use case: Request a pickup package and pick up 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 multilayer sequence diagram for each use case that includes domain classes and data access classes.

3) A separate multilayer sequence diagram for each use case that include the domain claes and the view layer classes.(We dont combine view and data access layers on the same drawing, it makes the drawing too complex).

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

In chapter 9, we defined four subsystems:

> Customer account subsystem(like customer account)

> Pickup request subsystem(like sales)

> Package delivery subsystem(like order fulfillment)

> Routing and scheduling subsystem.

Even though these subsystems are somewhat arbitrary, we can treat each one as 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 object from that class. Also, how dependency relationships among the various packages and classes.