The presented integrated meta-model has been reviewed and discussed by few
experts as we reported in Section 3 and its use was demonstrated by two illustrative
examples. The main subjects of the future work are therefore to test the integrated meta-
model in a real project, and thus also to investigate in which directions the artifact
should be improved; enlarge it to include even more detailed concepts, or enrich it with
the methods of use; or even extend it to support emerging approaches relying on new
requirements-related notions such as for capability-driven system development [22];
or, for example, by considering digital requirements sources in addition to human
customers / stakeholders.
Acknowledgment. We would like to express our gratitude to the experts mentioned in
Section 3 who dedicated their time for reviewing the meta-model artifacts throughout
their development.
References
1. Royce, W.W.: Managing the Development of Large Software Systems-Concepts and
Techniques. 1970. In: Proceedings of IEEE WESCON. pp. 1–9. TRW (1970).
2. Booch, G., Rumbaugh, J., Jacobson, I.: The unified modeling language user guide. Addison-
Wesley, Reading Mass (1998).
3. Inayat, I., Salim, S.S., Marczak, S., Daneva, M., Shamshirband, S.: A systematic literature
review on agile requirements engineering practices and challenges. Computers in Human
Behavior. 51, 915–929 (2015). https://doi.org/10.1016/j.chb.2014.10.046.
4. Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M.,
Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., others: Manifesto for agile software
development. (2001).
5. Zowghi, D., Coulin, C.: Requirements Elicitation: A Survey of Techniques, Approaches,
and Tools. In: Aurum, A. and Wohlin, C. (eds.) Engineering and Managing Software
Requirements. pp. 19–46. Springer-Verlag, Berlin/Heidelberg (2005).
https://doi.org/10.1007/3-540-28244-0_2.
6. Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley, Reading,
MA (2000).
7. Schwaber, K.: SCRUM Development Process. In: Sutherland, J., Casanave, C., Miller, J.,
Patel, P., and Hollowell, G. (eds.) Business Object Design and Implementation. pp. 117–
134. Springer London, London (1997). https://doi.org/10.1007/978-1-4471-0947-1_11.
8. Pohl, K.: Requirements engineering: fundamentals, principles, and techniques. Springer,
Heidelberg
; New York (2010).
9. Leffingwell, D.: Agile Software Requirements: Lean Requirements Practices for Teams,
Programs, and the Enterprise. Addison-Wesley, Upper Saddle River, NJ (2011).
10. Ramesh, B., Cao, L., Baskerville, R.: Agile requirements engineering practices and
challenges: an empirical study: Agile RE practices and challenges. Information Systems
Journal. 20, 449–480 (2007). https://doi.org/10.1111/j.1365-2575.2007.00259.x.
11. Rubin, K.S.: Essential Scrum: a practical guide to the most popular agile process. Addison-
Wesley, Upper Saddle River, NJ (2012).
12. Muneer, S.U., Nadeem, M., Kasi, B.: Comparison of modern techniques for analyzing NFRs
in Agile: A systematic literature review. Journal of Software Engineering Practice. 3, 1–12
(2019).