SaaS Usage Information for Requirements Maintenance

Ana Garcia, Ana C. R. Paiva

Abstract

The incorrect requirements elicitation, requirements changes and evolution during the project lifetime are the main causes pointed out for the failure of software projects. The requirements in the context of Software as a Service are in constant change and evolution which makes even more critical the attention given to Requirements Engineering (RE). The dynamic context evolution due to new stakeholders needs brings additional challenges to the RE such as the need to review the prioritization of requirements and manage their changes related to their baseline. It is important to apply methodologies and techniques for requirements change management to allow a flexible development of SaaS and to ensure their timely adaptation to change. However, the existing techniques and solutions can take a long time to be implemented so that they become ineffective. In this work, a new methodology to manage functional requirements is proposed. This new methodology is based on collecting and analysis of information about the usage of the service to extract pages visited, execution traces and functionalities more used. The analysis performed will allow review the existing requirements, propose recommendations based on quality concerns and improve service usability with the ultimate goal of increasing the software lifetime.

References

  1. Aasem, M. et al., 2010. Analysis and optimization of software requirements prioritization techniques.
  2. Ali, H. O., Rozan, M. Z. A. & Sharif, A. M., 2012. Identifying challenges of change impact analysis for software projects. 2012 International Conference on Innovation Management and Technology Research, pp.407-411. Available at: http://ieeexplore.ieee.org/ lpdocs/epic03/wrapper.htm?arnumber=6236428.
  3. Analytics, G.,Visited at May 2013. Google Analytics. Available at: http://www.google.com/intl/pt-PT_ALL/ analytics/index.html.
  4. Attarha, M. & Modiri, N., Focusing on the Importance and the Role of Requirement Engineering. , pp.181-184.
  5. Babar, M. I., Rarnzan, M. & Ghayyur, S. A. K., 2011. Challenges and Future Trends in Software Requirements Prioritization. , pp.319-324.
  6. Banerjee, A., 2011. Requirement Evolution Management: A Systematic Approach. 2011 IEEE Computer Society Annual Symposium on VLSI, pp.150-155. Available at: http://ieeexplore.ieee.org/lpdocs/epic03/wrapper. htm?arnumber=5992497 (Accessed September 5, 2013).
  7. Bbclone, Visited at May 2013. Bbclone. Available at: http://help.bbclone.de/index.php?n=Main.HomePage.
  8. Ben Charrada, E., Koziolek, A. & Glinz, M., 2012. Identifying outdated requirements based on source code changes. 2012 20th IEEE International Requirements Engineering Conference (RE), pp.61- 70. Available at: http://ieeexplore.ieee.org/lpdocs/ epic03/wrapper.htm?arnumber=6345840.
  9. Clickdensity, Visited at May 2013. Clickdensity Benefits. Available at: http://www.clickdensity.com/.
  10. Counter, S., Visited at May 2013. Stat Counter Features. Available at: http://statcounter.com/?PHPSESSID= 4a7ck7tttvei7ivkd7fidkkm63.
  11. Crazyegg, Visited at May 2013. Here Are The Features That Make Your Websites Convert More Visitors Into Revenue. Available at: http://www.crazyegg.com/ #what-you-get.
  12. Dominguez, J., 2009. Chaos report-2009 on it project failure. Available at: http://www.pmhut.com/thechaos-report-2009-on-it-project-failure.
  13. Firestats, Visited at 2013. Firestats. Available at: http://firestats.cc/.
  14. Gao, T., 2011. A Process Model of Software Evolution Requirement Based on Feedback. , pp.172-175.
  15. Greenwood, P. et al., 2011. Modelling adaptability and variability in requirements. 2011 IEEE 19th International Requirements Engineering Conference, pp.343-344. Available at: http://ieeexplore.ieee.org/ lpdocs/epic03/wrapper.htm?arnumber=6051667.
  16. Hayat, F. et al., 2010. A methodology to manage the changing requirements of a software project. 2010 International Conference on Computer Information Systems and Industrial Management Applications (CISIM), pp.319-322. Available at: http:// ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnum ber=5643642.
  17. Ibrahim, N., Kadir, W.M.N.W. & Deris, S., 2009. Propagating Requirement Change into Software High Level Designs towards Resilient Software Evolution. 2009 16th Asia-Pacific Software Engineering Conference, pp.347-354. Available at: http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm? arnumber=5358735 (Accessed July 2, 2013).
  18. Inverardi, P. & Mori, M., 2011. Requirements Models at Run-time to Support Consistent System Evolutions. , pp.1-8.
  19. iPerceptions, Visited at May 2013. iPerceptions. Available at: http://www.iperceptions.com/.
  20. Jawstats, Visited at May 2013. Jawstats. Available at: http://www.jawstats.com.
  21. Piwik, Visited at May 2013. Piwik Features. Available at: http://piwik.org/.
  22. Qureshi, N. a. & Perini, A., 2010a. Requirements Engineering for Adaptive Service Based Applications. 2010 18th IEEE International Requirements Engineering Conference, pp.108-111. Available at: http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm? arnumber=5636635 (Accessed March 3, 2013).
  23. Qureshi, N. a. & Perini, A., 2010b. Requirements Engineering for Adaptive Service Based Applications. 2010 18th IEEE International Requirements Engineering Conference, pp.108-111. Available at: http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm? arnumber=5636635 (Accessed July 2, 2013).
  24. Souza, V.E.S., Lapouchnian, A. & Mylopoulos, J., 2012. (Requirement) evolution requirements for adaptive systems. 2012 7th International Symposium on Software Engineering for Adaptive and Self-Managing Systems (SEAMS), pp.155-164. Available at: http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm? arnumber=6224402.
  25. Stat, W., Visited at May 2013. Web Stat. Available at: http://www.webstat.com/.
  26. Sun, X. & Li, B., 2011. Using Formal Concept Analysis to support change analysis. 2011 26th IEEE/ACM International Conference on Automated Software Engineering (ASE 2011), pp.641-645. Available at: http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm? arnumber=6100146.
  27. Tracewatch, Visited at May 2013. Tracewatch. Available at: http://www.tracewatch.com/.
  28. Wang, H. et al., 2010. Quantitative Analysis of Requirements Evolution across Multiple Versions of an Industrial Software Product. 2010 Asia Pacific Software Engineering Conference, pp.43-49. Available at: http://ieeexplore.ieee.org/lpdocs/ epic03/wrapper.htm?arnumber=5693179 (Accessed July 2, 2013).
  29. Woopra, Visited at May 2013. Woopra. Available at: http://www.woopra.com/.
Download


Paper Citation


in Harvard Style

Garcia A. and C. R. Paiva A. (2014). SaaS Usage Information for Requirements Maintenance . In Proceedings of the 16th International Conference on Enterprise Information Systems - Volume 2: ICEIS, ISBN 978-989-758-028-4, pages 323-330. DOI: 10.5220/0004898403230330


in Bibtex Style

@conference{iceis14,
author={Ana Garcia and Ana C. R. Paiva},
title={SaaS Usage Information for Requirements Maintenance},
booktitle={Proceedings of the 16th International Conference on Enterprise Information Systems - Volume 2: ICEIS,},
year={2014},
pages={323-330},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0004898403230330},
isbn={978-989-758-028-4},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 16th International Conference on Enterprise Information Systems - Volume 2: ICEIS,
TI - SaaS Usage Information for Requirements Maintenance
SN - 978-989-758-028-4
AU - Garcia A.
AU - C. R. Paiva A.
PY - 2014
SP - 323
EP - 330
DO - 10.5220/0004898403230330