Planning, coordinating and controlling software engineering in distributed settings are far more complex than in one-site projects. First, the process of analysis and design needs to be planned and organized differently. Second, the methods used to discuss, share and document design and architecture ideas need to take into account the fact that project members involved in these tasks are spread over multiple sites and organisations and don't have contact to end-users. Third, development, integration and releasing a high quality product are far more challenging.
As a conclusion, we need concepts and tools to support the specific tasks and process requirements in distributed development projects. Experience shows that an appropriate tool chain increases efficiency and success of distributed projects. Aspects like process assistance, knowledge management or project tracking ask for appropriate tools.
Therefore, the workshop will walk through the methods and concepts that are available and the tool chains that are used in global software development projects. After last years' successful editions (cf. first and second workshop), this workshop will explicitly focus on tools and infrastructures for GSD projects.
One of the objectives of this workshop is to structure the major research topics and to define a research agenda for further work in the area of "end-to-end" tool support in distributed system development. Besides that, there will be a demo session with presentations and live demonstrations of tools that are specifically dedicated to support distributed development projects.
In summary, this 1-day workshop will include different aspects of tool selection and orchestration in a distributed software development context, e.g.:
- Administration and tracking of documents, concepts, code, etc.: What are the consequences for the process and the tools if (all or some of the) processes of requirements engineering, design, development etc. are distributed?
- Collaboration and communication in software engineering: How need teams to be organized and coordinated when they are spread over two or more sites? How can projects achieve efficient collaboration and alignment? What are the lessons learned on tools and infrastructure for collaboration in different project phases? Which different requirements and characteristics do the different project phases have regarding tool support?
- Process assistance and support: How does an adequate process for distributed development look like and how should it be supported by tools and techniques? What tools or tool chains are adequate to assist different project roles?
- Tool orchestration: How should projects select their tools? How different are tool chains for different industries? What are the project characteristics that influence tool decisions most heavily? How different are the optimal tool chains for different levels of education and experience?
- Economic aspects: What is Return on Investment in dedicated tools in distributed development? How big is the impact of an appropriate tool chain on the cost efficiency of distributed development?
- Project management: Which tools can help to plan, control and track a project? Are risk management or workflow management tools different to those used in on-site projects?
- Lessons learned from OSS: How comparable are industry projects and open source projects regarding modes and tools of cooperation? What can be learned from big open source initiatives that are successful in delivering high quality software?
- Lessons learned from distributed development: What are factors to make distributed projects successful in practice? What methods worked - what did not? Do agile processes have advantages is distributed settings?
Topics of the 1-day Workshop:
The following is a non-exhaustive list of relevant topics:
- Models, tools and technologies for handling dynamics and complexity in the early phases of dispersed collaboration
- Models and tools for unifying processes respecting requirements engineering, software development, and operations and maintenance in global contexts
- Comparability and comparison with tools used in open source projects
- Process model design for distributed engineering and "mirroring" of these processes in SE tools
- Models and processes to define and predict usability, reliability, performance, quality and adequacy of development tools
- Impacts of tools on the cost efficiency of distributed development
These topics will be discussed based on presentations by participants. Based on
these contributions, we will try to structure the problems and challenges and want
to discuss a "research agenda for RE in GSD".
The workshop targets practictioners as well as researchers interested or involved
with geographically or organizationally distributed software development.
Deadline for paper submission to the workshop organizers
Decision of acceptance to paper authors
Final version of accepted papers due, according to IEEE standards
July 13, 2009
Papers must be submitted electronically by email to the organizers in PDF format. Your paper must
conform to the IEEE proceedings publication format (8.5" x 11", Two-Column Format)
IEEE/CPS. Research papers must be no longer than 6 pages including all text, references, pictures and appendices. Position papers, industrial experience papers and tool presentations must be no longer than 4 pages including all text, screenshots, references and appendices. Submissions that exceed the page limit or do not comply with the proceedings format will be desk rejected without review.
Stefan Biffl, TU Wien
Manfred Broy, TU München
Vesna Mikulovic, Siemens AG Austria
Jürgen Münch, Fraunhofer IESE
Daniel Paulish, Siemens Corporate Research
Andreas Rausch, TU Clausthal
Ita Richardson, Lero, Universitiy of Limerick
Bernhard Schätz, TU München
Jos van Hillegersberg, University of Twente