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

DEV475 Mastering Object-Oriented Analysis and Design with UMLDescribe ResponsibilitiesUse-Case Analysis Steps• Supplement the Use-Case Descriptions• For each Use-Case Realization• Find Classes from Use-Case Behavior• Distribute Use-Case Behavior to Classes• For each resulting analysis class• Describe Responsibilities• Describe Attributes and Associations• Qualify Analysis Mechanisms• Unify Analysis Classes• CheckpointsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 36At this point, analysis classes have been identified and use-case responsibilities havebeen allocated to those classes. This was done on a use-case-by-use-case basis, witha focus primarily on the use-case flow of events. Now it is time to turn our attentionto each of the analysis classes and see what each of the use cases will require ofthem. A class and its objects often participate in several Use-Case Realizations. It isimportant to coordinate all the requirements on a class and its objects that differentUse-Case Realizations may have.The ultimate objective of these class-focused activities is to to document what theclass knows and what the class does. The resulting Analysis Model gives you a bigpicture and a visual idea of the way responsibilities are allocated and what such anallocation does to the class collaborations. Such a view allows the analyst to spotinconsistencies in the way certain classes are treated in the system, for example, howboundary and control classes are used.The purpose of the Describe Responsibilities step is namely to describe theresponsibilities of the analysis classes.6 - 36