Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
An Empirical Study of Speed and Communication in Globally Distributed Software Development
IEEE Transactions on Software Engineering
Building Collaboration into IDEs
Queue - Distributed Development
Using Wikis in Software Development
IEEE Software
Identifying Nocuous Ambiguities in Natural Language Requirements
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Requirements Engineering
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
An Empirical Investigation on Text-Based Communication in Distributed Requirements Workshops
ICGSE '07 Proceedings of the International Conference on Global Software Engineering
Google this!: using Google apps for collaboration and productivity
Proceedings of the 37th annual ACM SIGUCCS fall conference: communication and collaboration
Using the Cloud to Facilitate Global Software Development Challenges
ICGSE-W '11 Proceedings of the 2011 IEEE Sixth International Conference on Global Software Engineering Workshop
Tools used in Global Software Engineering: A systematic mapping review
Information and Software Technology
A Process Framework for Global Software Engineering Teams
Information and Software Technology
Empirical Software Engineering
Hi-index | 0.00 |
Globally distributed software development teams face problems with software development life cycle phases, as the distributed nature of each of these phases make it even more challenging to communicate between the stakeholders. Global distance can give rise to incomplete requirements handovers which make the situation more difficult. It is important to address this issue as the end product is likely to deliver less business value when such problems arise. In this research, we propose a process to facilitate non-verbal communication among globally distributed requirements engineering teams. The focus of this research is the situation that occurs after requirements are handed to another site. Our proposed process endeavors to ensure that incomplete and conflicting requirements are identified and mitigated.