Controlling use case quality

Use cases are designed and documented by a lot of people. This leads to non-homogenous specifications, some being high-quality and others of different quality. We should take measures to help use case designers/specifiers make quality use cases and resources.

This could be in any form, e.g. (or a combination of those):

• A group within the Nuts community that assesses use case quality
• A checklist of things to keep in mind when designing use cases
  • e.g.: scope design, authorization policies
• A model to follow (find other vendors, define goals, look for information standards, PoC/hackaton, assess, implement, pilot, etc)
• I started a Wiki book on this at some point: https://wiki.nuts.nl/books/designing-a-nuts-use-case (incomplete)
• Tooling that helps checking formal specification

Start by reviewing the incomplete Designing a Nuts use case wiki book linked in the issue and compare it with the proposed checklist, quality-assessment group, lifecycle model, and formal-specification tooling options. No code files or tests are named; the work is complete only after the community agrees on a concrete quality approach and its supporting resources.