Whenever creating use cases it is a good idea to agree on what quality the use cases should have. Furthermore when creating use cases in a team with regularly review sessions it is desirable to establish an objective list of factors to check for when reviewing.
To do this you should establish a Use Case Completeness Checklist with factors that should all be true in order t label the use case "Complete". This way only "Complete" use cases are passed to review sessions and all team members know what, in this project, makes a "Complete" Use Case.
Feel free to use the embedded Use Case Completeness Tool and alter it to fit your project.
Comments