A Taxonomy and Visual Notation for Modeling Globally Distributed Requirements Engineering Projects

This paper presents a visual modeling notation for use in planning globally distributed requirements engineering projects. An underlying meta-model defines the elements of the modeling language, including site locations, stakeholder roles, communication flows, critical documents, and supporting tools and repositories. The modeling notation is motivated through the findings of eight in-depth interviews with requirements analysts who had worked on requirements elicitation, analysis, and specification tasks in globally distributed projects. We illustrate the modeling notation with examples drawn from telecommunications, video gaming, retail, and consulting projects. Based on a set of recurring problems and best practices identified in our interviews, the models are then analyzed, and specific recommendations are made to mitigate the identified risks.

[1]  Daniela E. Damian,et al.  Collaboration Patterns and the Impact of Distance on Awareness in Requirements-Centred Social Networks , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[2]  Jane Cleland-Huang,et al.  Requirements-Gathering Collaborative Networks in Distributed Software Projects , 2009, 2009 Collaboration and Intercultural Issues on Requirements: Communication, Understanding and Softskills.

[3]  James D. Herbsleb,et al.  Global Software Engineering: The Future of Socio-technical Coordination , 2007, Future of Software Engineering (FOSE '07).

[4]  Brian Berenbach,et al.  Impact of organizational structure on distributed requirements engineering processes: lessons learned , 2006, GSD '06.

[5]  Theodoros N. Arvanitis,et al.  Communication, Knowledge and Co-ordination Management in Globally Distributed Software Development: Informed by a scientific Software Engineering Case Study , 2009, 2009 Fourth IEEE International Conference on Global Software Engineering.

[6]  Daniela E. Damian,et al.  Stakeholders in Global Requirements Engineering: Lessons Learned from Practice , 2007, IEEE Software.

[7]  Daniel L. Moody,et al.  The “Physics” of Notations: Toward a Scientific Basis for Constructing Visual Notations in Software Engineering , 2009, IEEE Transactions on Software Engineering.

[8]  P. Gordon.  Numerical Cognition Without Words: Evidence from Amazonia , 2004, Science.

[9]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[10]  Philippe Kruchten,et al.  The Rational Unified Process Made Easy - A Practitioner's Guide to the RUP , 2003, Addison Wesley object technology series.

[11]  Kevin C. Desouza,et al.  Managing Knowledge in Global Software Development Efforts: Issues and Practices , 2006, IEEE Software.

[12]  Ian F. Alexander,et al.  Understanding project sociology by modeling stakeholders , 2004, IEEE Software.

[13]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[14]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[15]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[16]  Qing Li,et al.  Unified Modeling Language , 2009 .

[17]  Steve Howard,et al.  Methods & tools: the rich picture: a tool for reasoning about work context , 1998, INTR.

[18]  Mark T True,et al.  Software Requirements , 2005 .