Unconstrained natural language requirements can be vague, ambiguous, verbose, and confusing. In many cases, these requirements can lead to unexpected interpretations, erroneous implementations, costly scrap and rework, and – in the worst cases – disaster. The Easy Approach to Requirements Syntax – EARS, helps solve that problem by bringing just enough rigor to the process of writing requirements in natural language.

This clear and easy-to-digest guide kicks off the first part of our 3 part EARS series. The series is aimed at breaking down and showcasing the value of EARS  when authoring requirements in QVscribe. This guide, Part 1, shows readers how to write natural language requirements that are clear, concise, unambiguous, and testable. Furthermore, it provides an EARS quick reference sheet and demonstrates how to navigate the five fundamental EARS patterns and their corresponding QVscribe template:

  1. Ubiquitous
  2.  State-Driven
  3. Event-Driven
  4.  Optional Feature
  5.  Unwanted Behavior

Using the example of a garage door opener, readers learn the ins and outs of each EARS pattern and exactly when to use them. Each part of the pattern is defined, explained, and integrated into the example, leaving readers with a firm understanding of the pattern and the QVscribe template.