Requirements Writing

After numerous meetings between the customer and the creator, I have to wonder how many people really know how to write a requirement, how to read a requirement and why we use requirements. The thing is, I like formally written requirements for large formal projects (like when there is lots of money on the line). They work.

However, for smaller projects it is still a good idea to apply the fundamentals of requirements.

Things to think about:
* requirements are What not How
* stepping through use scenarios helps
* assumed functionality requirements are the most dangerous
* coming back to ultimate goals is key to having a full set
* use previously made scope decisions as hard limits
* again, what not how