A REQUIREMENTS ENGINEERING PROCESS MODEL FOR DISTRIBUTED SOFTWARE DEVELOPMENT - Lessons Learned

Leandro Teixeira Lopes, Jorge Luis Nicolas Audy

2008

Abstract

In the growing market of global software development (GSD), requirements engineering emerges as a critical process impacted by distribution. The need of a process to address the difficulties caused by team dispersion in requirements engineering is recognized. The objective of this paper is to present lessons learned from a case study conducted to evaluate a requirements engineering process model for distributed software development. Empirical results were obtained in a multinational organization that develops software with teams distributed in a global setting. The main contribution of this paper is providing an insight in the use of a requirements engineering process model for GSD, as well as, new information on current needs for changes or revision in traditional requirements engineering models.

References

  1. The Standish Group International (1995). Chaos Report. [Online], Available: http://www.standishgroup.com/.
  2. Herbsleb, J.; Moitra, D. Global Software Development. IEEE Software. 2001.
  3. Karolak, D. Global Software Development - Managing Virtual Teams and Environments. IEEE Computer Society. Los Alamitos, EUA. 1998. 159p.
  4. Thayer, R.; Dorfman, M. System and Software Requirements Engineering - Second Edition. IEEE Computer Society Press Tutorial. 2000. 528p.
  5. Zowghi, D. “Does Global Software Development Need a Different Requirements Engineering Process?” Proceedings of International Workshop on Global Software Development (ICSE 2002). 2002.
  6. Damian, D.; Zowghi, D. “An insight into the interplay between culture, conflict and distance in globally distributed requirements negotiations”. Proceedings of the 36th Hawaii International Conference on Systems Sciences (HICSS'03). IEEE. 2003.
  7. Lloyd, J.; Rosson, M..; Arthur, J.. Effectiveness of Elicitation Techniques in Distributed Requirements Engineering. Proceedings of the IEEE Joint International Conference on Requirements Engineering (RE'02). IEEE. 2002. 8p.
  8. Yin, R. K, Case study research: design and methods, Sage, 1994.
  9. Lopes, L.; Prikladnicki, R.; Majdenbaum, A.; Audy, J. “Distributed Requirement Specification: Minimizing the effect of geographic dispersion”. Proceedings of the 6th International Conference on Enterprise Information Systems, Porto, Portugal, 2004.
  10. Leite, J.; Leonardi, M. “Business Rules as Organizational Policies”. Proceedings of the Ninth International Workshop on Software Specification and design. IEEE Computer Society. 1998.
  11. Armour, F.; Miller, G. Advanced Use Case Modeling. Addison Wesley. 2001
  12. Goguen, J.. “Formality and Informality in Requirements Engineering”. Proceedings of the 2nd International Conference on Requirements Engineering (ICRE 7896). IEEE. 1996.
  13. Siddiqi, J.; Shekaran, M. Requirements Engineering: the emerging wisdom. IEEE Software. 1996.
  14. Damian, D. et alli. “An industrial experience in process improvement: An early assessment at the Australian Center for Unisys Software”. Proceedings of the 2002 International Symposium on Empirical Software Engineering (ISESE'02). IEEE. 2002.
  15. Rational Software. The principles behind good requirements. Webinar. [Online] http:// www.rational.com/September 2003.
  16. Kamsties, E. 2001. Surfacing Ambiguity in Natural Language Requirements. PhD Thesis. FraunhoferInstitue für Experimentelles Software Engineering. 2001.
  17. Al-Rawas, A.; Easterbrook, S. Communication problem in requirements engineering: A field study. Proceedings of the Westminster Conference on Professional Awareness in Software Engineering, 1996, London.
  18. Mahemoff, M. J.; Johnston, L. Software Internationalisation: Implications for Requirements Engineering. Proceedings of the Australian Workshop on Requirements Engineering, 1998, Geelong, Australia. p. 83-90.
Download


Paper Citation


in Harvard Style

Teixeira Lopes L. and Luis Nicolas Audy J. (2008). A REQUIREMENTS ENGINEERING PROCESS MODEL FOR DISTRIBUTED SOFTWARE DEVELOPMENT - Lessons Learned . In Proceedings of the Tenth International Conference on Enterprise Information Systems - Volume 6: ICEIS, ISBN 978-989-8111-38-8, pages 117-122. DOI: 10.5220/0001682901170122


in Bibtex Style

@conference{iceis08,
author={Leandro Teixeira Lopes and Jorge Luis Nicolas Audy},
title={A REQUIREMENTS ENGINEERING PROCESS MODEL FOR DISTRIBUTED SOFTWARE DEVELOPMENT - Lessons Learned},
booktitle={Proceedings of the Tenth International Conference on Enterprise Information Systems - Volume 6: ICEIS,},
year={2008},
pages={117-122},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0001682901170122},
isbn={978-989-8111-38-8},
}


in EndNote Style

TY - CONF
JO - Proceedings of the Tenth International Conference on Enterprise Information Systems - Volume 6: ICEIS,
TI - A REQUIREMENTS ENGINEERING PROCESS MODEL FOR DISTRIBUTED SOFTWARE DEVELOPMENT - Lessons Learned
SN - 978-989-8111-38-8
AU - Teixeira Lopes L.
AU - Luis Nicolas Audy J.
PY - 2008
SP - 117
EP - 122
DO - 10.5220/0001682901170122