This video describes how we structure the requirements documents in the mechatronics research group, and in what part we use the EARS syntax. On the go we briefly explain the way we describe Use Scenarios, and how we make our functional architiecture. Enough content for five more videos!
Any content presented in this video is the way how we in our group decided to formulate and structure requirements; using Planguage for User Requirements, discriminating between functional requirements (no implementations) and technical requirements (limiting the solution space), and giving each requirement an identifier and a rationale. This way of work may or may not work for any other company or research group. Our intention is to share what works for us, and hope that you will get some value out of it!


If you'd like to know more about EARS, please see our video about the EARS syntax: https://video.saxion.nl/id/1_uz3qtyie
For Planguage *and* EARS, see this presentation from John Terzakis:  https://www.iaria.org/conferences2013/filesICCGI13/ICCGI_2013_Tutorial_Terzakis.pdf