Abstract
Requirements traceability is a requirements management activity used to identify relations between requirements and to enable the comprehension of its dependencies. In the agile development changes are normal and occur at any moment in the project, requirements are written in the format of user stories which have dependencies between them. These dependencies can be technical or related to the business being developed. Handling dependencies among requirements and impact analysis is a challenge due to the possibility of refactoring and maintenance caused by not analyzed changes. This paper aims to propose a metamodel that enables requirements traceability and impact analysis in agile methods. The proposed metamodel presents the following contributions: enable traceability analysis through the mapping of dependencies between user stories; (b) allow identification of dependencies between user stories and between tasks; (c) management of the evolution of requirements; (d) support on impact analysis of changes.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Ambler, S.: Agile Modeling: Effective Practices for Extreme Programming and the Unified Process. Wiley, New York (2002)
Breitman, K., Leite, J.C.S.P.: Managing user stories. In: International Workshop on Time-Constrained Requirements Engineering (2002)
Briand, L.C., Labiche, Y., O’Sullivan, L.: Impact analysis and change management of UML models. In: Proceedings of the International Conference on Software Maintenance. ICSM, 22–26 September 2003. IEEE Computer Society, Washington, DC (2003)
Cohn, M.: User Stories Applied: For Agile Software Development. Addison-Wesley Professional, Boston (2004)
Cohn, M.: Succeeding with Agile: Software Development Using Scrum. Pearson Education, London (2010)
Espinoza, A., Garbajosa, J.: A study to support agile methods more effectively through traceability. Innovations Syst. Softw. Eng. 7, 53–69 (2011)
Gaur, V., Soni, A.: A novel approach to explore inter agent dependencies from user requirements. Procedia Technol. 1, 412–419 (2012)
Gomez, A., Rueda, G., Alarcón, P.P.: A systematic and lightweight method to identify dependencies between user stories. In: Sillitti, A., Martin, A., Wang, X., Whitworth, E. (eds.) XP 2010. LNBIP, vol. 48, pp. 190–195. Springer, Heidelberg (2010). https://doi.org/10.1007/978-3-642-13054-0_17
Hoffmann, M., Kuhn, N., Weber, M.: Requirements for requirements management tools. In: Proceedings of the 12th IEEE International Requirements Engineering Conference, pp. 301–308 (2004)
Kannenberg, A., Saiedian, H.: Why software requirements traceability remains a challenge. CrossTalk J. Def. Softw. Eng. 22(5), 14–19 (2009)
Kassab, M., Ormandjieva, O., Daneva, M.: Traceability metamodel for change management of nonfunctional requirements. In: Proceedings of the 2008 Sixth International Conference on Software Engineering Research, Management and Applications. IEEE Computer Society, Washington, DC (2008)
Lang, M., Duggan, J.: A tool to support collaborative software requirements management. Requir. Eng. J. 6, 161–172 (2001)
Leffingwell, D.: Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Addison-Wesley Professional, Boston (2010)
Letelier, P.: A framework for requirements traceability in UML-based projects. In: Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering (TFFSE 2002) (2002)
Martakis, A., Daneva, M.: Handling requirements dependencies in agile projects: a focus group with agile software development practitioners. In: 2013 IEEE Seventh International Conference on Research Challenges in Information Science (RCIS). IEEE (2013)
Object Management Group: Unified Modeling Language Specification. UML 2.5 with Action Semantics, Final Adopted Specification (2015). www.omg.org
Pressman, R.S.: Software Engineering: A Practitioner’s Approach. Palgrave Macmillan, New York (2005)
Ramesh, B., Powers, T., Stubbs, C., Edwards, M.: Implementing requirements traceability: a case study. In: Proceedings of the Second IEEE International Symposium on Requirements Engineering. IEEE (1995)
Ramesh, B., Jarke, M.: Toward reference models for requirements traceability. IEEE Trans. Softw. Eng. 27, 58–93 (2001)
Sliger, M., Broderick, S.: The Software Project Manager’s Bridge to Agility. Addison-Wesley Professional, Boston (2008)
Rosenberg, D., Stephens, M.: Extreme Programming Refactored: The Case Against XP. Apress, Berkeley (2008)
Trkman, M., Mendling, J., Krisper, M.: Using business process models to better understand the dependencies among user stories. Inf. Softw. Technol. 71, 58–76 (2015)
Version One: 11th annual state of agile survey. Technical report, Version One (2017)
Rossberg, J.: Beginning Application Lifecycle Management. Apress, Berkeley (2014)
Sayão, M., Leite, J.C.S.P.: Rastreabilidade de requisitos. RITA 13.1 (2006)
Author information
Authors and Affiliations
Corresponding authors
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2018 Springer International Publishing AG
About this paper
Cite this paper
Carniel, C.A., Pegoraro, R.A. (2018). Metamodel for Requirements Traceability and Impact Analysis on Agile Methods. In: Santos, V., Pinto, G., Serra Seca Neto, A. (eds) Agile Methods. WBMA 2017. Communications in Computer and Information Science, vol 802. Springer, Cham. https://doi.org/10.1007/978-3-319-73673-0_9
Download citation
DOI: https://doi.org/10.1007/978-3-319-73673-0_9
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-73672-3
Online ISBN: 978-3-319-73673-0
eBook Packages: Computer ScienceComputer Science (R0)