Thus far, we have focused on identifying the analysis classes that participate in a use case and distributing the responsibilities of the use case to the identified classes. This has been done in the context of interaction diagrams, which primarily capture the dynamic behavior of a use case.
Classes often participate in several use cases, and it is equally important to understand their static relationships to ensure consistency across the system.
We now turn our attention to this aspect by defining the classes and their relationships more precisely based on the Use Case Analysis work done thus far. We use the Transfer funds use case as a means to illustrate these static relationships.
The UML class diagram is useful for capturing ...