DEV475 Mastering Object-Oriented Analysis and Design with UML ...

Module 6 - Use-Case AnalysisDescribe ResponsibilitiesDescribe Responsibilities• What are responsibilities?• How do I find them?Interaction Diagram:Client:Supplier// PerformResponsibilityClass DiagramSupplier// PerformResponsibilityMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 37A responsibility is a statement of something an object can be asked to provide.Responsibilities evolve into one (or more) operations on classes in design; they can becharacterized as:• The actions that the object can perform.• The knowledge that the object maintains and provides to other objects.Responsibilities are derived from messages on Interaction diagrams. For eachmessage, examine the class of the object to which the message is sent. If theresponsibility does not yet exist, create a new responsibility that provides therequested behavior.Other responsibilities will derive from nonfunctional requirements. When you createa new responsibility, check the nonfunctional requirements to see if there are relatedrequirements that apply. Either augment the description of the responsibility, orcreate a new responsibility to reflect this.Analysis class responsibilities can be documented in one of two ways:• As “analysis” operations: When this approach is chosen, it is important thatsome sort of naming convention be used. This naming convention indicates thatthe operation is being used to describe the responsibilities of the analysis classand that these “analysis” operations WILL PROBABLY change/evolve in design.• Textually: In this approach, the analysis class responsibilities are documented inthe description of the analysis classes.For the OOAD course example, we will use the “analysis” operation approach. Thenaming convention that will be used is that the “analysis” operation name will bepreceded by '//'.6 - 37