Use Cases Tips

• Indicate An Association Between An Actor And A Use Case If The Actor Appears Within The Use Case Logic  
• Avoid Arrowheads On Actor-Use Case Relationships  
• Apply <<include>> When You Know Exactly When To Invoke The Use Case 
• Apply <<extend>> When A Use Case May Be Invoked Across Several Use Case Steps  
• Introduce <<extend>> associations sparingly 
• Generalize Use Cases When a Single Condition Results In Significantly New Business Logic  
• Do Not Apply <<uses>>, <<includes>>, or <<extends>> 
• Avoid More Than Two Levels Of Use Case Associations 
• Place An Included Use Case To The Right Of The Invoking Use Case 
• Place An Extending Use Case Below The Parent Use Case  
• Apply the “Is Like” Rule to Use Case Generalization 
• Place an Inheriting Use Case Below The Base Use Case 
• Apply the “Is Like” Rule to Actor Inheritance 
• Place an Inheriting Actor Below the Parent Actor