Java™ Design: Objects, UML, and Process

8.2. Responsibility Allocation

In this section, we'll illustrate the concepts by example. In Chapter 6, we presented a use case model that captured the requirements for a payroll system, and in Chapter 7, we identified initial classes we derived from the use case model. In this section, we transform our system into a set of interacting objects by combining the behavioral requirements with the structural boundary, entity, and control stereotypes we applied to the appropriate types of classes. Let's begin with the Run Payroll use case's primary flow of events.

The following reviews the primary flow of events presented in Figure 6.5 in Chapter 6 for the Run Payroll use case:

1.	The system retrieves a list of employees with signed time cards for ...