Вы находитесь на странице: 1из 1
EARS quick reference sheet E asy A pproach to R equirements S yntax Sentence types

EARS quick reference sheet

Easy Approach to Requirements Syntax

Sentence types

Ubiquitous

•The <system name> shall <system response> •The kitchen system shall have an input hatch.
•The <system name> shall <system response>
•The kitchen system shall have an input hatch.

Event-driven

•When <optional preconditions> <trigger>, the <system> shall <system response> •When
•When <optional preconditions> <trigger>, the <system> shall <system response>
•When the chef inserts a potato to the input hatch, the kitchen system shall peel the potato.

State-driven

•While <in a state>, the <system> shall <system response> •While the kitchen system is in
•While <in a state>, the <system> shall <system response>
•While the kitchen system is in maintenance mode, the kitchen system shall reject all input.

Unwanted

behavior

•If <optional preconditions> <trigger>, then the <system> shall <system response> •If
•If <optional preconditions> <trigger>, then the <system> shall <system response>
•If a spoon is inserted to the input hatch, then the kitchen system shall eject the spoon.

Optional

•Where <feature>, the <system> shall <system response> •Where the kitchen system has a food
•Where <feature>, the <system> shall <system response>
•Where the kitchen system has a food freshness sensor, the kitchen system shall detect rotten foodstuffs.

Steps to take in applying EARS

Identify whether you are working with a requirement, or something else (e.g. note or example)

Iterate as required

or something else (e.g. note or example) Iterate as required Identify compound requirements , i.e. whether

Identify compound requirements, i.e. whether the requirement needs to be Identify compound requirements , split split

, i.e. whether the requirement needs to be split Review requirements if possible Identify the acting

Review requirements if possible requirements if possible

needs to be split Review requirements if possible Identify the acting system, person or process Analyse

Identify the acting system, person or processIdentify the

if possible Identify the acting system, person or process Analyse the translated requirements for ambiguity,

Analyse the translated requirements for Analyse ambiguity, conflict and repetition ambiguity, conflict and repetition

requirements for ambiguity, conflict and repetition Analyse the needed sentence type(s) • E.g. 2 states and

Analyse the needed sentence type(s) sentence type(s)

conflict and repetition Analyse the needed sentence type(s) • E.g. 2 states and 2 events usually

E.g. 2 states and 2 events usually produce 4 requirements

Identify possible missing requirements Identify possible

Some characteristics of a good requirement

Unambiguous •One interpretation
Unambiguous
•One
interpretation
Traceable •Has unique identifier
Traceable
•Has unique
identifier
Consistent •Doesn't conflict other requirements
Consistent
•Doesn't conflict
other
requirements
Verifiable •Possible to check system meets requirement
Verifiable
•Possible to check
system meets
requirement
Complete •Not lacking relevant information
Complete
•Not lacking
relevant
information