If a system is a solution, requirements state the problem. Since a solution to the wrong problem is useless, stating the problem is as important as building the solution. Hence the centrality of requirements engineering — also known as business analysis — in information technology, especially in the future era of massive use of LLMs, where prompting engineering will be a required skill. Good requirements are among the most treasurable assets of a project. Bad requirements hamper it at best and doom it at worst. Nevertheless, in today’s curriculum, requirements engineering is often perceived by students as boring and superficial. This tutorial aims to combine (i) an organised and systematic approach towards writing requirements so that they support rather than hinder the projects, and (ii) a teaching framework that illustrates the importance of benefiting, also at that level, from versioning and management tools such as Git repositories. It will provide the attendees with concrete and immediately applicable guidance, both for practitioners and for teachers.