EARS — Easy Approach to Requirements Syntax
Defining your system.
Read through a slide desk from Intel about the Easy Approach to Requirements
Syntax (EARS)
After reading about EARS, this EARS quick reference sheet may be a useful summary.
QRA: 21 Tips for Writing Exceptionally Clear Requirements also includes a short summary of EARS as Tip #11 on pdf page 7.
Meet with your group to clarify and refine your problem or need description. Remember that, at this point, you are focusing on “defining success” by describing the behavior of a good solution instead of describing how it works.
Open and make a copy of this Google Doc, give edit access to your team members, and comment access to Prof. White (dan.white@valpo.edu).
Write a three-minute story: "A day in the life of …". This is a short description of your project from a User’s point of view. What is the situation they are in where they would engage with your solution? What problem is the User experiencing and how do they interact with your project to address this problem.
Create a minimum of 4 bullet-points that describe the major objectives of your project. These serve as a starting framework for creating more detailed requirement statements. Examples:
The system detects and then notifies a user when their load of clothes in the washing machine is ready for drying.
The system reads a set of assigned homeworks and determines a proposed schedule for completing the work.
Swap project description and requirements lists between a pair of groups.
Evaluation sheet
Our World in Data https://ourworldindata.org/
NAE Grand Challenges for Engineering http://www.engineeringchallenges.org/challenges.aspx
UN Sustainable Development Goals https://sustainabledevelopment.un.org/sdgs