Use Case Card Inspection Checklist

• Name. Does the use case card document the name of the use case?
  • Is the name of the use case a uniqueunambiguous, meaningful active verb phrase that captures the goal of the primary actor?
  • Is the name of the use case from the actors's external viewpoint rather than the internal viewpoint of the business, application, or component?
  • Does the name of the use case include the name of the primary actor that benefits from the use case?
• Actor. Does the use case card document the primary actor benefiting from the use case?
• Requirement. Does the use case card provide provide a textual requirement?
  • Is the use case requirement functionally cohesive?
  • Does the use case requirement capture its functional abstraction and the actor's goal?
  • Is the use case essential (i.e., does not unnecessarily specify architecture or design decisions)?
• Business Rules. Does the use case card document any business rules or policies that impact the use case?
• Business Justification. Does the use case card provide the business justification for the use case?
• Use Case Paths. Does the use case card list the use case paths?
  • Is each normal path listed?
  • Is each exceptional path listed?
  • Doe the name of the path provide enough information to imply the path requirement, preconditions, and postconditions?