Automatic Generation of a Requirements Graph from the Application code
Abstract
The software requirements change significantly during the software process. These changes may result in high cost, while the software process evolves, due the complexity in maintaining the traceability among requirements and because of the impact caused by changes in these requirements. This paper proposes an automatic generation of a requirements graph, by mapping the dependency graph of modules of an application and the requirements associated with them. In this way, it is possible to use the relationship among modules in order to maintain the equirements’ traceability. This allows the assessment of the impact that a change in one requirement may cause in others. A case study with 34 modules and 24 requirements is presented to illustrate the proposed technique.
Keywords:
Automatic Generation, Requirements Graph, Application Code
References
Arnold, K., Gosling, J., and Holmes, D. (2005). Java(TM) Programming Language, The (4th Edition). Addison-Wesley Professional.
Asuncion, H. U., Asuncion, A. U., and Taylor, R. N. (2010). Software traceability with topic modeling. In ICSE ’10: Proceedings of the 32nd ACM/IEEE International Con ference on Software Engineering, pages 95–104, New York, NY, USA. ACM.
Charette, R. (2005). Why software fails [software failure]. Spectrum, IEEE, 42(9):42 –49.
Cheng, B. H. C. and Atlee, J. M. (2007). Research directions in requirements engineering. In FOSE ’07: 2007 Future of Software Engineering, pages 285–303, Washington, DC, USA. IEEE Computer Society.
Cleland-Huang, J., Hayes, J. H., and Domel, J. M. (2009). Model-based traceability. In TEFSE ’09: Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering, pages 6–10, Washington, DC, USA. IEEE Computer Society.
Cleland-Huang, J., Settimi, R., BenKhadra, O., Berezhanskaya, E., and Christina, S. (2005). Goal-centric traceability for managing non-functional requirements. In ICSE ’05: Proceedings of the 27th international conference on Software engineering, pages 362–371, New York, NY, USA. ACM.
Cleland-Huang, J., Zemont, G., and Lukasik, W. (2004). A heterogeneous solution for improving the return on investment of requirements traceability. In RE ’04: Proceedings of the Requirements Engineering Conference, 12th IEEE International, pages 230–239, Washington, DC, USA. IEEE Computer Society.
Egyed, A. (2003). A scenario-driven approach to trace dependency analysis. IEEE Trans. Softw. Eng., 29(2):116–132.
Gotel, O. and Finkelstein, C. (1994). An analysis of the requirements traceability problem. In Requirements Engineering, 1994., Proceedings of the First International Conference on, pages 94 –101.
Hayes, J. H., Dekhtyar, A., and Osborne, J. (2003). Improving requirements tracing via information retrieval. In RE ’03: Proceedings of the 11th IEEE International Conference on Requirements Engineering, page 138, Washington, DC, USA. IEEE Computer Society.
IBM (2003). Developing pet store using rup and xde. http://www.ibm.com/developerworks/rational/library/1072.html.
IBM (2010). Ibm rational requisitepro software. http://www-01.ibm.com/software/awdtools/reqpro/.
Konrad, S. and Gall, M. (2008). Requirements engineering in the development of large scale systems. In International Requirements Engineering, 2008. RE ’08. 16th IEEE, pages 217 –222.
Nuseibeh, B. and Easterbrook, S. (2000). Requirements engineering: a roadmap. In ICSE’00: Proceedings of the Conference on The Future of Software Engineering, pages 35–46, New York, NY, USA. ACM.
Oracle (2010). Java ee 6 at a glance. http://www.oracle.com/technetwork/java/javaee/overview/index.html.
Pressman, R. S. (2006). Engenharia de Software. MgGraw-Hill, São Paulo, 6 edition.
Ramesh, B. and Jarke, M. (2001). Toward reference models for requirements traceability. IEEE Trans. Softw. Eng., 27(1):58–93.
Sommerville, I. (2007). Engenharia de Software. Pearson Addison-Wesley, São Paulo, 8 edition.
Asuncion, H. U., Asuncion, A. U., and Taylor, R. N. (2010). Software traceability with topic modeling. In ICSE ’10: Proceedings of the 32nd ACM/IEEE International Con ference on Software Engineering, pages 95–104, New York, NY, USA. ACM.
Charette, R. (2005). Why software fails [software failure]. Spectrum, IEEE, 42(9):42 –49.
Cheng, B. H. C. and Atlee, J. M. (2007). Research directions in requirements engineering. In FOSE ’07: 2007 Future of Software Engineering, pages 285–303, Washington, DC, USA. IEEE Computer Society.
Cleland-Huang, J., Hayes, J. H., and Domel, J. M. (2009). Model-based traceability. In TEFSE ’09: Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering, pages 6–10, Washington, DC, USA. IEEE Computer Society.
Cleland-Huang, J., Settimi, R., BenKhadra, O., Berezhanskaya, E., and Christina, S. (2005). Goal-centric traceability for managing non-functional requirements. In ICSE ’05: Proceedings of the 27th international conference on Software engineering, pages 362–371, New York, NY, USA. ACM.
Cleland-Huang, J., Zemont, G., and Lukasik, W. (2004). A heterogeneous solution for improving the return on investment of requirements traceability. In RE ’04: Proceedings of the Requirements Engineering Conference, 12th IEEE International, pages 230–239, Washington, DC, USA. IEEE Computer Society.
Egyed, A. (2003). A scenario-driven approach to trace dependency analysis. IEEE Trans. Softw. Eng., 29(2):116–132.
Gotel, O. and Finkelstein, C. (1994). An analysis of the requirements traceability problem. In Requirements Engineering, 1994., Proceedings of the First International Conference on, pages 94 –101.
Hayes, J. H., Dekhtyar, A., and Osborne, J. (2003). Improving requirements tracing via information retrieval. In RE ’03: Proceedings of the 11th IEEE International Conference on Requirements Engineering, page 138, Washington, DC, USA. IEEE Computer Society.
IBM (2003). Developing pet store using rup and xde. http://www.ibm.com/developerworks/rational/library/1072.html.
IBM (2010). Ibm rational requisitepro software. http://www-01.ibm.com/software/awdtools/reqpro/.
Konrad, S. and Gall, M. (2008). Requirements engineering in the development of large scale systems. In International Requirements Engineering, 2008. RE ’08. 16th IEEE, pages 217 –222.
Nuseibeh, B. and Easterbrook, S. (2000). Requirements engineering: a roadmap. In ICSE’00: Proceedings of the Conference on The Future of Software Engineering, pages 35–46, New York, NY, USA. ACM.
Oracle (2010). Java ee 6 at a glance. http://www.oracle.com/technetwork/java/javaee/overview/index.html.
Pressman, R. S. (2006). Engenharia de Software. MgGraw-Hill, São Paulo, 6 edition.
Ramesh, B. and Jarke, M. (2001). Toward reference models for requirements traceability. IEEE Trans. Softw. Eng., 27(1):58–93.
Sommerville, I. (2007). Engenharia de Software. Pearson Addison-Wesley, São Paulo, 8 edition.
Published
2011-06-06
How to Cite
VIEIRA, Marcelo M.; TIRELO, Fabio; MARQUES NETO, Humberto T..
Automatic Generation of a Requirements Graph from the Application code. In: BRAZILIAN SOFTWARE QUALITY SYMPOSIUM (SBQS), 10. , 2011, Curitiba.
Anais [...].
Porto Alegre: Sociedade Brasileira de Computação,
2011
.
p. 295-309.
DOI: https://doi.org/10.5753/sbqs.2011.15402.
