- "The predominant tool for defining requirements proved to be Microsoft Word, which results
in large documents that are not easily reviewed, shared or amended."
(Market Snapshot Report, vokeStream, August 2008)
- "the cost difference between detecting an error in the design at the time of capturing the requirements versus detecting an error after the system has been produced is over 270 times the amount"
(Gartner Group)
- "Of the top ten risks resulting in software project failure, requirements shortfalls account for four of the top six risk factors"
(Boehm, B)

Benefits of Simulating Your Requirements:
- Clarify and validate your requirements early in the process
- Visualize system behavior
- No need to write code
- Bridge communication gap between Business and IT
- Speed time to market
- Reduce risk
- Eliminate re-work cost