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

Module 3 - Requirements OverviewCheckpoints: Requirements: Use-Case SpecificationsCheckpoints: Requirements: Use-Case Specifications• Is it clear who wants to perform a usecase?• Is the purpose of the use case alsoclear?• Does the brief description give a truepicture of the use case?• Is it clear how and when the usecase's flow of events starts and ends?• Does the communication sequencebetween actor and use case conformto the user's expectations?• Are the actor interactions andexchanged information clear?• Are any use cases overly complex?Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 29Include any (nonfunctional) requirements to be handled in the object models in theuse-case Special Requirements.Behavior might exist that is activated only when a certain condition is not met. Thereshould be a description of what will happen in such a case.If you want your Use-Case Model to be easy to understand, you might have to splitup complex use cases. A use case that contains disparate flows of events will be verydifficult to understand and to maintain. It is best to divide such use cases into two ormore separate ones.3 - 29