- Practice performing ambiguity reviews on requirements documents
- Improve requirements and reduce errors in software
- Design the right tests with clear and unambiguous requirements
- Take back a practical ambiguity review checklist
Studies have shown that poor requirements are one of the most significant contributors to project failure—and half of all defects have their origin in bad requirements. If specifications are ambiguous, there is nearly a 100% chance that there will be one or more defects in the corresponding code.
Finding Ambiguities in Requirements explores ways to review specifications quickly and quantitatively to identify what is unclear about them. This powerful, yet practical, method helps you ensure that requirements documentation is clear, concise, and unambiguous.
Learn about and practice simple, effective review techniques that can reduce the ambiguity rate by 95% on subsequent specifications. In addition you’ll learn to determine if the requirements are detailed enough to produce a sufficient set of test cases to validate the system's functionality. To reinforce lectures and discussions, you’ll practice your newly acquired knowledge and skills in classroom exercises.
You can apply these same techniques to design specifications, user manuals, training materials, and online help, as well as agreements and contracts for software development projects.
This course is intended to help those who write and review functional requirements and those who develop and test systems based on those requirements. The audience includes business analysts, test analysts, requirements engineers, developers, technical writers, and project managers. No specific prerequisites are assumed.
