Use Cases and Testing

Testing UML Models, Part 1
  1. from highest to lowest levels?
  2. Is there a context-setting, highest-level use case at the outermost design scope for each primary actor?


  1. Are all the system's functional requirements reflected in the use cases?
  2. Are all the information sources listed?


  1. Do the use cases define all the functionality within the scope of the system and nothing outside the scope?
  2. Can we trace each use case back to its requirement(s)?
  3. Can we trace each use case forward to its class, sequence, and state-transition diagrams?

This set of questions, based on syntax, domain expert, and traceability testing, and focused on completeness, correctness, and consistency, is designed to get you started testing in an area with which you may not be familiar. Future articles will apply the same principles to testing sequence diagrams, class diagrams, and state-transition diagrams.

Good luck testing.

Other articles in this series:

Sequence Diagrams: Testing UML Models, Part 2

Class Diagrams: Testing UML Models, Part 3

State-Transition Diagrams: Testing UML Models, Part 4

User Comments

1 comment
Fiona Benichou's picture
Fiona Benichou

Hi Lee,

In addition to this article, I recently purchased and enjoyed your book on “A Practitioner’s guide to software test design”. The techniques are really helpful! Is there a tool/software downloads/test management system available that encompasses ALL of the test design techniques discussed in the book?

April 9, 2013 - 1:16pm

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.