Software development practices have changed over the last twenty years, with agile development more prevalent than traditional waterfall development. While the agile manifesto prefers working code over documentation, there is a need for models that can help communicate and document a high level understanding. Clear models are particularly important as software development teams are increasingly multi-disciplinary due to the expansion of application domains where software is essential. The increase in disciplines places greater demands on communication as less knowledge can be assumed. Both technical and non-technical team members are able -- and often expected -- to contribute to ongoing discussions and decisions about requirements.
In this paper, we present a case study on how Motivational Modelling (MM) can be used effectively to support the creation of better agile requirements artifacts by software engineering students at the University of Melbourne. As an outcome of our analysis in the presented case study, nine Consistency Principles (CP) were created to support the cross validation between motivational models, personas, and user stories in Requirements Engineering (RE).
All the details from this study (and analysis) will soon be available on SERP'21. Link will be posted here.
Let us know your thoughts about it. We'd love to hear from you.