Menu

Preliminary Agenda
8:00-09:00 Registration


09:00 - 09:10 Welcome
09:10 - 09:45 Invited Talk

Christoph Treude. How Do Social Media Artifacts Support Collaborative Software Development? Empirical Studies from the University of Victoria

09:45 - 10:30 Social Requirements Engineering
(S) Leif Singer, Norbert Seyff and Samuel A. Fricker. Online Social Networks as a Catalyst for Software and IT Innovation
(S) Dennis Pagano. Towards Systematic Analysis of Continuous User Input


10:30 - 11:00 Coffee break


11:00 - 12:30 Empirical Studies on Social and Human Aspects
(L) Antony Tang, Ton Gerrits, Peter Nacken and Hans Van Vliet. On the Interplay between Software Architects and Software Engineers in an Agile Environment: Who Should Do What?
(S) Pierre Robillard. The Learning Component in Social Software Engineering
(L) Irwin Kwan and Daniela Damian. Extending Socio-technical Congruence with Awareness Relationships


12:30 - 14:00 Lunch


14:00 - 15:30 Collaboration, Communication, and Awareness
(S) Patrick Wagstrom. Engineering Software Engineering Teams
(S) Thomas Fritz and Gail Murphy. Socially Mediated Technology Awareness
(S) Fabio Calefato, Filippo Lanubile, Nicola Sanitate and Giuseppe Santoro. Augmenting Social Awareness in a Collaborative Development Environment
(S) Jonathan Bell, Swapneel Sheth and Gail Kaiser. Secret Ninja Testing with HALO Software Engineering


15:30 - 16:00 Coffee break


16:00 - 17:00 Round Table Discussion
17:00 - 17:30 Summary of discussion, feedback, and closing


19:30  Social Event at http://www.regihid.hu/en/


(S) Short paper: 15min. presentation + 7min. discussion.

(L) Long paper:  20min. + 10min. discussion.


Details:



Christoph Treude. How Do Social Media Artifacts Support Collaborative Software Development? Empirical Studies from the University of Victoria

Today's generation of software developers frequently use social media artifacts to support development processes such as task management and documentation. Social media tooling is either used as an adjunct or integrated into a wide range of tools ranging from code editors and issue trackers to IDEs and web-based portals. Based on the results of several empirical studies we conducted out of the University of Victoria, we highlight how social media artifacts such as tags, feeds, and dashboards bridge lightweight and heavyweight task management in software development, and we illustrate how blogs, developer wikis and Q&A; websites are changing the way software is documented. Our findings indicate that lightweight informal tool support, prevalent in the social computing domain, may play an important role in improving collaborative software development practices.



Antony Tang, Ton Gerrits, Peter Nacken and Hans Van Vliet. On the Interplay between Software Architects and Software Engineers in an Agile Environment: Who Should Do What?


As there is considerable freedom for software workers to decide what to do in an agile environment, there is a need to be explicit about social aspects such as task ownership between roles and the agility in owning those tasks. We have conducted interviews and a survey at a large organization to explore these issues. The results indicate that there are areas where architects and software engineers have different views on task ownership. Some of the less exciting tasks such as documentation and issue clarification then easily become a hot potato nobody wants.



Pierre Robillard. The Learning Component in Social Software Engineering

The interactions that occur in a social software engineering context, both face-to-face and virtual and from the mundane to the professional have many purposes. Professional interactions can be planned or ad hoc, and their purposes are both varied and intertwined. They could serve to build trust, or be used to share or acquire knowledge or knowhow. Social software engineering can also be collective or solo. In this paper, we contend that an important component of social software engineering is learning. A model, based on existing learning theory, is proposed to describe the knowledge and knowhow content of professional social software engineering. The model is applied within the context of an observational study in a professional environment where ad hoc interactions are audio-visually recorded. We found that 60% of the social software engineering occurring within this collocated team was aimed at improving knowhow on the use of tools, while 40% of the interactions were conducted for the purpose of acquiring knowledge on the application to be implemented.



Irwin Kwan and Daniela Damian. Extending Socio-technical Congruence with Awareness Relationships

Coordination in software engineering is necessary for software teams, but to advance its study, we need a a way to measure this coordination. Socio-technical congruence is one such measure. To enable coordination, team members should have awareness of other's tasks and abilities. However, the conceptualizations for socio-technical congruence do not easily include awareness.

In this paper, our goal is to include awareness in socio-technical congruence. To do this, we conduct an empirical investigation of a team's awareness behaviour. We examine how developers transmit awareness information in a global software-engineering environment in a project called Ship using direct observations, interviews, and a questionnaire. We found that team members were satisfied with using simple awareness mechanisms such as email and meetings. We also identified that experienced team members served as brokers and filled coordination gaps, and that team members used multiple types of media simultaneously. Based on this work, we propose an aggregated socio-technical congruence measurement that can be used to specify multiple relationships, such as awareness relationships, as  interactions that satisfy technical dependencies.



Fabio Calefato, Filippo Lanubile, Nicola Sanitate and Giuseppe Santoro. Augmenting Social Awareness in a Collaborative Development Environment

Adequate tool support is paramount to enable distributed teamwork, and thus global software teams usually rely on a Collaborative Development Environment (CDE) to cope with geographical distance. The most recent and full-featured CDEs typically provide presence and workspace awareness in one place, but lack any support to social awareness for reducing the sociocultural distance. We argue that disseminating social awareness information within a CDE can both speed up the establishment of a cross-organizational shared context and help developers who have little or no chances to meet and then develop trust-based inter-personal connections. For this reason, we propose to extend a commercial CDE in order to provide members of global software teams with information collected from corporate microblogging and professional social networks.



Dennis Pagano. Towards Systematic Analysis of Continuous User Input

Novel requirements elicitation approaches suggest to continuously gather and communicate user input to engineering teams. The resulting data usually consists of a large amount of unstructured information in the form of natural language and may include conflicting user needs that have to be detected and resolved to obtain consistent requirements. This position paper provides a first step towards a systematic analysis of continuous user input by identifying its main challenges and aligning helpful techniques from requirements engineering research to address the challenges in a common framework.



Jonathan Bell, Swapneel Sheth and Gail Kaiser. Secret Ninja Testing with HALO Software Engineering

Software testing traditionally receives little attention in early computer science courses. However, we believe that if exposed to testing early, students will develop positive habits for future work. As we have found that students typically are not keen on testing, we propose an engaging and socially-oriented approach to teaching software testing in introductory and intermediate computer science courses. Our proposal leverages the power of gaming utilizing our previously described system HALO. Unlike many previous approaches, we aim to present software testing in disguise - so that students do not recognize (at first) that they are being exposed to software testing. We describe how HALO could be integrated into course assignments as well as the benefits that HALO creates.



Thomas Fritz and Gail Murphy. Socially Mediated Technology Awareness

New technology can reduce a developer's work. Yet, given how fast technology changes, it is close to impossible for a developer to stay aware of technological advances that might ease his work. In this paper, we propose an approach that increases the likelihood of a developer becoming aware of technology that might help him. Our approach uses a developer's interaction with the development environment to characterize a profile of the developer's use. This profile can then be used to find relevant posts on social news web sites. We use the votes on the social web sites as a means to filter and rank relevant information for the developer.



Patrick Wagstrom. Engineering Software Engineering Teams

In this paper we discuss some novel ideas for understanding how software engineering teams communicate and coordinate. We utilize these ideas to understand how these teams should be constructed and what individuals and managers can do to ensure that teams perform at high levels. Our view is based on numerous observations and interactions with enterprise software engineering teams and influenced by economic models of information sharing. We propose that neither a fully top-down nor bottom-up approach is entirely suitable for teams; rather teams must recognize this issue and work to embrace both models of information flow. This, in turn, can be facilitated by the role of intercessor who seeks to properly guide, direct, and curate both top-down and bottom-up information flows.



Leif Singer, Norbert Seyff and Samuel A. Fricker. Online Social Networks as a Catalyst for Software and IT Innovation

People have many creative ideas, but only a few of these ideas are realized and lead to innovation. Good ideas often fail because they are not shared between innovators and stakeholders, hence are unlikely to be realized. Consequently, many opportunities are missed to excite customers and to gain a competitive advantage. This paper proposes an innovation process that uses online social networks to lower the hurdle to sharing ideas. The process leverages diffusion effects of social networks while supporting the generation, evaluation, consolidation, and implementation of innovative ideas with lightweight activities. The process is illustrated and discussed using an application example. Although we are focusing on innovation regarding software-intensive systems, we foresee that the discussed process has the potential to be applied to other domains as well.
 

This page is hosted by the Chair for Applied Software Engineering of the Technische Universität München.
Imprint (Impressum)