Nazzaro & Associates

The Future of Technology Today SM


 

Home
Training
Services
Presentations
Modeling
Books
Links
Contact Us

Use Case Development 

Download Use Case Development In a Nutshell (PDF)

Iterations:

  • Assign use cases to various iterations, based on priority, complexity, and dependency.

  • You will most likely write your use case descriptions over multiple iterations of your project.

Flow of Work:

  1. Determine the use case's goal.

  2. Write a brief description for each identified use case.

  3. Review and agree on brief description.

  4. Work with Subject Matter Experts (SMEs) and develop the use case descriptions for that iteration.

Things to Consider When Writing Use Case Descriptions:

  1. Before writing use case descriptions determine the actors’ flow of work when interacting with the system. 

  2. Always challenge yourself and ask “Am I describing a something that has meaningful / observable value for the business?”

  3. Ask yourself “What is the actor really trying to do?” 

If you have use cases like “Find Order,” “Search for Index,” or “Locate Carrier”

 

– ask yourself –

 

why am I trying to “Find an Order,” “Search for an Index,” or “Locate Carrier.” 

 

This simple question may help you level set and see that your use cases were too granular. 

 

You may find that you are really trying to “Place an Order,” “Manage an Index,” or “Assign Load to Carrier.”

  1. Again, think meaningful / observable value for the business and the actor.

  2. Stay away from technology, screens, or simply focusing on screen flow.

  3. Leverage a Use Case Template, but if the template isn’t capturing the information you want then modify it.

  4. Describe the workflow in the use case template and use indenting to aid readability.

  5. On your first pass ignore reusable logic.  Focus on describing the business process.

  6. Do not focus on <<include>> and <<extend>> relationship.

  7. Use a simple class diagram or glossary to help in writing.

Last But Not Least… 

  • Review use cases with subject matter experts (SMEs) and stakeholders to gain consensus.

  • You may wish to develop screen snapshots or even a simple prototype for each use case.

  • Adjust the class diagram & glossary as necessary.

  • Whether or not you actually develop formal, essential use case descriptions I've found it's the discussions with the SMEs to be of the most value.

  • Be pragmatic!!!

 

Back to Top