This is a best practices question, not really a support request, but I thought someone might be able to help:
One of the writing style tips for the main steps of the use case is to "Ignore user interface". I know that some use case books suggest this as well, but I'm wondering where do most people document user interface detail and is there a place in CaseComplete that can or is designed to accommodate this?
Thanks,
Marc
Please sign in to leave a comment.
I prefer to put this detail in a mockup or wireframe that is associated with the use case. It lets me keep the use case clean and put the UI detail in a much more effective place.
On projects that demand very precise definitions of the UI, in addition to the wireframe I'll include screen specification in Excel format that describes each field, its constraints, validations, etc.
(Marc, I already mentioned this in my reply to your support ticket on this, but thought I would post here too). In addition to creating wireframe diagrams as Matt suggests, you can also document your UI using non-functional requirements. For example, you might have a requirement, "A help button must be available". In this example, the requirement might be applicable to the entire application, but for requirements specific to a subset of use cases, you can assign the requirement to the use case(s) it applies to. Then you can use the Requirements Cross Reference report to show the use cases that each requirement is applicable to, and vice versa, see the requirements for each use case.
