For each use-case realization there can be one or more class diagrams depicting its participating classes. A class and its objects often participate in several use-case realizations. It is important while designing to coordinate all the requirements on a class and its objects that different use-case realizations can have. The figure below shows an analysis class diagram for the realization of the Receive Deposit Item use case. Note the use of boundary-control-entity stereotypes to represent analysis classes (see Guideline: Entity-Control-Boundary Pattern).