Section 27. Ideas for Solutions


27. Ideas for Solutions

Ideas for solutions are obviously not requirements, but it is impossible when gathering requirements not to become interested in how they might be implemented. Rather than discarding the ideas oreven worsewriting them as if they are requirements, a practical idea is to simply set aside a section of your specification for these ideas. Record each one faithfully in this area, and then hand them over, along with the requirements, to your designer.

In exceptional circumstances, you might consider writing your ideas for solutions against individual requirements. Take care when doing so, as it is all too easy to become engulfed in cool solutions and forget for the moment you are supposed to be gathering requirements.

We said at the beginning of the "Project Issues" section earlier in this chapter that all of these components do not necessarily belong in a requirements specification. The ideas for solutions are an ideal subject for a blog. This is, after all, the place for ideas, and blogs are a great place for creativity and building on one another's ideas.




Mastering the Requirements Process
Mastering the Requirements Process (2nd Edition)
ISBN: 0321419499
EAN: 2147483647
Year: 2006
Pages: 371

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net