Advertisement

Manage Software Requirements Specification Using Web Analytics Data

  • Jorge Esparteiro Garcia
  • Ana C. R. Paiva
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 746)

Abstract

In the context of SaaS (Software as a Service) where software has to be up and running 7 days a week and 24 h a day, keeping the requirements specification up to date can be difficult. Managing requirements in this context have additional challenges that need to be taken into account, for instance, re-prioritize requirements continuously and identify/update new dependencies among them. We claim that extracting and analyzing the usage of the SaaS can help to maintain requirements updated and contribute to improve the overall quality of the services provided. This paper presents REQAnalytics, a recommendation system that collects the information about the usage of a SaaS, analyses it and generates recommendations more readable than reports generated by web analytic tools. The overall approach has been applied on several case studies with promising results.

Notes

Acknowledgments

This work is financed by the ERDF – European Regional Development Fund through the Operational Programme for Competitiveness and Internationalisation - COMPETE 2020 Programme within project «POCI-01-0145-FEDER-006961», and by National Funds through the Portuguese funding agency, FCT - Fundação para a Ciência e a Tecnologia as part of project «UID/EEA/50014/2013».

References

  1. 1.
    Akerkar, R., Badica, C., Burdescu, D.D.: Desiderata for research in web intelligence, mining and semantics. In: Proceedings of the 2nd International Conference on Web Intelligence, Mining and Semantics - WIMS 2012, p. 1. ACM Press, New York (2012). http://dl.acm.org/citation.cfm?id=2254129.2254131
  2. 2.
    Arnold, R.S.: Software Change Impact Analysis. IEEE Computer Society Press, Los Alamitos (1996)Google Scholar
  3. 3.
    Garcia, J.E., Paiva, A.C.R.: An automated approach for requirements specification maintenance, pp. 827–833. Springer International Publishing, Cham (2016).  https://doi.org/10.1007/978-3-319-31232-3_78CrossRefGoogle Scholar
  4. 4.
    Garcia, J., Paiva, A.: Maintaining requirements using web usage data. Procedia Comput. Sci. 100, 626–633 (2016). Varajao, J., Cruzcunha, M., Martinho, R., Rijo, R., Bjornandersen, N., Turner, R., Alves, D. (eds.) International Conference on Enterprise Information Systems, Centeris 2016CrossRefGoogle Scholar
  5. 5.
    Garcia, J.E., Paiva, A.C.R.: A requirements-to-implementation mapping tool for requirements traceability. J. Softw. 11(2), 193–200 (2016)CrossRefGoogle Scholar
  6. 6.
    Garcia, J.E., Paiva, A.C.R.: REQAnalytics: a recommender system for requirements maintenance. Int. J. Softw. Eng. Appl. 10(1), 129–140 (2016)Google Scholar
  7. 7.
    Khatoon, A., Motla, Y.H., Azeem, M., Naz, H., Nazir, S.: Requirement change management for global software development using ontology. In: 2013 IEEE 9th International Conference on Emerging Technologies (ICET), pp. 1–6. IEEE, December 2013. http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnumber=6743519
  8. 8.
    Lemos, J., Alves, C., Duboc, L., Rodrigues, G.N.: A systematic mapping study on creativity in requirements engineering. In: Proceedings of the 27th Annual ACM Symposium on Applied Computing - SAC 2012, p. 1083. ACM Press, New York, March 2012. http://dl.acm.org/citation.cfm?id=2245276.2231945
  9. 9.
    Maalej, W., Thurimella, A.K. (eds.): Managing Requirements Knowledge. Springer, Heidelberg (2013).  https://doi.org/10.1007/978-3-642-34419-0Google Scholar
  10. 10.
    Mohebzada, J.G., Ruhe, G., Eberlein, A.: Systematic mapping of recommendation systems for requirements engineering, pp. 200–209, June 2012. http://dl.acm.org/citation.cfm?id=2664360.2664388
  11. 11.
    Paiva, A.C.R., Faria, J.C.P., Tillmann, N., Vidal, R.A.M.: A model-to-implementation mapping tool for automated model-based GUI testing. In: Lau, K.-K., Banach, R. (eds.) Proceedings of the 7th International Conference on Formal Methods and Software Engineering, ICFEM 2005. Lecture Notes in Computer Science, vol. 3785, pp. 450–464. Springer, Heidelberg (2005). http://dl.acm.org/citation.cfm?id=2099878.2099918CrossRefGoogle Scholar
  12. 12.
    Pazzani, M.J., Billsus, D.: Content-based recommendation systems, pp. 325–341, January 2007. http://dl.acm.org/citation.cfm?id=1768197.1768209
  13. 13.
    Robillard, M., Walker, R., Zimmermann, T.: Recommendation systems for software engineering. IEEE Softw. 27(4), 80–86 (2010). http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnumber=5235134CrossRefGoogle Scholar
  14. 14.
    Standish Group: CHAOS Report Group, pp. 11–13 (1995). http://www.standishgroup.com
  15. 15.
    Wiegers, K.E.: Automating requirements management. Softw. Dev. 7, 1–5 (1999)Google Scholar

Copyright information

© Springer International Publishing AG, part of Springer Nature 2018

Authors and Affiliations

  1. 1.INESC TECPortoPortugal
  2. 2.Faculty of EngineeringUniversity of PortoPortoPortugal
  3. 3.Polytechnic Institute of Viana do CasteloViana do CasteloPortugal

Personalised recommendations