The requirements you capture must be stated in business terms, must be clearly stated, must be concise, and must be feasible. To ensure that requirements are clearly stated, you should have them proof read by someone external to the project (or at least someone not familiar with the requirements you've captured). Any questions raised by your proof reader should trigger a re-write of that requirement. Clean the language up until your proof reader understands the requirement.

[Read the rest of this article...]

I've seen alot of buzz and movement in the industry around requirements visualization. There have been talks, white papers, discussions, new tools, a...

[Read the rest of this article...]