• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations

Global software engineering: The future of socio-technical coordination (2007)

by J D Herbsleb
Venue:In FOSE, IEEE
Add To MetaCart

Tools

Sorted by:
Results 1 - 10 of 107
Next 10 →

Does distributed development affect software quality? an empirical case study of windows vista

by Christian Bird, Premkumar Devanbu, Harald Gall, Brendan Murphy - In ICSE ’09: Proceedings of the 2009 IEEE 31st International Conference on Software Engineering , 2009
"... It is widely believed that distributed software development is riskier and more challenging than collocated development. Prior literature on distributed development in software engineering and other fields discuss various challenges, including cultural barriers, expertise transfer difficulties, and ..."
Abstract - Cited by 57 (14 self) - Add to MetaCart
It is widely believed that distributed software development is riskier and more challenging than collocated development. Prior literature on distributed development in software engineering and other fields discuss various challenges, including cultural barriers, expertise transfer difficulties, and communication and coordination overhead. We evaluate this conventional belief by examining the overall development of Windows Vista and comparing the postrelease failures of components that were developed in a distributed fashion with those that were developed by collocated teams. We found a negligible difference in failures. This difference becomes even less significant when controlling for the number of developers working on a binary. We also examine component characteristics such as code churn, complexity, dependency information, and test code coverage and find very little difference between distributed and collocated components. Further, we examine the software process and phenomena that occurred during the Vista development cycle and present ways in which the development process utilized may be insensitive to geography by mitigating the difficulties introduced in prior work in this area. 1.
(Show Context)

Citation Context

... is an increasingly common strategic response to issues such as skill set availability, acquisitions, government restrictions, increased code size, cost and complexity, and other resource constraints =-=[5, 10]-=-. In this paper, we examine development that is globally distributed, but completely within Microsoft. This style of global development within a single company is to be contrasted with outsourcing whi...

Latent social structure in open source projects

by Christian Bird, David Pattison, Vladimir Filkov, Premkumar Devanbu - PROCEEDINGS OF THE 16TH ACM SIGSOFT INTERNATIONAL SYMPOSIUM ON FOUNDATIONS OF SOFTWARE ENGINEERING , 2008
"... Commercial software project managers design project organizational structure carefully, mindful of available skills, division of labour, geographical boundaries, etc. These organizational “cathedrals ” are to be contrasted with the “bazaarlike” nature of Open Source Software (OSS) Projects, which ha ..."
Abstract - Cited by 51 (8 self) - Add to MetaCart
Commercial software project managers design project organizational structure carefully, mindful of available skills, division of labour, geographical boundaries, etc. These organizational “cathedrals ” are to be contrasted with the “bazaarlike” nature of Open Source Software (OSS) Projects, which have no pre-designed organizational structure. Any structure that exists is dynamic, self-organizing, latent, and usually not explicitly stated. However, in large, complex, successful, OSS projects, we expect that sub-communities will form organically within the “bazaar ” of developer teams. Studying these sub-communities, and their behavior can shed light on how successful OSS projects self-organize. This phenomenon could even hold important lessons for how commercial software teams might be organized. Building on wellestablished techniques for detecting community structure in complex networks, we extract and evaluate latent subcommunities from the email social network of several projects: Apache HTTPD, Python, PostgresSQL, Perl, and Apache ANT. We then validate them with software development activity history. Our results show that subcommunities do indeed form within these projects. We find, in other words, that “chapels ” (if not cathedrals) spontaneously arise within the bazaar as OSS systems and the teams evolve. We also find that these subgroups manifest most strongly in technical discussions, and are significantly connected with collaboration behaviour. 1.
(Show Context)

Citation Context

...ated socio-technical issues [45, 33, 48, 63]. In fact, a recent invited talk at ICSE describes the importance of issues facing socio-technical coordination in a global environment (a key facet of OSS)=-=[32]-=-. 3. RELATED WORK Prior work related to this study can be divided into three categories: first, on social networks; second on the effect of organizational structure on effectiveness; and finally, on d...

Software design and architecture: The once and future focus of software engineering

by Richard N. Taylor - In FOSE ’07: 2007 Future of Software Engineering , 2007
"... The design of software has been a focus of software engineering research since the field’s beginning. This paper explores key aspects of this research focus and shows why design will remain a principal focus. The intrinsic elements of software design, both process and product, are discussed: concept ..."
Abstract - Cited by 22 (1 self) - Add to MetaCart
The design of software has been a focus of software engineering research since the field’s beginning. This paper explores key aspects of this research focus and shows why design will remain a principal focus. The intrinsic elements of software design, both process and product, are discussed: concept formation, use of experience, and means for representation, reasoning, and directing the design activity. Design is presented as being an activity engaged by a wide range of stakeholders, acting throughout most of a system’s lifecycle, making a set of key choices which constitute the application’s architecture. Directions for design research are outlined, including: (a) drawing lessons, inspiration, and techniques from design fields outside of computer science, (b) emphasizing the design of application “character ” (functionality and style) as well as the application’s structure, and (c) expanding the notion of software to encompass the design of additional kinds of intangible complex artifacts. 1.
(Show Context)

Citation Context

...ocess is recognized, advances in network communications can be brought to bear to improve their participation. Collaboration technologies in general offer significant potential for the design process =-=[39]-=-. Communication technologies are, relatively-speaking, free; designers should exploit that. Display technology offers another basis for improvement in design practice. Very high resolution, very large...

Virtual Open Conversation Spaces: Towards Improved Awareness in a GSE Setting

by Kevin Dullemond, Ben Van Gameren, Rini Van Solingen - in Proceedings of the IEEE 2010 International Conference on Global Software Engineering. IEEE Computer , 2010
"... Abstract—Conversations between colleagues in collaborative software engineering are important for coordinating work, sharing knowledge and creating knowledge. Overhearing con-versations of others is useful as well since this: (i) provides access to the information discussed in the conversations, (ii ..."
Abstract - Cited by 8 (7 self) - Add to MetaCart
Abstract—Conversations between colleagues in collaborative software engineering are important for coordinating work, sharing knowledge and creating knowledge. Overhearing con-versations of others is useful as well since this: (i) provides access to the information discussed in the conversations, (ii) offers the possibility of joining the conversations and (iii) provides insight in the communication structure of the project team. When working in a GSE setting, specialized tooling is required to be able to have conversations and to know what conversations others are having. In this paper we discuss how conversations support collaborative software engineering and how this can be supported by technology in a GSE environment. To do this, we introduce Communico: a virtual open conversation space which features: (i) initiating conversations by selecting people to converse with, (ii) sharing information regarding the involvement of project members in these conversations and (iii) having access to persistent conversations with an explicit status indicating whether they are ongoing. I.
(Show Context)

Citation Context

...with an explicit status indicating whether they are ongoing. I. INTRODUCTION Global Software Engineering (GSE) is becoming increasingly interesting due to the globalization of business [1], [2], [3], =-=[4]-=-, [5], [6]. In GSE the software development process is distributed between several geographically dispersed locations [7], [3], [8]. Advantages of GSE include: market-proximity [9], [10], [3], reducin...

A Relationship-Based Approach to Model Integration

by Marsha Chechik, Shiva Nejati, Mehrdad Sabetzadeh
"... A key problem in model-based development is integrating a collection of models into a single, larger, specification as a way to construct a functional system, to develop a unified understanding, or to enable automated reasoning about properties of the resulting system. In this article, we suggest th ..."
Abstract - Cited by 5 (1 self) - Add to MetaCart
A key problem in model-based development is integrating a collection of models into a single, larger, specification as a way to construct a functional system, to develop a unified understanding, or to enable automated reasoning about properties of the resulting system. In this article, we suggest that the choice of a particular model integration operator depends on the inter-model relationships that hold between individual models. Based on this observation, we distinguish three key integration operators studied in the literature – merge, composition and weaving – and describe each operator along with the notion of relationship that underlies it. We then focus on the merge activity and provide a detailed look at the factors that one must consider in defining a merge operator, particularly the way in which the relationships should be captured during merge. We illustrate these factors using two merge operators that we have developed in our earlier work for combining models that originate from distributed teams.
(Show Context)

Citation Context

...e believe that results of this article would provide a useful guide for the development of new model integration operators. Particularly, with the recent interest in Global Software Engineering (GSE) =-=[14]-=-, there is now an increasing demand for flexible integration techniques for consolidating models that are built by geographically distributed teams. We anticipate GSE to spur new research on model int...

Understanding Open Source Software Peer Review

by Peter C. Rigby, Peter C. Rigby - Review Processes, Parameters and Statistical Models, and Underlying Behaviours and Mechanisms. thechiselgroup.org/rigby-dissertation.pdf, Dissertation , 2011
"... This dissertation is available under the Creative Commons Attribution-ShareAlike License. ii ..."
Abstract - Cited by 5 (4 self) - Add to MetaCart
This dissertation is available under the Creative Commons Attribution-ShareAlike License. ii

GloSE-Lab: Teaching Global Software Engineering

by Constanze Deiters, Christoph Herrmann, Eric Knauss, Marco Kuhrmann, Andreas Rausch, Bernhard Rumpe, Kurt Schneider
"... Abstract—In practice, more and more software development projects are distributed, ranging from partly distributed teams to global projects with each stakeholder located differently. Teaching actual practice in software engineering at university needs a proper mixture of theory and practice. But set ..."
Abstract - Cited by 5 (1 self) - Add to MetaCart
Abstract—In practice, more and more software development projects are distributed, ranging from partly distributed teams to global projects with each stakeholder located differently. Teaching actual practice in software engineering at university needs a proper mixture of theory and practice. But setting up practical exercises for global software engineering is hard, because students have to cooperate across different locations and situations reflecting the teaching intentions have to be provoked explicitly. This paper presents the concepts behind our common teaching environment for global software engineering – the GloSE-Lab. It describes the experiences on setting up a distributed course and reports our teaching intentions based on each universities main focus: project management, requirements engineering & quality assurance, architecture, and implementation. Furthermore, we discuss our setup – a stage-gate process, where each location takes care of a different phase – and report occurred problems and how they supported or interfered with our teaching intentions. Keywords-global software engineering; teaching; GloSE-Lab I.
(Show Context)

Citation Context

...hitecture, typically stay in high-wage countries, e.g., USA or Germany. Although the understanding of Global Software Development has grown in the recent years, it is not yet a mature discipline [1], =-=[2]-=-, [3]. According to [4] 68% of GSDbased teaching/training experiences are presented as case studies, mainly presented by universities. An example for courses/lectures is the Global Studio Project [5]....

Culture in global software development - a weakness or strength

by Sadhana Deshpande, Ita Richardson, Sarah Beecham - in Global Software Engineering (ICGSE), 2010 5th IEEE International Conference on, Aug 2010
"... Abstract: Cultural diversity is assumed to be a fundamental issue in global software development. Research carried out to date has raised concerns over how to manage cultural differences in global software development. Our empirical research in India, a major outsourcing destination, has helped us i ..."
Abstract - Cited by 5 (1 self) - Add to MetaCart
Abstract: Cultural diversity is assumed to be a fundamental issue in global software development. Research carried out to date has raised concerns over how to manage cultural differences in global software development. Our empirical research in India, a major outsourcing destination, has helped us investigate this complex issue of global software development. A triangulated study based on a questionnaire, telephonic interviews and structured face-to-face interviews with 15 Project Managers and Senior Executives has revealed how they cope with the demands of cultural differences imposed by a geographically distributed environment. This research study brings forward various techniques initiated by these project managers to deal with cultural differences that exist within geographically distributed software development teams. We also discuss different strategies and make a case to explain how to build on and take advantage of cultural differences that exist in global software development. I.
(Show Context)

Citation Context

...many organisationsstoday and the popularity of this strategy continues tosincrease. Companies are endeavoring to gain and maintainseconomic advantage through numerous technical andscommercial factors =-=[1]-=-[2]. The revolution in availability ofsvarious communication tools and their accessibility with ansoption to utilize remotely located competent workforce hasshelped globalisation of software developme...

Offshore Insourcing: A Case Study on Software Quality Alignment

by Sebastian Barney, Claes Wohlin, Panagiota Chatzipetrou, Lefteris Angelis - Proc. 6th IEEE International Conference on Global Software Engineering , 2011
"... Abstract—Background: Software quality issues are com-monly reported when offshoring software development. Value-based software engineering addresses this by ensuring key stakeholders have a common understanding of quality. Aim: This work seeks to understand the levels of alignment between key stakeh ..."
Abstract - Cited by 5 (2 self) - Add to MetaCart
Abstract—Background: Software quality issues are com-monly reported when offshoring software development. Value-based software engineering addresses this by ensuring key stakeholders have a common understanding of quality. Aim: This work seeks to understand the levels of alignment between key stakeholders on aspects of software quality for two products developed as part of an offshore insourcing arrangement. The study further aims to explain the levels of alignment identified. Method: Representatives of key stakeholder groups for both products ranked aspects of software quality. The results were discussed with the groups to gain a deeper understanding. Results: Low levels of alignment were found between the groups studied. This is associated with insufficiently defined quality requirements, a culture that does not question man-agement and conflicting temporal reflections on the product’s quality. Conclusion: The work emphasizes the need for greater support to align success-critical stakeholder groups in their understanding of quality when offshoring software develop-ment. Keywords-software, quality, global software development I.
(Show Context)

Citation Context

...n, proximity to markets and making use of different competencies [2], but there are also many challenges. The most commonly cited challenges in GSD contexts concern communication [3] and coordination =-=[4]-=-, both essential elements in creating alignment between stakeholders [5]. There is a wide body of evidence showing that organisations that can create alignment through “convergent intentions, shared u...

How Can Agile Practices Minimize Global Software Development Coordination Risks?

by Emam Hossain , Muhammad Ali Babar , June Verner - In Proceedings of the 16th European Conference on Software Process Improvement (EuroSPI’09), Madrid, CCIS 42, , 2009
"... Abstract. Project stakeholder distribution in Global Software Development (GSD) projects causes significant project communication, coordination and collaboration challenges. There is a growing interest in applying agile practices in GSD projects in order to leverage the advantages of both approache ..."
Abstract - Cited by 5 (3 self) - Add to MetaCart
Abstract. Project stakeholder distribution in Global Software Development (GSD) projects causes significant project communication, coordination and collaboration challenges. There is a growing interest in applying agile practices in GSD projects in order to leverage the advantages of both approaches; in some cases, GSD project managers use agile practices to reduce project distribution challenges. We use an existing coordination framework to identify GSD coordination problems due to temporal, geographical and socio-cultural distance. An industry-based case study is used to describe, explore and explain how the use of agile practices reduces various challenges that impact GSD coordination. For example our case study findings reveal that the agile practice "Daily Scrum meetings" with distributed project stakeholder participation through video-conferencing helped to reduce challenges related to GSD coordination. We conclude with comments on future research.
(Show Context)

Citation Context

...esearch is to explore how the effective use of agile practices can reduce challenges that impact on GSD coordination processes. 3. Coordination Coordination is considered to be a key organizational activity in any software development. A traditional co-located software development team usually builds up the coordination of their different tasks in a number of ways. A highly idealized traditional co-located development team has a shared view of work processes and coordination is achieved either because of shared defined processes, or by acquiring a common set of habits and vocabulary over time [12]. Herbsleb [12] suggests that through frequent formal and informal interactions, co-located team members have a clear idea of who has what sort of expertise, and how responsibilities are allocated throughout the development team. The development team uses informal communication along with formal instructions throughout the development process. But geographical, temporal and socio-cultural distances make GSD communication, coordination and control process difficult and they require more development time than their co-located development counterpart [13, 15]. Herbsleb et al [13] comment that a d...

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University