I have a question regarding scenarios and requirements. In addition to writing complete scenarios (full stories), I have found it very helpful to write only sentence-long scenarios/requirements for telling about users' wishes. For example, I was working on an application for selecting among five thousand plants from a nursery. After having created a few personas, I wrote sentences like this:
"Adam wants a rather high tree to keep out the sun during summertime."
"Lynda wants red flowers that flower as long as possible throughout the summer."
I created about thirty of these, and then checked my prototype against these sentences.
I don't know what these should be called; both "scenarios" and "requirements" sound a little off. I just call them "wishes" or "user wishes". Is there a correct term that I'm missing here?
Also, in the Head First book on OOAD a scenario is (once again) a very short description. In an example where a gameboard maker application is developed, two example scenarios are as follows:
"The game designer creates a new board 8 squares wide by 10 squares high."
"Player 1 kills Player 2's troops at (4, 5) so the board removes Player 2's troops from that tile."
The upside of using this short manner of writing scenarios is emphasized: "...when you're writing use cases, putting together a requirements list, and using lots of scenarios to chart out all the paths through a use case."
It seems like the OOAD book and I are using scenarios somewhat the same way – to ensure no feature is overlooked. However, this is not how they are explained in IxD literature, where they are much longer and cover just one out of many possible complete interactions with a system. (A difference between my "user wishes" and the "scenarios" of the book is that I make them personal, as I would with a traditional scenario.)
I'd really appreciate if someone could explain what I'm doing.