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.

Techniques for Quickly Reviewing Requirements for AmbiguitiesFinding 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.

Who Should AttendThis 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.

1-Day Course Outline

Introduction

Definition of good requirementsTestable requirementsDeterministic results and requirements

Confusing ConstructsLimitations of the English languageExamples of ambiguityAmbiguity review checklistPerforming an ambiguity reviewExercise: Identify ambiguities in various mini-specs

Class Daily Schedule

Training Course Fee Includes

• Tuition

• Course notebook

• Continental breakfasts and refreshment breaks

• Lunches

• Letter of completion

Richard Bender has over forty-five years experience in software with a primary focus on quality assurance and testing. He has consulted internationally to large and small corporations, government agencies, and the military. Richard’s work has included a wide variety of application classes and technology bases from embedded systems to super computer-based systems—and everything in between—consulting to both vendors and IT departments alike. He has been active in establishing industry standards for software quality and is a frequent speaker at conferences, universities, and corporate events. He was one of the first programmers ever awarded IBM’s Outstanding Invention Award for his breakthroughs on code based testing.

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.

Techniques for Quickly Reviewing Requirements for AmbiguitiesFinding 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.

Who Should AttendThis 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.

Virtual Package Includes:

Easy course access: You attend training right from your computer, and communication is handled by a phone conference bridge utilizing Cisco’s WebEx technology. That means you can access your training course quickly and easily and participate freely.

Valuable course materials: Our live-virtual training uses the same valuable course materials as our classroom training. Students will have direct access to the course materials.

Hands-on exercises: An essential component to any learning experience is applying what you have learned. Using the latest technology, your instructor can provide students with hands-on exercises, group activities, and breakout sessions.

Peer interaction: Networking with peers has always been a valuable part of any classroom training. Live-virtual training gives you the opportunity to interact with and learn from the other attendees during breakout sessions, course lecture, and Q&A.

Convenient schedule: Course instruction is divided into modules no longer than three hours per day. This schedule makes it easy for you to get the training you need without taking days out of the office and setting aside projects.

Small class size: Live-virtual courses are limited to the same small class sizes as our instructor-led training. This provides you with the opportunity for personal interaction with the instructor.

Richard Bender has over forty-five years experience in software with a primary focus on quality assurance and testing. He has consulted internationally to large and small corporations, government agencies, and the military. Richard’s work has included a wide variety of application classes and technology bases from embedded systems to super computer-based systems—and everything in between—consulting to both vendors and IT departments alike. He has been active in establishing industry standards for software quality and is a frequent speaker at conferences, universities, and corporate events. He was one of the first programmers ever awarded IBM’s Outstanding Invention Award for his breakthroughs on code based testing.

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.

Techniques for Quickly Reviewing Requirements for AmbiguitiesFinding 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.

Who Should AttendThis 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.

1-Day Course Outline

Introduction

Definition of good requirementsTestable requirementsDeterministic results and requirements

Confusing ConstructsLimitations of the English languageExamples of ambiguityAmbiguity review checklistPerforming an ambiguity reviewExercise: Identify ambiguities in various mini-specs

Training Course Fee Includes

Richard Bender has over forty-five years experience in software with a primary focus on quality assurance and testing. He has consulted internationally to large and small corporations, government agencies, and the military. Richard’s work has included a wide variety of application classes and technology bases from embedded systems to super computer-based systems—and everything in between—consulting to both vendors and IT departments alike. He has been active in establishing industry standards for software quality and is a frequent speaker at conferences, universities, and corporate events. He was one of the first programmers ever awarded IBM’s Outstanding Invention Award for his breakthroughs on code based testing.

Gary Mogyorodi has over 33 years of experience in the computing industry. Gary consults, trains, and mentors in software testing, specializing in Requirements-Based Testing. Some of his customers include Siemens, Cendant, Rockwell Automation, Boeing, EMC, IBM, LexisNexis, RBC, H&R Block, CIBC, TELUS, CGI, FiLogix, and Home Hardware. Gary is a Certified Tester, and Advanced Level Functional Tester with the ASTQB. He has managed testing efforts, developed testing methodologies, and created standards and procedures for quality assurance and testing. Gary obtained a Bachelor of Science degree in Mathematics from the University of Waterloo, and an M.B.A. from McMaster University. A prolific speaker, he has delivered presentations at premier software events throughout North America. Gary obtained a Bachelor of Science degree in Math from the University of Waterloo, and an M.B.A. from McMaster University. A prolific speaker, Gary has delivered presentations at premier software events throughout North America.