# Easy Approach to Requirements Syntax and the segue to Behavior Driven Development

DevFeed: [Easy Approach to Requirements Syntax and the segue to Behavior Driven Development](<https://devfeed.tech/articles/easy-approach-to-requirements-syntax-and-the-segue-to-behavior-driven-development-20778.md>)

Original publisher: [Read original article](<https://conductofcode.io/post/easy-approach-to-requirements-syntax-and-the-segue-to-behavior-driven-development/>)

Author: {"twitter"=\>"hlaueriksson"}

Published: 2017-07-31T20:00:00Z

Content type: article

Language: en

Sources: [Henrik Lau Eriksson](<https://devfeed.tech/sources/henrik-lau-eriksson.md>)

Topics: [Requirements](<https://devfeed.tech/topics/requirements.md>), [Behavior-driven development](<https://devfeed.tech/topics/bdd.md>), [Specifications](<https://devfeed.tech/topics/specifications.md>), [User Stories](<https://devfeed.tech/topics/user-stories.md>)

Tags: [bdd](<https://devfeed.tech/tags/bdd.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [event](<https://devfeed.tech/tags/event.md>), [feature](<https://devfeed.tech/tags/feature.md>), [features](<https://devfeed.tech/tags/features.md>), [format](<https://devfeed.tech/tags/format.md>), [precision](<https://devfeed.tech/tags/precision.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [simple](<https://devfeed.tech/tags/simple.md>), [specflow](<https://devfeed.tech/tags/specflow.md>), [specifications](<https://devfeed.tech/tags/specifications.md>), [state](<https://devfeed.tech/tags/state.md>), [test](<https://devfeed.tech/tags/test.md>), [user-stories](<https://devfeed.tech/tags/user-stories.md>)

## AI overview

The article introduces Easy Approach to Requirements Syntax (EARS) as a structured way to write requirements and examines how its templates may help translate user stories and acceptance criteria into Behavior-Driven Development tests. It describes five requirement types and the problems EARS aims to reduce, including ambiguity, vagueness, complexity, omission, duplication, wordiness, inappropriate implementation detail, and untestability.

## Source excerpt

I was attending a conference six months ago and listened to a talk about quality. During the talk, I was introduced to EARS -- Easy Approach to Requirements Syntax. This way of writing requirements struck a chord with me, given my prior experience reading and writing requirement specifications.