Checklist: Business Use Case Model
This checklist helps ensure the business Use-Case Model is complete and accurate
Check Items
For the business goals
  • Has the business strategy been translated into business goals?
  • Are the business goals concrete and measurable?
  • Are the relationships between the business goals clear?
  • Have all the business goals been identified?
For the business actors
  • Have all business actors been found?
  • Does each business actor express a role, not a person? Try to name at least two people that can act as the actor.
  • Does each business actor model something outside the business?
  • Is each business actor involved with at least one business use case? If not, remove it.
For the business use cases
  • Do the business use cases conform to the business you want them to describe?
  • Have all the business use cases been found? Taken together, the business use cases should perform all activities within the business.
  • Are there multiple business use cases with very similar names? If so, consider merging them or changing their names.
  • Are the business use cases aligned with the business strategy?
  • Does each business use case support at least one business goal?
  • Are all activities within the business included in at least one business use case?
  • Is there a balance between the number and the size of the business use cases?
  • Is each business use case unique? If not, consider merging it with a similar business use case.
  • Is each business use case involved with at least one business actor?  If not, is it meaningful?
For the business use case diagrams
  • Do the diagrams appear to be well structured?
  • Do the diagrams provide an easy-to-understand overview of the business use cases?
  • Are there too many relationships in the diagrams?
  • Are the diagrams so large and complex that they should be broken down into several smaller ones?
For packages in the Business Use Case Model
  • Is the name and purpose of each business use-case package clear?
  • Is the contents of each business use-case package consistent with its name and purpose?
  • Is the ratio between number of packages and the number of business goals, business actors, and business use cases reasonable?  There should not be more than about 20 elements (directly) in a business use case package.
  • Are the business use-case packages nested too deeply?
  • Does the package structure add to the clarity and understandability of the model?