Hey, all. I'm working on creating the specs for a "smart client" (i.e., Windows client application), which involves a lot of standard functionality built into the control classes themselves. This is functionality I don't want to includes in the use cases, since it's very specific on a per-window basis, down to the individual field level.
I'd like to create some requirements on the control classes themselves. (Or, I may make a "User Interface Controls" formal requirements package, then link these external requirements to the control classes.)
Some examples to illustrate what I'm trying to do:
Entity Name Text Box
- Limited to 64 characters
- Automatically capitalizes the entry when the focus leaves the text box
State Text Box
- Limited to 5 characters
- Characters forced to uppercase as they're typed
My question is: How do I make sure my QA people "find" this information, since it won't be directly included in the use cases, and won't be directly included in the object model for the user interface? (This is because the behavior will be linked to the control classes, as opposed to instances of the controls.)
Do I create test cases for each? Do I just make sure that the QA team is pointed to the "User Interface Controls" requirements, which would include information on which control classes realize those requirements?
Or, do any of you have an entirely different suggestion on how to handle this?
