Skip to main content
SQE Training logo
  • Join Our Mailing List
  • Email Us
  • 888.268.8770
  • About Us
  • By Topic
    • Agile Software Development
    • Configuration Management
    • Software Security
    • Software Requirements
    • Software Testing
    • Visual Studio
  • By Location
    • All
    • West
    • Midwest
    • Southeast
    • Northeast
    • Canada
  • Delivery Options
    • Public
    • Live Virtual
    • eLearning
    • On-Site
  • Certification
    • ISTQB Software Tester Certification
    • Agile Development Certification
    • PMI PDUs
    • IIBA CDUs
  • Consulting Services
    • Agile Development
      • Agile Process Improvement
      • Agile Software Development
      • Continuous Integration
      • Program & Project Management
      • Requirements Envisioning
    • Application Security
      • Application Security Assessments
      • Application Security Remediation
      • Application Security Training
      • Secure SDLC Improvement
    • Software Quality
      • Agile Software Testing
      • Independent Verification & Validation
      • QA Center of Excellence
      • Test Automation
      • Test Process Improvement
    • Our Consultants
  • Meet the Experts
  • Learners
  • Team Managers
  • Training Managers
Send by emailPrint This Page

Finding Ambiguities in Requirements

Techniques for Improving Requirements and Software
Public: $795.00
Live Virtual: $599.00
On-site: Contact us!
  • Public
  • Live Virtual
  • On-Site
  • Description/Outline
  • Location & Dates
  • Instructors
  • 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.

1-Day 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 Daily Schedule
Sign-In/Registration 7:30–8:30am
Morning Session 8:30am–12:00pm
Lunch 12:00–1:00pm
Afternoon Session 1:00–5:00pm
Times represent the typical daily schedule. Please confirm your schedule at registration.
 
Training Course Fee Includes
• Tuition
• Course notebook
• Continental breakfasts and refreshment breaks
• Lunches
• Letter of completion

 

Course Name Events Dates Location Venue
Finding Ambiguities in Requirements
RequirementWk
Sep 16-Sep 16, 2013 Boston VENUE Attend

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.

  • Description/Outline
  • Location & Dates
  • Instructors
  • 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.

Daily 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

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

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.
  • 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 class sizes as our instructor-led training. This provides you with the opportunity for personal interaction with the instructor.

 

Course Name Dates Location
Finding Ambiguities in Requirements Aug 13-Aug 14, 2013 Your desktop Attend

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.

  • Description/Outline
  • Location & Dates
  • Instructors
  • 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.

1-Day 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 Daily Schedule
Sign-In/Registration 7:30–8:30am
Morning Session 8:30am–12:00pm
Lunch 12:00–1:00pm
Afternoon Session 1:00–5:00pm
Times represent the typical daily schedule. Please confirm your schedule at registration.
 
Training Course Fee Includes
• Tuition
• Course notebook
• Continental breakfasts and refreshment breaks
• Lunches
• Letter of completion

 

Course Name Dates Location
Finding Ambiguities in Requirements Call to schedule Your location Contact

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.

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.

  • FAR
  • Software Requirements
  • Software Testing

  • SQE.com
  • Privacy Policy
  • About SQE

Copyright © 2012-2013 Software Quality Engineering, All rights reserved.