EARS

A requirements-writing technique that expresses natural-language requirements in five fixed sentence patterns, developed at Rolls-Royce.

1 articleLast mentioned

EARS (Easy Approach to Requirements Syntax) is a technique for writing natural-language requirements using a small set of fixed sentence patterns. It was developed by Alistair Mavin and colleagues at Rolls-Royce to improve requirements for aircraft engine control systems and was published in 2009.

EARS classifies requirements into five types: ubiquitous, event-driven (WHEN), state-driven (WHILE), unwanted behaviour (IF-THEN), and optional feature (WHERE), each written with its keyword and the word SHALL. The aim is to reduce ambiguity and omissions and produce testable requirements. It is also used in spec-driven development as a format for passing requirements to AI coding agents.

This entry is based on AIPOST articles and widely known facts. If something is wrong, please send us a correction request.

Articles covering this entry

  • Levi Strauss Cuts App Delivery From 9 Months to 2.5 With GitHub Copilot AgentsAI in Practice ·

    Requirements are written in EARS (Easy Approach to Requirements Syntax), a structured format for unambiguous specifications, and agents are instructed to stop a…

    Read article

Found a mistake or missing an entry?

Wiki entries are based on AIPOST articles and widely known facts. If an entry is wrong, send us a correction request and we will check and fix it. Names from new articles are added to the wiki after the article is published.