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

Module 6 - Use-Case AnalysisCheckpoints: Analysis ClassesCheckpoints: Analysis Classes• Are the classes reasonable?• Does the name of each classclearly reflect the role it plays?• Does the class represent a singlewell-defined abstraction?• Are all attributes andresponsibilities functionallycoupled?• Does the class offer the requiredbehavior?• Are all specific requirements onthe class addressed?Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 61(continued)The above checkpoints for the analysis classes might be useful.Note: All checkpoints should be evaluated with regards to the use cases beingdeveloped for the current iteration.The class should represent a single well-defined abstraction. If not, consider splittingit.The class should not define any attributes or responsibilities that are not functionallycoupled to the other attributes or responsibilities defined by that class.The classes should offer the behavior the Use-Case Realizations and other classesrequire.The class should address all specific requirements on the class from the requirementspecification.Remove any attributes and relationships if they are redundant or are not needed bythe Use-Case Realizations.6 - 61