TIP: Refer back to your use cases document. Use them for ideas and make sure that you cover all of them. Remember that test cases are more precise than use cases, test cases should reference specific details of your implementation, and there may be several test cases for a given use case.

TIP: The test case suite can be organized into nested lists according to other coverage criteria, e.g., by actor. Or, it can be organized into tables that consider two aspects at a time, e.g., business objects vs. actor. If a certain section of the tree or table does not need test cases, explicitly mark it "N/A". Otherwise, if a section needs more test cases than you have written yet, mark it "TODO". If one cell or list item contains many tests, break that section out into its own table, as done for the enrollment feature below.