Finding Ambiguities in Requirements

Techniques for Improving Requirements and Software

Learn ways to review specifications quickly and quantitatively to identify what is unclear about them in this one-day course. Learn about and practice simple, effective review techniques that can reduce the ambiguity rate by 95% on subsequent specifications.

Upcoming Classes

Dates
Mode
Location
Event
Venue
Call to Schedule
Anytime
Virtual Classroom
Your Location
Anywhere
Oct 31Nov 01, 2017
Virtual Classroom
Desktop
Anywhere
Select a learning mode button (Public, On-Site, etc.) for specific class details and fact sheet.
Description
  • 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.

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

Who Should Attend?
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.

Questions? 888.268.8770 [email protected]
Course Outline

Introduction
Definition of good requirements
Testable requirements
Deterministic results and requirements

Confusing Constructs
Limitations of the English language
Examples of ambiguity
Ambiguity review checklist
Performing an ambiguity review
Exercise – Identify ambiguities in various mini-specs

Jargon and Complexity
The language barrier
Carelessness
Assumed functional knowledge
Exercise – Translate jargon into plain English
Unnecessary complexity
Exercise – Simplify overly complex writing

Defining Clear Objectives
Objectives vs. requirements
Quantitative vs. qualitative objectives
Identifying the objectives of all stakeholders
Product vs. project objectives
Templates for the objectives specification
Exercise – Identify the true objectives

Introduction to Writing Testable Requirements
Alternative styles
Guidelines for writing clear specifications
Summary of how ambiguities are addressed

Introduction to Requirements-Based Testing
Quality filters
Advantages of rigorous testing
Using test cases to validate requirements

Dates
Mode
Location
Event
Venue
Oct 31Nov 01, 2017
Virtual Classroom
Desktop
Anywhere
Price: $599 USD Course Duration: 2 Days
Description
  • 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.

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

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

Questions? 888.268.8770 [email protected]
Course Outline

Introduction
Definition of good requirements
Testable requirements
Deterministic results and requirements

Confusing Constructs
Limitations of the English language
Examples of ambiguity
Ambiguity review checklist
Performing an ambiguity review
Exercise – Identify ambiguities in various mini-specs

Jargon and Complexity
The language barrier
Carelessness
Assumed functional knowledge
Exercise – Translate jargon into plain English
Unnecessary complexity
Exercise – Simplify overly complex writing

Defining Clear Objectives
Objectives vs. requirements
Quantitative vs. qualitative objectives
Identifying the objectives of all stakeholders
Product vs. project objectives
Templates for the objectives specification
Exercise – Identify the true objectives

Introduction to Writing Testable Requirements
Alternative styles
Guidelines for writing clear specifications
Summary of how ambiguities are addressed

Introduction to Requirements-Based Testing
Quality filters
Advantages of rigorous testing
Using test cases to validate requirements

Class Schedule
Day 1: 1:00pm-4:00pm ET/10:00am-1:00pm PT
Day 2: 1:00pm-4:00pm ET/10:00am-1:00pm PT
Class Fee Includes
  • Easy course access: Attend training right from your computer and easily connect your audio via computer or phone. You can access your training course quickly and easily and can participate freely.
  • Live, expert instruction: See and hear your instructor presenting the course materials and answering your questions in real-time.
  • 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.
  • Real-time communication: Communicate real-time directly with the instructor. Ask questions, provide comments, and participate in the class discussions.
  • 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
Instructors
Richard Bender
BenderRBT
Dates
Mode
Location
Event
Venue
Call to Schedule
Anytime
Virtual Classroom
Your Location
Anywhere
Course Duration: 1 Day
Description
  • 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.

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

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

Questions? 888.268.8770 [email protected]
Course Outline

Introduction
Definition of good requirements
Testable requirements
Deterministic results and requirements

Confusing Constructs
Limitations of the English language
Examples of ambiguity
Ambiguity review checklist
Performing an ambiguity review
Exercise – Identify ambiguities in various mini-specs

Jargon and Complexity
The language barrier
Carelessness
Assumed functional knowledge
Exercise – Translate jargon into plain English
Unnecessary complexity
Exercise – Simplify overly complex writing

Defining Clear Objectives
Objectives vs. requirements
Quantitative vs. qualitative objectives
Identifying the objectives of all stakeholders
Product vs. project objectives
Templates for the objectives specification
Exercise – Identify the true objectives

Introduction to Writing Testable Requirements
Alternative styles
Guidelines for writing clear specifications
Summary of how ambiguities are addressed

Introduction to Requirements-Based Testing
Quality filters
Advantages of rigorous testing
Using test cases to validate requirements

Class Schedule
Sign-In/Registration 7:30 - 8:30 a.m.
Morning Session 8:30 a.m. - 12:00 p.m.
Lunch 12:00 - 1:00 p.m.
Afternoon Session 1:00 - 5:00 p.m.
Times represent the typical daily schedule. Please confirm your schedule at registration.
Class Fee Includes
• Tuition
• Course notebook
• Letter of completion
Instructors
Richard Bender
BenderRBT
Gary Mogyorodi
Software Testing Services

Questions?

Get in Touch Ways To Save

On-Site Training

Let us bring the training directly to you! Choose from over 60 courses.

View all on-site courses

Combine World-Class Training and

Certification with a Conference

Maximize Your Learning Potential

Agile Dev Conference logo

Better Software Conference logo

Devops Conference logo

STAR Conference logo

Never Miss a Thing.

Get special offers and program announcements in your inbox