Agile Development Conference & Better Software Conference West 2012: EARS: The Easy Approach to Requirements Syntax
One key to specifying effective functional requirements is minimizing misinterpretation and ambiguity. By employing a consistent syntax in your requirements, you can improve readability and help ensure that everyone on the team understands exactly what to develop. John Terzakis provides examples of typical requirements and explains how to improve them using the Easy Approach to Requirements Syntax (EARS). EARS provides a simple yet powerful method of capturing the nuances of functional requirements. John explains that you need to identify two distinct types of requirements. Ubiquitous requirements state a fundamental property of the software that always occurs; non-ubiquitous requirements depend on the occurrence of an event, error condition, state, or option. Learn and practice identifying the correct requirements type and restating those requirements with the corresponding syntax. Join John to find out what’s wrong with the requirements statement-“The software shall warn of low battery”-and how to fix it.
Recommended Web Seminars
|The Testing Practices Fueling High-Performing Software Teams
|Building Confidence in Your Automation
|Leveraging Open Source Tools for DevSecOps
|Five Reasons Why Agile Isn't Working
|Building a Stellar Team