Appendix D - Bournemouth University

7 downloads 586 Views 2MB Size Report
However, considering the illustration presented in the paper, we include this paper in the localized ...... Coordination
Appendix D Paper Title: Authors Affiliations Publication

Microblogging in Global Software Development : Klimpke, L. : University of Mannheim, Germany : Proceeding of the Conference on Advanced Information Systems Engineering (CAiSE) Doctoral Consortium, London (CEUR Workshop Proceeding) Publication Year : 2011 Origin of the Paper : Germany Summary: This paper proposes further exploitation of social media, especially microblogging, for communication and collaboration in a global software development (GSD). The paper identifies the communication and collaboration problems that occur in a small to medium-sized organization, through a series of eight case studies. A tool that increases the awareness that facilitates communication and collaboration among developers in a GSD environment is proposed to overcome the identified problems. Criteria: Areas of Study: Design The paper proposes a tool that applies the methodology to increase awareness, facilitate communication and collaboration, and improve documentation among developers in a GSD environment. Research Type: Solution The paper introduces the idea of exploiting social media, especially microblogging, in supporting communication and collaboration among developers in a GSD environment. However, the development of the tool has only reached the initial stage without further validation. Therefore, this paper is concluded as a solution proposal. Form of Study: Case Study and Literature Review The paper performed eight case studies to search for communication and collaboration problems in a small to medium-sized enterprises. However, it also performed a thorough analysis and research through documents and current market at that time to produce a theoretical concept of the tool's methodology. Social Techniques: Blog/Microblog The research is focused on social media, especially microblogs, to support communication and collaboration. Microblogs enable postings of short messages as a simpler way to convey ideas in an informal way, thus particularly supporting communication. Social Connectivity: Adapted In this paper, microblogs are used by the organization to support communication and collaboration. This means that the microblogs are adopted and adapted to serve the needs of the organization. Therefore, we categorize its connectivity as a hybrid due to its public use and its adaptation to the organization to act as a designated tool. Social Interaction: One-to-many This paper emphasized the main function of microblog to post short messages into a personal blog. Each posted message is available to other user for viewing and commenting. Through this mechanism, a communication is formed by the posted messages to the viewed and replied of the post. Social Location: Distributed The paper discussed the use of microblogging in a global software development. A global software development is defined as software development project undertaken at geographically separated locations connected by communication and coordination among each team. Honeycomb framework: Conversation and Sharing The paper described the adoption of microblogging to support synchronous and asynchronous communication. Microblogging allow members of the project to converse and exchange content in a more convenient way.

*) Forster, S., Pinggera, J., and Weber, B., 2013. Toward an Understanding of the Collaboration Process of Process Modeling. In: Proceedings of the CAiSE'13 Forum at the 25th International Conference on Advanced Information Systems Engineering (CAiSE), 17-21 June 2013, Spain. Valencia: CEUR-WS.org, 98-105

130

Paper Title: Authors Affiliations Publication

Social Forking in Open Source Software: An Empirical Study : Fung, K. H., Aurum, A., and Tang, D. : University of New South Wales, Australia : Proceeding of the Conference on Advanced Information Systems Engineering (CAiSE Forum), Gdansk, Poland (CEUR Workshop Proceeding) Publication Year : 2012 Origin of the Paper : Australia Summary: The use of forking to create new software projects by basing them upon the development on top of another project has drawn the interest of industries. Forking has a mature versioning control and is highly supported by open source software. This paper focuses the research on how forking is used to facilitate open source software. Criteria: Areas of Study: Coding and Software and Verification Forking uses an existing artifact that is manipulated into a new software project where the artifact is not limited to source code only. This means that any related artifacts such as documentation and testing are included in the forking. Research Type: Evaluation The paper does not introduce any novel methodology or research. However, it conducted research of several communities within open source software. It also presents a clear result of the research. Form of Study: Case Study Nine communities that used one programming language in open source software were studied. It identifies how forking is created, contributed, and used socially in open source software. Social Techniques: Crowd sourcing Social coding site (i.e. GitHub) hosted the development communities where it supports forking. This allows developers to communicate in a sense of crowd sourcing. Social Connectivity: Public Forking is available to the public and is hosted by a social coding site which is open to the public. Social Interaction: Many-to-many Involvement of communities to develop forking enables the input from many users to be used by many other users. Social Location: Distributed Social coding website is available to the public regardless time and location. Therefore, although the paper did not mention it explicitly, a distributed pattern is applied in this research. Honeycomb Framework: Identity, Conversation, Sharing, and Groups The study represents several blocks of the honeycomb network. Within the case study used in the paper, Identity represents the members of GitHub. Conversation and Sharing represents the communication activity among members to conduct forking. Furthermore, Groups represents multiple groups available for different project topics.

131

Paper Title: Authors Affiliations Publication

Investigating the Collaborative Process of Process Modeling : Forster, S. : University of Innsbruck, Austria : Proceeding of the Doctoral Consortium of the 25th International Conference on Advanced Information Systems Engineering (CAiSE), Valencia, Spain (CEUR Workshop Proceeding) Publication Year : 2013 Origin of the Paper : Austria Summary: This paper investigates the modeler's activity towards the modeling environment. It enables distributed teams to provide information, solution, and knowledge, shared alternatives, and divide workloads regarding process modeling. By collecting and analyzing data of the collaboration process, this paper will identify the interaction of process modeling with individual process (i.e. comprehension, modeling, and reconciliation) Criteria: Areas of Study: Requirements/Specifications The paper investigates the collaborative process of process modeling. We categorize process modeling as part of requirements/specifications due to the nature of process modeling as the basic form that can be used repeatedly for developing applications. Research Type: Solution The paper proposes an infrastructure for analyzing the collaborative process of process modeling to consequently be used to investigate the process itself. However, until the paper was published, only the infrastructure to record and to analyze the collaboration has been developed. Further research to observe the collaboration using the tools proposed in this paper is described in a Paper Titled Toward an Understanding of the Collaborative Process of Process Modeling*. Form of Study: Non-empirical This paper only proposes conducting an empirical research for further investigation. Social Techniques: General Concept Techniques used in this paper were not described explicitly. However, it was mentioned that messages were exchanged to transfer knowledge, negotiate alternatives, and evaluate processes. It was also described that using this exchange message media provides the information of whom, when, and why a process is linked to a user. Therefore, we include this exchange messages into general category. Social Connectivity: Designated The collaboration presented in this paper is specifically developed to fulfill the collaborative process of process modeling. Tools applied in this process are designated tools to facilitate the collaboration. Social Interaction: One-to-many It can be assumed from the social technique used to mediate the collaboration that the communication interaction applied is one-to-many. Users are able to concurrently conduct editing towards the process model, where other users are able to see the changes made to the process model. Social Location: Mixture The collaboration facilitates users within localized and distributed location. Therefore, the social location presented by this paper is a mixture. Honeycomb Framework: Conversation and Sharing One of the features described in the paper is the ability to allow participants to exchange messages and knowledge. This represents the conversation and sharing in the honeycomb framework.

Paper Title: Authors Affiliations Publication

Augmenting Social Awareness in a Collaborative Development Environment : Calefato, F. and Lanubile, F. : Universita degli Studi di Bari Aldo Moro, Italy : Proceedings of 5th International Workshop on Co-operative and Human Aspects of Software Engineering, CHASE 2012, Zurich, Switzerland Publication Year : 2012 Origin of the Paper : Italy Summary: The paper introduced a new tool to support collaboration in software development environments by adding social networking and microblogging techniques into the communication. The tool was an extension of the current collaboration development environment that includes the microblog services of the paper being written. Future development is to include social networking as a part of the services. Criteria: Areas of Study: Requirements/Specification The paper proposed and presented an evaluation tool to gather stakeholders and prioritize them according to their relevance towards a project. Selecting the relevant stakeholders is an important part of the requirements process in a software development project. Research Type: Solution The paper proposed a tool as a solution to increase awareness and interaction between developers by sharing personal and technical information. Development of this tool will answer the hypothesis that aggregating several social media could increase awareness and trust between members in distributed environment. Form of Study: Non-empirical The paper proposed a tool that is still under development at the time the paper was written. Further development to aggregate several other social media and conduct empirical tests on the tool are upcoming iterations. Social Techniques: Blog/Microblog The paper described that current development of the tool has aggregated microblogs, with the aggregation of social networking as a future iteration. Therefore, the social technique used in this paper is microblog. Social Connectivity: Adapted The tool proposed in the paper is an extension tool that aggregates public social media. Therefore, the social media are adapted into the tool to provide additional services for the tool itself. Social Interaction: One-to-many The concept of microblogging is to post messages in a limited amount of space where they are accessible by others. Therefore, one posted message from a developer will be available to many other related developers. This is included in a one-to-many social interaction. Social Location: Distributed The paper did not explicitly mention the coverage of the tool. However, the aim of the tool is to support collaboration in a global software development environment. Therefore, the social location coverage is distributed. Honeycomb Framework: Identity, Conversation, Sharing, and Presence The paper described a tool that uses social media to support communication between developers. This tool combines microblogging (and social network for further development) that represents Identity, supports Conversation and Sharing between developers, and builds awareness of other developer's Presence.

Paper Title: CVS Integration with Notification and Chat: Lightweight Software Team Collaboration Authors : Fitzpatrick, G., Marshall, P., and Phillips, A. Affiliations : University of Sussex, Brighton, UK Publication : Proceedings of the 2006 ACM Conference on Computer Supported Cooperative Work, CSCW, Canada Publication Year : 2006 Origin of the Paper : UK Summary: The paper discussed the use of a lightweight event notification system combined with a tickertape tool to display the notification messages and a chat system to augment CVS. The paper described a study on how the combination of these tools increase communication pattern, especially in growing team culture, stimulating discussion, supplementing information, etc. Description of the results, which are in support of the use of these lightweight systems, is provided in the paper. Criteria: Areas of Study: Coding and Distribution, Maintenance, and Enhancement The paper reviewed the use of lightweight systems to enhanced CVS in supporting communication between developers. According to the paper, developers performed information exchange regarding codes and bug fixes through notifications displayed in the tickertape and chat messages attached to the CVS. Therefore, this paper is included in the coding and maintenance areas of study. Research Type: Evaluation The study described in the paper conducted an evaluation of the supporting role of the lightweight systems in augmenting CVS. The combination of the lightweight systems and CVS has been used in a long term run by one developer group. This paper presents the evaluation of that particular group in using the tools. Form of Study: Observation The paper explicitly described the type of research conducted to assess the use of lightweight systems combined with CVS. The study observed one developer group that has implemented the use of these tools in a long-term run. Result showed that the group has been able to maintain code changes, communication, collaborative work, and even shown an increase in team culture. Social Techniques: Instant Messaging and Email/Alert The paper mentioned several lightweight social techniques were combined to augment the CVS. These techniques include chat and notification system. We include chat in the instant messaging technique and the notification system in the email/alert technique. Social Connectivity: Adapted The paper described the lightweight systems that were used to combine with CVS, which were not specifically built to support communication. However, the developers within the observation group adopted and adapted these tools and combined them with CVS to support their communication. Social Interaction: One-to-many The paper described the communication formed between developers. We conclude that the communication and collaboration between the developers is a one-to-many interaction. Social Location: Distributed According to the group of developers observed in the study, most of the contributed developers are co-located within the same area. However, there are several developers located in different cities, even different countries and time zones. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversation, Sharing, Relationship and Presence We categorize the chat and notification system used for communication between developers into several honeycomb blocks. Conversation and Sharing represents the communication including information exchange through chat. Relationship represents the links between developers involved in the CVS system and Presence represents the availability of other developers through the notification system.

134

Paper Title: Authors Affiliations

Shared Waypoints and Social Tagging to Support Collaboration in Software Development : Storey, M., Cheng, L., Bull, I., and Rigby, P. : University of Victoria, Canada IBM Research, Cambridge, USA Publication : Proceedings of the 2006 ACM Conference on Computer Supported Cooperative Work, CSCW, Canada Publication Year : 2006 Origin of the Paper : Canada and USA Summary: The paper proposed a conceptual design of a collaboration tool that combines navigation and tagging to support communication between software developers. Description of the design and implementation of TagSEA is provided in the paper. This includes a preliminary evaluation to a small group of programmers at different sites, and the results. Criteria: Areas of Study: Coding and Distribution, Maintenance, and Enhancement The paper presented a design of TagSEA to support communication between software developers. TagSEA is used to mark specific location within lines of codes that is identified by tags. This mechanism helps to support documentation of any changes applied by developers to use in future code navigation. Therefore, this paper is included in the coding and maintenance areas of study. Research Type: Solution TagSEA proposed a solution for supporting communication between software developers by combining navigation and tagging. This tool assists developers in identifying particular bugs or tasks created or related to other developers. Form of Study: Non-empirical The paper mentioned a preliminary evaluation conducted to assess TagSEA. The evaluation process presented in the paper is not a complete description. However, it illustrates the use of TagSEA including comments made by the developers. Result showed that navigation and tagging were useful mechanism to support communication between developers. Social Techniques: Tag The paper explicitly described the use of tagging by TagSEA in supporting communication between software developers. A set of tags were used to mark navigation within certain lines of codes. The preliminary result showed that tagging was useful to assist developers in identifying bugs or tasks. Social Connectivity: Designated The paper described the conceptual design of TagSEA to support communication between software developers by providing navigation and tagging. This tool is specifically built to assist collaboration between developers. Therefore, we include this paper in the designated tool social connectivity. Social Interaction: One-to-many TagSEA supports communication between software developers by implementing navigation and tagging. Emphasizing in the use of tags, we conclude that social interaction patterns formed with tags is a one-to-many. This means that a set of tags created by developers to mark certain codes will be seen by other related developers. Social Location: Distributed The paper did not explicitly describe the coverage of TagSEA in supporting collaboration between software developers. However, according to the environment set that was used for evaluation, the TagSEA supports two different locations. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversation and Presence TagSEA is used to support collaboration between software developers by providing navigation and tagging in certain parts within the codes. We categorized TagSEA in several honeycomb blocks. Conversation represents the content of messages left with the tags and Presence represents the availability of other developers to create tags.

135

Paper Title: Social Coding in GitHub Transparency and Collaboration in an Open Software Repository Authors : Dabbish, L., Stuart, C., Tsay, J., and Herbsleb, J. Affiliations : Carnegie Mellon University, USA Publication : Proceedings of the 2012 ACM Conference on Computer Supported Cooperative Work, CSCW, Seattle, USA Publication Year : 2012 Origin of the Paper : USA Summary: The paper presented research into user activity transparency that might support the potential to improve collaboration and learning. A case study was conducted to a social coding site to examine the value of transparency and how it support collaboration and learning in practice. Result showed that users made social inferences and combined them into effective strategies to increase their work and reputation. Criteria: Areas of Study: Management, Coding, and Distribution, Maintenance, and Enhancement The paper presented research of how transparency supports collaboration and learning methods. It described how users made use of transparency for coordinating project, leveraging technical skills, and managed their reputation. Therefore, we include this paper in the management, coding, and distribution, maintenance, and enhancement areas of study. Research Type: Evaluation The paper presents an evaluation of how transparency supports collaboration and learning method in a social coding site, GitHub. It described the evaluation process conducted to identify different functionalities provided by GitHub that user exploited the most. Result showed that users made a rich set of social inferences that support collaboration. Form of Study: Case Study The research in the paper conducted a case study to a social coding site, GitHub, to identify how transparency and functionalities within GitHub can support collaboration. Semi-structured interviews were conducted to GitHub users to collect data. Analysis and results were presented in the paper. Social Techniques: Social Networking The paper described the investigation performed at a social coding site, GitHub. We include this paper in the social networking due to the similarity shared between the social coding site and the concept of social networking. Social Connectivity: Public GitHub is a social web-based hosting service. The presence of GitHub is available for public use and accessible regardless location and affiliation. Therefore, we include this paper in the public tools connectivity. Social Interaction: Mixture Considering the social techniques used in the research is a social coding site. We include this paper in the mixture social interaction that covers each type of interaction in a social coding site, including one-to-one interaction through direct messages, one-to-many interaction through comments or changes in codes, and many-to-many interactions through the dashboard. Social Location: Distributed Considering the accessibility of GitHub as a social coding site, we include this paper in the distributed social location. Honeycomb framework: Identity, Conversation, Sharing, Presence, Relationship, Reputation, and Groups The paper described research on a social coding site that provides similar social interaction to social networking. Furthermore, GitHub allows transparency that supports collaboration between developers by exploiting several functionalities provided. Therefore, we include this paper in the honeycomb blocks as mentioned above.

136

Paper Title: Authors Affiliations Publication Publication Year Origin of the Paper

Global Software Engineering: The Future of Socio-Technical Coordination : Herbsleb, J. D. : Carnegie Mellon University, USA : International Conference on Software Engineering, ICSE 2007 Workshop on the Future of Software Engineering, FOSE 2007 : 2007 : USA

Summary: This paper presents a review of the current situation in the areas of software engineering from globally distributed environment. For each area discussed, this paper also presents challenge for future development to increase collaboration support. Criteria: Areas of Study: Requirements/Specifications, Design, Coding, and Management According to the author, there are four critical areas of software engineering. For each area, the author described current situation of collaboration mechanism and suggests challenges to improve them. Therefore, this paper is included in four areas of study. Research Type: Opinion The paper presents the author's argument towards collaboration in the global distributed environment. It also provides the author's point of view in the existing collaboration situation within software engineering. In the summary, the author raises reasonable doubts as input for future development. Form of Study: Non-empirical The paper presented the author's point of view towards his research in determining the needs for coordination and identifying the mechanism to support it. The author described the papers that he chose to include in his research, such as conference and journal papers, to provide a more recent work. Social Techniques: General Concept One of the four critical areas that were discussed in the paper was the environments and tools to assist collaboration between developers. The paper described various existing studies that emphasize in the development of environments and tools. From those studies, there were various types of techniques proposed to support collaboration. There was no specific technique more prominent compare to others. Therefore, we include this paper in the general social techniques. Social Connectivity: Designated and Public The paper described various existing studies that focus their research in building environments and tools to support collaboration. Most of the tools mentioned in the studies were specifically designed to support collaboration. However, this research also mentioned how the developers made use of existing standalone systems to support their collaboration. Therefore, we include this paper in the designated and public tools. Social Interaction: Mixture Due to the various types of social media discussed in this paper, the combination of the tools and applications used in public covers the mixture of social interaction. Social Location: Distributed Due to the general discussion towards collaboration in globally distributed environment, we decided to include this paper in the distributed social location. Honeycomb Framework: Conversation, Sharing and Presence The paper did not explicitly describe any techniques used for communication. However, in the challenges mentioned in the paper, several necessities required to be addressed. Those requirements are interaction, information exchange, and the sense of awareness.

137

Paper Title: Authors Affiliations Publication

Collaborative Process Management and Virtual Teams : Donker, H. and Blumberg, M. : Dresden University, Germany : Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : Germany Summary: The paper discusses the creation of symbiosis between project management tools and collaborative tools based on the needs of virtual teams. The paper also described the problems that occurs in virtual teams, thus proposes a solution to facilitate management and collaboration between developers. Criteria: Areas of Study: Design and Management Several requirements on how to produce symbiosis between project management and collaborative tools were described in the paper. These requirements were then used as the basis of the symbiosis product's performance. Research Type: Opinion It is explicitly mentioned that the paper is a positional paper that discussed the needs to facilitate virtual teams. The paper is supported by arguments regarding problems that occur in the collaboration and potential solutions to overcome the problems. Form of Study: Non-Empirical The paper provided descriptions of current project management tools and collaboration tools. It emphasized the needs of a hybrid between the tools in order to support projects. It presents the general overview of expected tools including the requirements of further tool development. Social Techniques: General Concept The paper did not mention any specific social technique used in the proposed symbiosis between project management and collaborative tools. However, it indicates the use of social techniques by describing the common use of social computing to support collaboration. Social Connectivity: Designated Considering the symbiosis tool is to facilitate virtual teams in collaboration and project management, we concluded this as designated tool. Social Interaction: Mixture The paper mainly discussed the need to create a symbiosis tool supported by arguments of the problems, possible solutions and benefits. However, the discussion is considered preliminary and it did not discuss any possible framework used for the symbiosis tool. Therefore, to cover several different possibilities in which social interaction is used in the symbiosis tool, we concluded it as mixture social interaction. Social Location: Distributed According to the paper, the main purpose of creating a symbiosis tool is to facilitate virtual collaborative work in distributed companies. Therefore, we include this paper in the distributed social location. Honeycomb Framework: Sharing and Relationship Considering that the paper did not describe any particular social technique used to support the projects, based on the description of the potential solution of the future tool, we conclude that this paper is included in the sharing and relationship honeycomb blocks. The paper mentioned that the future tool needs to provide information sharing that could be accessed through an interface where it can create a relationship between the users.

Paper Title:

Communication Patterns in Geographically Distributed Software Development and Engineers' Contributions to the Development Effort Authors : Cataldo, M. and Herbsleb, J. D. Affiliations : Bosch Corporate Research, USA Carnegie Mellon University Publication : Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : USA Summary: The paper described a comparison in communication pattern between two geographically distributed software development (GDSD) projects. Project A showed a centralized pattern that suggests a certain group of developer were at the center of information acting as bridge to all other developers to communicate. Project B showed a very different pattern in which only several individuals acted as bridges creating connection between each location. The result showed that social collaboration and information exchange is better facilitated with a centralized sharing. Criteria: Areas of Study: Management The paper did not explicitly describe the area of study that it supports. However, we conclude, from the communication and coordination management involving positioning developers within a team, that this paper is to be included in the management area of study. Research Type: Evaluation Two sets of observation were reported in this paper. The main objective of the study is to observe the communication pattern in a geographically distributed software development. Thus, identify which pattern presents a better approach towards collaboration. Form of Study: Observation Observation was conducted at two unrelated geographically distributed software development projects. A large distributed system was observed in project A and a large medical system was observed in project B. Social Techniques: Instant Messaging and Dashboard The paper explicitly mention online chat system as one of the method used in the communication and collaboration. However, we conclude that the modification request tracking system mentioned in the paper uses dashboard to provide and distribute information. Social Connectivity: Adapted The social techniques used in the paper are adapted from public tools to facilitate collaboration and communication in geographically distributed software development. Social Interaction: One-to-many As mentioned in the result, according to the paper, a centralized communication was proven to support development the most. A centralized communication uses a group of people to bridge the communication from one end to another. Therefore, we include this paper in the one-tomany social interaction. Social Location: Distributed According to the paper, the main focus of the study is the geographically distributed software development. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversation, Sharing, Relationship, Reputation, and Groups The paper described one of the tools used to conduct communication and collaboration is through chat system. This represents the conversation and sharing of the honeycomb block. Furthermore, the centralized system represents the relationship between users with the central groups where we conclude that the central group has a higher reputation among other users.

139

Paper Title: Authors Affiliations

Can Peer Code Reviews be Exploited for Later Information Needs? : Sutherland, A. and Venolia, G. : University of Saskatchewan, Canada Microsoft Research Publication : Companion Volume of 31st International Conference on Software Engineering, ICSE 2009, Vancouver, Canada (New Ideas and Emerging Results) Publication Year : 2009 Origin of the Paper : Canada Summary: The study described an observational study performed at Microsoft on methods of code reviewing collaboration. The survey result showed that there is slightly higher percentage in the use of asynchronous communication (email based review) compared to synchronous communication (meeting based review). Inadequate communication tools support might result in issues related to data retention and retrieval. Criteria: Areas of Study: Maintenance The main discussion of the paper is to observe communication between developers in performing code review. We conclude that code review applies at maintenance phase related to bug fixing. Research Type: Experience The paper described the author's experience in conducting observation through survey at Microsoft. Form of Study: Case Study and Observation The study takes Microsoft as a case to observe its communication routine in performing code reviewing. There is no intervention taken by the authors where the result is originally based on the survey. Social Techniques: Email/alert The paper mentioned that other than face-to-face meeting, another social medium used at Microsoft to conduct code review is email. Results from the survey showed that respondent gave encouraging feedback due to ease in using email for preparing and carrying out review. However, according to the respondents, it was difficult to retain data using email. Therefore, the author suggest the use of a collaboration tool that supports task-oriented structuring as well as a feature for retaining and querying the structure list including discussion around them. Social Connectivity: Public The paper did not explicitly mention the type of emails used in conducting code reviewing. However, we can assume that the emails used are common available emails for public. Social Interaction: One-to-many Email communication enables at least two kinds of social interaction. One-to-one interaction enables direct communication from one developer to another, while one-to-many enables communication from one developer to certain groups or more than one other developer. Social Location: Localized The author did not explicitly mention the distribution of their survey respondent. However, we conclude that the survey was taken within a localized location under the Microsoft Company. Honeycomb Framework: Identity, Conversation, and Sharing The research in the paper described that there is a higher percentage of asynchronous communication compare to synchronous. Asynchronous is related to the use of emails between developers for communication. Thus, Conversation and Sharing both represents communication and information exchange that occurs between developers. However, suggestion of future tools includes data retention and structure in list of changes. Therefore, we also include Identify in this paper.

Paper Title: Authors Affiliations Publication

Codebook: Social Networking over Code? : Begel, A., and DeLine, R. : Microsoft Research : Companion Volume of 31st International Conference on Software Engineering, ICSE 2009, Vancouver, Canada (New Ideas and Emerging Results) Publication Year : 2009 Origin of the Paper : USA Summary: The paper proposed a new tool for developers to be connected socially and professionally. Codebook uses the concept of social networking to track other developers’ latest statuses and coordinate activities. It also acts as an information portal to manage collaboration between developers. Criteria: Areas of Study: Management The paper described that Codebook could be used in many areas of software development. It raises awareness among developers at the beginning of a project, building coding environments, and mediating the use of other artifacts within software development. Therefore, we include the study in management. Research Type: Solution Codebook is proposed to be the solution for developers to collaborate and to interact in a social and professional way. Form of Study: Experiment The paper mentioned an experiment of attaching the Codebook to the Bridge where it has been acknowledge by the Microsoft. However, it did not present any result related to that attachment. Social Techniques: Social Networking The paper mentioned that the Codebook adapted the social networking concept. Therefore, we categorize this paper into the social networking social techniques. Social Connectivity: Designated The Codebook is specifically built to facilitate users in a social and professional way through their personal pages and the artifacts they shared. Social Interaction: Many-to-many The use of social networking allows developer to have a many to many relationship with other developer. User has the options to connect to other users through various ways and post informative information on their page. Social Location: Localized Currently Codebook is still in preliminary stage. Furthermore, according to the authors, the Codebook initial implementation is limited to the "universal" use within the Microsoft environment. Honeycomb Framework: Identity, Conversation, Sharing, Relationship and Groups Considering the concept of social networking applied to Codebook, several honeycomb blocks match social network features. Identity represents other developers that correspond within the same project or has Relation to certain project. Conversation and Sharing represents the communication that occurs between developers and Groups represents different teams working in different projects.

141

Paper Title: Authors Affiliations Publication

Murphy: A Web 2.0 Approach for Proactive Risk Management in Hardware/Software Co-Design : Blagojevic, V., Codenie, W., Dedecker, J., Gonzales-Deleito, N., and Deleu, J. : Software Engineering Group, Sirris, Belgium : Companion volume of 31st International Conference on Software Engineering, ICSE 2009, Vancouver, Canada (New Ideas and Emerging Results) Publication Year : 2009 Origin of the Paper : Belgium Summary: The paper described a new approach to increase monitoring towards risk management against product failure in software development by using web 2.0. This approach consists of three major components of communication activity that allows information exchange throughout the team. Criteria: Areas of Study: Management The paper mainly discussed the risk management of product failure as part of software engineering. Therefore, we concluded that the risk management is included in the software engineering management. Research Type: Solution The paper introduced a novel approach for monitoring risk management and knowledge sharing among the developers. It provides the latest update of all identified risks, analysis result of the risks, and repository of common risks. Form of Study: Non-empirical The paper proposed an approach through web2.0 social technologies to monitor risk. However, the paper is only based on the authors' opinion and is not supported by an empirical result. Therefore, we include this paper in the non-empirical form of study. Social Techniques: Dashboard The paper did not explicitly describe the social techniques used in Murphy. However, according to the image example provided in the paper, the wall activity consists of message postings, and so is similar to dashboard. Therefore, we conclude that the social technique used in Murphy is a dashboard. Social Connectivity: Designated Murphy’s approach is specifically designed to facilitate risk management in software development. Therefore, we include this paper in the designated tool social activity. Social Interaction: One-to-many Based on the proposed social techniques, we conclude that the social interaction applied to Murphy is a one-to-many interaction. Each message posted by a user is available to other related users. Social Location: Localized It is mentioned in the paper that there is a consideration of attaching current Murphy to collaboration tools. Therefore, we conclude that current proposed Murphy facilitates only localized social location. Honeycomb Framework: Conversation and Sharing Considering the social technique described in the paper, we conclude that Conversation and Sharing represents the communication that occurs between developers.

142

Paper Title: Authors Affiliations Publication

End-User Requirements Blogging with iRequire : Seyff, N, Graf, F., and Maiden, N. : City University London, United Kingdom : Proceedings of 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010, Cape Town, Africa (Formal research demos: Software development environments) Publication Year : 2010 Origin of the Paper : United Kingdom Summary: The paper proposed an approach allowing user involvement in determining requirements. Users were allowed to blog their needs through a mobile application. These needs will then be gathered and used as input for the elicitation of requirements. IRequire allows requirement collection directly from the user. Criteria: Areas of Study: Requirements/Specifications The tool proposed in the paper, iRequire, enables requirements collection directly from the user. This tool allow user to blog their needs based on their daily requirements without interrupting their activities. Research Type: Solution The paper proposed a novel approach for requirements collection through blogs according to the user’s daily activities. A detailed description of the tool and its function is presented in the paper. Form of Study: Experiment The paper did not described in detail of the exploration to identify the limitations and benefits of the tool. However, it mentioned that a prototype has been developed and has been installed to be observed. Social Techniques: Blog/Microblog iRequire enable users to blog their needs and send them as requirements. Therefore, the technique used to collect the requirements is through blogging. Social Connectivity: Designated Although the approach of iRequire is using blog to collect user requirements, iRequire is designed specifically to gather user needs through blog post. Therefore, we categorized iRequire as designated tool. Social Interaction: One-to-one The study did not mention if the blog posted by the user will be visible to other users as it will be visible to the developers. However, we conclude that the user blog post is similar to direct feedback provided by the user. Therefore, it is a one-to-one social interaction. Social Location: Distributed The study did not describe the social location covered by iRequire. However, iRequire is a tool installed on mobile phones. Therefore, it is most likely that it covers distributed locations, as mobile phones enable distributed coverage. Honeycomb Framework: Sharing The paper proposed a method of supplying feedback through the concept of blogging. Sharing represents the information exchange between users. However, in this context, Sharing only represents the distribution of information through blogs written by users.

Paper Title: Authors Affiliations

StakeNet: Using Social Networks to Analyse the Stakeholders of Large-Scale Software Projects : Lim, S. L., Quercia, D., and Finkelstein, A. : University College London, UK MIT SENSEable City Lab Cambrigde, USA Publication : Proceedings of 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010, Cape Town, Africa Publication Year : 2010 Origin of the Paper : UK and USA Summary: The paper introduced a tool to identify and prioritize stakeholders by building a social network based on recommendations from the stakeholders themselves. StakeNet identifies stakeholders based on certain project scope and uses the identified stakeholders to search for other stakeholders. Social network links were drawn between the stakeholders and StakeNet provides measures for the network to prioritize the stakeholders. Assessment of StakeNet was conducted throughout the project, resulting in a better list of stakeholders compared to the existing system. Criteria: Areas of Study: Requirements/Specifications The paper proposed and presented an evaluation tool for gathering stakeholders and prioritizing them according to their relevance towards a project. Selecting the relevant stakeholders is an important part of the requirements process in a software development project. Research Type: Solution and Validation The paper proposed a new method, StakeNet, to identify and prioritize stakeholders. Then, the authors conducted a StakeNet evaluation of a library system at University College London. The result was a comparison between the list provided by the existing system and the list provided by StakeNet. Therefore, we include this paper as Solution and Validation research. Form of Study: Case Study The paper used the University of College London as a case study to evaluate the initial result of using StakeNet to assess their library system. Detailed methods and results were presented in the paper. Social Techniques: Social Networking StakeNet uses a common approach of social networking by identifying other related stakeholders from the significant stakeholders. However, the approach in this study requires a third party, which is the authors, to conduct the recommendation collection. Social Connectivity: Designated StakeNet was designed specifically to identify, to collect and to connect stakeholders. The result was a list of prioritized stakeholders based on the social network measures of importance. Social Interaction: One-to-many The social technique used in the paper stated that each stakeholder is able to recommend other related stakeholder. Therefore, this study is included in the one-to-many social interaction. Social Location: Localized The paper did not explicitly describe the social location coverage of the StakeNet. However, considering the case study used in this study, we conclude that StakeNet covers localized social location. Honeycomb framework: Relationship The StakeNet social network link represents relationship between stakeholders with other stakeholders.

Paper Title: Requirements Bazaar Social Requirements Engineering for Community-Driven Innovation Authors : Dominik Renzel, Malte Behrendt, Ralf Klamma, Matthias Jarke Affiliations : Aachen University Publication : 21st IEEE International Conference on Requirements Engineering (RE) Publication Year : 2013 Origin of the Paper : Germany

Summary: The authors present Requirements Bazaar, a browser-based social software platform for Social Requirements Engineering (SRE). Stakeholders from diverse CoPs are brought together with service providers into an open, traceable process of collaborative requirements elicitation, negotiation, prioritization and realization. Criteria: Areas of Study: Requirements/Specification The authors propose a browser-based social software platform for Social Requirements Engineering. Research Type: Solution Requirements Bazaar is a solution to social software engineering subject. Form of Study: Non-empirical The authors provide no validation from human perception or judgment. Social Techniques: Crowd sourcing Requirement bazaar is a crowdsourcing platform for eliciting requirements. Social Connectivity: Designated The website specializes in its duty. Social Interaction: Many-to-many The crowd sourced platform allows many-to-many interactions. Social Location: Distributed The nature of crowd sourcing is distributed activities. Honeycomb Framework: Sharing, conversations, identity These honeycomb framework elements are available.

145

Paper Title: Authors Affiliations

StakeSource: Harnessing the Power of Crowdsourcing and Social Networks in Stakeholder Analysis : Lim, S. L., Quercia, D., and Finkelstein, A. : University College London, UK MIT SENSEable City Lab, Cambridge, USA Publication : Proceedings of 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010, Cape Town, Africa Formal research demos Publication Year : 2010 Origin of the Paper : UK and USA Summary: The paper proposed a web-based approach to automate stakeholders' identification and analysis. StakeSource introduced an evolutionary way of collecting stakeholders compared to its previous development, StakeNet. Other than that, StakeSource also offers a simpler yet powerful tool by applying crowd-sourcing method in the stakeholder collection. The result showed that StakeSource reduced expert workload and is suitable for large-scale projects. Criteria: Areas of Study: Requirements/Specifications The paper introduced an expansion of a previous tool, StakeNet, to automatically gather stakeholders and categorize them based on priority. StakeSource adopts the crowd sourcing method to collect relevant stakeholders automatically. Furthermore, its ability to identify potential problems and display information of a stakeholder supports the collection of the right stakeholders. Research Type: Solution The paper introduced StakeSource as an expansion tool of StakeNet to collect and analyze stakeholders. A detailed description of what and how StakeSource proposed to do is described in the paper. Form of Study: Non-empirical The paper proposed an advancement of StakeNet to identify and prioritize stakeholders with a method called StakeSource. It provides the comparison between StakeSource and StakeNet based on the same case study used by StakeNet, which is the RALIC for University College London. Result showed that the use of StakeSource exceeded StakeNet in delivering the objective of the RALIC project. Social Techniques: Crowd sourcing The paper explicitly mentioned the adopted approach used by StakeSource to gather the required stakeholders that is by using crowd sourcing. Therefore, we include this study in the crowd sourcing social technique category. Social Connectivity: Designated Similar to StakeNet, according to the paper, StakeSource is specifically designed to enhance the ability of StakeNet. Although it adopts the method of crowd sourcing to gather stakeholders, the main reason behind the development of StakeSource is to assist the project. Social Interaction: Many-to-many The concept of crowd sourcing facilitates many-to-many social interaction. Social Location: Localized It is not mentioned in the paper that StakeSource covers the localized social location. However, considering that the paper discussed the comparison between StakeSource and StakeNet in the same environment of RALIC project, we conclude that StakeSource covers the same social location with StakeNet that is localized. Honeycomb framework: Identity and Relationship The concept of StakeSource is to gather stakeholders and map the relationship between each stakeholder. StakeSource also has the ability to reveal the identity of a stakeholder from the use of the web-based interface.

146

Paper Title: Authors Affiliations Publication

SEREBRO: Facilitating Student Project Team Collaboration : Jorgensen, N. M., Hale, M. L., and Gamble, R. F. : University of Tulsa : Proceedings of the 33rd International Conference on Software Engineering, ICSE 2011, Waikiki, Honolulu, USA (Research Demonstrations) Publication Year : 2011 Origin of the Paper : USA Summary: The paper presented a lightweight tool to support student collaboration in a software engineering class. SEREBRO combines various techniques including wiki page, version controlling, profile page, tagging, etc, in order to maintain interaction between discussions and results. The paper claimed that SEREBRO is easy to learn and has been used for the last two years. Criteria: Areas of Study: Management and Distribution, Maintenance, and Enhancement The paper described SEREBRO as a tool that supports student collaboration in software engineering class. SEREBRO adopts the software project management with the main aim of supporting the management of interaction, discussion, and work results within the software engineering class. Therefore, we include this paper in the management and distribution, maintenance, and enhancement areas of study. Research Type: Solution SEREBRO has been used for two consecutive years with input and experiments on student use to reach current implementation. The latest improved SEREBRO integrates various new features, especially in the use of social media. Form of Study: Non-empirical The paper did not provide any empirical research towards SEREBRO. This paper only described the features supported by SEREBRO and illustrated how to use the interface. Social Techniques: Dashboard, Email, Tag, and Wiki The paper described various techniques used by SEREBRO to support collaboration and communication between students in software engineering class. These techniques include dashboard, email, tagging, and wiki as mentioned in the paper. Social Connectivity: Designated The paper described the features that support SEREBRO. It adopts several social techniques and integrates them to become features in SEREBRO. However, SEREBRO itself is specifically built to support collaboration between students. Social Interaction: Mixture Considering various types of social techniques integrated within SEREBRO to support collaboration, we conclude that SEREBRO applies to mixture social interaction. Various types of social techniques support interaction from one-to-many to many-to-many. Therefore, we include this paper in the mixture social interaction. Social Location: Localized The paper did not explicitly describe the coverage of SEREBRO in supporting collaboration between students. However, considering that SEREBRO is used within the software engineering class, we conclude that SEREBRO is a localized tool. Honeycomb framework: Identity, Conversation, Sharing, Presence, and Relationship SEREBRO is used to support collaboration between students in a software engineering class. We categorize SEREBRO in several honeycomb blocks. Identity represents the specific features of user profile, Conversation and Sharing represents comments and the content within comments within the idea network, Presence represents the availability or other user to performed revision to wikis, and Relationship represents the existing link between users within the version controlling.

Paper Title: Authors Affiliations

StakeSource2.0: Using Social Networks of Stakeholders to Identify and Prioritise Requirements : Lim, S. L., Quercia, D., and Finkelstein, A. : University College London, UK MIT SENSEable City Lab, Cambridge, USA Publication : Proceedings of 33rd International Conference on Software Engineering, ICSE 2011, Waikiki, Honolulu, Hawaii, USA Publication Year : 2011 Origin of the Paper : UK and USA Summary: The paper proposed an expansion of an existing study, StakeSource. An additional feature of StakeSource2.0 is to collect and analyze requirements as it collects and analyzes stakeholders. Other than that, StakeSource2.0 proposes the ability to recommend requirements of interest and highlights stakeholders that are in conflict. This is a shift of requirement collection, thus reducing the workload of the analysts. Criteria: Areas of Study: Requirements/Specifications The paper introduced an expansion of a previous tool, StakeSource, to include requirement identification, collection and prioritization. StakeSource2.0 allows the requirements determination to be done through crowd sourcing instead of being elicited by the analyst. Furthermore, StakeSource2.0 has the ability to recommend requirements of interest and highlight any potential conflict between stakeholders related to requirements. Research Type: Solution The paper introduced StakeSource2.0 as an expansion tool of StakeSource to include the collection and prioritization of requirements. A detail description of what and how StakeSource2.0 proposed to do is described in the paper. Form of Study: Non-Empirical The paper proposed advancement from previous study of StakeSource. StakeSource2.0 was compared in this paper based on the same case study used by StakeNet (the initial development of StakeSource and StakeSource2.0), which is the RALIC for University College London. A list of advancement and key requirements of further development of StakeSource2.0 was provided in this research. Social Techniques: Crowd sourcing The paper explicitly mentioned that the StakeSource2.0 still adopting the same method of StakeSource, that is crowd sourcing. Therefore, we include this study in the crowd sourcing social technique category. Social Connectivity: Designated As an expansion of StakeSource, StakeSource2.0 is specifically designed to enhance the ability of StakeSource. Social Interaction: Many-to-many The concept of crowd sourcing facilitates many-to-many social interaction. Social Location: Distributed The paper explicitly stated that one of the significant advancement of StakeSource2.0 is the ability to support larger number of stakeholders in distributed locations. Therefore, we include this study in the distributed social location. Honeycomb framework: Identity, Relationship, and Sharing The concept of StakeSource2.0 is mainly similar to StakeSource with the addition of requirement identification and prioritization. It still creates a relationship link between each stakeholder that is now not only for stakeholder identification but also for the requirements. Related to the requirements, StakeSource2.0 enables the sharing of requirement information. Furthermore, StakeSource2.0 still has the ability to reveal the identity of a stakeholder from the use of the web-based interface.

148

Paper Title: A New Perspective on the Socialness in Bug Triaging A Case Study of the Eclipse Platform Project Authors : Hayato Yoshiyuki, Hayato Yoshiyuki Affiliations : Wakayama University, Japan Publication : International Workshop on Social Software Computing Publication Year : 2013 Origin of the Paper : Japan

Summary: The authors explore how social relationships among developers impact on the efficiency of bug fixes from the case study of the Eclipse Platform project. Criteria: Areas of Study: Management Their findings imply that we need to not only consider who should fix this bug? but also take into account a fixer’s perspective who should assign this bug? or who should ask to whom?, in order to better support the bug triaging process. Research Type: Evaluation The authors use a case study to evaluate the impact of social relationships among developers on the efficiency of bug fixes. Form of Study: Case Study For their case study, the authors collected bug reports from the Eclipse Platform project where all the bug information is managed by one of the most popular bug tracking systems called Bugzilla. Social Techniques: Social Networking The use of Eclipse Platform Project implies social networking techniques. Social Connectivity: Public The original data set included 52,593 bugs reported from October 2001 to October 2012. After collecting the original data set using our web crawler program, the authors carried their data cleaning and several preprocessing filters. Social Interaction: Mixture The nature of Eclipse Platform Project allows for mixed social interactions. Social Location: Distributed The use of Eclipse Platform project shows a distributed social location. Honeycomb Framework: Identity, Conversations, Sharing, Presence, relationship, Reputation, Groups Eclipse Project Platform allows for all these items.

149

Paper Title: Authors Affiliations Publication

Continuous Social Screencasting to Facilitate Software Tool Discovery : Murphy-Hill, E. : North Carolina State University, USA : Proceedings of 34th International Conference on Software Engineering, ICSE 2012, Zurich, Switzerland (NIER for Verification and Evolution) Publication Year : 2012 Origin of the Paper : USA Summary: The paper introduced a novel approach to increase developer awareness with the concept of continuous social screencasting. The tool enables developers to recognize new tools remotely from their peers in order to support their tasks. Furthermore, it has the ability to store and share information. Further research is required to evaluate the effectiveness of this mechanism. Criteria: Areas of Study: Coding The main aim of the continuous social screencasting is to collect relevant tools and share them among developers who are looking for information. This discovery mechanism by increasing awareness is part of developing codes. Research Type: Opinion The study described the author's opinion in developing a tool to increase awareness among developers with the concept of discovery mechanism. Further evaluation of the prototype is part of future research. Form of Study: Non-empirical The paper is a proposal paper that described the concept of a novel approach. The tool itself has not yet been built completely and still requires evaluation through empirical study. Social Techniques: Crowd sourcing The paper did not explicitly mention the technique used in the proposed tools. However, considering how the tool works, we conclude that it is similar with the concept of crowd sourcing. The developers are allowed to store a known tool to them where it might be shared as an unknown tool for other developers. Social Connectivity: Adapted The concept of crowd sourcing is derived from public tools. Furthermore, the paper described that other public tools such as facebook, blog or vimeo were to be aggregated to share the content of the this tool. Social Interaction: Many-to-many Since we conclude that the continuous screencasting is using the concept of crowd sourcing, we include this study in the many-to-many interaction. Social Location: Distributed The paper proposed a continuous social screencasting mechanism to assist developers in gaining awareness from remote and asynchronous peers. This means that the mechanism proposed in the paper support distributed social location. Therefore, we include this paper in the distributed social location. Honeycomb Framework: Conversation, Sharing, Presence, Reputation, and Groups The paper proposed a crowd-sourcing concept to collect and provide information to support development. This method is included in several honeycomb blocks. Conversation and Sharing represents the information exchange by users, Presence represents the availability of other developer to provide information, Groups represents the various group discussions, and Reputation represents the rank of developers/groups that provide information.

150

Paper Title: Authors Affiliations

Towards a GLobal Software Development Community Web Identifying Patterns and Scenarios : Miguel Monasor, Aurora Vizcaino, Mario Piattini, John Noll, Sarah Beecham : University of Limerick University of Castilla La Mancha Publication : 8th International Conference on Global Software Engineering Workshop Publication Year : 2013 Origin of the Paper : Spain, Ireland

Summary: The authors propose a method for collecting and defining GSD scenarios and related patterns. Scenarios depicting events that happen in certain GSD contexts associated with communication, coordination are central to this method. Criteria: Areas of Study: Management The paper proposes a management style GSD community web intended to promote collaboration between industry and academia. Research Type: Solution The authors integrate pattern model into a GSD Community Web. Form of Study: Non-empirical The authors provide no empirical study and method. Social Techniques: Social Networking The authors mention no specific social technique. Social Connectivity: Designated The authors design a specific web application, GSD Community Web. Social Interaction: Mixture The authors’ tool allows for mixed social interactions. Social Location: Distributed The nature of the Community Web is distributed. Honeycomb Framework: Identity, Conversations, Sharing, Presence, Relationships These are the factors in honeycomb framework.

151

Paper Title: Authors Affiliations

ProxiScientia: Toward Real-Time Visualization of Task and Developer Dependencies in Collaborating Software Developer Teams : Borici, A., Blincoe, K., Schrother, A., Valetto G., and Damian, D. : University of Victoria, Canada Drexel University Philadelphia, USA Publication : Proceedings of the 5th International Workshop on Co-operative and Human Aspects of Software Engineering, CHASE 2012, Zurich, Switzerland Publication Year : 2012 Origin of the Paper : USA Summary: The paper introduced a tool that displays information for building awareness between developers involved in collaborative software development activities. The tool collects data, computes the work proximity for each developer, and presents the result to every developer so they can identify the nearest developer to collaborate. The paper also described an initial evaluation performed on the tool with positive feedback as the result. Criteria: Areas of Study: Coding, Distribution, Maintenance, and Enhancement, and Management The paper described the main aim of ProxiScientia to increase and maintain awareness among developers in the software development environment. Awareness between developers is required to facilitate collaboration in the area of coding and maintenance where it is very important for developers to be involved in communication and interaction. Furthermore, management is related to task distribution and awareness. Research Type: Solution The paper was presented as a concept of a solution for building awareness among developers involved in distributed software development. It described the approach of ProxiScientia in solving communication between developers by presenting information related to their collaboration. Therefore, we include this paper as a solution paper. Form of Study: Experiment It was mentioned in the paper that an initial evaluation of ProxiScientia was performed to identify expert judgment where six experienced participants was involved. The result showed that ProxiScientia is assessed as being useful in maintaining awareness among developers. Social Techniques: General Concept The paper did not explicitly mention the social technique used in ProxiScientia to support the awareness among developers. However, according to the paper, ProxiScientia provides information for developers to become aware of others thus enable somewhat communication between developers. Social Connectivity: Designated ProxiScientia is specifically designed to increase awareness among developer by providing information of other developers involved. ProxiScientia is currently implemented as plug-ins within a software team tools environment. Social Interaction: Many-to-many Considering that it was not mentioned in the paper which type of social technique was used in ProxiScientia, we conclude that the way ProxiScientia provides information that is similar to Dashboard. The paper described the information presented by ProxiScientia, which was displayed to be used by developers in order to identify other related developers, thus building awareness among them. Social Location: Distributed The paper mentioned that ProxiScientia aims to provide real time information to maintain and increase awareness between developers in a distributed software development environment. Therefore, we include this study in the distributed social location. Honeycomb framework: Presence and Relationship As described in the paper, ProxiScientia gathers data from involved developers and provides calculated proximity in the relationship between the developers. The awareness built from ProxiScientia represents the concept of presence in the honeycomb framework and the approximation provided by ProxiScientia represents the relationship among developers.

152

Paper Title: Authors Affiliations

StackOverflow and GitHub Associations Between Software Development and Crowdsourced Knowledge : Bogdan Vasilescu, Vladimir Filkov, Alexander Serebrenik : Eindhoven University of Technology UC Davis Publication : International Conference on Social Computing (SocialCom) Publication Year : 2013 Origin of the Paper : The Netherlands, USA

Summary: The authors investigate the interplay between Stack-Overflow activities and the development process, reflected by code changes committed to the largest social coding repository, GitHub. Criteria: Areas of Study: Coding StackOverflow and GitHub are coding sites. Research Type: Evaluation The authors evaluate the interplay between the two coding sites. Form of Study: Case Study The authors collect data from the two sites and compare and reflect upon them. Social Techniques: Social networking, Crowd Sourcing The essence of these two sites are social networking and crowdsourcing. Social Connectivity: Public The authors collect data already on these two sites for comparison purposes. Social Interaction: Many-to-Many The nature of the two sites allow for many-to-many social interactions. Social Location: Distributed The two sites allow distributed social locations. Honeycomb Framework: Identity, Conversation, Sharing, Presence, Relationship, Reputation, Groups All the elements are present in these two websites.

153

Paper Title: Authors Affiliations Publication

Winbook: A Social Networking Based Framework for Collaborative Requirements Elicitation and WinWin Negotiations : Kukreja, N. : University of Southern California, USA : Proceedings of the 34th International Conference on Software Engineering, ICSE 2012, Zurich, Switzerland ACM Student Research Competition Publication Year : 2012 Origin of the Paper : USA Summary: The paper presented a combined approach, using Facebook and Gmail, to provide a way for users to generate discussion topics through wall posts. These were color-coded based on topic agreement in order to facilitate communication and interaction within members of a project. WinBook has been deployed in several organizations with successful results. Criteria: Areas of Study: Requirements/Specifications The main aim of WinBook is to provide a medium for members involved in a project to raise discussions or issues and suggest options or answers on the discussion related to the project. WinBook was also used as a tool to brainstorm and organize ideas in the most convenient way for the user. Therefore, we include this paper in the area of requirements/specifications. Research Type: Solution The paper was presented as an initial solution, adapted from existing studies, for the members in a project to discuss issues and organize ideas. A thorough description of what and how the tool is used is provided in the paper. Therefore, we include this paper as a solution paper. Form of Study: Non-empirical The paper did not present a specific evaluation of the tool. It described the deployment of the tool in several organizations and the feedback given based on the result. However, the paper emphasized the comparison between existing work and further enhancement applied to WinBook. Therefore, we include this paper as literature review form of study. Social Techniques: Social Networking The paper explicitly described the approach used by WinBook, which is similar to that of Facebook. Although the color coding described in the paper was adopted from Gmail's technique for organizing emails, the main approach of WinBook is broadly adapted from Facebook. Social Connectivity: Designated WinBook is specifically designed to facilitate communication among members within a project, despite the similarity of posting techniques with that on Facebook. Social Interaction: Many-to-many It is described in the paper that WinBook facilitates discussions among members of a project. Every member is able to raise a topic as well as provide a suggestion of another different topic. Therefore, the tool enables many-to-many social interaction. Social Location: Localized The paper did not explicitly describe the social location covered by WinBook. However, from the results section, we conclude that the use of WinBook has only initially accommodated the localized area within Los Angeles. Honeycomb framework: Conversations and Groups As described in the paper, WinBook facilitates communication between members of a project. Although in the form of posting issues, commenting messages, and providing agreement, a form of communication is shaped between the members. Furthermore, various topic discussions formed various smaller groups that involves only the interested people.

154

Paper Title: User Involvement in Software Evolution Practice: A Case Study Authors : Pagano, D. and Bruegge, B. Affiliations : Technische Universitat Munchen, Munich, Germany Publication : Proceedings of 35th International Conference on Software Engineering, ICSE 2013, San Fransisco, USA Publication Year : 2013 Origin of the Paper : Germany Summary: The paper reported a study identifying the current practice of user involvement in software evolution. This is to understand the developer's workflow, problems, and motivations in involving users in software development. The study emphasized the needs of the developers to assessed and analyzed potential feedback. Result from the study showed that a tool to consolidate, structure, analyze, and track feedback is required. Criteria: Areas of Study: Requirements/Specifications The paper described the needs and expectations of users identified from feedback, which were used to maximize the system usefulness and usability. This means the user feedback was gathered, analyzed, and used as an input for further software evolution. Research Type: Evaluation The paper presented an evaluation of the current use of user feedback in several professional companies. Result showed that user feedback is part of important information used by the developers to improve software quality. Form of Study: Case study The study in this paper uses 5 professional software development companies to evaluate the current use of user feedback. Result showed that developers had a good response towards tools that could consolidate user feedback. Social Techniques: General Concept The paper utilized the case study to identify the current use of user feedback. Results showed that email was used most frequently to provide feedback. However, further research showed that email was not helpful in providing information due to some content missing. From analyzing the results, the paper suggested a tool that could identify similar and duplicate report, capture feedback content, and document the targeted feature without specifying any techniques to be used. Therefore, we include this paper in the general social technique. Social Connectivity: Designated The paper did not explicitly describe the types or kinds of social techniques used in the suggested tool. However, the research result suggested a designated tool to help developers in collecting, organizing, and analyzing user feedback. Therefore, we include this paper in the designated tool category. Social Interaction: One-to-one The paper did not explicitly describe the interaction performed by the emails. However, we conclude that the emails sent by the users were intentionally addressed as feedback. Therefore, the email interaction is included in the one-to-one interaction. Social Location: Distributed The paper did not explicitly describe the location of the users. However, considering the companies used in the case study, we conclude that this study is included in the distributed social location. Honeycomb framework: Conversation The communication between the users to the developers was formed through emails. Although we raise the assumption that this type of communication is a one-way communication, to some extent a conversation is likely to occur. Therefore, we include this study in the conversation honeycomb framework.

155

Paper Title: Collaboration Patterns and the Impact of Distance on Awareness in Requirements-Centred Social Networks Authors : Damian, D., Marczak, S., and Kwan, I. Affiliations : University of Victoria, Canada Publication : Proceedings of the 15th IEEE International Requirements Engineering Conference, RE 2007, New Delhi, India Publication Year : 2007 Origin of the Paper : Canada Summary: The paper presents a research of collaboration and awareness between local and distributed members of an industrial software team related to requirements. The authors used social network analysis in a case study to identify the interactions. The result showed that "changes to requirements" was the main reason for communication. Furthermore, the result also showed that distance affects communication frequency between distributed members. The paper also provided further suggestion for collaboration tools. Criteria: Areas of Study: Requirements/Specifications and Management The paper showed several reasons for communication to occur between the members of the team. Among the reasons, "changes to requirements" was considered to be the main topic of discussion. This means that the members of the team are most likely to interact in the area of requirements management. Therefore, we include this research in support of Requirements/Specifications and Management areas of study. Research Type: Evaluation By using the social network analysis, the paper assessed the collaboration and awareness between local and distributed members of software development teams. Result presented in tables and charts showed that communication performed was dominated by changes to requirements. The paper also gave several other results and discussions for further study. Form of Study: Case study The paper explicitly described the case study used in the research. The project selected as the case study was based on the significant communication between two different locations, Brazil and USA. It consisted of developers, system architects, test leaders and technical leaders. The authors conducted three collection data methods, including document inspection, questionnaire, and interview. Social Techniques: Social Network The study explicitly described the use of social network analysis to identify collaboration and awareness between members of the software development teams. The paper showed the relationship between the members of the team towards collaboration and awareness using nodes and indicators. Social Connectivity: Designated The paper did not explicitly describe how the members of the software development team communicate. However, the analysis using the social network represents a designated tool that identifies the communication occurs between them. Therefore, we include this paper in the designated tool social connectivity category. Social Interaction: Mixture Considering the social technique used to describe the communication between the members of the software development team, we include this study in the mixture social interaction. It was also pictured in the relationship with nodes and indicators. Social Location: Mixture The paper explicitly described that the main study of the research was to identify collaboration and awareness between members of the software development team. Based on the case study used in the paper, the team is located in two different locations where they interact with each other across sites and within the sites. Honeycomb framework: Conversation, Sharing, and Presence We conclude that the social network analysis used to assess the collaboration and awareness between the members of the team represents the conversation, sharing, and presence of the honeycomb framework blocks.

Paper Title: Authors Affiliations

Pricing Crowdsourcing-Based Software Development Tasks : Ke Mao, Ye Yang, Mingshu Li, Mark Harman : University of Chinese Academy of Sciences University of College London Publication : International Conference on Software Engineering Publication Year : 2013 Origin of the Paper : China, UK

Summary: The authors address the problem of pricing by introducing 16 cost drivers for crowdsourced development activities and evaluate 12 predictive pricing models using 4 popular performance measures. They evaluate their predictive models on TopCoder, the largest current crowdsourcing platform for software development. Criteria: Areas of Study: Metrics, Management The study looks at pricing as a management issue and introduces metrics to deal with it. Research Type: Evaluation The authors evaluate their predictive models on TopCoder, the largest current crowdsourcing platform for software development. They analyze all 5,910 software development tasks (for which partial data is available), using these to extract our proposed cost drivers. They evaluate their predictive models using the 490 completed projects (for which full details are available). Form of Study: Experiment The authors use an experimental evaluation style. Social Techniques: Crowd sourcing The authors apply their idea in crowdsourced tasks. Social Connectivity: Public The authors use TopCoder. Social Interaction: Many-to-many The nature of crowd sourcing tasks is a many-to-many interaction. Social Location: Distributed Crowd sourcing activities are distributed by nature. Honeycomb Framework: Sharing, Conversation, identity These honeycomb framework elements are available.

157

Paper Title: Authors Affiliations

Social Software Product Lines : Ali, R., Solis, C., Dalpiaz, F., Maalej, W., Giorgini, P., and Nuseibeh, B. : The Irish Software Engineering Research Centre, Ireland University of Trento, Italy Technische Universitat Munchen, Germany The Open University, UK Publication : Proceedings of the First International Workshop on Requirements Engineering for Social Computing, RESC 2011, Trento, Italy Publication Year : 2011 Origin of the Paper : Ireland, Italy, Germany, and UK Summary: The paper proposed a new framework of Social Software Product Lines (SSPL) to capture user evaluation of product quality and exploit them to configure further production. User feedback shaped the adaptation process at either design time or at runtime. The paper also provides the foundation and challenges of SSPL. Criteria: Areas of Study: Requirements/Specifications The paper introduced SSPL to identify, collect, and manage user feedback into the main driver of product's configuration process. We conclude that this method is similar with the method of collecting requirements for further product release. Therefore, we include this paper in the requirements/specification areas of study. Research Type: Philosophical The paper proposed the SSPL framework as a method of managing user feedback leading to adaptation that influenced further products. The background nature of SSPL was introduced in the paper together with the flow of SSPL and challenges that occurs. Therefore, we include this paper as a philosophical paper. Form of Study: Non-empirical The research presented in the paper did not perform any empirical study. The paper did not conduct any case study and did not report any observation or experiment. Therefore, we include this paper in the non-empirical form of study. Social Techniques: Crowd sourcing The paper explicitly described that the SSPL adopts the use of crowd sourcing to identify and collect user feedback. According to the authors, the crowd sourcing technique will provide freedom for users to make their own choices in giving feedback. Social Connectivity: Designated The SSPL framework is specifically developed to manage user feedback into requirements where it influenced the production process. Therefore, SSPL framework is a designated tool that support requirements in a production process. Social Interaction: One-to-one Although the social technique adopted by the SSPL is a crowd sourcing, we assume that every feedback given by the user is a one-to-one interaction where each user supplies a feedback to certain process. Therefore, we include this paper in the one-to-one social interaction. Social Location: Distributed Considering the social technique used by the SSPL, crowd sourcing is used by the distributed social coverage area. It enables users from different locations to supply the feedback where it became a part of the process adaptation for further products. Honeycomb framework: Presence Since this paper emphasized the use of user feedback in supplying requirements for production process, we conclude that the presence of the users is an important part of the production process. Therefore, this paper is included in the presence honeycomb block.

158

Paper Title: A Brechó-EcoSys Extension to Support Negotiation in the Software Ecosystems Context Authors : Rodrigo Pereira dos Santos, Lucas Rodrigues Tostes, Cláudia Maria Lima Werner Affiliations : Federal University of Rio de Janeiro, Brazil Publication : IEEE 14th International Conference on Information Reuse and Integration (IRI) Publication Year : 2013 Origin of the Paper : Brazil

Summary: In this paper, the focus is on presenting a value-based mechanism to support components negotiations in a reuse repository based on SECO context, since no research work has been found in this direction. It was implemented at the Brechó-EcoSys environment. The contribution is on complementing the stakeholders’ value proposition and realization, as well as incorporating a nontechnical mechanism in components repositories. Criteria: Areas of Study: Requirements/Specification, Distribution, Maintenance, and Enhancement The paper complements the stakeholders’ value proposition and realization, and supports components negotiation in reuse repositories. Research Type: Solution The authors provide an extension to Brecho-EcoSys environment. Form of Study: Case Study The authors, in order to demonstrate Brechó-EcoSys’ negotiation mechanism in action, present a use scenario. Social Techniques: General Concept The authors do not mention any specific social technique. Social Connectivity: Adapted The authors provide an extension to Brecho-EchoSys environment. Social Interaction: Mixture Brecho-EchoSys provides different social interaction types. Social Location: Not Acknowledged The authors do not mention the scope of the region. Honeycomb Framework: Identity, Conversations, Sharing, Presence The environment supports these items.

159

Paper Title: Authors Affiliations

Visualizing Requirements in Distributed System Development : Savio, D., PC, A., Patil, A., and Creighton, O. : Siemens Corporate Research and Technologies, Bangalore, India Siemens Corporate Research and Technologies, Munich, Germany Publication : Proceedings of the 2nd IEEE International Workshop on Requirements Engineering for Systems, Services, and Systems-of-Systems, RESS 2012, Chicago, IL, USA, Co-located with IEEE Requirements Engineering Conference. Publication Year : 2012 Origin of the Paper : India and Germany Summary: The paper introduced a tool to visualize requirements at several levels of granularity viewed from different stakeholders in a distributed project. This tool combines visual and text based representation to describe requirements in order to provide snapshot overview for distributed stakeholders. The paper also provided the authors' experience in using ReBlock to develop an application within an ultrasound system. Criteria: Areas of Study: Requirements/Specifications The paper described the tool development including a number of built-in features. The main objective of this tool is to enhance stakeholder's knowledge towards requirements thus avoiding any requirements overlap from many different stakeholders. Therefore, we include this paper in the requirements area of study. Research Type: Solution The paper introduced ReBlock as a tool to visualize requirements at various levels of granularity from the perspective of different stakeholders. The development of this tool, including the features that supports ReBlock, is also introduced in the paper. Form of Study: Case Study The paper reported the authors' experience in developing a sub-system application of an ultrasound system by using ReBlock. Result showed that the use of ReBlock was assisting the visualization of requirements very well. Social Techniques: Dashboard The paper did not explicitly describe the social technique used in supporting ReBlock. However, since ReBlock is aimed to visualize the requirements from different stakeholders, we categorize this paper into the dashboard social technique. Social Connectivity: Designated The paper proposed a tool that could visualize requirements at various level of granularity thus aiding decision-making. ReBlock is specifically built to address the needs of various stakeholders in information exchange. Social Interaction: One-to-many The paper proposed that ReBlock could be used by various numbers of stakeholders simultaneously. This enables a one-to-many social interaction from one stakeholder to the other stakeholders. Therefore, we include this paper in the one-to-many social interaction. Social Location: Distributed The paper explicitly described that ReBlock supported distributed development collaboration. The authors' experience presented in the paper also showed that ReBlock was used in distributed situation. Honeycomb framework: Sharing and Relationship The ReBlock tool described in the paper enables information exchange related to requirements between different stakeholders. It presented the information into multiple layers of granularity that was related from one to another. Therefore, Sharing represented the information exchange between the stakeholders while Relationship represented the stakeholders' relation towards requirements.

Paper Title: Authors Affiliations

FASTDash: A Visual Dashboard for Fostering Awareness in Software Teams : Biehl, J. T., Czerwinski, M., Smith, G., and Robertson, G. G. : University of Illinois, IL, USA One Microsoft Way, Redmond, WA, USA Publication : Proceedings of the CHI Conference on Human Factors in Computing Systems 2007, California, USA Publication Year : 2007 Origin of the Paper : USA Summary: The paper introduced a new interactive user interface, designed to improve awareness between developers using spatial representation based on the member's activities. FASTDash enables developers to identify which files were checked out, which files were currently being viewed, and what changes were applied to the files. This includes the ability to identify the person who performed the activities. An evaluation of FASTDash and the result obtained were presented in the paper. Criteria: Areas of Study: Coding and Distribution, Maintenance, and Enhancement The paper described an interface to increase awareness and support collaboration between developers in a software development environment. FASTDash is used to share existing artifacts between multiple developers within a workspace. Therefore, we include this paper in the Coding and Distribution, Maintenance, and Enhancement areas of study. Research Type: Solution and Evaluation The paper introduced a solution tool to increase awareness and support collaboration between developers. FASTDash enabled access to key information shared through the interface to reduce artifact dependence and increase communication. Furthermore, the paper also presented an evaluation of the usefulness of FASTDash. A number of results gained from the evaluation were presented in the paper. Form of Study: Observation and Experiment The paper conducted a series of observations and experiments of a number of developers, in order to identify their collaboration process before and after they were introduced to FASTDash. The results showed that most developers gave a positive response towards FASTDash. Social Techniques: Dashboard and Crowd sourcing The paper described a tool that increased awareness and support collaboration between developers. FASTDash introduced a visualization of key information based on shared codes to increase awareness, with the addition of comment attachments to specific files to support communication. Social Connectivity: Designated The tool proposed in the paper is specifically designed to increase awareness between developers, including the support of communication based upon shared codes. Therefore, we include this paper in the designated tool connectivity category. Social Interaction: One-to-many The paper described the use of FASTDash to support collaboration and communication between developers. By visualizing key information obtained from shared codes, every activity that occured will be available for other users. Therefore, FASTDash supported a one-to-many social interaction. Social Location: Localized The paper did not explicitly describe the location spread from where the developers need to collaborate. However, according to the observations and experiments conducted to identify the usefulness of FASTDash, the accommodated developers were co-located. Therefore, we include this paper in the localized location. Honeycomb framework: Identity, Conversation, Sharing , Presence, and Relationship The paper introduced a tool that could increase the awareness and support collaboration between developers. We include this tool in several honeycomb blocks. Identity represents the active user profile when a developer performs an activity. Conversation represents the communication that occurs between developers through attached comments. Sharing represents the information exchange that occurs between developers through the interface. Presence represents the knowledge of other developer's current activity. Furthermore, Relationship represents the link that rises from activity dependent towards other developers.

Paper Title: Authors Affiliations

DiscoTech: A Plug-In Toolkit to Improve Handling of Disconnection and Reconnection in Real-Time Groupware : Roy, B., Graham, T. C. N., and Gutwin, C. : Queen's University, Kingston, Canada University of Saskatchewan, Canada Publication : Proceedings of the 2012 ACM Conference on Computer Supported Cooperative Work, CSCW, Seattle, USA Publication Year : 2012 Origin of the Paper : Canada Summary: The paper proposed a new toolkit to help developers with disconnection problem in synchronous groupware. The system utilized five design dimensions on how to store information and manipulate them, why disconnection occurs and how information is to be sent once the disconnection is solved. DiscoTech also provides plug-in architecture of groupware application to encompass behaviors that developers might need during disconnection. Criteria: Areas of Study: Management The paper proposed a DiscoTech toolkit to help developers in retrieving delayed information when disconnection occurs. We assume that disconnection might happen anytime anywhere and for a relative amount of time, where it disturbed communication between developers. Therefore, we conclude that this paper supports the area of management. Research Type: Solution and Evaluation The paper introduced the DiscoTech toolkit that handles disconnection and reconnection problems that occurs within synchronous groupware. DiscoTech emphasized its ability to handle disconnection, ease of use by developers, and enabling various plug-ins. An initial evaluation was performed to four developers who were familiar with the concept of groupware. Results showed encouraging feedback. Form of Study: Experiment The paper did not explicitly describe the experiment conducted to assess the use of DiscoTech. However, the paper provided two application examples using DiscoTech. Both showed the benefit of using DiscoTech plug-ins to overcome disconnection. Social Techniques: General Concept The paper proposed DiscoTech tool that enables plug-ins to overcome disconnection for applications used by developers to support communication and collaboration. This means that DiscoTech has the flexibility to support social techniques used by developer to communicate. Therefore, we include this paper in the general social technique. Social Connectivity: Designated The DiscoTech tool is specifically built to overcome the disconnection and reconnection problem that occurs in synchronous groupware. Therefore, we include this paper in the designated tool. Social Interaction: One-to-one The tool proposed in the paper, DiscoTech, is using the client-server architecture concept to store delayed messages when disconnection occurs. This means that messages were stored in the server when a client is disconnected. When a client is reconnected, they will receive the messages in a timely manner so that the client will not miss any information. Therefore, we conclude that the server client communication represents the one-to-one interaction. Social Location: Distributed The paper described the client-server concept of DiscoTech covers distributed social location. Connected through the server, location of the clients could be in a distributed environment. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversation, Sharing, Presence, and Relationship The paper described the proposed tool that handles disconnection and reconnection between users in synchronous groupware. We include this tool in several honeycomb blocks. Conversation and Sharing represents communication that occurs between developers assisted by DiscoTech to avoid a disconnection problem. Presence represents the availability of the delayed content in the server even when a client is disconnected. Furthermore, Relationship represents the link between developers involved in the synchronous groupware.

Paper Title: Authors Affiliations

Tool Support for Distributed Software Engineering : Spanjers, H., Huurne, M., Graaf, B., Lormans, M., Bendas, D., and Solingen, R. : Philips Applied Technologies, The Netherlands Delft University of Technology, The Netherlands University of Oulu, Finland LogicaCMG and Drenthe University, The Netherlands Publication : Proceedings in the 1st IEEE International Conference on Global Software Engineering, ICGSE 2006, Florianopolis, Brazil Publication Year : 2006 Origin of the Paper : The Netherlands and Finland Summary: The paper discussed a system that was developed to automate build and test processes controlled remotely. It provides collaboration between multi-site developments through a web interface. SoftFab supported communication through information sharing, thus increasing awareness. A case study to identify the usefulness of SoftFab and results were presented in the paper. Criteria: Areas of Study: Coding, Software/Program Verification, and Distribution, Maintenance, and Enhancement The paper described a system that automates building and testing process that could be controlled from remote to increase collaboration to support distributed software engineering. SoftFab was claimed to be the backbone for tool interoperability for providing various features to ease collaboration. A feature list of SoftFab is presented in the paper. Research Type: Solution The paper introduced SoftFab as a means of providing support for collaboration within distributed software engineering. This tool is used to increase the speed of an integration process due to its web interface and multi-site remote awareness. Therefore, we include this paper in the solution research type. Form of Study: Case Study The paper explicitly described the case study conducted to identify the usefulness of the automatic building and testing system, SoftFab. The case study was conducted in Finland involving multiple partners. Challenges and benefits from using SoftFab obtained from the case study were presented in the paper. Social Techniques: Dashboard The paper did not specifically describe any social technique used by SoftFab. However, it mentioned that SoftFab is a web-based system that enables collaboration and communication between distributed locations. Furthermore, considering the display view of the SoftFab system, we include this paper in the Dashboard social technique. Social Connectivity: Designated The paper explicitly described that the original aim of SoftFab was to enable building and testing processes that support multiple site development. Therefore, we include this paper in the designated tool connectivity. Social Interaction: One-to-one The paper described the use of SoftFab as enabling communication and collaboration between multiple sites. However, from the case study described in the paper, we include this paper in the one-to-one social interaction, due to the ability of SoftFab to assist collaboration. According to the case study, a direct relationship was built between connected sites to perform the build and test processes. Social Location: Distributed The paper explicitly stated that SoftFab has the ability to supporting distributed software engineering. Therefore, we include this paper in the distributed social location category. Honeycomb framework: Sharing, Presence, and Relationship The paper described SoftFab as a tool that enables communication and collaboration between multiple software engineering sites. We include SoftFab into several honeycomb blocks. Sharing represents the information exchange available through the web interface. Presence represents the work status at other locations to increase awareness, and Relationship represents the connection that was built through the control center.

Paper Title: Authors Affiliations Publication

Keeping Up With Your Friends: Function Foo, Library Bar.DLL, and Work Item 24 : Begel, A. and Zimmermann, T : Microsoft Research, Redmond, WA, USA : Proceedings of the 1st International Workshop on Web 2.0 for Software Engineering (Web2SE) 2010, Cape Town, Africa Publication Year : 2010 Origin of the Paper : USA Summary: The paper proposed a plug-in tool, on top of an existing tool, Codebook, that enabled a newsfeed stream of software development activities mined from software repositories. Description of the newsfeed architecture was described in the paper, including several illustrations of how the use of the proposed newsfeed could increase collaboration and information exchange between developers. Criteria: Areas of Study: Requirement/Specification, Coding, Software/Program Verification, and Distribution, Maintenance, and Enhancement The paper described the use of newsfeed in providing real-time information on top of the Codebook platform. This activity newsfeeds provides various information related to artifacts including bug reports, function in codes, builds, specification document, etc. Therefore, we include this paper in the areas of study as mentioned above. Research Type: Solution The paper proposed a plug-in approach in a form of newsfeed on top of Codebook platform to share information among developers. A real-time and aggregated form of newsfeed is proposed to be available for each related developer, depending on the artifact. Description of the newsfeed architecture is provided in the paper. Form of Study: Non-Empirical The paper presented existing studies that became the background of the proposed newsfeed plug-in. Several illustrations of how the newsfeed would be implemented, and how it is useful to build awareness and share information between developers, were presented in the paper. Social Techniques: Feed The paper explicitly focused the research in the use of the newsfeed to increase awareness and collaboration between developers. Therefore, we include this paper in the Feeds technique. Social Connectivity: Designated The paper described the architecture of the proposed newsfeed, including the provider of the information and the display of the information. This plug-in is specifically designed to assist collaboration between developers. Therefore, we include this paper in the designated connectivity. Social Interaction: One-to-many Considering the mechanism of the newsfeed in providing information for developers, we include this paper in the one-to-many interaction. This is due to the information retrieved from a developer's activity which is then shared to the rest of the related developers. Social Location: Localized The paper described the awareness built between developers improved by the real-time newsfeed of developers' activities. The paper did not mention the coverage of this plug-in tool. However, considering the illustration presented in the paper, we include this paper in the localized location. Honeycomb framework: Sharing and Presence The paper proposed an approach to provide information via a newsfeed to build awareness between developers. Considering the approach in the result, we include this paper in several honeycomb blocks. Sharing represents the information available for developers through the newsfeed, and Presence represents the availability of other developers in supporting the information exchange.

Paper Title: Authors Affiliations Publication

Promoting Developer-Specific Awareness : Holmes, R. and Walker, R. J. : University of Calgary, Canada : Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : Canada Summary: The paper discussed problems that appeared between developers regarding specific awareness. Then it proposed an extension tool, YooHoo, a developer specific awareness system, to be assimilated into the Integrated Development Environment (IDE). This tool is claimed to increase awareness and support developers in coding collaboration. Criteria: Areas of Study: Coding The increase in awareness is to prevent code malfunction or further bug appearances due to any changes applied to the code without notification towards other related developers. Therefore, YooHoo is proposed to assist developers specifically in coding collaboration. Research Type: Solution The paper proposed YooHoo, a developer specific awareness (DSA) system, to increase awareness between developers thus preventing them from lacking information or having too much information. Form of Study: Document Analysis and Non-empirical The paper provides specific details of YooHoo and its features including a scenario wherein developers encounter problems at keeping the latest update of changes in code. Furthermore, there was no empirical study presented in the paper. Therefore, we include this paper into document analysis and non-empirical form of study. Social Techniques: General Concept The paper did not explicitly mention any type of social techniques used in Yoohoo design system. However, the Yoohoo system is applicable as an IDE extension. Social Connectivity: Designated The Yoohoo system is specifically designed to facilitate developers at maintaining code. Therefore, it is a designated tool to mediate collaboration between developers. Social Interaction: Many-to-many The Yoohoo system integrates with the work of developers and provides notification to other developers. This means that the Yoohoo system allows a developer to update code whilst other related developers will be notified of any changes made. Yoohoo also shows notification of other code that might be affected by the changes. Social Location: Distributed It is not explicitly mentioned in the paper that the observation was conducted in a distributed environment. However, the Yoohoo system is designed to facilitate a distributed software development environment. Honeycomb Framework: Sharing and Presence The paper proposed YooHoo as a means of support coding collaboration between developers. The YooHoo system provides notifications to the developers in a flexible manner. This builds awareness of changes in code where it represents presence of other developer's existence. Furthermore, YooHoo connects to the code repository where notified developers could retrieve the latest codes.

165

Paper Title: Authors Affiliations Publication

An Environment for Synchronous Software Development : Hattori, L. and Lanza, M. : University of Lugano, Switzerland : Companion Volume of 31st International Conference on Software Engineering, ICSE 2009, Vancouver, Canada (New Ideas and Emerging Results) Publication Year : 2009 Origin of the Paper : Switzerland Summary: The paper proposed an approach to reduce the negative impact of distributed collaboration by providing real time collaboration information. Syde is designed as an extension to software configuration management (SCM). It has had a preliminary implementation and been observed to have a compatible match between the proposed concepts and the result. Criteria: Areas of Study: Coding, Distribution, Maintenance, and Enhancement, and Management The paper described the main objective of Syde, which is to provide synchronization between developers in real time code changes. Syde enables developers to know if there are any changes performed by other developers who worked on the same system. However, the paper mentioned that the main activity of Syde is bug fixing. Furthermore, Syde is also used to monitor any activities relating to code changes. Therefore, we include this paper in the coding, maintenance, and management areas of study. Research Type: Solution The paper proposed a new approach to provide real time information related to code changes among developers in a distributed software environment. Syde is claimed to be able to provide information without disrupting developers. The tool itself is designed to be a complement of existing SCM. Form of Study: Experiment The research in the paper provides a preliminary experiment of Java projects to identify developers' behavior when programming. Result showed that maintenance has a higher rate of successful compilations compare to development. However, in fixing code, developers tend to avoid compilation errors. Social Techniques: Email/Alerts Every change of code committed to Syde will trigger notification. Syde will send this notification to related developers. In this paper, Syde is introduced as an Eclipse plug-in where Syde is not meant to replace the function of IDE. Therefore, Syde is only utilized in sending notification that was designed not to interrupt the developers. Social Connectivity: Adapted Syde is specifically built to facilitate distributed collaboration as an extension for software configuration management. Therefore, we include this paper in the adapted tools social connectivity. Social Interaction: One-to-many Syde sends every notification to related developers. Every changes made to the code will trigger Syde into sending alerts to other developers. This means that every developer is bound to send notification to other developers through Syde. Social Location: Distributed The paper explicitly described that the main purpose of Syde is to facilitate software development in a distributed environment. Therefore, we include this paper in the distributed social location. Honeycomb Framework: Identity and Presence Considering that the social technique used by Syde is through alert notification, we conclude this paper in the Identity and Presence honeycomb block. Identity represents the user profile of other developer that performed changes in code using Syde. Presence represents awareness between developers within distributed software development.

166

Paper Title: How Tagging Helps Bridge the Gap Between Social and Technical Aspects in Software Development Authors : Treude, C. and Storey, M. Affiliations : University of Victoria, Canada Publication : Proceedings of 31st International Conference on Software Engineering, ICSE 2009, Vancouver, Canada Publication Year : 2009 Origin of the Paper : Canada Summary: The paper presents a report of tagging adaptation and implementation in supporting software engineering. A research was conducted with professional distributed teams from IBM. The result reported a frequent use of tagging and how tagging supports the informal collaboration process. Criteria: Areas of Study: Maintenance According to the most frequently shared tags table presented in the paper, the main use of work tagging is in the area of bug fixing and improving performance. Therefore, we include this paper in the maintenance category. Research Type: Evaluation The paper identifies the use of tagging for work to support software development. A search for answers to address the research questions was conducted with the distributed teams from IBM. The result showed that a large amount of developers has adopted and adapted to work tagging for their daily work. Form of Study: Case study The study was conducted to approximately 175 respondents with approximately 30 distributed professional teams from IBM. The results showed that they were able to address the research questions proposed in the beginning of the paper. Social Techniques: Tag The paper discussed how tagging has been used and adapted to support software development. It mentioned that tagging provides freedom classification mechanism to the user to categorize the used artifacts. Social Connectivity: Adapted Tagging is originally part of social media available for public use. However, work tagging discussed in this paper is adapted from social tagging. Therefore, it has several significant differences compared to the social tagging. Social Interaction: Many-to-many Tagging enables many-to-many communication due to its ability to provide classification to artifacts. This classification allows the artifacts to be searched by other users and for each artifact may contain more than one tag. Social Location: Distributed The research in this study was performed with professional teams from IBM. The teams were distributed at 15 different locations worldwide. Honeycomb Framework: Sharing and Relationship The paper discussed the use of tagging to support collaboration between developers. As mentioned in the paper, tags are rarely used as direct communication. However, tags are applied to help other developers to become aware of particular work items. Therefore, tags are represented by Relationship and the information exchange that built awareness is represented by Sharing.

167

Paper Title: Analysis of User Comments: An Approach for Software Requirements Evolution Authors : Carreno, L. V. G. and Winbladh, K. Affiliations : University of Delaware, USA Publication : Proceedings of 35th International Conference on Software Engineering, ICSE 2013, San Fransisco, USA Publication Year : 2013 Origin of the Paper : USA Summary: The paper discussed a method to extract feedback requirements given by users through a mobile application. This study aimed to automate topic extraction from user comments by adapting topic modeling and conducting an evaluation on public data sets. The result showed that automatic data extraction generates a good result compared to the manual extraction. Criteria: Areas of Study: Requirements The paper explicitly discussed a method to extract requirements from user feedback through a mobile application. This is to build an automatic data extraction thus minimizing manual data extraction effort. Research Type: Evaluation The paper described evaluation conducted at the automatic data extraction method and at the report generated for the developers. Several public data sets of user comments were used to evaluate the method, together with two other methods for classifying topics. Furthermore, two sets of human subjects were used to evaluate the report. Form of Study: Experiment The paper conducted experiments using three sets of public data retrieved from three different mobile applications. Two types of experiment were performed with each data set. The results were then compared to the manual data extraction. Social Techniques: General Concept The paper did not explicitly mention any method used by the mobile applications to send the user feedback. Several approaches including the concept of email were mentioned. However, we include this paper into general technique. Social Connectivity: Public Considering the assumption that the social technique used in this study is an email, we categorized this paper in the public tool social connectivity. Social Interaction: One-to-one The paper described that the use of the user feedback is to gather requirements for further development. Therefore, the user email sent from the mobile application is specifically directed as feedback. This is included as one-to-one social interaction. Social Location: Distributed The paper did not specifically mention the social location discussed in this paper. However, we consider user as a stakeholder considering that they supply requirement feedback for further development. The mobile application used by the user to send feedback is distributed. Therefore, we include this study in the distributed social location. Honeycomb framework: Sharing In the consideration that users are a part of the stakeholders, feedback sent by users was included in the sharing honeycomb block. With mutual interest, users provide developers with requirements and developers provide users with the latest development that includes the requirements.

168

Paper Title: Service Networks for Development Communities Authors : Damian A. Tamburri, Patricia Lago, Hans van Vliet Affiliations : VU University Amsterdam Publication : International Conference on Software Engineering Publication Year : 2013 Origin of the Paper : The Netherlands

Summary: Much work is still needed to support developers’ communities with mechanisms able to proactively react to community dynamism. The authors argue that service-networks can be used to deliver this support. Service-networks are sets of people and information brought together by the internet. Criteria: Areas of Study: Management The paper discusses the management of relationships among developers in a big software organization. Research Type: Validation The authors validate their own idea presented in a previous paper. Form of Study: Case Study The authors use a case study approach in their paper. Social Techniques: General Concept The authors do not mention any specific social technique. Social Connectivity: Designated The authors use a specific social computing tool. Social Interaction: Mixture The paper implies that different social interactions may be used. Social Location: Localized Their case study involves a big centralized organization. Honeycomb Framework: Identity, Conversations, Sharing, Presence, Relationship These honeycomb framework elements are available.

169

Paper Title: Categorizing Bugs with Social Networks: A Case Study on Four Open Source Software Communities Authors : Zanetti, M. S., Scholtes, I., Tessone, C. J., and Schweitzer, F. Affiliations : ETH Zurich, Switzerland Publication : Proceedings of 35th International Conference on Software Engineering, ICSE 2013, San Fransisco, USA Publication Year : 2013 Origin of the Paper : Switzerland Summary: The paper proposed a practical method to identify valid bug reports. The authors demonstrated the method using bugs retrieved from BUGZILLA of four major open source communities. Result showed that the social aspect of the bug reporters' position is a strong indicator in determining the quality of the bug report. Based on the finding, an automated classification bug scheme was developed and analyzed. Criteria: Areas of Study: Distribution, Maintenance, and Enhancement The paper discussed the method used to identify valid bug reports from open source communities. Therefore, we include this paper in the distribution, maintenance, and enhancement area of study. Research Type: Validation paper The paper introduced a method to identify validity of bug reports indicated from the positions of bug reporter in the collaboration development of open source communities. The study proposed several hypotheses and was validated by the result of investigation from case study described in the paper. Form of Study: Case study The paper used data collected from BUGZILLA of four OSS communities including MOZILLA FIREFOX, MOZILLA THUNDERBIRD, ECLIPSE, and NETBEANS. Using this case study, the authors were able to generate results that validated their hypothesis. Social Techniques: Social Networking The paper explicitly described that the investigation of the bug reporters' position becomes the indicator of bug's validity mapped with social network. Therefore, we include this paper in the social networking techniques. Social Connectivity: Designated The method is developed specifically to automate bug classification that can be integrated with bug tracking platform. Social Interaction: Many-to-many Considering the social technique used in the paper, we include this study in the many-to-many social interaction. Social Location: Distributed The paper studied the collaboration network in bug identification of four OSS communities. Considering the open source platform with distributed members, we include this study in the distributed social location. Honeycomb framework: Reputation The main purpose of this paper is to identify valid bug reports. Investigation results showed that the position of the bug reporters in the OSS communities represents the validity of the bug report. Therefore, we include this study in the reputation block.

170

Paper Title: Authors Affiliations

Enabling Collaboration in Distributed Requirements Management : Sinha, V., Sengupta, B., and Chandra, S. : IBM India Search Lab, India IBM T. J. Watson Research Center, USA Publication : IEEE Software Journal, Volume: 23, Issue: 5, Pages: 52 - 61 Publication Year : 2006 Origin of the Paper : India and USA Summary: The study proposed a tool to support collaboration for distributed requirements management. The paper presented a detailed description of the design motivation of the tool. Then, the tool was evaluated to identify its usability and suggest further enhancements were also mentioned in the paper. Criteria: Areas of Study: Requirements/Specifications The paper explicitly described the aim of the tool, which is to support requirements in communication and management across distributed teams. Therefore, we include this study in the requirements area of study. Research Type: Solution The paper discussed a new tool that presented a set of views including the use of social media to support requirement discussion and collaboration for distributed teams. A detailed description of the design and usability of the tool is presented in the paper. Form of Study: Case study Initial evaluation was performed using a number of practitioners and tool builders, where it received a positive response. Next, a trial run was conducted to twelve practitioners from three projects where nine among them responded to an online usability survey. Social Techniques: Email and Instant Messaging The study combines the use of email and instant messaging to come up with a novel feature. Thus, it supports synchronous and asynchronous communication towards requirements collaboration. Social Connectivity: Designated EGRET is specifically designed to support requirements collaboration between distributed teams. The tool adopted social techniques including email and instant messaging to provide shared context for distributed stakeholders. Social Interaction: Mixture Considering the social techniques used in EGRET, the combination of email and instant messaging represents mixture interaction. Therefore, we include this study in the mixture social interaction. Social Location: Distributed The paper explicitly described that the main aim of EGRET is to support requirements collaboration between distributed teams. Therefore, we include this study in the distributed social location. Honeycomb framework: Identity, Conversation, Sharing, and Presence EGRET supports requirements discussion and informal communication through email and instant messaging. Both represent conversation and sharing from the honeycomb blocks. From the instant messaging display, a sense of identity disclosure is applied. This is also to build awareness of other developer's presence.

171

Paper Title: Authors Affiliations

How Social Q&A Sites are Changing Knowledge Sharing in Open Source Software Communities : Bogdan Vasilescu, Alexander Serebrenik, Premkumar Devanbu, Vladimir Filkov : University of Technology, The Netherlands University of California, Davis, USA Publication : 17th ACM Conference on Computer Supported Collaborative Work and Social Computing Publication Year : 2013 Origin of the Paper : USA, The Netherlands

Summary: The authors use a case study of R (a widely-used tool for data analysis) to investigate how mailing list participation has evolved since the launch of StackExchange. Their main contribution is the assembly of a joint data set from the two sources, in which participants in both the r-help mailing list and StackExchange are identifiable. This permits their activities to be linked across the two resources and also over time. Criteria: Areas of Study: Requirements/Specification, design, Coding, Software/program Verification, Distribution, Maintenance and Enhancement StackExchange website allows for all these SE activities. Research Type: Evaluation The authors investigate an existing technique in the paper. Form of Study: Case Study The authors use a case study of R. Social Techniques: Social Networking, Email/alert The authors use a social networking site and also the impact on email communications. Social Connectivity: Public The authors use StackExchange website. Social Interaction: Mixture The essence of the website under study is mixed interactions. Social Location: Distributed Use of StackExchange means distributed social locations. Honeycomb Framework: Identity, Conversations, Sharing, Presence, relationship, Reputation, Groups StackExchange website allows for all these items.

172

Paper Title: Authors Affiliations

On the Need for Mixed Media in Distributed Requirements Negotiations : Damian, D., Lanubile, F., and Mallardo, T. : University of Victoria, Canada University or Bari, Italy Publication : IEEE Transaction on Software Engineering, Volume 43, Issue 1, Page 116 - 132 Publication Year : 2008 Origin of the Paper : Canada and Italy Summary: The paper presented a research of synchronous and asynchronous communication modes required for collaboration of engineering in a distributed environment. Research in the paper conducted an empirical study of six projects to identify the effectiveness of having an asynchronous communication prior to synchronous communication in requirement negotiations. Investigation through analyzing the result showed that asynchronous communication supported the collaborative environment as well as providing more efficient negotiations. Criteria: Areas of Study: Requirements/Specifications The paper described a study of asynchronous and synchronous communication used to support collaborative work in requirement negotiations. Research in the paper investigates the usefulness of both approaches to address the hypothesis of a combination of lean and rich media for an effective requirement negotiation. Therefore, we include this paper in the Requirements/Specifications area of study. Research Type: Evaluation and Experience The paper presented an evaluation of the usefulness of both asynchronous and synchronous communications to support collaborative work for requirement negotiations. This paper used an empirical research in attempt to address the proposed hypotheses. A thorough description of the empirical research was presented in a clear way in the paper. Therefore, we include this paper in the evaluation and experience research types. Form of Study: Case study Research in the paper described that a case study was conducted using six academic teams, all in distributed environments. Two study methods were applied to the teams in order to compare the results. Three teams were involved in an asynchronous communication prior to synchronous communication, while the other three teams involved directly in the synchronous communication. The outcome of these projects was to create a software requirement specification. Results were presented in the paper. Social Techniques: Dashboard There were two communication methods described in the paper, text-based asynchronous communication and synchronous video-conferencing communication. Regarding our research topic, we only consider asynchronous communication to be categorized. Asynchronous communication described in the paper utilized the Internet Based Inspection System (IBIS)*. This tool enables stakeholders to post messages and vote for requirements. Therefore, we include this paper in the dashboard social technique. Social Connectivity: Designated The paper described the collaboration tool that supported asynchronous communication between developers in requirement negotiations. According to the paper, this tool was specifically used to support requirement negotiation between stakeholders especially in a distributed environment. Therefore, we include this paper in the designated connectivity. Social Interaction: Many-to-many Considering the asynchronous communication mode described in the paper, we include the interaction between stakeholders into the many-tomany interaction. This is due to the messages posted in IBIS to communicate between developers in requirement negotiations. Social Location: Distributed The paper explicitly described that the communication modes used by the team projects, based on the case study, were to assist distributed environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Conversation, and Sharing The paper described the text-based asynchronous communication mode to support collaborative requirement negotiations between stakeholders in a distributed environment. We include this study in several honeycomb blocks. Conversation represents the communication that occurs between stakeholders through messages in IBIS. Furthermore, Sharing represents the information exchange between stakeholders in order to resolve uncertainties in the requirements.

173

Paper Title: Authors Affiliations Publication

Leveraging Collaborative Technologies in the IO Requirements Process : Recio, R., Salzberg, C., Palm. J., and Machuca, C. : IBM : Proceedings of the 16th IEEE International Requirements Engineering Conference, RE 2008, Barcelona, Catalunya, Spain Publication Year : 2008 Origin of the Paper : USA Summary: The paper provides a report of team collaboration in developing the IBM's Systems IO and Data Center Networking (DCN). The most important team in the process is the IO Technical Community (IOTC) that mainly supports the interaction across other teams in the project. This paper described the technologies used by IOTC to provide such support, including further suggestions to leverage the use of IOTC. Criteria: Areas of Study: Requirements/Specifications The paper explicitly described the process of collecting requirements and turning them into product. A number of teams that operate collaboratively, supported by the IOTC, conducted this process. Therefore, we include this paper in the requirements/specifications area of study. Research Type: Evaluation The paper presents an overview of a process conducted by a number of collaborative teams in turning requirements into product. It described the teams involved in the process and emphasized the most significant team that supported the collaboration. Several conclusions were derived from the performance of IOTC to leverage further collaboration process. Form of Study: Observation The paper described the authors' observation regarding the process of changing requirements into product of the IBM's Systems IO and Data Center Networking (DCN). It described the process including the collection of requirements and the collaboration performed by teams involved in turning the requirements into product. Social Techniques: Instant Messaging, Blog/Microblog, Dashboard, and Email/Alert The paper described one of the most important team, IOTC, which supports the collaboration between other teams in changing requirements into product. It also described the tools used by IOTC in providing the support. We categorize the tools used by IOTC including dashboard (teamrooms), emails (blue groups), instant messaging, and blogs/microblogs (wiki). Social Connectivity: Designated The paper described tools used by IOTC to support collaboration between teams in changing requirements into product. Although most of the tools used by the IOTC are adapted from public tools, they were specifically built to support the project collaboration. Therefore, we include this paper in the designated tools social connectivity. Social Interaction: Mixture Considering the types of social techniques used to describe the communication that occurs between teams in the project collaboration, we conclude that the social interaction that occurs is a mixture social interaction. More than one type of social interaction applied to the social techniques mentioned above. Social Location: Localized The paper did not explicitly describe the social location covered by the IOTC. However, considering the authors' observation in the IBM's Systems IO and Data Center Networking (DCN), we conclude that IOTC only covers localized social location within the IBM development center. Honeycomb framework: Identity, Conversation, Sharing, Presence, and Groups Considering a number of types of social techniques used by the IOTC to provide the support, we classified the techniques into several blocks of honeycomb framework. Identity represents the user profile of the peers or leaders. Conversation and Sharing presents the communication in instant messaging and dashboard. Presence was represented in blogs/microblogs posted by developers to support other developers. Furthermore, Groups presents the communities formed by mailing list.

174

Paper Title: Authors Affiliations

A Web Platform for Social Requirements Engineering : Lohmann, S., Dietzold, S., Heim, P., and Heino, N. : University of Duisburg, Germany University of Leipzig, Germany Publication : Proceedings of the Software Engineering 2009 - Workshop Band, Conference of the GI Department of Software Engineering, Kaiserslautern, Germany Publication Year : 2009 Origin of the Paper : Germany Summary: The paper introduced a web platform that adopts the concept of social software engineering to support collaboration and knowledge sharing in a distributed environment, in order to address requirement engineering. The objective of this platform is to enable collection, discussion, development, and structuring of software requirements in a large group of stakeholders. Description of the overview and the features offered by the web platform is presented in the paper. Criteria: Areas of Study: Requirements/Specifications The paper described the overview of the web platform and its features that utilizes the social software engineering. This web platform offers lightweight support for social requirements engineering through collaborative collection, discussion, and classification. Therefore, we include this paper in the requirements/specifications area of study. Research Type: Philosophical The paper explicitly introduced a web platform that utilizes social software engineering to support collaborative requirement engineering. This platform adopts several social software including Wiki and Tags to enrich its support for assisting requirement engineering. There is no specific tool introduced within this paper. However, the web platform could be used as a framework for further collaboration tool development. Form of Study: Experiment The paper provided a description of the overview and features adopted by the web platform, including several existing studies that became the background of this study. However, the paper presented a screenshot that suggested the web platform was experimented to identify its usefulness as described in the paper. Therefore, we include this paper as an experimental form of study. Social Techniques: Wiki and Tag The paper states that several features adopted by the web platform were derived from social software engineering. These techniques include the concept of Wiki and Tags, where it provides the ease of use for collaborative work in requirement engineering. The stakeholders used the concept of Wiki to enter new requirements, edit existing requirements, and define the relation between requirements. Furthermore, Tags were used to collaboratively assigned keywords for requirements. Therefore, we include this paper in the Wiki and Tags social techniques. Social Connectivity: Designated The paper introduced the web platform to support collaborative work in a distributed environment where it utilized the social software engineering. This platform is specifically designed to assist stakeholders in requirements engineering. Therefore, we include this paper in the designated connectivity. Social Interaction: One-to-many and Many-to-many Considering the nature of the social technique described in the paper, we include this paper in one-to-many and many-to-many interaction. Wiki enabled both interactions through web content publication that is available for other stakeholders including through stakeholders feedback. Furthermore, Tags enable a one-to-many interaction through specific wordings to assist requirement definition for other stakeholders. Social Location: Distributed The paper stated that the main objective of the web platform is to support collaborative work in requirement engineering at a large and distributed environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Conversation, Sharing and Presence The paper introduced the web platform to assist collaborative work in requirement engineering. We include this paper in several honeycomb blocks. Identity represents the stakeholder profile involved in the requirement process. Conversation represents the communication that occurs between stakeholders through feedback and web content. Sharing represents the information exchange between stakeholders throughout the requirement process. Furthermore, Presence represents the availability of other stakeholders to get involved in the requirement process.

175

Paper Title: Authors Affiliations

Colaba: Collaborative Design of Cross-Organizational Processes : Chopra, A. K. and Singh, M. P. : University of Trento, Italy North Carolina State University, USA Publication : Proceedings of the Requirements Engineering for Systems, Services and Systems-of-Systems (RESS) Workshop, Trento, Italy Publication Year : 2011 Origin of the Paper : Italy and USA Summary: The paper proposed a new method to support collaboration in designing a cross-organizational process. Colaba accommodates requirements from multiple stakeholders by using and maintaining a repository for business protocols. Through this repository, stakeholders communicate via discussion with each other to design a collaborative business process. The paper also reported an evaluation of Colaba through a case study. Criteria: Areas of Study: Requirements/Specifications The paper introduced Colaba to support communication between stakeholders in order to design the business process collaboratively. Certain requirements need to be identified with Colaba to support the design. Therefore, we include this paper in the requirements areas of study. Research Type: Solution and Evaluation The paper introduced Colaba as a new method to collaborate stakeholders into designing business process. Then, the paper evaluates the features of Colaba through the discursive communication and the repositories. The result showed that a mutual agreement was achieved using Colaba between two different stakeholders. Form of Study: Case Study The paper used a case study of two different stakeholders collaborating into designing business process. A series of argumentations and designing steps from both stakeholders were described in the paper. Social Techniques: General Concept The paper did not explicitly describe the type of social technique used in the communication between the stakeholders. However, the communication occurred through the repositories where it stores the argumentation and the design of the latest business process. Social Connectivity: Designated The paper explained that Colaba is specifically built to support collaborative business process design. Therefore, we include this paper in the designated social connectivity. Social Interaction: One-to-one The paper explicitly described through the case study that the communication that occurs between the stakeholders was performed through the repository. Therefore, each communication is a one-to-one interaction via the repository. Social Location: Distributed The paper described that the Colaba method is used to support cross-organizational collaboration processes. Although the locations of the organizations are not mentioned in the paper, we assume that Colaba is applicable for organization that are distributed in location. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversation and Sharing The paper emphasized the use of repository to support argumentations between the stakeholders. This kind of communication represents the conversation and sharing blocks of the honeycomb framework.

176

Paper Title: Authors Affiliations Publication

StakeCloud: Stakeholder Requirements Communication and Resource Identification in the Cloud : Todoran, I. : University of Zurich, Switzerland : Proceedings of the Doctoral Symposium in the 20th IEEE International Requirements Engineering Conference (RE), Chicago, IL, USA Publication Year : 2012 Origin of the Paper : USA Summary: The paper proposed the concept of a cloud service marketplace to address both customers and providers for cloud services that best meet their needs. This paper also introduced the platform proposed for the customer, a cloud service marketplace, and provider interaction. Although the concept is still in the preliminary stage, it claimed that it would benefit both customers and providers. Criteria: Areas of Study: Requirements/Specifications The paper introduced the cloud service marketplace as a community platform that could change the customer's needs into requirements for the benefit of the providers. Therefore, we include this paper in the requirements area of study. Research Type: Solution The paper proposed a concept of cloud service marketplace to accommodate user's needs to search for a cloud service that best meet their needs. Furthermore, in the concept, providers will be able to turn these needs into requirements to meet their benefits. Form of Study: Literature Review The research in the paper is still in the preliminary stage. It has proposed a platform for the blueprint of the customer, cloud service marketplace, and provider interaction. However, as mentioned in the paper, the author is conducting a further literature review to support this method. Social Techniques: Dashboard The paper did not explicitly describe the type of social technique used in supporting communication on the platform. However, the paper proposed a dynamic interface to facilitate both user and provider in searching for the cloud service. Therefore, we include this paper in the dashboard social technique. Social Connectivity: Designated Considering that the paper has only proposed a platform without any tool attached, we conclude that a designated tool is included in the vision. Therefore, we include this paper in the designated social connectivity. Social Interaction: One-to-many The paper proposed a cloud service marketplace platform that could support both users and providers. This means that the platform act as one source in supporting many users and providers. Therefore, we include this paper in the one-to-many interaction. Social Location: Distributed Considering that the platform proposed in the paper is a cloud service, a distributed social location is supported. Therefore, we include this paper in the distributed social location. Honeycomb framework: Identity and Sharing The research in the paper has not yet reached a mature stage. In this preliminary stage, we conclude that the cloud service marketplace has only represented the identity and sharing blocks from the honeycomb framework. Identity represents the user or provider that uses the marketplace and sharing represents the information exchange occurs in the marketplace.

177

Paper Title: UDesignIt: Towards Social Media for Community-Driven Design Authors : Phil Greenwood, Awais Rashid, and James Walkerdine Affiliations : Lancaster University, UK Publication : 34th International Conference on Software Engineering ICSE Publication Year : 2012 Origin of the Paper : UK

Summary: The authors present the UDesignIt platform that combines social media technologies with software engineering concepts to empower communities to discuss and extract high-level design features. It combines natural language processing, feature modelling and visual overlays in the form of “image clouds” to enable communities and software engineers alike to unlock the knowledge contained in the unstructured and unfiltered content of social media where people discuss social problems and their solutions. Criteria: Areas of Study: Requirements/Specification, Design The social media platform presented in this paper, UDesignIt, aims to overcome these limitations by enabling communities to not only discuss problems but also to identify their own solutions Research Type: Solution The paper proposes a platform for the software related activities. Form of Study: Non-empirical The authors propose a system at early stages of deployment. Social Techniques: General Concept The authors use different social media techniques to gather their related data. Social Connectivity: Designated UDesignIt is a specific social computing tool. Social Interaction: Mixture The authors propose different types of social media and thus different types of social interactions are possible. Social Location: Not Acknowledged The authors do not specify the scope of the region. Honeycomb Framework: Identity, Conversations, Sharing, Presence, Relationship, Reputation, Groups The authors benefit from all social media techniques and interactions, thus all social aspects are present.

178

Paper Title: Authors Affiliations Publication

Experiences in Distributed Software Development with Wiki : Al-Asmari, K. R. and Yu, L. : Indiana University South Bend, IN, USA : Proceedings of the International Conference on Software Engineering Research and Practice, SERP 2006, Volume 1, Las Vegas, Nevada, USA Publication Year : 2006 Origin of the Paper : USA Summary: The paper proposed a method of using social media especially Wiki to provide support for collaboration among team members in a software development environment. Furthermore, the paper also provided the authors' experience in utilizing Wiki at a software development project. Several benefits from utilizing Wiki were identified as described in the paper, including the collaboration process by using Wiki. Criteria: Areas of Study: Requirements/Specification, Distribution, Maintenance, and Enhancement and Management The paper described the use of Wiki as identified through the experience of the authors. Several of those benefits includes creating and coediting project plan and documentation, task assignments, brainstorming, status progress, etc. However, the main usage of Wiki in the project was to enable collaborative document editing and provide display for tracking service. Therefore, we include this paper in the areas as mentioned above. Research Type: Solution and Experience The paper proposed a method to support collaboration and communication among team members in software development environment. Wiki were introduced to communicate, coordinate, and develop concept collaboratively. Furthermore, the paper described the authors' experience in utilizing Wiki for a software development project. Form of Study: Experiment and Observation The paper described the authors' experience in utilizing Wiki for a software development project at the Indiana University South Bend. Collaborative processes were recorded throughout the usage and were presented in the paper. This paper also identified several benefits and challenges from utilizing Wiki through a real-world software development project. Social Techniques: Wiki The paper mentioned several social techniques used in providing support for communication and collaboration among team members in the software project case study. However, the paper described that the team members utilized Wiki as their main communication tool. Therefore, we include this paper in the Wiki social technique. Social Connectivity: Adapted The paper described how Wiki was used for communication and collaboration between team members in the software development environment. The concept of Wiki was publicly available, was adopted by the case study, and was specifically designed to support communication in the case study. Therefore, we include this paper in the adaptive connectivity. Social Interaction: Many-to-many Considering the social technique discussed in the paper, we include this paper as a many-to-many interaction. Co-editing enabled by Wiki allowed users to edit web content collaboratively. Social Location: Distributed Research in the paper showed that Wiki enabled users to edit Web page content from anywhere at any time through the internet. This means that Wiki supports distributed software development environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Sharing, Presence, and Groups The paper described the use of Wiki to provide support for collaboration between team members in a software development environment. We include this paper in several honeycomb blocks. Identity represents the user profile of other member in the team that performed co-editing. Sharing represents the information provided through the web page performed collaboratively by the team members. Presence represents the availability of other team members to provide information and edit the web content, and Groups represents the different co-editing groupings available through wiki.

179

Paper Title: Authors Affiliations

A Socio-Technical Framework for Supporting Programmers : Ye, Y., Yamammoto, Y., and Nakakoji, K. : University of Colorado, Boulder, USA University of Tokyo, Japan SRA Key Technology Lab, Tokyo, Japan Publication : Proceedings of the 6th joint meeting of the European Software Engineering Conference and the ACM SIGSOFT International Symposium on Foundations of Software Engineering, Dubrovnik, Croatia (Developer-centric studies) Publication Year : 2007 Origin of the Paper : USA and Japan Summary: Building a bridge between programmers and their resources is important to support the software development lifecycle. This paper thus proposes a conceptual STEP_IN framework to serve as that bridge. It supports communication between programmers who are seeking information. It also serves as a socio-technical relationship consisting not only of communication but also exchange in code, documents and relevant information regarding other programmers. Criteria: Areas of Study: Coding and Distribution, Maintenance, and Enhancement STEP_IN envisions the information exchange in code, documents, and support communication between programmers. It encompasses the areas of coding with documents and code exchange where it builds the programming environments. It also supports project maintenance by providing information space for bug reports and management logs. Research Type: Philosophical and Evaluation This paper introduces STEP_IN as a new framework to be the foundation for collaboration and communication among programmers. The framework is anticipated to increase the effectiveness of information exchange by redirecting search to the right place or person hence minimizing any negative impact to the team. An initial assessment of the framework was performed through the Java community to facilitate a Java class library information exchange. Form of Study: Observation The paper stated that in order to assess the feasibility of STEP_IN framework, the authors developed the SIJ to help programmers gather information related to Java class libraries. However, it did not mention the form of study used to assess SIJ. Therefore, we include this paper in the observation form of study due to the description provided in the paper related to how the programmers used SIJ. Social Techniques: Emails/Alerts and Crowd sourcing STEP_IN uses interface to perform search queries and present the search results. We include this as crowdsourcing due to its connectivity towards every other programmer where they can post comments and retrieve information mediated by the interface. However, for further search query, it requires sending messages to the experts in which we included as emails/alerts. Social Connectivity: Designated STEP_IN framework is designed specifically to facilitate communication and collaboration between programmers in a software development environment. Social Interaction: One-to-many Every search for information performed by a programmer is redirected by STEP_IN to the identified capable group of peers. Messages containing the search query will be sent to each member of that group thus consequently established as a forum. This means that other members within that group, including the programmer who searched for the information, will receive further replies. Social Location: Distributed It is mentioned in the paper that the focus study of social aspect in the STEP_IN framework is different from the social coordination in geographically distributed environment. However, it described one of STEP_IN features that enable information sharing even without the developers knowing each other. Therefore, we include this paper into distributed social location. Honeycomb Framework: Conversation, Sharing, Groups, and Reputation The paper introduced STEP_IN framework that emphasized the importance of peer review. Considering the type of social techniques used to support peer communication, we include this paper in several blocks of honeycomb framework. Conversation and Sharing represents the communication between peers while Groups and Reputation represents peer's rank within the community.

180

Paper Title: Authors Affiliations

Publication

Publication Year Origin of the Paper

The Impact of Social Media on Software Engineering Practices and Tools : Storey, M. A., Deursen, A., and Cheng, L. : University of Victoria, BC, Canada Delft University of Technology, Delft, Netherland IBM TJ Watson Research Lab, Cambridge, USA : Proceeding of the Workshop on Future Software Engineering Research, FoSER 2010, at the 18th ACM SIGSOFT International Symposium on Foundation of Software Engineering, 2010, Santa Fe, USA (Position papers) : 2010 : Canada, Netherland, and USA

Summary: This paper described the importance of social media in supporting software engineering including the benefits, risks, and challenges that occurs from implementation. It also present descriptions of current social media used in public and how to derived powerful tools from utilizing it. Criteria: Areas of Study: Management This paper discussed a wide area of software development with the potential of using social media as a collaborative mediator to communicate and share knowledge. Therefore, we include this study in the management area of study. Research Type: Opinion It is explicitly mentioned that this paper is a position paper where it introduces the importance of implementing social media to support software engineering. Form of Study: Non-empirical The paper did not provide any empirical study. Social Techniques: General Concept Various types of social media were discussed in this paper, each with its own benefits and challenges. Therefore, it encompasses every criterion in this specific category. Social Connectivity: Public Every tool and application discussed in this paper was used in public. Social Interaction: Mixture Due to the various types of social media discussed in this paper, the combination of the tools and applications used in public covers the mixture of social interaction. Social Location: Distributed The paper did not explicitly mention the distribution of the users. However, we can conclude, from the public tools and applications that were discussed, that the user of these tools and applications are widely distributed. Honeycomb Framework: Identity, Conversation, Sharing, Presence, Relationship, Reputation, and Groups The paper provides a general discussion of social media in software engineering. Various types of social media were classified and presented for their use in supporting software engineering. Therefore, we include this paper in the honeycomb blocks as mentioned above.

181

Paper Title: Authors Affiliations Publication

Effective Communication of Software Development Knowledge Through Community Portals : Treude, C. and Storey, M. : University of Victoria, BC, Canada : SIGSOFT/FSE'11 19th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-19) and ESEC'11: 13th European Software Engineering Conference (ESEC-13), Szeged, Hungary Publication Year : 2011 Origin of the Paper : Canada Summary: Community portals were recently used as a mediator for various communication channels that served as a place for developers to collaborate. This paper presents a study of one of the first closed community portals called IBM Rational Team Concert. A series of interviews were conducted to obtain clear descriptions on how the community portals were used. From the result, advice is given for managers and developers to exploit the effective use of community portals. Criteria: Areas of Study: Management This paper focused on the use of community portals to leverage communication between developers and customers. However, the discussion affects a wide area of software engineering with its use to manage the software development. Therefore, we categorize this paper in the area of management. Research Type: Solution and Evaluation The paper proposed a concept of community portal to support communication between developers. The community portals adopted several types of social media with the aim of encouraging developers to contribute and communicate. Furthermore, the paper also presented research of how developers communicate using portals. Form of Study: Case Study The research presented in the paper conducted a case study of RCT team at IBM. To assess the communication between developers, data was collected from 150 distributors in about 30 functional teams. A complete result to address several important questions was presented in the paper. Social Techniques: Dashboard The paper proposed a concept of community portal to support communication between developers. This method combines several social techniques to encourage developers to share and communicate. Several adopted social techniques including blogs, forums, wikis, mailing list, etc. Therefore, we include this paper in the dashboard social techniques. Social Connectivity: Designated IBM RCT was developed for a closed software project. This means that the tool itself is not open to the public and is limited only to related people. Therefore, it is included as designated tools. Social Interaction: Mixture Various channels of communication included in the community portals serve various social interactions. It enables a one-to-one interaction through instant messaging or emails, up to many-to-many interaction through forums and wikis. Therefore, the social interaction discussed in this paper is a mixture. Social Location: Distributed It is stated in the paper that the members of IBM RCT were located in 15 different locations, the main locations being North America and Europe. This means that IBM RCT enables distributed communication and collaboration. Honeycomb Framework: Identity, Conversation, Sharing, Presence, and Groups The concept of the community portal presented in the paper is a combination of several social techniques to support communication between developers. These techniques were represented by several blocks of honeycomb. Identity represents the user profile from blogs, Conversation and Sharing represents communication, Presence represents the availability of other developers to supply information, and Groups represents the crowd within forums.

182

Paper Title: Authors Affiliations

A Survey of Social Media Use in Software Systems Development : Black, S., Harrison, R., and Baldwin, M. : University of Westminster, London, UK Oxford Brookes University, Oxford, UK Publication : Proceedings of the 1st International Workshop on Web 2.0 for Software Engineering (Web2SE) 2010, Cape Town, South Africa Publication Year : 2010 Origin of the Paper : UK Summary: The paper reported an empirical research survey to identify the use of social media in global software development. This survey was aimed at determining which social media were used by software developers and how social media assists in software developing. Results from the survey were presented in the paper. Criteria: Areas of Study: Requirements/Specifications, Design, Coding, and Distribution, Maintenance, and Enhancement The paper presented a study that investigated the use of social media in global software development. The result showed that social media were used to communicate technical information, including source code samples, specification and design, and brainstorming for new ideas. Therefore, we include this paper in the Requirements/Specifications, Design, Coding, and Distribution, Maintenance, and Enhancement areas of study. Research Type: Evaluation The paper presented an evaluation of the use of social media systems, especially in a global software development environment. The research was conducted through survey and description of the evaluation activities were presented in the paper. Form of Study: Case Study The paper described the case study used to conduct the survey. The survey was carried out online in respond to a Twitter request made by one of the authors. The survey received a number of respondents that supported some interesting findings. Results were presented in the paper. Social Techniques: Blog/Microblog and Instant Messaging Research in the paper identified the use of social media in global software development. Based on the research result, there were several techniques used by the respondents (in several cases a single developer uses more than one technique). However, the result showed that Twitter (blogs/microblogs) and instant messaging are the most popular technique used by the developers. Social Connectivity: Public The paper reported a survey to identify the use of social media in global software development. This research investigates the tools used by developers in supporting communication. The result showed that the tools used by the developers were public tools. Social Interaction: Mixture Considering the social techniques used and described in the paper, we conclude that social interaction that occurs between these techniques includes a mixture interaction. Therefore, we include this paper in the mixture interaction. Social Location: Distributed The paper explicitly stated that the main aim of the survey was to identify the use of social media in global software development. Therefore, we include this paper in the distributed location. Honeycomb framework: Conversation, Sharing, and Presence The paper presented a survey to identify the use of social media in global software development. We include this research in several honeycomb blocks. Conversation represents the communication that occurs between developers through the selected social media. Sharing represents the information exchange to support collaboration between developers. Furthermore, Presence represents the availability of other developers through the social media.

183

Paper Title: Authors Affiliations

From Collective Knowledge to Intelligence: Pre-Requirements Analysis of Large and Complex Systems : Liang, P., He, K., Avgeriou, P., and Xu, L. : Wuhan University, China University of Groninger, The Netherlands Bournemouth University, UK Publication : Proceedings of the 1st International Workshop on Web 2.0 for Software Engineering (Web2SE) 2010, Cape Town, South Africa Publication Year : 2010 Origin of the Paper : China, The Netherlands, and UK Summary: The paper proposed a framework to address challenges that arise from pre-requirements analysis in a large and complex system through the intelligence and technologies of Web 2.0, including wiki, tags, and semantic web. The framework was composed from three steps, including collecting requirements through collaborative tagging, transforming collected tags into requirement ontology, and support decision making based on the ontologies through reasoning. Description of the use of this framework was presented in the paper. Criteria: Areas of Study: Requirements/Specifications The paper explicitly proposed a framework to support and improve pre-requirements analysis in a large and complex system by utilizing Web 2.0 technologies. This method collects, filters, and assists decision making for determining requirements. Therefore, we include this paper in the requirements/specifications area of study. Research Type: Philosophical Research in the paper proposed a framework to support pre-requirements analysis without actually proposing a tool. The paper discuss the utilization of Web 2.0 technologies to assist pre-requirements collection thus filter them using ontology and support decision making to determine requirements. Background and arguments towards the proposition of this method were presented in the paper. Form of Study: Non-empirical The paper presented a research of existing studies through literature review to support the proposed framework. Challenges that need to be addressed by the framework were derived from these studies. Furthermore, the paper described the mechanism of the framework to support pre-requirement analysis. Social Techniques: Tag The paper described three steps included in the framework to provide support for pre-requirement analysis. Tags were used in the first step of the framework in order to collect the pre-requirement analysis from stakeholders. Although the paper also mentioned that the mechanism for the stakeholders to document these tags was through utilizing wiki, we only include this paper in tag social technique because the main technique presented in the framework is through tags. Social Connectivity: Designated, Adapted, and Public Considering the method proposed in the paper was a framework to support pre-requirement analysis, we conclude that there could be various types of connectivity build utilizing this framework. Therefore, we include this paper in the social connectivity as mentioned above. Social Interaction: One-to-many The paper proposed a framework to support pre-requirement analysis by utilizing Web 2.0 technologies, especially tagging. We include tag assigning to requirement statements into a one-to-many interaction. Social Location: Distributed The paper did not explicitly describe the use of this framework to provide assistance only for distributed environment. However, it mentioned that one of challenges addressed to be answer by this framework was to support communication requirements in a large and distributed complex system. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity and Sharing The paper proposed a framework that supports pre-requirement analysis to assist collaborative decision making towards requirements. We include this framework in several honeycomb blocks. Identity represents the acknowledgment of other user's profile in providing tags for requirements. Sharing represents the information exchange between stakeholders through tagging.

184

Paper Title: Authors Affiliations Publication

Supporting the Cooperation of End-User Programmers through Social Development Environments : Singer, L. and Schneider, K. : Leibniz Universitat Hannover, Germany : Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering (Web2SE) 2011, Waikiki, Honolulu, Hawaii Publication Year : 2011 Origin of the Paper : Germany Summary: The paper presented a literature study and investigation of the use of social software together with Communities of Practice in supporting software development for end-user software engineers. The approaches were aimed at bringing end users together to share experience and help one another with the expectation of elevating the quality of the product. Several methods utilizing social software to build relationship between developers and to motivate contribution of the developers were presented in the paper. Criteria: Areas of Study: Coding, Distribution, Maintenance, and Enhancement, and Management The paper described several types of social software used to support knowledge sharing between end user software engineers in Communities of Practice. This Communities of Practices enables end users and developers that have the same interest to gain and share information among themselves. It is also the most important tool for knowledge management in a distributed development environment. Therefore, we include this paper in the coding, distribution, maintenance, enhancement, and management. Research Type: Philosophical The paper presented a number of criteria needed to build a tool to support Communities of Practices. This tool was designed to utilize social software in providing support for information exchange between developers. These criteria were derived from the literature study to address the needs for building the collaboration tool. A set of frameworks for further development was introduced in the paper. Form of Study: Literature Review The paper described a number of existing studies that discussed the use of social software to support collaborative work. These studies were used to investigate how social software could be used for supporting end user software programming. A thorough investigation was provided in the paper. Social Techniques: Wiki, Social Networking, Blog/Microblog, and Crowd sourcing The paper discussed several social software types that could be used by end user programmers in supporting their work. We categorized these social techniques into several criteria as mentioned above. Social Connectivity: Adapted The paper described the social techniques that could be used to support the work of the end user programmers. This includes the adoption and adaptation of social software to build the collaborative framework. Considering the social techniques described in the paper, we include this paper in the adaptive connectivity. Social Interaction: Mixture Considering various social techniques described in the paper, we concluded that this study encompasses several social interactions, including one-to-one, one-to-many, and many-to-many interactions. One-to-one interaction derived from comment posting directed to the post owner. One-to-many interaction derived from micro blogging post or through wiki. Furthermore, many-to-many interaction derived from crowd sourcing through forum discussion. Social Location: Mixture The paper did not explicitly describe the location spread to be encompassed by this framework. However, the paper mentioned that the spatial location together with being socially connected is less important. Therefore, we include this paper in the mixture social location to encompass both locations. Honeycomb framework: Identity, Conversation, Sharing, and Presence The paper described a framework derived from combining social software together with Communities of Practice to build knowledge sharing between end user developers. We include this study in several honeycomb blocks based on the features adopted by the framework. Identity represents the user profile in the community to provide a sense of comfort. Conversation and Sharing represents the communication and information exchange that occurs between developers through social software. Presence represents the availability of other developers in providing information through wiki, micro blogging post or answering in forums.

185

Paper Title: Authors Affiliations Publication

Wikigramming: A Wiki-based Training Environment for Programming : Hattori, T. : Keio University Kanagawa, Japan : Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering (Web2SE) 2011, Waikiki, Honolulu, Hawaii Publication Year : 2011 Origin of the Paper : Japan Summary: The paper proposed a tool that utilized Wiki combined with any programming language to provide support for collaboration between developers. Each page in Wikigramming contains source code that users were able to edit. To avoid destruction of source code, every modified version needs to pass unit tests written by other developers. Architecture and features of Wikigramming were presented in the paper. Criteria: Areas of Study: Coding and Distribution, Maintenance, and Enhancement The paper presented a description of functionality offered by Wikigramming. The main function of this tool is to provide a collaboration environment for software development, emphasizing code programming. Therefore, we include this paper in the areas of coding and distribution, maintenance, and enhancement. Research Type: Solution The paper proposed a tool that supports collaboration between developers by utilizing Wiki. Wikigramming displays source code and enable users to edit them collaboratively in order to improve the code. Furthermore, Wikigramming provides facilities to write and modify code and documents, view other users' code, and instantly recognize of any changes made. Form of Study: Non-empirical The paper explicitly described that Wikigramming is currently still a prototype and that there were no empirical study towards the tool presented in the paper. Although it provided the architecture and list of features adopted by Wikigramming, we include this paper into nonempirical form of study. Social Techniques: Wiki The paper focused its study in the use of Wiki combined with other programming language to provide support among developers. Through Wikigramming, a more casual collaborative method was introduced and was expected to meet the needs for collaboration tool. We include this paper into Wiki technique. Social Connectivity: Adapted The paper described the adoption of Wiki to provide a lightweight tool in supporting collaboration between developers. Wikis, such as Wikipedia, are a public document oriented project that enable users to edit and improved the content on each page. This paper adopted Wiki to provide Wikigramming for developers by implementing its basic concept. Social Interaction: Many-to-many Considering the technique used in Wikigramming, we include this paper in the many-to-many interaction. This is due to the ability of Wiki pages to be edited by users and provide information for other users at the same time. Social Location: Distributed The paper did not explicitly describe the area covered by the proposed tool. However, considering the basic concept of Wiki and its implementation through the web, we include this paper in the distributed location. Honeycomb framework: Sharing and Presence The paper proposed Wikigramming that adopted Wiki in providing support for software development. We include this tool in several honeycomb blocks. Sharing represents the information exchanged between developers through the Wiki page. Furthermore, Presence represents the availability of other developers in modifying codes displayed through the Wikigramming.

186

Paper Title: Mobilis - Comprehensive Developer Support for Building Pervasive Social Computing Applications Authors : Daniel Schuster, Robert Lübke, Sven Bendel, Thomas Springer, Alexander Schill Affiliations : Technische Universität Dresden Publication : PIK-Praxis der Informationsverarbeitung und Kommunikation Publication Year : 2013 Origin of the Paper : Germany

Summary: The Mobilis framework provides developer support for mobile social apps (native Android and HTML5), a service environment for dynamic deployment of services, authentication and robust communication over unreliable networks as well as an emulation environment to be able to mimick user behavior and to test applications in a lab environment before field tests. Criteria: Areas of Study: Software/Program Verification It provides an emulation environment to be able to mimick user behavior and to test applications in a lab environment before field tests. Research Type: Solution Mobilis is proposed by the authors as a solution. Form of Study: Case Study The paper proposes a demo. Social Techniques: Social Networking The tool is available on GitHub. Social Connectivity: Designated The authors design Mobilis as a tool on GitHub. Social Interaction: Many-to-Many The nature of the tool on GitHub allows for many-to-many interactions. Social Location: Distributed GitHub allows for distributed location. Honeycomb Framework: Identity, Conversations, Sharing, Presence These elements are present.

187

Paper Title: Authors Affiliations

Communication Tools for Distributed Software Development Teams : Thissen, M. R., Page, J. M., Bharathi, M. C., and Austin, T. L. : RTI International, NC, USA RTI International, FL, USA RTI International, Bangalore, India RTI International, GA, USA Publication : Proceedings of the 2007 ACM SIGMIS CPR Conference on Computer Personnel Research 2007, April 19-21, 2007 Publication Year : 2007 Origin of the Paper : USA and India Summary: The paper presented research of a communication tool for collaboration in a distributed software development environment. Three case studies were discussed relating to communication tools used in each study to provide collaboration support. Tools described in the paper allowed team members to work collaboratively to produce software and data products through distributed locations. The research result showed positive feedback for globalization work environment. Criteria: Areas of Study: Requirements/Specifications, Design, Software/Program Verification, and Management The paper presented several case studies to identify the use of communication tools in supporting the work of these teams. Each case study described the areas of study supported by various communication tools to build collaboration environment. These areas are included in the requirements/specifications, design, software/program verification, and management. Research Type: Evaluation The paper described researches to identify types of communication utilized by teams described in the case study. Each communication tool was investigated for its usefulness in providing collaboration support. Results from each team were presented in the paper. Form of Study: Case Study The paper conducted three case studies on three different projects at the non-profit research organization, RTI International. Each case was investigated to identify the types of communication tool used to provide support for their collaboration work. Investigation results were described in the paper. Social Techniques: Instant Messaging and Email There are several combinations of communication tools identified from the case studies. The complete result was presented in a table in the paper. Considering the relevancy to our topic research, we only include this paper in the instant messaging and email techniques. Social Connectivity: Public The paper presented the description of the types of communication tools used by the developers to support their collaboration. Based on the classification of the communication tools described in the paper, we include this paper in public connectivity. Social Interaction: Mixture Considering the classification that we assigned to the social techniques as described in the paper, we include this study in the mixture interaction. Instant messaging and email enables both one-to-one interaction and one-to-many interaction. Furthermore, both techniques also enable the many-to-many interaction through group chat and mailing list. Social Location: Distributed Based on the case studies presented in the paper, the location of the team members were described as scattered into several different locations. Therefore, we include this paper in the distributed location. Honeycomb framework: Conversation, Sharing, and Presence The paper described the types of communication tools used by team members in different case studies to support communication and collaboration among distributed environment. We include this research in several honeycomb blocks. Conversation represents the communication that occurs between members of the team. Sharing represents the information exchanged through the communication tools. Furthermore, Presence represents the availability of other team members for collaboration process.

188

Paper Title: Authors Affiliations Publication

Del.icio.us Development Tools : DeLine, R. : One Microsoft Way, Redmond, WA, USA : Proceedings of the International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : Germany Summary: The paper proposed a tool designed to assist developers in answering their information needs through the concept of social bookmarking and tagging. Del.icio.us is a social bookmarking website that offers incentives for users when entering data and provides value by combining data from different users. Using the principle of social bookmarking, the author suggests designing a tool that would enable collective knowledge to increase performance and effectiveness. Criteria: Areas of Study: Coding, Distribution, Maintenance, and Enhancement, and Management The paper discussed a suggestion to build a collaboration tool to increase developers' performance through collective knowledge. Knowledge managed by the proposed tool will be used to assist developers to complete their tasks and to increase their performance. Therefore, we include this paper in the coding, distribution, maintenance, and enhancement, and management areas of study. Research Type: Opinion The paper presented the author's suggestion, including background reviews in the current existing knowledge management tools. Benefits and challenges in implementing social bookmarking principle in building tools to support developer's collaboration were presented in the paper. Form of Study: Non-empirical The paper described existing websites that implemented the main principle of social bookmarking. The paper also described several similar existing tools but have not yet implementing the Del.icio.us principle. Social Techniques: Tag The paper described the main principle of Del.icio.us, and the author suggests building a collaboration tool that implements this principle. Del.icio.us utilized social bookmarking by associating it with a set of tags. Therefore, we include this paper in the tagging and bookmarking social techniques. Social Connectivity: Designated The paper proposed to build a tool that embodied the principle of Del.icio.us. This means that the future tool will implement Del.icio.us in the form of its principle and not the website itself. Therefore, we include this paper in the designated tools. Social Interaction: One-to-many The paper described the main principle of Del.icio.us, which is to accumulate collective knowledge by providing social bookmarking associated with a set of tags. This means that each time a user inputs a new bookmark described through tags, it would be available for other users as well. Therefore, we include this paper in the one-to-many social interaction. Social Location: Distributed The paper did not explicitly describe the location of the potential users of this suggested tool. However, considering the main principle of Del.icio.us that is available through the internet, we include this paper in the distributed social location. Honeycomb framework: Identity, Sharing, and Presence The paper suggested building a tool that would embody the principle of Del.icio.us through social bookmarking and tagging. From the principle, we include this paper in several honeycomb blocks. Identity represents the ability of a user to be discovered by other users through bookmarking and tagging records. Sharing represents the information exchanged through bookmarking and tagging. Furthermore, Presence represents the availability of other users to provide information.

189

Paper Title: Geo-Locating the Knowledge Transfer in StackOverflow Authors : Dennis Schenk, Mircea Lungu Affiliations : University of Bern, Switzerland Publication : International Workshop on Social Software Engineering Publication Year : 2013 Origin of the Paper : Switzerland

Summary: The authors analyze the transactions in Stack Over how we can get a glimpse of the way in which the different geographical regions in the world contribute to the knowledge market represented by the website. In this paper we aggregate the knowledge transfer from the level of the users to the level of geographical regions. Criteria: Areas of Study: Requirements/Specification, Design, Coding, Software/Program Verification, Distribution, Maintenance, and Enhancement Authors utilize StackOverflow website which encompasses all these activities. Research Type: Evaluation The authors investigate into existing data in StackOverflow. Form of Study: Non-empirical The authors use a non-empirical approach to find out most contributing regions. Social Techniques: Social networking The use of StackOverflow implies social networking. Social Connectivity: Public The authors use data from StackOverflow website. Social Interaction: Mixture StackOverflow allows for mixed social interactions. Social Location: Distributed Different regions are under study in this paper. Honeycomb Framework: Identity, Conversations, Sharing, Presence, relationship, Reputation, Groups StackOverflow allows for all these framework items.

190

Paper Title: Authors Affiliations Publication

Look Ma, No Email!: Blogs and IRC as Primary and Preferred Communication Tools in A Distributed Firm : Johri, A. : Virginia Tech, VA, USA : Proceedings of the 2011 ACM Conference on Computer Supported Cooperative Work, CSCW, Hangzhou, China Publication Year : 2011 Origin of the Paper : USA Summary: The paper presented a research on the use of social media, other than email, to improve coordination and knowledge sharing in a distributed software development environment. Research was conducted using a small company, through interview and survey. Several social media other than email were described in the paper as the most utilized tools for collaboration. Results from the research were presented in the paper. Criteria: Areas of Study: Coding, Distribution, Maintenance, and Enhancement, and Management The paper provided a research of the use of social media other than email in a distributed company. The paper described that social media such as instant messaging were used for communication, although it did not describe the areas of study discussed using instant messaging. Furthermore, it described the use of blog to share code that supported the areas of coding and maintenance. The paper also described the minimal use of email in supporting the managerial area. Research Type: Evaluation The paper presented a research of the use of social media in a small and distributed company to support collaboration. Several communication and collaboration utilizing social media were described in the paper, although the paper stated that the use of email was not primary. The study was aimed at identifying the environment described in the paper that functioned without using email. Form of Study: Case Study Research in the paper conducted the case study to identify the use of social media other than email that supports collaboration at a small and distributed company. Interviews and surveys were used to collect information related to the use of social media in the company. Result showed that informants prefers and utilizes blogs and instant messaging over other social media especially emails as presented in the paper. Social Techniques: Blogs and Instant Messaging The paper presented the result obtained from interviews and surveys of the conducted case study. It showed that the informants preferred blogs and instant messaging to share the collaborative experience. We include this paper into blogs and instant messaging social techniques. Social Connectivity: Adapted and Public The paper described the type of blogs used by the company as an internal blogging site. We include this as an adaptive connectivity. Furthermore, the paper also described Skype and IRC used by the informant for instant messaging. We include this in public connectivity. Social Interaction: Mixture Considering the types of social techniques discussed in the paper, we include this research into mixture interaction. One-to-one interaction was performed through Skype or other instant messaging as described in the paper. Furthermore, one-to-many and many-to-many interaction were supported through blogs. Social Location: Distributed The paper described the environment of the case study used in the research. It stated that the company has most of the employees located in a distributed fashion. Therefore, we include this paper in distributed location. Honeycomb framework: Conversation, Sharing, Presence, and Groups The paper described research towards the use of social media in a distributed company to support communication and collaboration. We include this research in several honeycomb blocks. Conversation represents the communication that occurs between developers through instant messaging. Sharing represents the information exchanged through blogs. Presence represents the availability of other employee showed through instant messaging or content update through blogs. Groups represents the different grouping blogs based on activity.

191

Paper Title: Authors Affiliations Publication

Smarter Social Collaboration at IBM Research (China) : Chi, C., Liao, Q., Pan., Y., and Zhiao, S. : IBM Research, China : Proceedings of the 2011 ACM Conference on Computer Supported Cooperative Work, CSCW, Hangzhou, China Publication Year : 2011 Origin of the Paper : China Summary: The paper presents various research projects developed by IBM in several different locations across the world. Projects in the paper were related to smart social collaboration, which allows principles and technologies of social collaboration to be shared between developers, in order to support communication and work performance. We divided the paper into several reviews due to the research difference and discussion. In this review, we summarized a project from IBM China. Criteria: Areas of Study: Management IBM China, in this paper, introduced Dandelion as a tool to manage collaboration between users based on content. Dandelion supports coauthoring in writing documents or shared information through wikis. It also uses tags to augment wikis by allowing user to specify co-authoring tasks. Research Type: Solution The paper introduced Dandelion to support collaborative authoring. Dandelion supports two roles: coordinators can insert tags and specifies tasks, and participants can become co-authors thus writing wiki content. Form of Study: Experiment The paper did not explicitly describe the experiment performed to identify Dandelion’s usefulness. However, the paper mentioned several pilot usages were observed and the results were reported. The results showed that four out of five pilot trials were successful, representing the usefulness of Dandelion. Social Techniques: Wiki, Tag, and Email/Alert The paper described the use of wikis and tagging in an earlier version of Dandelion. Tags were used to specify tasks by the coordinators and wiki were used to store information. However, due to the unpopularity of Dandelion after certain amount of time, Dandelion was improved by utilizing emails to support communication. Social Connectivity: Designated The paper introduced Dandelion to support content collaboration by using wikis, tags, and emails. Dandelion is specifically built to meet the user's needs of collaboration. Therefore, we include this paper in the designated tool connectivity. Social Interaction: Mixture Considering social techniques used by Dandelion, we assume that the social interactions applying to Dandelion is a mixture. One-to-one interaction applies to direct email communication, one-to-many interaction applies to broadcast emails, and tag and wiki share. Furthermore, many-to-many interaction applies also to wiki share. Social Location: Localized The paper explicitly stated that Dandelion has been deployed internally since April 2009. Therefore, we assumed that the internal deployment is a localized social location. Honeycomb framework: Conversation, Sharing, and Presence The paper described communication and information exchange supported by Dandelion. We include Dandelion in several honeycomb blocks. Conversation and Sharing represents email and tag communication between users. Sharing represents information exchange provided by wiki and tag, while Presence represents the co-authoring for wiki.

192

Paper Title: Can Social Awareness Foster Trust Building in Global Software Teams? Authors : Fabio Calefato, Filippo Lanubile, Francesco Sportelli Affiliations : University of Bari Publication : International Workshop on Social Software Engineering Publication Year : 2013 Origin of the Paper : Italy

Summary: The authors discuss building trust among developers with few or no chances to meet is an open issue. To overcome such a challenge, they hypothesize that increased social awareness may foster trust building in global software teams. Criteria: Areas of Study: Management The focus of the study is management of developers’ interactions. Research Type: Solution The authors developed SocialCDE, a tool that adds social awareness to Application Lifecycle Management (ALM) platforms. Form of Study: Case Study The authors present two different empirical studies, specifically designed to test their hypotheses. Social Techniques: General Concept The authors use a general concept of social techniques. Social Connectivity: Designated The authors developed SocialCDE, a tool that adds social awareness to Application Lifecycle Management (ALM) platforms. Social Interaction: Many-to-many The tool allows for many-to-many interactions. Social Location: Not Acknowledged The scope of the region is not specified. Honeycomb Framework: Identity, relationship These honeycomb framework elements are available.

193

Paper Title: Authors Affiliations Publication

Identification of Coordination Requirements Implications for the Design of Collaboration and Awareness Tools : Cataldo, M., Wagstrom, P. A., Herbsleb, J. D., and Carley, K. M. : Carnegie Mellon University, Pittsburgh, USA : Proceedings of the 2006 ACM Conference on Computer Supported Cooperative Work, CSCW, Alberta, Canada Publication Year : 2006 Origin of the Paper : USA Summary: The paper presents an examination measuring task dependencies among people, their congruence, and their coordination activities. Certain techniques were developed to perform the measurements. The results showed that, over time, people adapted to communication tools that supported their performance. Furthermore, techniques and results described in the paper provide opportunities for future studies. Criteria: Areas of Study: Metrics The paper introduced a technique developed to measure task dependencies among people, congruence between tasks and people, and coordination activities among people. Measurement results provide representation on how communication and coordination formed between individuals in executing tasks with various interdependencies. Research Type: Evaluation The research in the paper presents an evaluation using certain techniques to address several proposed research questions. Measurement results on task dependencies, congruence between task and people, and coordination activities among people were provided in the paper. Furthermore, evolution on congruence over time is also provided in the paper. Form of Study: Case Study The research in the paper conducted measurements on a software development project of a large distributed system in a company engaged in data storage industry. Data were collected from eight teams in distributed locations. Measurements were performed using the collected data and results were presented in the paper. Social Techniques: General Concept The paper provides a study of the implications of the proposed technique and task dependencies for designing collaborative and awareness tools. Research in the paper described the research setting used to conduct the study where the developers involved used Internet Relay Chat (IRC) to communicate, besides other tools. However, the technique proposed in the paper is not limited only for collaboration through instant messaging but also through other techniques. Therefore, we include this paper in the general social technique. Social Connectivity: Designated, Public, and Adapted The paper described a technique towards task dependencies and activities coordination performed by individuals. Considering the paper investigated the proposed technique and the case study described instant messaging as the social technique used by the developers, it leads to the conclusion that the approach is applicable to any social connectivity. Therefore, we include this paper in the above social techniques. Social Interaction: Mixture Considering the social techniques used in this study, we conclude that IRC encompassed mixture types of social interaction. Instant messaging is able to provide one-to-one, one-to-many, and even many-to-many interaction. Social Location: Distributed The paper explicitly described the environment settings used to performed measurement. The case study was a large software development project that involves hundreds of developers divided into eight teams across three different locations. Therefore, we include this paper in the distributed location. Honeycomb framework: Conversation, Sharing, and Presence The paper did not describe communication method built between the developers. From what is mentioned in the paper, communication between developers was performed through instant messaging and MR tracking system. We conclude to include these communications in several honeycomb blocks. Conversation represents communication between developers through IRC, and Sharing and Presence represents awareness built through MR tracking system.

194

Paper Title: Authors Affiliations

Discovering Essential Code Elements in Informal Documentation : Peter C. Rigby, Martin P. Robillard : Concordia University McGill University Publication : International Conference on Software Engineering Publication Year : 2013 Origin of the Paper : Canada

Summary: The authors propose a novel traceability recovery approach to extract the code elements contained in various documents. As opposed to previous work, their approach does not require an index of code elements to find links, which makes it particularly well-suited for the analysis of informal documentation. Criteria: Areas of Study: Coding The authors propose to detect which of the code elements in a document are salient, or germane, to the topic of the post. Research Type: Evaluation They have an evaluation of their code extractor on 188 StackOverflow answer posts containing a total of 993 code elements. Form of Study: Document Analysis Their study is based on document analysis in StackOverflow. Social Techniques: Social Networking StackOverflow is similar to social networking sites. Social Connectivity: Designated The authors design a code extractor to extract code from texts in StackOverflow. Social Interaction: Many-to-many The website allows for many-to-many interactions. Social Location: Distributed The website allows distributed social locations. Honeycomb Framework: Identity, Conversations, Sharing, reputation, Groups These elements are available in StackOverflow.

195

Paper Title: Authors Affiliations

Communication Networks in Geographically Distributed Software Development : Cataldo, M. and Herbsleb, J. D. : Research and Technology Center, Bosch Corporate Research, Pittsburgh, USA Carnegie Mellon University, Pittsburgh, USA Publication : Proceedings of the 2008 ACM Conference on Computer Supported Cooperative Work, CSCW, San Diego, USA Publication Year : 2008 Origin of the Paper : USA Summary: The paper presents research into communication development in geographically distributed projects, in order to address modular design strategy limitations. The paper also reported a series of evaluations conducted to a distributed project in order to identify the development. Several research questions were raised to keep the focus of the study and the result was obtained to address the questions. Criteria: Areas of Study: Management The paper did not explicitly describe the main areas supported by communication and collaboration between developers. However, the study emphasized the importance of communication between the developers. We conclude that this paper supports communication in the management area of study. Research Type: Evaluation The study described in the paper conducted an evaluation to investigate the communication development in a distributed environment. Evaluation was performed to a large distributed system of a company that operates in the data storage industry. Results were provided in the paper. Form of Study: Observation and Case Study The paper conducted an evaluation at a large distributed system using a case study of a company that runs in the data storage industry. Data was collected after several months, through observation and interviews involving a maximum of one hundred and nineteen developers. A series of analysis was applied to the data and results were reported in the paper. Social Techniques: General Concept The paper described an investigation of how communication networks in distributed environment evolve to overcome the limits of the modular design strategy. The case study identifies frequent use of instant messaging to communicate development and debugging work. However, the result from the investigation is not limited only to the use of instant messaging. Therefore, we include this paper in the general social technique. Social Connectivity: Adapted, Designated, and Public Although the paper described several public tools used by the developers within the case study, the result of the investigation is applicable for any types of social connectivity. Therefore, we include this paper in the above social connectivity. Social Interaction: Mixture Considering the social techniques used in this study, we conclude that IRC encompasses a mixture of types of social interaction. Instant messaging is able to provide one-to-one, one-to-many, and even many-to-many interaction. Social Location: Distributed The paper explicitly stated that the topic of the study is to identify the communication development in geographically distributed projects. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversation, Sharing, and Groups The paper presents a research towards communication development in geographically distributed projects. This study encompassed multiple teams that worked together within a project. Considering the type of social technique used in supporting the communication, we include this paper in the Conversation and Sharing honeycomb block. Furthermore, considering the cross-site communication that also supported in the study, we include this paper in the Groups honeycomb block.

196

Paper Title: Example Overflow Using Social Media for Code Recommendation Authors : Alexey Zagalsky, Ohad Barzilay, Amiram Yehudai Affiliations : Tel-Aviv University Publication : 3rd International Workshop on Recommendation Systems for Software Engineering (RSSE) Publication Year : 2012 Origin of the Paper : Israel

Summary: The authors present Example Overflow, a code search and recommendation tool which brings together social media and code recommendation systems. Example Overflow enables crowd-sourced software development by utilizing both textual and social information, which accompany source code on the Web. Its browsing mechanism minimizes the context switch associated with other code search tools. They describe the development of the tool, provide preliminary evaluation, and discuss its contribution to an example centric programming paradigm. Criteria: Areas of Study: Coding Example Overflow is a code search tool. Research Type: Solution, Evaluation The authors provide a tool and its preliminary evaluation. Form of Study: Non-Empirical The authors provide no empirical study in this paper. Social Techniques: Blog/microblog, Crowd sourcing The authors use Stack Overflow website and their tool allows for crowd sourced software development. Social Connectivity: Designated The authors utilize Stack Overflow website. Social Interaction: Many-to-Many The authors’ use of Stack Overflow shows that the interactions should be many-to-many. Social Location: Distributed The authors’ use of Stack Overflow website shows the distributed nature of the social location. Honeycomb Framework: Identity, Conversation, Sharing, Presence, Relationship, Reputation, Groups These honeycomb framework elements are available.

197

Paper Title: Authors Affiliations

Conflict Detection and Resolution for Product Line Design in a Collaborative Decision Making Environment : Liu, X. F., Barnes, E. C., and Savolainen, J. E. : Missouri University, Missouri, USA Danfoss Power Electronics Grasten, Denmark Publication : Proceedings of the 2012 ACM Conference on Computer Supported Cooperative Work, CSCW, Seattle, USA Publication Year : 2012 Origin of the Paper : USA and Denmark Summary: The paper proposed a framework to resolve non-functional requirements (NFR) conflicts between distributed stakeholders using a method for dividing high-level NFR conflicts into sub-problems. Stakeholders are able to argue when using the system to determine the best alternative design for NFR. The paper also provided an empirical research for examining this approach. The result showed that the system is effective in resolving conflict through collaboration. Criteria: Areas of Study: Requirements The research in the paper explicitly stated that the proposed approach was to solve NFR conflict. Therefore, this paper supports the requirements areas of study. Research Type: Solution The paper proposed a framework to solve NFR conflict by applying an existing NFR conflict analysis technique to support resolution through a web-based decision support system. This approach allows stakeholders to propose design alternatives and select a solution alternative through an argumentation process. Form of Study: Experiment The research in the paper described an experiment conducted using a group of graduate level software engineering students. This experiment involves introducing and using the approach to analyze and solve conflict. The result showed that the argumentation system included in the framework is effective in promoting better design alternatives. Furthermore, the result also showed that the framework is effective in supporting decision-making. Social Techniques: Dashboard and Instant Messaging The paper provided a description of the structure of the decision support system that is developed in aclient-server architecture. From the description, we concluded that the client side utilized a web-based user-friendly interface that is similar to dashboard and also make use of chat box that we include as instant messaging. Therefore, we include this paper in the dashboard and instant messaging social techniques. Social Connectivity: Designated The framework proposed in the paper to resolve NFR conflict in a distributed environment is specifically built to assist stakeholders in making decisions. Therefore, we include this paper in the designated tool connectivity. Social Interaction: Mixture The paper described the client-server architecture that is used as the structure of the decision support system. From the system, we conclude that the communication that occurs between stakeholders through the client user-friendly interface enables mixture interaction. A one-to-one interaction was enabled through chat, on the other hand, one-to-many and many-to-many interactions were enabled through comment posting. Social Location: Mixture The paper explicitly described that the decision support system, through the web-based approach, assisted distributed environment. However, according to the experiment reported in the paper, the decision support system was conducted to a localized location within university. Therefore, we include this paper in the mixture social location. Honeycomb framework: Conversation, Sharing, Presence and Relationship The paper proposed a framework to solve NFR conflict using a web based decision support system. We include this system in several honeycomb blocks. Conversation represents the communication that occurs between stakeholders through chat and comment posting. Presence represents the availability of other stakeholders. Sharing represents the proposed alternative designs, and Relationship represents the link between involved stakeholders.

198

Paper Title: Social Media and Success in Open Source Projects Authors : Jason Tsay, James Herbsleb and Laura Dabbish Affiliations : Carnegie Mellon University, USA Publication : Interactive Poster in ACM Conference on Computer-Supported Collaborative Work Companion Publication Year : 2012 Origin of the Paper : USA

Summary: Adapted from the open source literature, the authors develop two measures of project success, Developer Attention and Work Contribution. They find that projects with highly socially connected developers are not necessarily the most active or popular projects. Oddly, projects with a high level of developer multitasking, i.e., splitting effort equally across multiple projects, tend to receive less Developer Attention, but greater Work Contribution. Criteria: Areas of Study: Management, Metrics They are measuring the project success according to various metrics. Research Type: Solution The authors identify to metrics for success and evaluation of software. Form of Study: Case Study Using these measures of project success, the authors use social and technical characteristics of the project’s contributors to predict both Developer Attention and Work Contribution of a project. Social Techniques: Social Networking The authors make use of GitHub. Social Connectivity: Public The nature of Github website allows for public social connectivity. Social Interaction: Mixture GitHub allows mixed social interaction. Social Location: Distributed Github can be used by everyone in the world, which shows the distributed nature of it. Honeycomb Framework: Identity, Coversations, Sharing, Presence, Relationship, Reputation, Groups Github allows for all these framework items.

199

Paper Title: Authors Affiliations

Closure vs. Structural Holes: How Social Network Information and Culture Affect Choice of Collaborators : Gao, G., Hinds, P., and Zhao, C. : Cornell University, Ithaca, USA Stanford University, California, USA One Microsoft Way, Washington, USA Publication : Proceedings of the 2013 ACM Conference on Computer Supported Cooperative Work, CSCW, Texas, USA Publication Year : 2013 Origin of the Paper : USA Summary: The paper presented a study of how people use social networking information to determine with whom to collaborate. The research tried to evaluate how social networking sites affect developers when choosing peers to work with. Evaluation through a case study was presented in the paper. The result showed that shared information within social networking combined with the desire to collaborate with certain candidates, and affects how developers selected their collaborators. Criteria: Areas of Study: Management The paper investigates the use of social networking in supporting developers when choosing collaborators with whom they prefer to work. We conclude that the area supported by this research is management. Therefore, we include this paper in the management area of study. Research Type: Evaluation The paper proposed several hypotheses to guide the authors' investigation into the use of social networking. The main aim of the research was to address these hypotheses by conducting a series of methods to gather and evaluate data from the case study. Form of Study: Case Study The paper described research that was conducted using a global IT company. The respondents were chosen from two different locations (USA and China), and they were validated depending upon their culture and location. Result showed that the use of social networking delivered two different approaches depending upon the culture and location. Social Techniques: Social Networking The paper presented an investigation into the use of social networking for determining collaborators. This research sought to identify how influential social networking is in supporting developers when selecting people with whom they want to work. Therefore, we include this paper in the social networking technique. Social Connectivity: Adapted The paper did not specifically mention any existing social networking site that supports the selection of collaborators. Furthermore, the research result suggests a better enterprise system, which is not covered by the existing system, to provide a social network that could enhance information sharing especially for a distributed environment. Therefore, we include this paper in the adaptive tool. Social Interaction: Mixture The paper investigates the use of social networking in determining collaborators. From social networking, we conclude that interaction occurs between developers is a combination of various social interactions. Therefore, we include this paper in the mixture social interaction. Social Location: Mixture The paper described the case study used to investigate the importance of social network in determining collaborators. From the case study presented in the paper, we knew that a localized social location was applied to the investigation. However, result suggested that the social networking method is also applicable for distributed location by providing information that is more explicit. Therefore, we include this paper in the mixture social location. Honeycomb framework: Identity, Relationship, and Reputation The paper described the use of social networking in identifying potential collaborators. We include this method in several honeycomb blocks. Identity represents developer profile included in the social network. Relationship represents the link that connects developer with other developers within the social network. Reputation represents the information of culture described in the user profile.

200

Paper Title: Authors Affiliations

WikiWinWin: A Wiki Based System for Collaborative Requirements Negotiation : Yang, D., Wu, D., Koolmanojwong, S., Brown, W., and Boehm, B. W. : Chinese Academy of Science, China University of Southern California, CA, USA Publication : Proceeding of the 41st Annual Hawaii International Conference on System Sciences, Waikoloa, Hawaii, USA Publication Year : 2008 Origin of the Paper : China and USA Summary: The paper proposed a tool to capture various requirements from multiple stakeholders using Wiki. WikiWinWin is a development from a previous tool EasyWinWin* that utilized dashboard to provide support for requirements collaboration. A description on how to use WikiWinWin and case study conducted to identify the usefulness including the results were presented in the paper. Criteria: Areas of Study: Requirements/Specifications The paper described a tool that supported stakeholders' decisions in determining requirements. The paper also described the sequence of steps and instructions of the negotiation process to acquire mutual decision. Therefore, we include this paper in the requirements/specifications area of study. Research Type: Solution and Evaluation The paper proposed a successor tool to its previous tool, EasyWinWin, to support requirements collaboration between stakeholders by utilizing Wiki. WikiWinWin was introduced to increase stakeholders' participation and make ease the negotiation process in determining requirements. The paper also provided an evaluation process conducted to WikiWinWin to identify the use of this tool to facilitate requirements negotiation. Results were presented in the paper. Form of Study: Case Study The paper conducted a case study to identify the usefulness of WikiWinWin to facilitate stakeholders in making mutual decisions towards requirements. The case study was conducted to a group of students at USC who were developing a web based database system. Results were presented in the paper. Social Techniques: Wiki The paper explicitly described the social technique used in WikiWinWin to support collaboration between stakeholders. The paper also described the benefits and challenges in utilizing Wiki to assist the negotiation process. Therefore, we include this paper in the wiki social technique. Social Connectivity: Designated The paper proposed a tool that utilizes Wiki to support decision making between stakeholders regarding requirements. Although the tool adopts Wiki to assist the negotiation process, WikiWinWin is specifically designed to increase collaboration by assisting decision-making. Therefore, we include this paper in the designated tool connectivity. Social Interaction: Many-to-many The paper described the use of Wiki in assisting the negotiation process in the WikiWinWin tool. The Wiki was used to present the terminology list where stakeholders collaborate in determining a mutual requirement. The list is collected from every stakeholder involved and is available for every stakeholder involved. Therefore, we include this paper in the many-to-many interaction. Social Location: Mixture The paper did not explicitly describe the location of the stakeholders that were covered by the WikiWinWin tool. Considering the case study that was conducted upon a group of students, we include this paper in the localized social location. However, considering the ability of Wiki to be used on the internet, we also include this paper in the distributed social location. Therefore, we include this paper in the mixture social location. Honeycomb framework: Identity, Conversation, Sharing, and Presence The paper proposed a WikiWinWin tool to support requirements decision making between stakeholders. We include WikiWinWin tool to several honeycomb blocks. Identity represents the stakeholder profile in the WikiWinWin tool to be identified by other stakeholders. Conversation represents the communication occur between stakeholders through comments attached to a Wiki page. Sharing represents the information exchange using the Wiki, and Presence represents the availability of other developers in conducting the collaboration.

Paper Title: Authors Affiliations

Technology Selection to Improve Global Collaboration : Aranda, G. N., Vizcaino, A., Cechich, A., and Piattini, M. : Universidad Nacional del Comahue, Buenos Aires, Argentina University de Castilla-La Mancha, Ciudad Real, Spain Publication : Proceedings in the 1st IEEE International Conference on Global Software Engineering, ICGSE 2006, Florianopolis, Brazil Publication Year : 2006 Origin of the Paper : Argentina and Spain Summary: The paper presented a discussion of techniques in cognitive styles that could be used to improve distributed collaboration. This technique helps to select suitable groupware tools and elicitation techniques based on the stakeholders' characteristics. A case study to evaluate the proposed hypothesis and results were presented in the paper. Criteria: Areas of Study: Management The paper described a technique used to identify the most suitable groupware tools and elicitation techniques based on the characteristics of the stakeholders to increase collaboration in a distributed software development environment. The study claimed that communication for the elicitation process could be improved by understanding the stakeholders' characteristics, and suitable groupware tools might reduce differences that occur from culture and language. Therefore, we include this paper in the management area of study. Research Type: Validation The paper proposed a cognitive style approach to identify suitable groupware and elicitation techniques based upon the stakeholders' characteristics. This hypothesis claimed to increase communication and avoid misunderstandings between stakeholders. A case study was conducted to validate the hypothesis and the results were presented in the paper. Form of Study: Case Study The paper conducted a case study using a number of developers and users that were accustomed to and had sufficient proficiency of the use of groupware tools. Due to the limited number of respondents, studied groupware was classified into asynchronous and synchronous. Analysis of the result was presented in the paper. Social Techniques: General Concept The paper proposed an identification technique to determine the most suitable groupware tools to be used. Therefore, it did not describe any specific social technique in the research due to its coverage on several social techniques. Thus, we include this paper in the general social technique. Social Connectivity: Designated The identification of groupware tools and elicitation technique using the cognitive style approach is specifically proposed to investigate the possibility in providing a better communication and collaboration support between distributed software development environments. Therefore, we include this paper in the designated connectivity. Social Interaction: Mixture Considering the general social techniques discussed in the paper, we include this study in a mixture social interaction. Social Location: Distributed The paper explicitly described the aim to identify the most suitable groupware tool and elicitation techniques to support distributed processes. Therefore, we include this paper in the distributed location. Honeycomb framework: Conversation, Sharing, and Relationship The paper discussed an approach to identify the most suitable groupware tools and elicitation techniques based on the stakeholders' characteristics. We include this technique in several likelihood honeycomb blocks. Conversation and Sharing represents the possible communication and information sharing by using the most suitable groupware tool. Furthermore, Relationship represents the connection raised between distributed environments where it provides comfort for the stakeholders to communicate and collaborate.

202

Paper Title: Building Test Suites in Social Coding Sites by Leveraging Drive-By Commits Authors : Raphael Pham, Leif Singer, and Kurt Schneider Affiliations : Leibniz Universitat Hannover Publication : International Conference on Software engineering Publication Year : 2013 Origin of the Paper : Germany Summary: The authors present an approach for reducing the effort required by project owners for extending their test suites. They aim to utilize the phenomenon of drive-by commits: capable users quickly and easily solve problems in others’ projects—even though they are not particularly involved in that project—and move on. Criteria: Areas of Study: Coding, Software/Program Verification The idea of drive-by commits is built upon testing the available codes on GitHub. Research Type: Solution The authors propose a solution to the test issues encountered on GitHub codes. Form of Study: Non-empirical The authors use a non-empirical approach to the phenomenon of drive-by commits. Social Techniques: Social Networking, Crowdsourcing The authors use crowdsourcing to improve projects’ quality assurance efforts in GitHub, which is similar to social networking sites. Social Connectivity: Adapted The authors make use of GitHub and propose a new idea of drive-by commits built upon it. Social Interaction: Many-to-many GitHub allows for many-to-many social interactions. Social Location: Distributed The use of GitHub implies a distributed social location. Honeycomb Framework: Identity, Conversations, Sharing, Groups These honeycomb framework elements are available.

203

Paper Title: Authors Affiliations Publication

The Role of Blogging in Generating a Software Product Vision : Park, S. and Maurer, F. : University of Calgary, Alberta, Canada : Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering, CHASE 2009, Vancouver, Canada Publication Year : 2009 Origin of the Paper : Canada Summary: The paper presented the authors' opinion of the use of social media, especially blogging, to support knowledge creation in the envisioning process of a software tool. Stakeholders utilized blogs to express their opinion and requirements towards the software tool through both storytelling and demos. Several methods of storytelling, including a description of the benefits and challenges of utilizing blogs, were presented in the paper. Criteria: Areas of Study: Requirements/Specification and Software/Program Verification The paper described the use of blogging to share requirements information, where it provides collaboration between stakeholders to help make decisions regarding requirements for a software tool. Furthermore, through the story telling exposed in the blog, stakeholders provide information related to software testing to convey their opinion. Therefore, we include this paper in the requirements/specification and software/program verification areas of study. Research Type: Opinion The paper presented the authors' opinion of the use of blogging in supporting collaboration related to requirements. The paper described the use of blog to convey and to convince envision of a stakeholder towards requirements of a software tool. Form of Study: Document Analysis and Case Study The paper described a case study conducted in a research to identify the use of blogging in providing information that supports requirements collaboration between stakeholders. A preliminary document analysis of a number of blogs was performed to collect data. This case study was conducted using a group of practitioners incorporated in a testing tool workshop organized by Agile Alliance. The research derived a number of discussion topics from blogs by these practitioners. Social Techniques: Blog/Microblog The authors focused their research in the use of blogs to support requirement collaboration between stakeholders. Therefore, we include this paper in the blog social technique. Social Connectivity: Public The paper stated that, based on the research, the blogging site used by a stakeholder could refer to another blogging site as a recommendation. Although the paper did not describe the type of blogging site used by the practitioners, we assumed that these were public blogging sites. Therefore, we include this paper in the public connectivity. Social Interaction: One-to-many and Many-to-many Considering the social technique discussed in the paper, we include this paper into both one-to-many and many-to-many interaction. Each post published in a blog represents the one-to-many interaction. However, other stakeholders are able to post a comment related to the published story and initiate discussion with other stakeholders within the same page. We consider this as many-to-many interaction. Social Location: Distributed The paper stated that the use of this tool supports knowledge management in a global distributed environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Sharing and Presence The paper discussed the use of blogging to support knowledge management and requirement collaboration between stakeholders in a distributed environment. We include this study in several honeycomb blocks. Identity represents the user profile of the stakeholders. Sharing represents the information provided through blogs by stakeholders, and Presence represents the availability of other stakeholders to provide information through blogs.

204

Paper Title: Impression Formation in Online Peer Production Activity Traces and Personal Profiles in GitHub Authors : Jennifer Marlow, Laura Dabbish, Jim Herbsleb Affiliations : Carnegie Mellon University Publication : International Conference on Computer Supported Collaborative Work Publication Year : 2013 Origin of the Paper : USA

Summary: The authors describe a qualitative investigation of impression formation in an online distributed software development community with social media functionality. Criteria: Areas of Study: Coding GitHub, which is used by the authors, is a coding site. Research Type: Evaluation The authors evaluate the impression formation in GitHub website. Form of Study: Case Study The authors conducted an interview-based investigation of impression formation in GitHub. Social Techniques: Social Networking There are similarities between social networking sites and GitHub. Social Connectivity: Public GitHub allows for public connectivity. Social Interaction: Many-to-many Interactions on GitHub follow many-to-many rules. Social Location: Distributed The nature of GitHub allows for a distributed location. Honeycomb Framework: Identity, Conversations, Sharing, Groups All these items are available in GitHub.

205

Paper Title: Supporting Creative Collaboration in Globally Distributed Companies Authors : Gumienny, R., Gericke, L., Wenzel, M., and Meinel, C. Affiliations : Hasso Plattner Institute, Postdam, Germany Publication : Proceedings of the 2013 ACM Conference on Computer Supported Cooperative Work, CSCW, Texas, USA Publication Year : 2013 Origin of the Paper : Germany Summary: The paper proposed a digital whiteboard and sticky note system, Tele-Board. This web-based system supports creative collaboration particularly in the distributed environment. A complete description of what the system is and how the system works is presented in the paper. An evaluation to identify the use of this system was conducted. The result showed that Tele-Board complements existing systems, encouraging communication and increasing understanding. Criteria: Areas of Study: Requirement/Specification and Design The paper described the main objective of Tele-Board, which was to support communication and collaboration between developers even if the members were in a distributed environment. From the case study, the results showed that Tele-Board was primarily used during brainstorming and collecting feedback. We conclude that generating ideas from brainstorm matches the design area of study and collecting feedback supports the collection of requirements/specification. Research Type: Solution and Evaluation The paper proposed a web based whiteboard and sticky note system to support collaboration between developers. This system is designed to support creative teamwork in a co-located and distributed environment. Description of the system including how the system works and how it benefits the developers was presented in the paper. Furthermore, the tool was evaluated to a distributed team located in three different countries. Results of the evaluation were provided in the paper. Form of Study: Case Study The paper described a case study conducted at a large IT company that introduced the Tele-Board to one of their distributed team. A series of observations and interviews were conducted with members of the team. Result showed that users at branches used Tele-Board more than users at headquarters. It also showed encouraging feedback regarding the use of Tele-Board. Social Techniques: Dashboard The paper described the simple design of Tele-Board, which utilized a digital whiteboard combined with a sticky notepad. However, considering the web portal used for managing projects and panels, we conclude this research in the dashboard social technique. This categorization also considered the use of web portal to support communication from posting comments. Social Connectivity: Designated The paper described the design of Tele-Board, which was specifically built to support communication between developers. Therefore, we include this paper in the designated tool social connectivity. Social Interaction: Mixture The paper did not explicitly describe the interaction between developers when using the Tele-Board. We conclude that a one-to-many interaction was formed at comment posting available in the web portal. Furthermore, a many-to-many interaction was described from the amount and kinds of information available in the web portal. Therefore, we include this paper in the mixture social interaction. Social Location: Mixture The paper stated that the main aim of Tele-Board is to support communication between developers, specifically in the distributed environment. However, the paper mentioned that it does not rule out the possibility for a co-located environment to utilize this system. Therefore, we include this paper in the mixture social location. Honeycomb framework: Identity, Conversation, Sharing, Relationship and Groups The paper proposed a system that utilized a digital whiteboard and sticky notes to support collaboration between distributed developers. We include this system in several honeycomb blocks. Identity represents the user profile available in the web portal site. Conversation represents communication that occurs between developers through comment posting. Sharing represents the information exchanged or available through sticky notes. Furthermore, Relationship and Groups represents the connection between developers that were involved within certain projects.

206

Paper Title: Authors Affiliations Publication

An Adaptive Tool Integration Framework to Enable Coordination in Distributed Software Development : Sinha, V. S., Sengupta, B., and Ghosal, S. : IBM Research, Indian Institute of Technology, India : Proceedings in the 2nd IEEE International Conference on Global Software Engineering, ICGSE 2007, Munich, Germany Publication Year : 2007 Origin of the Paper : India Summary: The paper discussed the authors' point of view in building a collaborative framework that enables information sharing between different tools and provides loose coupling between the tools. A list of features that the framework has to adopt and a list of possible technologies to enable the framework were presented in the paper. Criteria: Areas of Study: Management The paper proposed a collaborative framework that enabled information management between existing tools, particularly in a distributed environment. This framework allows users to continue working with their choice of tools and build certain interface requirements to enable information exchange between different tools. Therefore, we include this paper in the management area of study. Research Type: Solution The paper proposed a novel adaptive integration framework that enables collaboration in a seamless fashion between tools to share information. The paper also discussed several main features that the framework needs to adopt and several possible technologies to enable this framework. Form of Study: Non-empirical The research presented in the paper is a view towards building a framework to enable multiple different tools to collaborate and share information. Supporting arguments presented in the paper were obtained from existing studies and tools. Therefore, we include this paper in the literature review form of study. Social Techniques: Email/Alert The paper described the design of the framework features and how these features enabled the collaboration between different tools. The paper also proposed a social technique, notification alert, to be used in the framework to increase awareness between users. Therefore, we include this paper in the alert technique. Social Connectivity: Designated The paper proposed a framework that could enable collaboration between different tools used in a software development environment. The paper mentioned that this framework is specifically proposed to enable information sharing in a seamless fashion, regardless of independent tooling. Therefore, we include this paper in the designated connectivity. Social Interaction: One-to-one The paper provided several examples of how the framework will accommodate collaboration between different tools. Based on these examples, we include this paper in the one-to-one social interaction. Social Location: Mixture The paper explicitly stated that the research was proposed to motivate the needs for integration between different tools in a software development lifecycle, particularly in a distributed environment. We conclude that this framework will be available to accommodate both localized and distributed locations. Therefore, we include this paper in the mixture social location. Honeycomb framework: Sharing and Presence The paper proposed a framework that enables collaboration between independent tooling. We include this paper in Sharing and Presence of the honeycomb blocks. Sharing represents the information exchange between different users and Presence represents the availability of other users within the development lifecycle through the notification alert.

207

Paper Title: Authors Affiliations Publication

Experiences of Instant Messaging in Global Software Development Projects: A Multiple Case Study : Niinimaki, T. and Lassenius, C. : Helsinki University of Technology, Finland : Proceedings in the 3rd IEEE International Conference on Global Software Engineering, ICGSE 2008, Bangalore, India Publication Year : 2008 Origin of the Paper : Finland Summary: The paper discussed the use of instant messaging in six different projects from two different companies. The study identified the benefits and challenges that occurred when instant messaging was used for communicating. Furthermore, it investigated factors that help the project to succeed and factors that might hamper the project. The results from the case study were described in the paper. Criteria: Areas of Study: Management The paper did not explicitly describe in which areas the instant messaging was used to support communication. However, it mentioned that most members involved in the project were using instant messaging to communicate within and between sites. We conclude that instant messaging was used through the software development lifecycle to support communication. Therefore, we include this paper in the management area. Research Type: Experience Research conducted in the paper aimed to identify the use of instant messaging in software development projects. It investigated the benefits, challenges, and factors that supported or hampered the success of a project. Considering the paper did not introduce any approaches or investigate any technique, and it described the authors' experience toward their investigation, we include this paper in the experience paper. Form of Study: Case study Research described in the paper conducted a case study to six different projects from two different companies. A series of semi-structured interviews was performed to collect data. The results were divided into several analysis frameworks that showed the benefits, challenges, and supporting factors of using instant messaging as a communication media, as described in the paper. Social Techniques: Instant Messaging The paper focused its research upon identifying the use of instant messaging in supporting communication and hence supporting the success of the project. Therefore, we include this paper in the instant messaging technique. Social Connectivity: Public The paper mentioned the tools used by the team members to communicate through instant messaging, which were Lotus Notes SameTime and Microsoft Office Communicator. Considering both tools were not specifically designed to support software engineering, we include this paper in the public connectivity. Social Interaction: Mixture Considering the type of social techniques used in the research, we assume instant messaging was used for both direct and group discussion. This means that several types of social interaction are applied to instant messaging. Therefore, we include this paper in the mixture social interaction. Social Location: Mixture The paper stated that the case study was performed in order to identify the use of instant messaging as a communication media in supporting a software development project. Based on the case study, it was found that the use of instant messaging accommodates both collocated and distributed site locations. Therefore, we include this paper in the mixture social location. Honeycomb framework: Identity, Conversation, and Presence The paper described the research of using instant messaging in a software development environment. We include this study in several honeycomb blocks. Identity represents the user profile of the other members involved. Conversation represents the communication that occurs between team members, and Presence represents the availability of other members involved in the project.

208

Paper Title: Authors Affiliations

CAMEL: A Tool for Collaborative Distributed Software Design : Cataldo, M., Shelton, C., Choi, Y., Huang, Y., Ramesh, V., Saini, D., and Wang, L. : Research and Technology Center, Robet Bosch LLC, PA, USA Carnegie Mellon University, PA, USA Publication : Proceedings in the 4th IEEE International Conference on Global Software Engineering, ICGSE 2009, Limerick, Ireland Publication Year : 2009 Origin of the Paper : USA Summary: The paper proposed a tool to support distributed collaborative virtual software design meetings. CAMEL provides an environment for stakeholders to communicate and share multiple diagrams in order to make decisions. CAMEL was designed to address challenges that arose from literature review and document analysis presented earlier in the paper. A complete design of CAMEL and future implementation were presented in the paper. Criteria: Areas of Study: Design The paper explicitly described the use of the proposed tool, CAMEL, which is to provide a collaborative environment for stakeholders to have a virtual design meeting in order to make decisions. Through its several key characteristics, CAMEL enriches the communication tools among distributed software design. It includes several features that allow stakeholders to create and discuss design using UML or freestyle through the use of a posterboard or whiteboard, and supported by a chat group window. Research Type: Solution The paper proposed a tool to support design collaboration between stakeholders in a distributed software developer environment. CAMEL supports communication by presenting a virtual environment of the important features of collocated meetings. Form of Study: Non-Empirical The paper presented the ultimate challenges that occur from a distributed software development environment that were identified from literature review. The tool presented in the paper was designed to address these challenges. Several features proposed for the tool were also derived from existing studies. Social Techniques: Dashboard and Instant Messaging The paper described the design of the proposed tool, CAMEL. It described several features implemented, including the meeting session, the paperboard, the whiteboard, and the group editor. We conclude that the sessions and boards provide similar function as the dashboard, and the group editor as an instant messaging application. Therefore, we include this paper in the dashboard and instant messaging techniques. Social Connectivity: Designated The paper explicitly stated that CAMEL was designed to address the challenges found from literature reviews. It was proposed in order to provide communication support for design collaboration. Therefore, we include this paper in the designated connectivity. Social Interaction: One-to-many The paper described the communication feature implemented in CAMEL. It supported group discussion through a group editor and also through the design dashboard. Therefore, we assume that the interaction occurs between stakeholders were one-to-many social interaction. Social Location: Distributed The paper described the use of CAMEL in supporting distributed software development environment. Therefore, we include this paper in the distributed social interaction. Honeycomb framework: Identity, Conversation, and Sharing The paper proposed a tool to provide virtual support in design collaboration. We include this tool in several honeycomb blocks. Identity represents the user profile of the other stakeholders involved in meeting. Conversation represents the communication that occurs between the stakeholders through the group editor, and Sharing represents the information exchange through the poster and white boards.

209

Paper Title:

Using a Real-Time Conferencing Tool in Distributed Collaboration: An Experience Report from Siemens IT Solutions and Services Authors : Damian, D., Marczak, S., Dascalu, M., Heiss, M., and Liche, A. Affiliations : University of Victoria, Canada Siemens IT Solution and Services, Vienna, Austria Publication : Proceedings in the 4th IEEE International Conference on Global Software Engineering, ICGSE 2009, Limerick, Ireland Publication Year : 2009 Origin of the Paper : Canada and Austria Summary: The paper discussed the use of Microsoft Office Communication Server (OCS) tool to increase collaboration between developers in a software development environment, within and between location sites. The paper provided a report of the significant changes that occurred in the environment through changes brought by the OCS. Several challenges were identified that were overcome by the changes described in the paper. Criteria: Areas of Study: Management The paper did not explicitly mention the area of study supported by the OCS. However, from the description of changes brought to increase collaboration within the software development environment, we conclude that this paper is in the management area of study. This includes work assignments, team management, and communication. Research Type: Experience The paper provided a complete experience of the authors' research in identifying significant changes brought by OCS to increase collaboration within a software development environment. Analysis results were compared between before OCS with after OCS, and were presented in the paper. Form of Study: Case Study The paper described a comparison from using the OCS tool in supporting collaboration. The study was conducted using a project team at the Siemens IT Solutions and Services. Therefore, we include this paper in the case study form of study. Social Techniques: Email and Instant Messaging The paper stated that the OCS tool utilizes several social techniques to support communication. However, considering our research in the use of social media to support software engineering, we subtract these techniques only into email and instant messaging. The paper mentioned that the use of email predominant the communication, and that the OCS supports a chat system similar to instant messaging. Social Connectivity: Adapted The paper mentioned that the OCS is a commercial tool that was adopted to fulfill the needs of communication support in a software development environment. We assumed that OCS is also available for other communication support and not only for software development. Therefore, we include this paper in the adaptive connectivity. Social Interaction: Mixture The paper described the changes delivered by OCS in supporting communication within a software development environment. It described the interaction between members of the project as one-to-one interaction as well as one-to-many interaction. Furthermore, the OCS ability to deliver group discussion represents the many-to-many interaction. Therefore, we include this paper in the mixture social interaction. Social Location: Mixture The paper described features utilized by OCS in supporting communication. These features, as mentioned in the paper, were valuable for collocated members as well as distributed members. Therefore, we include this paper in the mixture social location. Honeycomb framework: Identity, Conversation, Sharing, and Presence The paper discussed the use of OCS in supporting communication within a software development environment. We include this tool in several honeycomb blocks. Identity represents other members' user profiles within the contact list. Conversation represents communication that occurs between members through chat and email. Sharing represents information exchange between members that occurs along communication, and Presence represents the availability of other members notified by the OCS tool.

210

Paper Title: Authors Affiliations Publication

Virtual Open Conversation Spaces: Towards Improved Awareness in a GSE Setting : Dullemond, K., Gameren, B., and Solingen, R. : Delft University of Technology, Netherland : Proceedings in the 5th IEEE International Conference on Global Software Engineering, ICGSE 2010, Princeton, NJ, USA Publication Year : 2010 Origin of the Paper : Netherland Summary: The paper presented a discussion regarding communication in building awareness between developers in supporting software development environment. To increase awareness, the authors proposed a virtual open conversation tool to provide communication environment including initiating conversation, information exchange, and enabling access to persistent conversation. A description of Communico is presented in the paper, including its initial evaluation to gain usage feedback. Criteria: Areas of Study: Requirements/Specification, Coding, and Distribution, Maintenance, and Enhancement The paper did not explicitly describe the areas of study supported by Communico. However, considering the features implemented to address challenges in distributed communication, we include this paper into the areas of Requirements/Specification, Coding, and Distribution, Maintenance, and Enhancement. Research Type: Solution and Evaluation The paper proposed a new tool, Communico, to support communication between developers in a distributed software development environment. Communico is a virtual open space that provides communication functionalities through the Instant Messaging program of the Office Communications Server. Communico is claimed to be different from other existing tools due to its supporting features. An initial evaluation towards the use of Communico was performed with the aim of gaining instructive feedback. Form of Study: Case Study The paper described an initial evaluation that was performed in the research that was conducted using a small Dutch software company. This was to obtain feedback towards the use of Communico in a real distributed environment. The results showed that the developers provided positive feedback related to its being enjoyable and easy to use. Social Techniques: Instant Messaging The paper provided a description of the design of Communico. This tool implements the instant messaging from Office Communications Serves to capture conversations and provide communication interface. Therefore, we include this paper in the instant messaging social technique. Social Connectivity: Designated The paper introduced Communico as a tool that provides communication support between developers in a distributed software development environment. Communico is specifically designed to meet the challenge that originates from the lack of awareness in a distributed environment. Therefore, we include this paper in the designated connectivity. Social Interaction: Many-to-many The paper described the design of Communico in providing communication support between developers. Every conversation that occurs in Communico is available for public, including information shared through various levels of actors. Therefore, we include this paper in the manyto-many social interaction. Social Location: Distributed The paper explicitly proposed a tool to increase awareness between developers in a distributed environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Conversation, Presence, and Groups The paper proposed a tool to increase awareness between developers in a distributed environment. We include this tool in several honeycomb blocks. Identity represents the profile of other developers involved in the conversation. Conversation represents the communication that occurs between developers through Communico. Presence represents the availability of other developers being involved in the conversation or simply being aware of the conversation. Furthermore, Groups represents the different conversation topic managed by Communico.

211

Paper Title: Authors Affiliations Publication

Face-to-face, Email and Instant Messaging in Distributed Agile Software Development Project : Niinimaki, T. : Aalto University, Finland : Workshop Proceedings in the 6th IEEE International Conference on Global Software Engineering, ICGSE 2011, Helsinki, Finland Publication Year : 2011 Origin of the Paper : Finland Summary: The paper presented a comparison of different types of communication in a collocated and distributed software development site. Three types of communication (face-to-face, email, and instant messaging) were studied to identify the intensity of use of each type to support collaboration. A case study was conducted to address the proposed research question, and the results were presented in the paper. Criteria: Areas of Study: Management The paper did not explicitly describe the area within the software development lifecycle that it supported. However, the paper emphasized the communication within and between sites. We conclude that the communications that occurred are part of project management. Therefore, we include this paper in the management area of study. Research Type: Experience Research conducted in the paper was aimed to identify the amount of communication that occurs between developers within and between sites. Furthermore, it also compared several different types of communication to investigate the usefulness of each type. Considering that the paper did not introduce any approaches or investigate new techniques, we include this paper in the experience paper. Form of Study: Case study The author of the paper conducted a case study using a distributed software development team located in three different locations. The case study was to compare three different types of communication and identify how intensely each type was used. The results showed that each type showed a different intensity of use within and between sites as described in the paper. Social Techniques: Email and Instant Messaging The paper focused its research in comparing three different types of communication (face-to-face, email, and instant messaging) that occurs between developers. However, considering our main study to identify the use of social media in supporting software engineering, we include this paper only in the email and instant messaging social techniques. Social Connectivity: Public The paper described the tools used by the developers to send and receive emails and instant messaging. Microsoft Outlook was used for emails and Microsoft Office Communicator was used for instant messaging. Considering both tools were not specifically designed to support software engineering, we include this paper in the public connectivity. Social Interaction: Mixture Considering the types of social techniques used in the research, we assume that email and instant messaging were used for direct and group discussion through one-to-one interaction and one-to-many interaction through mailing list and group chat. Therefore, we include this paper in the mixture social interaction. Social Location: Mixture The paper stated that the study performed through the case study was to identify the communication intensity among developers within and between sites. Therefore, this paper is included in the localized and distributed social location. Honeycomb framework: Identity, Conversation, and Presence The paper described the research for identifying communication among developers within and between sites. We include this study in several honeycomb blocks. Identity represents the user profile of the other involved developers. Conversation represents the communication that occurs between developers, and Presence represents the availability of other developers involved in the project.

212

Paper Title: What Type of Thread Can Get Feedback in OSS User Mailing List Authors : Akinori Ihara, Yuji Tsuda, Ken-ichi Matsumoto Affiliations : Nara Institute of Science and Technology Publication : International Workshop on Social Software Engineering Publication Year : 2013 Origin of the Paper : Japan

Summary: In this study, the authros investigate what type of thread can get feedback in user mailing list. As a result of a case study using Apache and Python project data, a thread is posted by a deep experienced user would be received a useful answer. Criteria: Areas of Study: Distribution, Maintenance and Enhancement In order to provide technical support to end users, OSS projects manage a user mailing list. It is for discussion about bugs and new functions of OSS with end users. Research Type: Evaluation The authors investigate what type of thread can get feedback in user mailing list. As a result of a case study using Apache and Python project data, a thread is posted by a deep experienced user would be received a useful answer. In addition, they found threads written about internal system information of the OSS is more likely to be replied. Form of Study: Case Study The authors use a case study using Apache and Python project data, a thread is posted by a deep experienced user would be received a useful answer. Social Techniques: Email/alert The authors investigate what type of thread can get feedback in user mailing list. Social Connectivity: Public The authors Use Apache and Python project data to reveal what type of thread can get feedback in user mailing list in terms of the feature of sender, posting time, and message context. Social Interaction: One-to-one, One-to-many The use of emails implies a one-to-one and one-to-many interaction. Social Location: Not Acknowledged It is not mentioned the scope of the region. Honeycomb Framework: Identity, Conversations, Reputation These elements are present in the study.

213

Paper Title: Authors Affiliations Publication

DPMTool_ A Tool for Decisions Management in Distributed Software Projects : Garrido, P. J., Vizcaino, A., Andrada, J., Monasor, M. J., and Piattini, M. : University of Castilla-La Mancha, Ciudad Real, Spain : Proceedings in the 6th International Workshop on Tool Support Development and Management in Distributed Software Projects (REMIDI 2012), ICGSE 2012, Porto Alegre, Rio Grande de Sul, Brazil Publication Year : 2012 Origin of the Paper : Spain Summary: The paper proposed a tool that enabled support for decision management in distributed software development projects. The tool allows project managers to manage information and reuse the decisions taken in previous projects that had similar characteristics. Several features utilized by the system enabled distributed collaboration between stakeholders in software projects. A description of the system and its features were presented in the paper. Criteria: Areas of Study: Management The paper described the use of DPMTool to support decision management in distributed software development environment. It provides a way for stakeholders to collaborate in managing decisions and distributing information. Therefore, we include this paper in the management area of study. Research Type: Solution The paper proposed a tool to support management decision making in distributed software development environments. A description of the design and features of the tool, including how to use the tool, were described in the paper. Form of Study: Non-empirical Research in the paper proposed a tool to facilitate and encourage management decision making in software project. The tool was proposed to address challenges in distributed collaboration derived from a literature review. Therefore, we include this paper in the literature review form of study. Social Techniques: Dashboard The paper did not explicitly describe any social technique used in the DPMTool to support management decision making. However, from the description of the use of DPMTool, we include this study in the dashboard technique. Social Connectivity: Designated Research in the paper proposed a tool specifically built to address the challenges in providing support for collaboration decision making in distributed software development. Therefore, we include this paper in the designated tool. Social Interaction: Mixture The paper provided a description of the use of DPMTool in supporting management collaboration decision making. It described the interaction used in DPMTool that enables one-to-many as well as many-to-many social interaction. Therefore, we include this paper in the mixture social interaction. Social Location: Distributed The paper explicitly stated that the main aim of DPMTool is to support distributed collaboration decision making between members of software development team. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Conversation, Sharing, and Presence The paper proposed a tool that enables management collaboration decision making in distributed software development. We include this research in several honeycomb blocks. Identity represents the user profile of other stakeholders. Conversation represents communication that occurs between team members. Sharing represents the information exchange between stakeholders in order to collaborate for making decision, and Presence represents the awareness of other stakeholders through their availability.

214

Paper Title: Authors Affiliations Publication

SmartWiki: Support for High-Quality Requirements Engineering in a Collaborative Setting : Knauss, E., Brill, O., Kitzmann, I., and Flohr, T. : Leibniz Universitat Hannover, Germany : Proceedings of the 31st International Conference on Software Engineering (ICSE) Workshop on Wikis for Software Engineering (WIKIS4SE), 2009, Vancouver, BC, Canada Publication Year : 2009 Origin of the Paper : Germany Summary: The paper introduced a tool that automatically checks the consistency of content in a collaborative web based on Wiki. SmartWiki is designed to manage tasks, schedules, and responsibilities of the members involved in a project. Furthermore, this approach improves awareness by displaying project status, quality goals, and shared terminology. Architecture and features of SmartWiki is presented in the paper. An evaluation of the usefulness of SmartWiki in real projects was also provided in the paper. Criteria: Areas of Study: Requirements/Specification and Management The paper described the main use of Wiki, which was to assist the initial project by collecting and displaying demanded requirements information for the benefit of the project. This represents the requirements/specification area where members of the team were able to collaborate through Wiki. Furthermore, SmartWiki was also used for managing a project through task management and scheduling. Therefore, we also include this paper in the management area of study rather than only the requirements/specification. Research Type: Solution and Evaluation The paper introduced a tool that could overcome the challenges occurred from distributed environment. SmartWiki assist quality feedback and help maintain the consistency of the web content through specialized heuristic. Furthermore, the paper described the evaluation conducted through four case studies to identify the usefulness of SmartWiki. Results were presented in the paper. Form of Study: Case Study The researchers of the paper conducted four different case studies in both academic and industry sectors. This was performed to identify the usefulness of SmartWiki in a real project. Results showed that feedback given by respondents through all four cases were positive as presented in the paper. Social Techniques: Wiki The paper introduced a tool that utilizes Wiki to provide collaboration between members in a distributed environment. SmartWiki was built on top of the Semantic MediaWiki, an extension to a free web-based wiki software application that allows annotating semantic data within a wiki page. Therefore, we include this paper into wiki social technique. Social Connectivity: Adapted The paper described the architecture and features provided by SmartWiki to maintain quality feedback and manage collaboration between members of the team. Considering that SmartWiki was built on top of MediaWiki, we include this paper into the adaptive connectivity. Social Interaction: One-to-many and Many-to-many Considering the nature of the social technique described in the paper, we include this paper into one-to-many and many-to-many interaction. SmartWiki maintains quality feedback through heuristic feedback where it represents a many-to-many interaction. Furthermore, Wiki enabled team members to publish information for other members to act upon where it represents the one-to-many interaction. Social Location: Distributed The paper described the area coverage assisted by SmartWiki through the case studies. Furthermore, description of the SmartWiki explained that features adopted by SmartWiki enable distributed collaboration. Therefore, we include this paper in the distributed location. Honeycomb framework: Sharing and Presence The paper introduced SmartWiki to maintain quality feedback, assist task management and scheduling by utilizing Wiki. We include this paper in several honeycomb blocks. Sharing represents the information exchanged through the content published on Wiki. Furthermore, Presence represents the availability of other users in providing information through adding web content and feedback.

215

Paper Title: Authors Affiliations Publication

Combining Micro-Blogging and IDE Interactions to Support Developers in their Quests : Guzzi, A., Pinzger, M., and Deursen, A. : Delft University of Technology, The Netherlands : Proceedings of the 26th IEEE International Conference on Software Maintenance (ICSM), 2010, Timisoara, Romania Publication Year : 2010 Origin of the Paper : The Netherlands Summary: The paper introduced an approach to access knowledge gained during software engineering by combining micro blogging with interaction data automatically collected from IDE. This approach was implemented in James, an Eclipse plug-in, to evaluate its effectiveness and benefits from combining both data. An evaluation process was conducted for this as described in the paper. The result showed that the approach is promising for recording and sharing data knowledge. Criteria: Areas of Study: Coding, Software/Program Verification, and Distribution, Maintenance, and Enhancement The paper described the use of micro blogging integrated with IDE to record knowledge built up during software engineering. This knowledge was aimed to assist other developers in performing their task. Furthermore, according to the situations based on the case study conducted to evaluate the approach, areas of testing and bug fixing were also supported. Therefore, we include this paper in the areas of study as mentioned above. Research Type: Solution and Evaluation The paper presented an approach to combine lightweight technology and micro blogging into IDE, through the James plug-in to record knowledge from the software engineering process. The approach is to assist other developers as well as providing communication between developers. An evaluation towards this approach was conducted as described in the paper. Form of Study: Case Study The paper described a case study to evaluate the effectiveness of this approach to 7 developers in 5 different situations. Each situation covers different areas of study including how the micro blogging was being used. The result showed that the combination of micro blogging with IDE is highly promising as described in the paper. Social Techniques: Blog/Microblog The paper explicitly described the use of micro blogging combined with IDE to record knowledge. Furthermore, the paper also stated that micro blogging was used to support communication and information sharing between developers. We include this paper in the micro blogging technique. Social Connectivity: Designated The paper described the use of twitter-like micro blogging combine with IDE to support developers in providing information on what they are currently doing. This means that the micro blogging approach was specifically designed to assist information sharing. We include this paper in the designated connectivity. Social Interaction: One-to-many Considering the social technique described in the paper, we include this paper into the one-to-many social interaction. The concept of micro blogging in the study enabled developers to post messages that contain information or questions. These messages are available to other developers that were related. Social Location: Not Acknowledged The paper did not describe the location encompassed by this approach. It described the combination of micro blogging with IDE through an Eclipse plug-in, James. We considered this paper as unacknowledged social location due to the lack of information described in the paper. Honeycomb framework: Identity, Conversation, Sharing, and Presence The paper introduced James, which combines micro blogging with IDE to record and present knowledge throughout the software engineering process. We include this study in several honeycomb blocks. Identity represents the user that posted messages. Conversation represents the communication that might occur through micro blogging between developers. Sharing represents the knowledge exchange between developers, and Presence represents the availability of other users in a form of knowledge information posted through micro blogging.

216

Paper Title: Authors Affiliations

Using Wikis in Software Development : Louridas, P. : Greek Research and Technology Network, Greece The National and Kapodestrian University of Athens, Greece Publication : IEEE Software Journal, 23 (2), 88 - 91 Publication Year : 2006 Origin of the Paper : Greece Summary: The paper provides an overview of Wiki's popularity in enabling effective collaboration and knowledge sharing within a minimum budget. A history and implementation of Wiki were presented in the paper, including how it has reached its popularity. The paper is in favor of using Wiki in supporting distributed collaboration in a software development environment. Criteria: Areas of Study: Management The paper described the functions and advantages of using Wiki in a software development environment. Organizing work, tracking changes, and publishing work are among the advantages discussed in the paper. Concluding from the use of Wiki in supporting software development, we include this paper in the management area of study. Research Type: Opinion The paper discussed the use of Wiki to support distributed software development from the author's point of view. The author described the advantages and the ease of use in implementing Wiki to assist software development. Arguments were presented in the paper from a thorough research result. Form of Study: Non-empirical The paper did not provide any empirical research to support the author's arguments. However, the author presented a research of the background, the existing, and the future ideas for Wiki and its implementation. Social Techniques: Wiki The paper explicitly discussed the background of Wiki and how it can be used to support distributed software development. Therefore, we include this paper in the Wiki social technique. Social Connectivity: Public and Adapted The paper described the use of Wiki in supporting distributed software development. It described the existing Wiki platform that can be used publicly. However, it also described that Wiki is easy to build to fit the needs of the project. Therefore, we include this paper in the public and adaptive tool connectivity. Social Interaction: Many-to-many The paper described the principle of Wiki in supporting distributed software development. Collecting information from members involved within the project to assist organization, tracking and publication of their work. This means that various information acquired from various members is available for other members. Therefore, we include this paper in the many-to-many social interaction. Social Location: Distributed The paper described the use of Wiki in supporting software development. It emphasized the usefulness of Wiki in a distributed software development project. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Sharing, and Presence The paper described Wiki as a tool to support software development. We include Wiki in several honeycomb blocks. Identity represents the user profile for editing activity. Sharing represents the information shared in the Wiki, and Presence represents the availability of other users to be involved in editing the Wiki.

217

Paper Title: Authors Affiliations Publication

CodeSaw: A Social Visualization of Distributed Software Development : Gilbert, E. and Karahalios, K. : University of Illinois, USA : Proceedings of the Human-Computer Interaction (INTERACT 2007), 11th IFIP TC 13 International Conference, Rio de Janeiro, Brazil. Publication Year : 2007 Origin of the Paper : USA Summary: The paper introduced a social visualization tool combining code repositories and project communication to support distributed software development. Visualization and design processes, including tool evaluation using a field study, were presented in the paper. The result showed a positive reaction towards the tool, affecting communities and providing incentives for distributed developers. Furthermore, the result also suggests a novel interaction technique to further support communication through spatial messaging. Criteria: Areas of Study: Coding and Management CodeSaw, as described in the paper, visualized a software community combining code repositories with project communication. Users are allowed to compare with other developers, identify archives, and communicate within the interface itself. CodeSaw represents information required for developers to collaborate in code, task, and performance management. Therefore, we include this paper in the coding and management areas of study. Research Type: Solution The paper proposed a social visualization tool including a novel technique to communicate through spatial messaging to support collaboration for distributed software development. CodeSaw is viewed as a solution for developers, both insiders and outsiders, to identify and become aware of their community. Form of Study: Case Study To identify the use of CodeSaw, the paper presented a field study that was conducted to projects hosted by SourceForge.net. The result of the case study showed that users became aware of their community. Furthermore, CodeSaw presents a means for developers to identify their activities. Social Techniques: Email and Instant Messaging The paper described features embedded in CodeSaw in providing information and supporting communication between developers. Emails on project mailing list were used by CodeSaw to mine relevant information to be presented in the visualization. Furthermore, we conclude that the Spatial Messaging proposed to enrich CodeSaw is similar to the concept of instant messaging. Therefore, we include this paper in the email and instant messaging social technique. Social Connectivity: Designated The tool proposed in the paper, CodeSaw, utilizes emails and instant messaging to support communication and coordination between developers. CodeSaw was specifically designed to support large projects of distributed software development. Therefore, we include this paper in the designated tool. Social Interaction: One-to-many The paper described the use of email through mailing list and spatial messaging through the visualization that were used by CodeSaw. Through this tool, we conclude that the interaction that occurs between developers is a one-to-many social interaction. CodeSaw utilized the mailing list to provide information in the visualization. Furthermore, the description of spatial messaging implicitly described comments left in the visualization were available for other developers involved in the project. Social Location: Distributed The paper explicitly stated that the use of CodeSaw is to support distributed software development. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversation, Sharing, and Presence The paper proposed a tool to visualize a combination of code repositories and project communication. We include this paper in several honeycomb blocks. Conversation represents the communication occurs between developers through mailing list and spatial messaging. Sharing represents the information exchange through visualization. Furthermore, Presence represents the performance of other users in completing their tasks.

218

Paper Title: Authors Affiliations Publication

Annoki: A MediaWiki-based Collaboration Platform : Tansey, B. and Stroulia, E. : University of Alberta, Alberta, Canada : Proceedings of the 1st International Workshop on Web 2.0 for Software Engineering (Web2SE) 2010, Cape Town, Africa Publication Year : 2010 Origin of the Paper : Canada Summary: The paper introduced a Wiki tool that utilizes the MediaWiki collaboration platform to support its performance. Annoki was claimed to improve organization, manage access, assist creation, and display information regarding content stored in the Wiki. The platform of this tool is described in the paper, including the experience of implementing Annoki in two separate manners. Criteria: Areas of Study: Requirements/Specification, Design, Distribution, Maintenance, and Enhancement, Management, and Metric The paper described a tool that was utilized to provide space for requirement and design collaborative document. The tool was also used to file informal bug reports or request for features. Therefore, we include this paper in the areas of study as mentioned above. Furthermore, the tool provides metric calculation to identify the planning and implementation of a project. Research Type: Experience The paper presented the experience of the authors in utilizing the Annoki tool in the Software Engineering Research Lab (SERL), as well as implementing it as a platform for other collaboration tools. The architecture of Annoki, including the installation process for both manners, was described in the paper. Form of Study: Observation The paper introduced a collaboration platform to support collaborative work on the web. The authors of the paper described the architecture of Annoki including features that support collaboration to increase the work quality and productivity. Furthermore, the installation process and the adoption of Annoki for other tools were also described in the paper. Social Techniques: Wiki The paper focused its research and discussion on the use of Wiki to assist collaborative work. Although the paper mentioned that the Wiki allows users to assigned tags on their page, it did not discuss any further towards the use of tags. Therefore, we only include this paper into Wiki social technique. Social Connectivity: Adapted The paper described a tool that enabled collaborative work by web by using Wiki. It mentioned that the collaboration platform used for building Annoki is a free web-based wiki software, MediaWiki. Therefore, we include this paper into the adaptive connectivity. Social Interaction: One-to-many and Many-to-many Considering the nature of the social technique described in the paper, we include this paper into one-to-many and many-to-many interaction. Wiki enables collaborative work through editing where each user may build a page of content for other users (one-to-many interaction) then edited by other users to improve its content for other users as well (many-to-many interaction). Social Location: Localized The paper did not describe how the tool covers locations of the team members that utilize it. However, the paper mentioned that Annoki has been deployed to a Software Engineering Research Lab located at the University of Alberta and adopted for the development of WikiDev 2.0 accommodating team from the University and students. Therefore, we include this paper in the localized location. Honeycomb framework: Sharing and Presence The paper introduced Annoki to support collaboration for collaborative work by using Wiki. We include this paper in several honeycomb blocks. Sharing represents the information exchanged through building pages and collaboratively editing the content. Presence represents the availability of other users to build pages and perform editing towards the existing pages.

219

Paper Title: Authors Affiliations Publication

Automatic Status Updates in Distributed Software Development : King, A. and Lyons, K. : University of Toronto, Canada : Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering (Web2SE) 2011, Waikiki, Honolulu, Hawaii Publication Year : 2011 Origin of the Paper : Canada Summary: The paper proposed a plug-in that could automatically determine a user's activity in the Eclipse IDE and published the activity information as a status of the user's instant messenger client. A series of surveys through questionnaires and interviews were conducted to identify the usefulness of the proposed method to increase awareness between developers. Thorough results from the analysis to address the research questions were presented in the paper. Criteria: Areas of Study: Requirements/Specifications, Design, Coding, Software/Program Verification, Distribution, Maintenance, and Enhancement, and Management The paper presented a research in identifying the usefulness of an automatic status publication that showed the user's current activity in a distributed software development environment. This research was conducted using a number of respondents. However, the paper did not explicitly describe the areas of software lifecycle that the respondents relate to the use of the ASU tool. Therefore, we include this paper in several areas of study as mentioned above. Research Type: Evaluation The paper proposed a plug-in tool, ASU, which enabled automatic status publication based upon the user's current activity. The authors conducted an evaluation through questionnaires and interviews to identify the usefulness of this proposed tool. Research method, data collection and analysis including the results were described in the paper. Form of Study: Case Study Research in the paper conducted case study divided into two groups. The first group of respondents was interviewed after viewing a poster presentation describing the ASU tool, while the second group of respondents was interviewed after being shown a demonstration of the ASU tool, including viewing the poster presentation. The paper presented comparison and analysis results from both groups to address the research questions. Social Techniques: Instant Messaging The paper proposed a plug-in tool that enabled automation status update published to an instant messenger used by the developers. Therefore, we include this paper in the instant messaging social technique. Social Connectivity: Designated The paper proposed an Eclipse plug-in that enabled automatic status update based on the user's current activity. ASU tool was designed specifically to provide awareness between developers by updating status in instant messenger for other developers. Therefore, we include this paper in the designated tool. Social Interaction: One-to-many Considering the method used by the ASU tool to provide information for other developers through automatic status update, we include this paper in the one-to-many interaction. This means that each user automatically updated their status by using ASU to inform other developers. Social Location: Distributed The paper explicitly focused the conducted research in the distributed software development environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Presence The paper proposed a plug-in tool to increase awareness between developers in a distributed environment. Considering the use of this tool, we include this paper in the Presence honeycomb block that represents the awareness environment between developers.

220

Paper Title: Authors Affiliations Publication

Exploring the Role of Instant Messaging in a Global Software Development Project : Dittrich, Y. and Giuffrida, R. : University of Copenhagen, Denmark : Workshop (Doctoral Symposium) Proceedings in the 6th IEEE International Conference on Global Software Engineering, ICGSE 2011, Helsinki, Finland Publication Year : 2011 Origin of the Paper : Denmark Summary: The paper presented an empirical research of the communication method used by a small and distributed software development team. The study emphasized the use of instant messaging to build trust and awareness among developers and to build a connection between various other communication methods. The paper described investigation towards the use of instant messaging and results from it were presented in the paper. Criteria: Areas of Study: Requirements/Specification, Coding, Distribution, Maintenance, and Enhancement, and Management The paper described the areas that require collaboration between different sites from the case study presented in the paper. Communication that occurs through instant messaging mainly discussed requirements, coding and debugging, and coordinating task management. Therefore, we include this paper in the several areas of study as mentioned above. Research Type: Evaluation and Experience The paper presented a report of an empirical research towards collaboration between distributed software development environments, based upon the authors' experience. The authors described the case study conducted to identify the use of instant messaging as the coordinator of other communication methods. An evaluation of how instant messaging can be used to support software development was conducted through several qualitative studies. Results from this study were presented in the paper. Form of Study: Case Study Research in the paper conducted a case study using a small software development team in a distributed environment. The paper described the collaboration process that occurred between sites and how they mainly utilized instant messaging. The result showed that instant messaging not only coordinated communication among developers but also helped to increase awareness and sense of closeness. Social Techniques: Instant Messaging and Email The paper described several collaboration methods used by developers to work and communicate between sites. However, considering our main study in the topic of social media, we only identify the social techniques used by the developers. This includes instant messaging and email. Social Connectivity: Public The paper explicitly described the use type of social technique used in supporting communication for collaboration between developers in the case study. They utilized Skype, a public application for instant messaging communication. Considering the instant messaging communication uses a public application, we can only assume that the email used by the developers were also from public email. Social Interaction: Mixture The paper described the use of instant messaging and email between developers in the case study was to support one-to-one communication and collaboration. We assume that the collaboration activity described involves more than two developers communicating and brainstorming for solution or decision making. Therefore, we include this paper in the mixture social interaction. Social Location: Distributed The paper explicitly stated that the main study of the research was to identify the collaboration method used by a small team software development that were located in a distributed fashion. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Conversation, Sharing, and Presence The paper presented an empirical research towards the collaboration method emphasizing the use of instant messaging. We include this discussion in several honeycomb blocks. Identity represents the user profile of other developers through the Skype contact list. Conversation represents communication that occurs between developers either work or non-work related. Sharing represents the information exchange between developers through instant messaging, and Presence represents the awareness between developers through the availability displayed in contact list.

221

Paper Title: Authors Affiliations Publication

Factors Affecting Audio and Text-based Communication Media Choice in Global Software Development Projects : Niinimaki, T., Piri, A., and Lassenius, C. : Helsinki University of Technology, Finland : Proceedings in the 4th IEEE International Conference on Global Software Engineering, ICGSE 2009, Limerick, Ireland Publication Year : 2009 Origin of the Paper : Finland Summary: The paper presented an empirical study in a distributed software development environment, comparing the use of text-based communication with ad-hoc audio conferencing. The study was conducted using two software companies and eight case projects that were entirely distributed. The results showed the reasons for members of a project to communicate with certain tools compared to the others. A domplete description was provided in the paper. Criteria: Areas of Study: Requirements/Specification, Design, Coding, Software/Program Verification, Distribution, Maintenance, and Enhancement, and Management The paper identified the use of various communication tools in different levels of a software development project. It mentioned that communication tools were used from managerial level to software development. We assumed that these various levels encompass multiple areas of study as listed above. Research Type: Experience The paper conducted research using two different companies to identify the use of various communication tools in a software development environment. The result showed that there are different preferences in communication tool between managerial level and technical level. Reasons and background of this difference were described in the paper. Form of Study: Case Study The paper conducted eight case studies from two different companies that were entirely distributed. Data were collected through interview and were analyzed to identify the different use of communication tools at different levels. The result showed that text-based communication tools were still preferable compare to ad-hoc audio communication. However, there are certain situations that require different preferences, as described in the paper. Social Techniques: Email and Instant Messaging The paper compared text-based communication tools with ad-hoc audio communication tools and how they were used in different levels within software development project. The paper described text-based communication tools utilized by the project were email and instant messaging. Therefore, we include this paper in the email and instant messaging. Social Connectivity: Adapted The paper mentioned the types of tools used to support instant messaging communication. They were Lotus Notes SameTime and Microsoft Office Communicator. We assumed that these tools were also available for supporting other communication and not only for software development. Therefore, we include this paper in the adaptive connectivity. Social Interaction: Mixture The paper described communication mode that occurs between members of the software development project. The tools supported a one-toone communication, although if necessary it can also support many-to-many communication through instant messaging. Furthermore, email was described as the enabler of one-to-many communication. Therefore, we include this paper in the mixture social interaction. Social Location: Distributed The paper explicitly described the research presented were to identify distributed software development environment. Furthermore, based on the case study, the eight case studies conducted as described in the paper were entirely located in a distributed fashion. Honeycomb framework: Identity, Conversation, Sharing, Presence, and Groups The paper discussed the use of various communication tools at different levels within a software development environment. We include these tools in several honeycomb blocks. Identity represents other members' user profile through contact list in instant messaging. Conversation represents communication that occurs between members through chat and email. Sharing represents information exchange between members that occurs along communication. Presence represents the availability of other members notified through instant messaging, and Groups represents the mailing list grouping based on topic discussion. *Briggs, R. O. and Gruenbacher, P., 2002. EasyWinWin: Managing Complexity in Requirements Negotiation with GSS [online]. In: Proceedings of the 35th Annual Hawaii International Conference on System Sciences, 7 - 10 Januari 2012. Available from: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=993880 [Accessed 29 August 2013]

222

Paper Title: Authors Affiliations

Tools to Support Global Software Development Processes: A Survey : Portillo-Rodriguez, J., Vizcaino, A., Ebert, C., and Piattini, M. : University of Castilla-La Mancha, Ciudad Real, Spain Vector Consulting Services, Stuttgart, Germany Publication : Proceedings in the 5th IEEE International Conference on Global Software Engineering, ICGSE 2010, Princeton, NJ, USA Publication Year : 2010 Origin of the Paper : Spain and Germany Summary: The paper presents a description of existing tools that provide support for collaboration in a software development environment. These tools were classified using the ISO/IEC 12207 standard to determine which software lifecycle was supported by each tool. A complete description of these tools and challenges that might occur in using them was presented in the paper. Criteria: Areas of Study: Requirements/Specification, Design, Coding, Software/Program Verification, and Management The paper discussed various existing tools that provide support for collaboration in a software development environment. The tools described in the paper supported several areas of study within a software lifecycle as mentioned above. Several tools were also identified to enable multiple areas of study. Research Type: Experience The research presented in the paper identified several challenges that occur within a distributed software development. The survey conducted by the authors was to investigate various existing tools that could address the identified challenges. This survey discovered a list of various potential tools that could be considered to meet the needs of distributed software development. Form of Study: Case Study The paper claimed that the research presented was derived from a survey that uses the ISO/IEC 12207 standard to classify its result. However, the paper did not describe an in-depth survey regarding its subject, methods and analysis. Social Techniques: General Concept The paper did not explicitly describe any specific social technique. However, the tools discussed in the paper utilized one or more social techniques to provide support for the collaboration process. Therefore, we include this paper in the general social technique. Social Connectivity: Designated and Adapted The paper described various existing tools to support collaboration in a software development environment. From these tools, we recognized several tools that were not specifically built to assist software development (e.g. GoogleDocs). Therefore, we include the tools in this paper in the designated and adaptive connectivity. Social Interaction: Mixture The result from the survey in the paper provided a table that lists various existing collaboration tool classifications based on the ISO/IEC 12207 standard and communication mode. Based on the communication mode, we conclude that the social interactions applied to these tools are a mixture of various interactions. Social Location: Distributed The paper presents a survey of existing tools used for supporting collaboration in distributed software development environment. The tools described in the paper were specifically used to support a distributed environment, although it did not rule out the possibility of being used within a localized environment. Honeycomb framework: Identity, Conversation, Sharing, Presence, Relationship, Reputation and Groups The paper discussed various tools used to support collaboration in a software development. These tools provides various communication technique and connection method in supporting collaboration. Considering this, we conclude that the list could be described using the entire honeycomb block. Therefore, we include this paper into the blocks as mentioned above.

223

Paper Title: Authors Affiliations Publication

Collaboration in Software Engineering: A Roadmap : Whitehead, J. : University of California, Santa Cruz, USA : International Conference on Software Engineering, ICSE 2007 Workshop on the Future of Software Engineering, FOSE 2007 Publication Year : 2007 Origin of the Paper : USA Summary: This paper presents the importance of collaboration in software engineering. It described each stage of software development (requirements, architecture, design, testing and inspection, and traceability and consistency) supported by collaboration tools or applications. Thus, it presents guidance for future collaboration development using novel communications technologies. Criteria: Areas of Study: Requirements/Specification, Design, Coding, and Software/Program Verification The paper covered a wide area of software engineering. It described the existing tools and applications used for collaboration in each phase of software development, including the importance of its performance. Therefore, this paper is categorized in the least of four above criteria. Research Type: Opinion A number of goals, benefits and challenges including guidance for future development are presented in this paper. However, the paper was presented from the author's point of view, supported by examples and arguments without introduce or propose any new designs, techniques or methods Form of Study: Literature Review The paper provided an overview of existing studies in collaboration tools used in various areas to support software engineering. Based on these tools, the paper identified the trend that could indicate the future of collaboration tools. A description of the search results and future improvements were presented in the paper. Social Techniques: General Concept The paper did not explicitly describe any specific social techniques. However, considering a number of tools described in the paper to provide an overview of the existing collaboration tool, we include this paper in the general social technique. Social Connectivity: Designated The paper described existing collaboration tools and applications to support various areas within software development. These tools were specifically designed to provide support for communication and collaboration between stakeholders involved in a project. Therefore, we include this paper in the designated connectivity. Social Interaction: Mixture Due to the general discussion towards collaboration tools and applications in this paper, multiple social interactions are applied to this paper. The adaptation of direct social media, i.e. instant messaging and emails represents a one-to-one interaction, whereas others, i.e. mailing list and forum represent a one-to-many interaction. Social Location: Distributed The paper is focused upon distributed collaboration supported by the tools and applications described and proposed in the paper. Honeycomb Framework: Conversation, Sharing and Presence The paper described several techniques commonly used for communication between members of software development project. However, since the paper only provide an overall view of the necessary communication in a distributed project, it emphasized in the need of interaction and awareness. Therefore, we include this paper in the conversation, sharing, and presence block.

224

Paper Title: Authors Affiliations Publication

Sharing Usability Information in Interactive System Development : Bach, P. M., Jiang, H., and Carroll, J. M. : Penn State University, USA : Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : USA Summary: The paper reports a survey conducted in a large technology company to identify how usability sharing was performed among various levels of members in development teams. A survey was performed to gain information of the current methods used to share usability was through social computing. However, the survey also showed that most of the members preferred a very different approach towards sharing methods. Criteria: Areas of Study: Coding The main discussion of the study is to identify how usability is shared among various levels of members in development teams. Information about usability is required for developers to interpret design into codes. Therefore, we included usability sharing in the coding environment. Research Type: Evaluation The study is conducted to understand the methods of usability sharing in a large technology company. Information was retrieved and analyzed based upon an exploratory survey. This paper is the evaluation report of the study. Form of Study: Case Study/Observation The observation was performed at a large technology company by conducting an exploratory survey focusing on the usability sharing methods. From a series of survey questions, only three questions were used and reported in this paper. Social Techniques: Email, instant messaging, blogs, and wikis The survey result showed that most members of the company used several social techniques to share the discussion about usability. These techniques were emails, instant messaging, and web tools that included blogs, wikis and other collaborative web tools. Social Connectivity: Public Social techniques mentioned in the paper were publicly available and were not built intentionally to facilitate usability or sharing. There is no designated tool mentioned or proposed to support the sharing or act as an alternate of current used tools. Social Interaction: Mixture Since the paper covers various types of social techniques, we conclude that a mixture social interaction applies to this paper. Social Location: Mixture The paper implies that the observed company is a large localized. However, in the main discussion of the information sharing pattern, there's a possibility to have members that were distributed. Therefore, we categorize the social location as mixture. Honeycomb Framework: Identity, Conversation, Sharing, Presence, and Groups Considering the social techniques used for communication between developers in local and distributed area, we categorize this paper in several blocks of the honeycomb framework. Identity represents the other users that were revealed through blogs and wikis. Conversation and Sharing represents the communication using email and instant messaging. Furthermore, the ability of these tools to increase awareness is represented by Presence.

225

Paper Title: Authors Affiliations

The Economy of Collective Attention for Situated Knowledge Collaboration in Software Development : Ye, Y., Nakakoji, K., and Yamamoto, Y. : University of Colorado SRA Key Technology Lab, Tokyo, Japan KID Laboratory, RCAST, Tokyo, Japan Publication : Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : USA and Japan Summary: The paper proposed a new conceptual framework known as collective attention economy to understand the cost of different communication mechanisms in knowledge collaboration. This paper provides a comparison of a conventional mailing list with an ephemeral mailing list to identify the cost benefit structure. Result showed that the framework is capable to support in designing a new communication mechanism. Criteria: Areas of Study: Coding The paper did not explicitly describe the use of the collective attention economy as applied in a coding environment. However, the main purpose of the collective attention economy is to facilitate programmers to collaborate and share information with other programmers in an efficient way. Therefore, we include this paper in the coding environment. Research Type: Solution and Philosophical The paper proposed a new conceptual framework of collective attention economy to increase programmer's efficiency in searching for information. Form of Study: Experiment The paper illustrated two different communications using the conceptual framework to identify which mechanism is more efficient for each stakeholder. The result showed that the combination of emails and mailing list that is the ephemeral mailing list (EML) provided the most efficient collaboration. Social Techniques: Emails Social communication technique described as the mediator in the paper was conventional emails and ephemeral mailing list implemented in the STEP_IN system. Social Connectivity: Adapted Although conventional email that is public tool is discussed in the paper, the use of the ephemeral mailing list showed a significant difference in efficiency compare to the conventional email. The ephemeral mailing list is implemented by the STEP_IN system that is an adapted tool for facilitating collaboration. Social Interaction: One-to-many The ephemeral mailing list adopted both emails and mailing list to connect the asker to the specific helper. The system will automatically recognize the request and direct the questions by askers to the right group of expertise. Therefore, we conclude the social interaction into oneto-many. Social Location: Distributed The purpose of this new conceptual framework is to efficiently facilitate knowledge sharing for distributed software development. Honeycomb Framework: Conversation and Sharing Considering the type of social technique used in this paper to identify the cost benefit structure, we conclude this paper into the conversation and sharing blocks of honeycomb framework.

226

Paper Title: Authors Affiliations

Adinda: A Knowledgeable, Browser-Based IDE : Deursen, A., Mesbah, A., Cornelissen, B., Zaidman, A., Pinzger, M., and Guzzi, A. : Delft University of Technology, Netherlands Software Improvement Group Amsterdam, Netherlands Publication : Proceedings of 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010, Cape Town, Africa (New ideas and emerging results) Publication Year : 2010 Origin of the Paper : Netherlands Summary: The paper proposed an experimental approach to integrate services provided by IDE and made it available to be accessed through web browser supported by web 2.0 technologies. The paper described the author's visions and challenges in developing ADINDA, and it also presents the initial results of ADINDA's implementation. Criteria: Areas of Study: Maintenance The paper mentioned several services that ADINDA will assist, including compiling, editing, and testing. These activities are included in the maintenance category. Therefore, we include this study in the maintenance category. Research Type: Solution The paper proposed an approach to integrate services accessible by web browser. The paper also mentioned an initial evaluation of ADINDA, however it did not report the process or even the result of the evaluation. Therefore, we include this paper only into the solution research type. Form of Study: Non-empirical The paper introduced ADINDA to collect information when developers interact with the system. The vision of ADINDA, including research challenges to develop ADINDA, is provided in the paper. However, the research in the paper did not describe any empirical study performed using ADINDA. Therefore, we include this paper in the non-empirical form of study. Social Techniques: Tag and Blog/Microblog In the paper, ADINDA was proposed to adapt the web 2.0 collaboration techniques. Tagging and microblogging were proposed to support the informal communication and collaboration for software development projects. However, the implementation of microblogging has been trialled by applying James as a plug-in to combine status messages for data collection. Social Connectivity: Adapted In one of the experiments, an implementation of James as a plug-in adapted the use of microblogging to provide status messages of what a developer is doing. The messages would then be combined with information from other developers that were currently navigating through the code. Social Interaction: One-to-many A single post of short status messages from a developer will be available for other developers. This means that the interaction is one-to-many. Social Location: Localized It is not explicitly mentioned in the paper that ADINDA only covers localized area. However, in the related work discussion, it was mentioned that the approach is relevant for distributed work. This means that this approach is currently only applied for local area. Honeycomb Framework: Sharing and Relationship Social techniques described in the research were represented by at least two different blocks of the honeycomb framework. Sharing represents the information provided in the microblogs and relationship represents the node that ties users from tagging.

227

Paper Title: Authors Affiliations Publication

Syde: A Tool for Collaborative Software Development : Hattori, L. and Lanza, M. : University of Lugano, Switzerland : Proceedings of 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010, Cape Town, Africa. Formal research demos Publication Year : 2010 Origin of the Paper : Switzerland Summary: The paper introduces a tool with a novel approach of delivering the precise change in source code to the right developer. The main purpose of this tool is to rebuild awareness between developers by providing relevant information, whilst preventing information overload. Criteria: Areas of Study: Coding The paper discussed a tool that increases awareness among developers in a coding environment. The information filtering to build awareness is aimed at improving coding collaboration. Research Type: Solution Syde provides a real-time ability for developers to identify changes in codes. This method assists developers in conducting software development. Form of Study: Case Study According to the paper, assessment and adaptation has been performed to Syde through several case studies. However, the paper did not explicitly describe any of the case studies conducted to assess Syde. Social Techniques: Dashboard The paper did not explicitly mention the social technique used in Syde to support the communication between developers. However, the paper described several plug-ins implemented by Syde to support collaborative work. This plug-ins has its own interface that combines into a dashboard. Therefore, we include this paper into dashboard technique. Social Connectivity: Designated Syde is specifically designed to increase awareness among developers by assisting collaboration in coding environment. It has several plug-in to improve its facilities. Social Interaction: One-to-many Collaboration in the coding environment allows developers to identify changes performed by other developers. This means that any developer that is working on certain code is visible to many other related developers. Social Location: Distributed The paper did not explicitly mention the social location covered by Syde. However, the paper described the background rationale of Syde was to assist developers in a distributed environment. Therefore, we include this paper in the distributed location. Honeycomb Framework: Identity, Sharing, and Presence The paper introduced Syde’s infrastructure to increase team awareness by sharing information between developers in a distributed environment. We include this paper in several honeycomb blocks. Identity represents the user that conducted changes in codes as shown through one of the Syde's plug-in. Sharing represent the information exchange between developers performed through Syde. Furthermore, Presence represents the collaborative process of other users in performing changes to the codes.

228

Paper Title: Authors Affiliations Publication

The Hidden Experts in Software-Engineering Communication : Kwan, I. and Damian, D. : University of Victoria, Canada : Proceedings of 33rd International Conference on Software Engineering, ICSE 2011, Waikiki, Honolulu, USA (NIER Track) Publication Year : 2011 Origin of the Paper : Canada Summary: The paper presented a study of knowledge sharing among developers that involves experts. The study examines emails sent between developers and identified certain situations described in the emails that required experts to be involved. A case study was used to conduct the study and the result showed that experts not only respond to emergencies, but also to routine tasks. Criteria: Areas of Study: Management According to the study, information exchange through emails in the distributed team was mostly about requirements, testing, scheduling, resource allocation, implementation, and IT support. Therefore, we classified this study into management as it covers most of the areas mentioned earlier. Research Type: Evaluation The paper examines emails from a distributed team looking for emergent people and their involvement in certain discussions. Therefore, an evaluation was conducted to collect data and analyze the result. Form of Study: Case study A case study was conducted using a project team in a large corporation. The study collected emails and analyzed them to seek for emergent people involvement. Social Techniques: Email/Alert The paper mentioned several communication techniques used by the teams to communicate. However, the study focused on examining emails and analyzed the involvement of the emerging people in the emails. Social Connectivity: Public The paper did not explicitly mention a specific tool used by the teams to create communication and collaboration. Therefore, we conclude that the connection used by teams was performed through public tools. Social Interaction: One-to-many The use of emails applies to one-to-one social interaction through direct emails between developers. However, according to the study presented in the paper, most of the emails were directed to more than one recipient. Therefore, this study applies to one-to-many social interaction. Social Location: Distributed The paper used a case study of a software team in a large corporation. The team was distributed in different locations including Brazil, America, and Malaysia. Honeycomb Framework: Identity, Conversation, Sharing, and Reputation The paper conducted a research of why developers emerge in discussion within a distributed software development environment. Considering the type of social technique investigated in the paper, we conclude this paper in several honeycomb blocks. Identity represents the profile of the emergent people, Conversation represents communication between team members, Sharing represents information sharing between team members and emergent people, and Reputation represents the rank of importance of the emergent people.

229

Paper Title: Authors Affiliations Publication

Developing Requirements in an Established Domain Using Tags and Metadata : Cotran, L. C. and Taylor, R. N. : University of California, Irvine, USA : Proceedings of the Requirements Engineering for Systems, Services and Systems-of-Systems (RESS) Workshop, Trento, Italy Publication Year : 2011 Origin of the Paper : USA Summary: The paper introduced a technique that used existing information systems combined with the concept of 'reuse' to build requirements. COTRAN combines two approaches including making use of tags to connect requirements to correlating architecture and designs (either new or existing), and making use of a matrix to create an index of the tags. This paper provides a description on how to use COTRAN, with the example of FireSat spacecraft. Criteria: Areas of Study: Requirements/Specifications The paper described a technique to produce requirements using tags and metadata. The matrix provides the contextual information to write the requirements and tags allowed developers to reuse an existing system. This means that COTRAN supports the requirements area among other areas of study. Research Type: Solution The paper introduced COTRAN to enable the concept of reuse of an existing system to support requirements while targeting a better scope and testable requirements for further development. COTRAN provides efficiency by organizing requirements around the metadata and tags. Form of Study: Experiment The paper provides an example of an existing FireSat spacecraft to illustrate the use of COTRAN. The requirements for the FireSat spacecraft were defined using COTRAN. As the result, the authors built requirements in the matrix needed for the FireSat. Social Techniques: Tag The paper explicitly described the use of tags to identify requirements and connect them to the correlated architecture and design artifact. Therefore, we include this study in the tagging social technique. Social Connectivity: Designated The tagging and metadata described in the paper are specifically built to support the organization of the requirements. Therefore, we include this paper in the designated social connectivity. Social Interaction: One-to-many As described in the paper, a single tag can hold several pieces of information, depending on what is stored in the matrix. Other than that, the artifact tagging is used by the developers where the tags themselves were updated by developer to support other developers. Social Location: Localized The paper did not explicitly describe the social location covered by the COTRAN. However, considering the scope where the research was conducted, we conclude that this paper only covers localized location. Therefore, we include this study in the localized social location. Honeycomb framework: Sharing The paper explicitly described the reuse concept used by the COTRAN that involved previously existing systems. Therefore, the representation of sharing is included in this study.

230

Paper Title: Authors Affiliations Publication

Social Media for Software Engineering : Begel, A., DeLine, R., and Zimmermann, T. : Microsoft Research USA : Proceeding of the Workshop on Future of Software Engineering Research, FoSER 2010, at the 18th ACM SIGSOFT International Symposium on Foundations of Software Engineering, 2010, Santa Fe, USA Publication Year : 2010 Origin of the Paper : USA Summary: This paper presents significant factors of social media that have changed people’s collaboration and information sharing. It emphasizes the current use of social media, and how they can be applied to support software engineering. Descriptive points of benefits and challenges are presented, supported by examples. Criteria: Areas of Study: Management This paper described the potential of using social media at each stage of software development activity, starting from connecting with other programmers, exchanging ideas, collaborating, and developing the software. However, it only described the collaboration itself where it has the tendency to encompass a wide area of software engineering. Therefore, we include this paper as management due to its focus to manage the software development activities. Research Type: Opinion This paper introduces the benefits, the challenges, and the features of using social media to support software engineering. However, the study only presents descriptions of each features and challenges from the author's point of view, which it is supported by examples and arguments. It did not propose any new designs, techniques or methods. Form of Study: Non-empirical The paper described the authors' point of view without being supported by any empirical research. Therefore, we include this paper in the nonempirical form of study. Social Techniques: General Concept This paper focused on the use of social media in general to support software engineering. However, it discussed most of the current social media used publicly rather than a specific tool or application. Therefore, this study includes several commonly used social media as it is classified in this category. Social Connectivity: Public The study discussed social media tools or applications that were used publicly in general. It did not mention any adaptation applied to the tools or applications in order to facilitate the collaboration. Therefore, we include the study in the public tools. Social Interaction: Mixture Due to the general discussion of social media used in this paper, multiple social interaction is applied to this paper. The use of direct social media i.e. instant messaging represents a one-to-one interaction, whereas other social media i.e. blogs/microblogs and tagging represents a one-to-many interaction. Furthermore, crowd sourcing and social networking represents the many-to-many interaction. Therefore, we include this paper into the mixture interaction. Social Location: Distributed Due to its public usage, current social media connects people and create collaboration regardless geographic location. Therefore, we include the study in the distributed criterion. Honeycomb Framework: Groups, Conversation, Sharing, Presence, Identity, Relationship, and Reputation The paper discussed a general topic of using social media for software engineering. Several prominent types of social techniques were described related to their potential and challenges. Therefore, we conclude that the general discussion of this paper is included in the honeycomb blocks as mentioned above.

231

Paper Title: Interactional Identity: Designers and Developers Making Joint Work Meaningful and Effective Authors : Brown, J. M., Lindgaard, G., and Biddle, R. Affiliations : Carleton University, Ottawa, Canada Publication : Proceedings of the 2012 ACM Conference on Computer Supported Cooperative Work, CSCW, Seattle, USA Publication Year : 2012 Origin of the Paper : Canada Summary: The paper presented a research of collaboration between developers and designers. The research seeks identities formed by each developer and designer that support their collaboration and help them effectively in accomplishing their work. The results showed a map of identified responsibilities and their identity, called interactional identity. Interactional identities are cognitive tools that support collaboration in multidisciplinary environments, and help individuals to select effective identities to work with. Criteria: Areas of Study: Design, Coding, and Management The paper presented an interactional identity to support collaboration between users in a multidisciplinary environment. This cognitive tool identifies individuals to help other members of the team to increase effective collaboration. We conclude that the tool supports collaboration in several different areas of study, including design, coding, and management. Research Type: Experience and Solution The paper provides a description of the author's experience in identifying interaction of individuals involved in software development teams. Results from identifying the individuals were mapped into interactional identity that was valued as cognitive tool. Utilizing the information in the interactional identity, this tool was then proposed to increase collaboration between team members. Form of Study: Observation and Case Study The paper explicitly described the environment used in conducting the case study. Eight organizations were involved where the authors conducted an observation for more than three months in total. Furthermore, a series of interviews were conducted to gain further information. Results from the observation and interviews were presented in the paper. Social Techniques: General Concept The paper did not explicitly describe the social technique used to gather and distribute knowledge derived from interactional identity. However, the paper mentioned that the interactional identity was used to provide information to better support collaboration. Therefore, we include this paper in the general social technique. Social Connectivity: Designated The paper proposed the use of interactional identity that is valued as a cognitive tool to support collaboration between members of software development team. This means that interactional identity is specifically built to meet the needs for supporting collaboration. Therefore, we include this paper in the designated tool connectivity. Social Interaction: Many-to-many The paper stated that information gathered to complete the interactional identity is through observation and interview. Furthermore, information included in the interactional identity is used to support collaboration between members of the team. This means that the interactional identity tool holds information of individuals involved in the team and is available to support other members of the team. Therefore, we include this paper in the many-to-many social interaction. Social Location: Localized The paper described a concept of interactional identity that links user identity with work interaction. However, the paper did not mention the location coverage of the relationship between the team members that were connected with the interactional identity. Considering the location scope described in the case study, we include this paper in the localized location. Honeycomb framework: Identity, Sharing, and Reputation The paper proposed the interactional identity tool to identify individuals involved in a software development team and provide collaboration support by using this information. We include this paper in several honeycomb blocks. Identity and Reputation represents the individuals involved in the team together with the importance of that individual within the team. Sharing represents the interactional information shared between the members of the team to increase collaboration.

232

Paper Title: Authors Affiliations Publication

On Coordination Mechanisms in Global Software Development : Cataldo, M., Bass, M., Herbsleb, J. D., and Bass, L. : Carnegie Mellon University, PA, USA : Proceedings in the 2nd IEEE International Conference on Global Software Engineering, ICGSE 2007, Munich, Germany Publication Year : 2007 Origin of the Paper : USA Summary: The paper presented a discussion about the breakdown of communication structure in software development projects based upon four study cases. Several factors were found from the case studies, thus the paper emphasized the analysis of the ability for communication and collaboration between developers. A set of frameworks to analyze the use of the communication and results of the content analysis were presented in the paper. Criteria: Areas of Study: Requirements/Specification, Design, Coding, Distribution, Maintenance, and Enhancement, and Management The paper described several areas within the software development lifecycle that were supported by the communication between developers. From the case studies described in the paper, we concluded that communication discussed involved requirements/specification, design, coding, and distribution, maintenance, and enhancement. Furthermore, we also assumed that the communication used within and between includes management area of study. Therefore, we include this paper in the areas of study as mentioned above. Research Type: Evaluation and Experience The paper presented two different researches, experience in identifying the existing communication between developers and the evaluation to identify the use of the communication based on the experience result. From the experience result, the authors identify several breakdown problems that occur in communication between developers specifically in distributed sites. From the evaluation analysis, the authors concluded that a set of communication tools might not be as supportive as required to support communication and collaboration. Form of Study: Case Study Research in the paper described several breakdown problems that occur in software development environment based on the case studies. From the result, the paper presented further analysis to identify the use of communication between developers in collocated and distributed teams. Results were presented in the paper. Social Techniques: Wiki, Email and Instant Messaging Research in the paper focused on a Global Studio Project (GSP) provided by Siemens Corporate Research. The environment provided several means of communication tool to support collaboration between developers. The paper mentioned the tools that were provided by GSP, including Wiki, Email, and Instant Messaging. Social Connectivity: Designated The paper did not explicitly describe the product of tools that were used to provide communication support within the GSP. However, we assumed that, since GSP is specifically built as a test bed to understand the issues within the global software development environment, communication tools used by GSP are specifically implemented to support collaboration between developers. Therefore, we include this paper in the designated connectivity. Social Interaction: Mixture Considering the type of social techniques used in the research, we concluded that a combination of those social techniques encompassed various types of social interaction. Therefore, we include this paper in the mixture social interaction. Social Location: Mixture The paper described the various social techniques used to provide communication support between developers that were used in localized and distributed environment. Therefore, we include this paper in the mixture social location. Honeycomb framework: Identity, Conversation, and Sharing The paper described the analysis of the communication tools used by the developers. We include this study into several honeycomb blocks. Identity represents the user profile of the other members involved through instant messaging and wiki editing. Conversation represents the communication that occurs between developers. Sharing represents the information exchange through Wiki and email.

233

Paper Title: Authors Affiliations Publication

Distributed Requirements Elicitation Using A Spatial HypertextWiki : Solis, C. and Ali, N. : University of Limerick, Ireland : Proceedings in the 5th IEEE International Conference on Global Software Engineering, ICGSE 2010, Princeton, NJ, USA Publication Year : 2010 Origin of the Paper : Ireland Summary: The paper proposed a new collaborative tool to support creativity in the requirement elicitation process through virtual boards. This tool allows stakeholders from distributed locations to share, brainstorm, negotiate, and prioritize the ideas involved for requirements. A complete description of the development background and the use of the tool is described in the paper. Criteria: Areas of Study: Requirements/Specification The paper described the use of ShyWiki and a number of benefits from using ShyWiki to support requirement elicitation. This tool enables brainstorming, defines templates and relations, and defines a conceptual model for requirement engineering. Therefore, we include this paper in the requirements/specification area of study. Research Type: Solution The paper proposed a tool to support collaboration in requirement elicitation between stakeholders in a distributed environment. The tool provides visualization for the stakeholders to exchange ideas and communicate in order to make decision. A complete description of what ShyWiki supported is presented in the paper. Form of Study: Non-Empirical The paper presented a comparison between ShyWiki and other tools that also uses Wiki to support collaboration between stakeholders. Existing studies were identified through literature review and ShyWiki tried to address the challenges that occurred in previous studies. Social Techniques: Wiki The paper explicitly proposed a tool that utilized Wiki in supporting requirement elicitation collaboration between distributed stakeholders. Therefore, we include this paper in the Wiki social technique. Social Connectivity: Designated The paper described the main aim of ShyWiki, which is to facilitate collaborative interpretation task through visualization. This means that ShyWiki is specifically built to address the challenge in requirement elicitation collaboration between distributed stakeholders. Therefore, we include this paper in the designated connectivity. Social Interaction: Many-to-many The paper described the use of ShyWiki in supporting requirement elicitation collaboration between distributed stakeholders. The ability of ShyWiki to provide spaces for brainstorming and negotiate enables many-to-many interaction through discussion within these spaces. Social Location: Distributed The paper explicitly described use of ShyWiki in facilitating collaboration requirement elicitation through visualization between stakeholders in a distributed software development environment. Therefore, we include this paper in the distributed social location. Honeycomb framework: Identity, Sharing, Conversation, and Groups The paper discussed the use of ShyWiki to facilitate requirement elicitation collaboration. We include this tool in several honeycomb blocks. Identity represents other stakeholder through stakeholder instance. Conversation and Sharing represents communication and information exchange through brainstorm spaces. Groups represents multiple session conducted in parallel fashion.

234

Paper Title: Authors Affiliations Publication

How Globally Distributed Software Teams Can Improve their Collaboration Effectiveness? : Gupta, M. and Fernandez, J. : SETLabs Infosys Technologies Limited, Bangalore, India : Proceedings in the 6th IEEE International Conference on Global Software Engineering, ICGSE 2011, Helsinki, Finland Publication Year : 2011 Origin of the Paper : India Summary: Research in the paper emphasized the identification of a collaborative pattern among members in a distributed software development environment, and suggested new practice or improved existing patterns to enhance effectiveness. A set of frameworks, GOCOS, was proposed to investigate the existing collaboration pattern by mapping expected key factors to the choice of communication mechanism. The use of this framework was described in the paper. Criteria: Areas of Study: Metric The paper described the use of the GOCOS framework to identify the effectiveness of the existing collaboration pattern. This was performed through mapping of the key factors of expected collaboration to the current communication mechanism. The results provided suggestions either to implement a new collaboration pattern or to improve the existing pattern. Research Type: Philosophical The paper proposed a framework to identify the effectiveness of the current collaboration pattern in supporting communication among distributed software development environment. Results from conducting a mapping could completely alter the communication mechanism or simply improve it. Therefore, we include this paper in the philosophical research type. Form of Study: Case Study Research in the paper conducted a case study of three different companies that work together in a distributed environment. Data was collected by interviewing the key roles involved in the project. Research was restricted only to cover the requirement and design phases, and the complete result was presented in the paper. Social Techniques: General Concept The paper did not explicitly describe a specific social technique used for supporting communication between developers. However, it described the importance of having the right communication mechanism to increase collaboration effectiveness. Therefore, we include this paper in the general social technique. Social Connectivity: Designated The paper introduced a framework to identify the effectiveness of the current collaboration pattern in a distributed software development environment. This framework was specifically designed to address the challenge of investigating current collaboration pattern thus increasing its effectiveness. Therefore, we include this paper in the designated connectivity. Social Interaction: Mixture The paper did not describe any specific social technique used in the research to provide communication support among the distributed environment. To encompass various interaction between each stakeholders in different companies, we conclude that the communication mechanism resulted from mapping the current collaboration involves mixture social interaction. Social Location: Distributed The paper explicitly proposed GOCOS to investigate the effectiveness of the collaboration mechanism in a real life project within a distributed environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Conversation and Sharing The paper proposed a framework to be used to investigate current collaboration mechanism. We include this framework in several honeycomb blocks. Conversation represents the communication that occurs between members of the team, and Sharing represents the information exchange between them.

235

Paper Title: Authors Affiliations

Distributed Developers and the Non-Use of Web 2.0 Technologies: A Proclivity Model : Al-Ani, B., Wang, Y., Marczak, S. Trainer, E., and Redmiles, D. : University of California, Irvine, USA Pontificia Universidade Catolica do Rio Grande do Sul (PUCRS), Porto Alegre, Brazil. Publication : Proceedings in the 7th IEEE International Conference on Global Software Engineering, ICGSE 2012, Porto Alegre, Rio Grande de Sul, Brazil Publication Year : 2012 Origin of the Paper : USA and Spain Summary: The paper presented an investigation of the factors that support the use and non-use of existing technologies to support communication in a distributed environment. The authors conducted both qualitative and quantitative analysis to identify these factors. Several factors were identified and the results were presented by using a proclivity framework. Suggestions related to designing collaboration tools were described to conclude the research. Criteria: Areas of Study: Management The paper described a research to identify factors that influenced the use and non-use of technologies in supporting communication. Chosen respondents were gathered from various roles including management and software developer (technical). This study provided a wider view encompassing various roles including non-technical. Therefore, we include this paper in the management area of study. Research Type: Evaluation The paper described an investigation conducted across several multinational organizations in a distributed environment. Research was performed to identify the factors that influenced the use and non-use of technologies to support communication. Several analyses was drawn to identify these factors, and the results were presented in the paper. Form of Study: Case Study Research in the paper was conducted through case studies of several projects across distributed multinational organizations. Data was collected through a series of interviews, either directly over VOIP or by other technologies. Analyses were performed through qualitative and quantitative means to define several factors that influenced the use and non-use of technologies. Social Techniques: Social Networking, Blog/Microblog, and Wiki Research in the paper focused on the technologies offered by Web2.0, including social networking, blogs/micro blogging, and wikis. The use of the techniques included in Web2.0 was not described in-depth in the paper. However, we include this paper in the social networking, blogs/micro blog, and wikis. Social Connectivity: Public The paper did not explicitly describe the type of social techniques used by the members of the project team in the case studies. It only mentioned that the use of these techniques was to support communication between team members in a distributed environment. However, considering that the social techniques discussed in the paper were included in the Web2.0, we include this paper in the public tool. Social Interaction: Mixture The paper explicitly described the ability of the social techniques included in the Web2.0, which were to share information from one member to other related members. However, considering the social techniques and combined with prior knowledge, we include this paper in the mixture social interaction. Social Location: Distributed The paper described the main objective of the research, which was to identify the factors that influence the use and non-use of technologies in a distributed environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Sharing The paper investigated several factors that influenced the use and non-use of technologies in a distributed software development environment. Social techniques mentioned in the paper were described in a general fashion. However, the result mentioned that the use of these technologies described in the paper was to support information sharing. Therefore, we include this paper in the sharing honeycomb block.

236

Paper Title: Authors Affiliations Publication

Near-Synchronicity and Distance: Instant Messaging as a Medium for Global Software Engineering : Jaanu, T., Paasivaara, M., and Lassenius, C. : Aalto University, Finland : Proceedings in the 7th IEEE International Conference on Global Software Engineering, ICGSE 2012, Porto Alegre, Rio Grande de Sul, Brazil Publication Year : 2012 Origin of the Paper : Finland Summary: The paper reported an investigation of the use of instant messaging in a distributed software development environment. The Media Synchronicity Theory (MST) framework was used to evaluate the usefulness of instant messaging in providing communication support. Semistructured evaluation was conducted to several distributed case projects through interviews. The assessment result was presented in the paper. Criteria: Areas of Study: Metrics The paper discussed a research to identify the usefulness of instant messaging in providing communication support. MST was used to measure the instant messaging usefulness based on five media capabilities, including immediacy of feedback, symbol variety, parallelism, rehearsability, and reprocessability. Therefore, we include this paper in the metrics area of study. Research Type: Evaluation The paper presented an evaluation of the use of instant messaging in a distributed software development environment. Evaluation result was mapped through an MST framework based on several media capabilities. Results were presented in the paper. Form of Study: Case Study Research in the paper conducted a case study using several distributed case projects. Data was collected through semi-structured interviews with respondents, ranging from management to software developers. Social Techniques: Instant Messaging The paper focused the research upon the use of instant messaging to provide communication support for distributed software development. The result showed that in order to gain more benefit, the use of instant messaging needs to be coupled with other communication method, e.g. email and video conferencing. Social Connectivity: Public The paper did not explicitly describe the type of social technique used in the evaluation process. However, we concluded that the instant messaging used in the discussion was a public tool. Social Interaction: Mixture The paper described the use of instant messaging, which was to provide communication support between team members in a distributed software development environment. Considering that the social interaction offered by instant messaging includes one-to-one interaction through direct communication and many-to-many interaction through group chat, we include this paper in the mixture interaction. Social Location: Distributed The paper explicitly described the main study of the research, which was to identify the use of instant messaging on the MST framework, based upon several distributed case projects. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Conversation, Sharing, and Presence The paper presented an evaluation of the use of instant messaging categorized using the MST framework based upon several case studies. We include this research in several honeycomb blocks. Identity represents the user profile of other developers through the instant messaging contact list. Conversation represents communication that occurs between team members. Sharing represents the information exchange between developers through instant messaging, and Presence represents the awareness between developers through availability displayed in contact list.

237

Paper Title: Authors Affiliations

A Research Agenda for Distributed Software Development : Sengupta, B., Chandra, S., and Sinha, V. : Indian Institute of Technology, India IBM Research Hawthorne, NY, USA Publication : 28th International Conference on Software Engineering (ICSE 2006), Shanghai, China Publication Year : 2006 Origin of the Paper : India and USA Summary: This paper presents a study in distributed software development, focusing on collaboration and sharing tools for software development. Several critical areas for distributed software development were discussed in depth, in order to raise possible research issues for improving collaboration. Criteria: Areas of Study: Coding, Requirements/Specifications, Software/Program Verification, and Metrics According to the author, the study covers four critical areas in distributed software development environment. The existing situations for each area were discussed and possible research issues to improve collaboration and sharing were raised. Research Type: Opinion The authors states their opinion of each area discussed in the paper. Raised issues and suggestions to overcome challenges were the author's opinion, supported by research result. Form of Study: Case Study/Observation This paper provides observation results performed at IBM Research. The areas of software engineering were investigated in a distributed software development environment. This research includes a survey of more than 30 practitioners involved across 14 different projects. Social Techniques: Email/Alert and Instant Messaging The paper did not investigate any specific social techniques used to support the collaboration. However, it was mentioned in the paper that the common techniques used by the developers are through emails and chat. The paper also described the use of Collaborative Development Environment (CDE) that is adapted specifically to the needs of the developers. Social Connectivity: Designated Collaboration through CDE as mentioned in the paper is a form of designated tools specifically built to support the distributed software development. Social Interaction: Mixture CDE is considered as a community portal that serves more than one type of social interaction. Therefore, we include this paper in the mixture category. Social Location: Distributed Considering the case study used for observation in this paper and the focus study in distributed software development, we categorize this paper in the distributed category. Honeycomb Framework: Conversation, Sharing, Relationship The paper described the communication used by the members of the project to conduct interaction. The communication itself, which is outside of the management tool, is used to converse and share information. Relationships among members were built during face-to-face meetings.

238

Paper Title: Authors Affiliations Publication

Continuous Coordination within the Context of Cooperative and Human Aspects of Software Engineering : Al-Ani, B., Ripley, R., Sarma, A., Hoek, A. V. D., and Redmiles, D. : University of California, USA : Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : USA Summary: The paper described several tools (Workspace Activity Viewer, Ariadne, and World View) that implement the paradigm of the Continuous Coordination (CC) to support the collaboration work and increase the awareness among software developers. The discussion focused on the social-aspect of how collaboration was formed with the assistance of these tools. Criteria: Areas of Study: Coding We conclude that the tools described in this paper function to support coding development. The Workspace Activity Viewer reveals simultaneous work on the same artifact to prevent overlapping in submitting code. Ariadne increased awareness among developers including sharing knowledge of each other’s roles. On the other hand, World View supports distributed development in global distributed projects. Research Type: Solution The paper described three different collaboration methods to support software development. Each method has gone through certain validation mentioned briefly in this paper. However, further validations are required to validate the performance of these tools. Form of Study: Non-empirical The paper did not provide any empirical study. However, the paper provided a description of the background study towards the functions adopted by WAV, Ariadne, and WV. Therefore, we include this paper in the non-empirical and literature review form of study. Social Techniques: General Concept This paper did not explicitly mention any social techniques used or adapted to the tools described. However, it explained the implementation of socio-technical collaboration in the use of the tools among developers. Social Connectivity: Designated Each tools described in this paper is designed specifically to facilitate collaboration among developers; even the World View is designed to support distributed development. Social Interaction: One-to-many The tools discussed in the paper mainly facilitate the relationship between developers with codes. Any update performed by a developer will notify other developers to prevent code overlap and to increase awareness. This kind of relationship is formed from one developer to another. Social Location: Mixture The paper did not explicitly describe the social location coverage of the mentioned tools. However, we conclude that the Workspace Activity Viewer (WAV) and Ariadne facilitate localized development as well as distributed development together with World View Honeycomb Framework: Sharing, and Relationship The paper presents three different tools that support collaboration between software developers. Furthermore, World View (WV) provides a central repository where it visualized sharing and the relationship between developers.

239

Paper Title: Authors Affiliations Publication

Cooperation and Coordination Concerns in a Distributed Software Development Project : Panjer, L. D., Damian, D., and Storey, M. : University of Victoria, Canada : Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : Canada Summary: The paper presents several key factors that emerged from a field study observation on how the developers maintained their awareness of dependencies in a distributed software development team. Each factor was described and further research plans were raised to improve the method used by the developers. According to the paper, further validation of activities performed by the developers to coordinate interdependent elements of projects is necessary. Criteria: Areas of Study: Design, Distribution, Maintenance, and Enhancement, and Management It is mentioned in the paper that developer builds awareness during the design and implementation phases. Furthermore, it investigated how people coordinate activities in a distributed environment. Therefore, we include this paper into the design, distribution, maintenance, and enhancement, and management categories. Research Type: Evaluation The paper observed the current collaboration and awareness system used in a distributed software engineering through a case study. From the observation, several important key factors to raise further research were described. Form of Study: Case Study The study of this paper was conducted at a regional office with approximately 100 people in a distributed software development organization. The result is based on seven project members that were involved in 31 teams worldwide. Social Techniques: Wiki The paper mentioned that developers used shared project wiki to post their activities within certain milestones where it also served as activity documentation. Therefore, we include this paper in the blogs/microblogs with consideration of similarities between the two social techniques. Social Connectivity: Designated Based on the case study, the paper did not explicitly describe the social technique used to support collaboration. However, we conclude that the technique used in the case study was specifically built to facilitate the collaboration of the distributed software development teams. Social Interaction: One-to-many The shared project wiki facilitate developers to identify other developer's status and build awareness in the project. Each wiki page provided information for more than one other developer. Therefore, we conclude that the paper has a one-to-many social interaction. Social Location: Distributed The study was conducted at a regional office of a large and geographically distributed software development organization. Furthermore, the participants were located primarily in North America and Europe. Therefore, this study has a distributed social location. Honeycomb Framework: Presence, Relationship, Conversation, and Sharing The paper described three significant importance resulted from observing the case study, proximity, modification request, and uncooperative behaviors. These results represent presence, relationship, conversation, and sharing consecutively from the honeycomb blocks.

240

Paper Title: Authors Affiliations Publication

The Application of Knowledge-Sharing Workspace Paradigm for Software Architecture Processes : Babar, M. A. : University of Limerick, Ireland : Proceedings of the 3rd International Workshop on Sharing and Reusing Architectural Knowledge, SHARK 2008, Leipzig, Germany

Publication Year Origin of the Paper

: :

2008 Ireland

Summary: The paper proposed the use of an electronic workspace paradigm to facilitate distributed collaboration in capturing and sharing knowledge. This is to support the software architecture processes as part of software engineering in global software development. An example of workspace provided by LiveNet is discussed in the paper to model the relationship between individuals in the global software development environment. Criteria: Areas of Study: Design The main purpose of the study is to propose the use of workspace in the global software development for sharing architecture knowledge. This knowledge is required to support the architecture processes as part of the design in software engineering. Research Type: Solution The paper proposed a solution for capturing and sharing architectural knowledge in distributed and virtual teams in the context of global development. It applies an electronic workspace paradigm to support the architecture process. Form of Study: Case Study The paper used workspaces provided by LiveNet to implement the model process for evaluating software architecture. LiveNet provided the majority features of knowledge sharing, and is free for research and education. Social Techniques: Dashboard It is mentioned in the paper that the social collaboration between users was applied through blogs or instant messaging (chat). However, since the main focus of the tools itself is considered similar to a dashboard where it has more than one social techniques applied, we categorize the study in the dashboard social techniques. Social Connectivity: Designated The paper proposed a specifically built tool to support capturing and sharing architectural knowledge. Therefore, we include this paper in the designated tool social connectivity. Social Interaction: Mixture It is mentioned in the paper that the social techniques used in the electronic workspace paradigm were a combination of several techniques. Therefore, we conclude that the interaction occurring between the developers is a mixture interaction. Social Location: Distributed The main purpose of this study is to propose a workspace paradigm to facilitate distributed software development. Honeycomb Framework: Conversation and Sharing The main purpose of the research in this paper is to propose the use of an electronic workspace to support architectural knowledge. Considering the social techniques implemented in the electronic workspace, we innclude this paper in several blocks of honeycomb framework. Conversation represents the communication that occurs between developers through instant messaging. Furthermore, Sharing represents information exchange between developer through both blogs and instant messaging.

241

Paper Title: Authors Affiliations

Predicting Build Failures using social Network Analysis on Developer Communication : Wolf, T., Schroter, A., Damian, D., and Nguyen, T. : Siemens Corporate Technology, Germany University of Victoria, Canada Publication : Proceedings of 31st International Conference on Software Engineering, ICSE 2009, Vancouver, Canada Publication Year : 2009 Origin of the Paper : Germany and Canada Summary: The paper described a study conducted on a set of data that was retrieved from IBM's distributed development project. The main purpose of this study was to identify the communication structure between developers to indicate the failure/success of a project. The result showed that communication between developers is an important factor for the quality of software integration. Criteria: Areas of Study: Management The main purpose of the study was to observe the importance of communication between software developers, and its ability to identify the failure or success of a project. Therefore, we considered that the activity is related to risk management. Research Type: Validation The paper described that a social network could not be used to indicate the success level of a project. However, the authors built a predictive model that combines network measures. This model was validated using several projects with results between 55% and 75%. Form of Study: Case Study The paper used data from the IBM Jazz project to study the high intensity communication structures of a development team. It builds a predictive model that could be used to indicate the success level of a project. We include this paper in the case study form of study. Social Techniques: General Concept The paper did not describe any specific social techniques used in communication between developers. However, this paper identified the importance of communication to leverage the success level of a project. Therefore, we considered the study provides a general discussion of the social techniques. Social Connectivity: Designated The model described in the paper uses data from the IBM Jazz environment. We consider Jazz as the tool that supports communication between developers. Jazz was specifically built to address the needs for collaboration between developers in a project. Therefore, we include this paper in the designated tool social connectivity. Social Interaction: Many-to-many Jazz is a development environment that enables collaboration between distributed developer locations. The paper did not explain type of interaction applied in Jazz but we concluded that Jazz has a many-to-many social interaction to enable collaboration. Social Location: Distributed The paper mentioned that the research main object is to study coordination instances during code integration in a large and distributed software teams in relation to the communication structures. Honeycomb Framework: Conversation, Sharing and Relationship Considering that the paper did not specify any social technique used in the communication between developer, we emphasized the relationship between communication structures and coordination outcome that determines the success level of a project. However, it also stated that developers performed communication through commenting. Therefore, we include this paper in the conversation, sharing, and relationship block.

242

Paper Title: Tesseract: Interactive Visual Exploration of Socio-Technical Relationships in Software Development Authors : Sarma, A., Maccherone, L., Wagstrom, P., and Hersleb, J. Affiliations : Carnegie Mellon University, USA Publication : Proceedings of 31st International Conference on Software Engineering, ICSE 2009, Vancouver, Canada Publication Year : 2009 Origin of the Paper : USA Summary: The paper introduced an approach to capture information towards relations between artifacts, developers, bugs, and communications. An interactive tool, Tesseract, utilized a web-based display to present gathered relationships among the developers. A complete description of Tesseract including the architecture and features are provided in the paper. The authors also included in the paper a validation of Tesseract using several experienced developers. Criteria: Areas of Study: Coding and Distribution, Maintenance, and Enhancement The main function of Tesseract is to facilitate communication and collaboration between developers related to code, bugs, etc. Therefore, we categorize this study into 2 different areas of study, coding and distribution, maintenance, and enhancement. Research Type: Evaluation and Validation The study evaluated Tesseract with data from a large-scale open source project. Consequently, validation on feasibility techniques was achieved by the evaluation result. Therefore, we categorize this study in two different research type, evaluation and validation. Form of Study: Laboratory Study To assess Tesseract usability, an informal lab experiment was conducted in the study. This was to assist identifying bugs and features for further improvement. Social Techniques: General Concept The paper did not mention any specific social techniques used in Tesseract. A general discussion of web based communication to create collaboration between developers was defined as part of Tesseract's design and architecture. Social Connectivity: Designated Tesseract was developed specifically to facilitate developers related to the complex relationship of codes, developers, communication, and bugs. It visualizes a cross-linked web based display to present the relationship. Social Interaction: Many-to-many The paper did not explicitly mention the social interaction applied for Tesseract. However, we conclude that web based display used to present the relationship among developer, codes, bugs, and communication facilitates many-to-many social interaction. Social Location: Distributed The paper did not explicitly describe the use of Tesseract in the distributed or localized environment. However, both evaluation and feedback gathering was conducted in a distributed environment. Honeycomb Framework: Identity and Relationship The paper did not explicitly describe the social techniques used in the communication between developers. However, according to the scenarios and images presented in the paper, we conclude that this paper reflected the Identity and Relationship blocks. The ability of Tesseract to provide identification of related developers was represented in Identity, and the nodes presented by Tesseract binds users in a relationship associated with their current activities.

243

Paper Title: Authors Affiliations Publication

Advanced Hands-on Training for Distributed and Outsourced Software Engineering : Nordio, M., Mitin, R., and Meyer, B. : ETH Zurich, Switzerland : Proceedings of 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010, Cape Town, Africa Publication Year : 2010 Origin of the Paper : Switzerland Summary: The paper reported the authors' experience in teaching distributed projects within an educational context for students. The experience includes how to elaborate requirements, develop interface specification, and implementation. All of the steps mentioned required distributed communication. Criteria: Areas of Study: Requirement The paper reported upon the entire collaboration project. However, it also emphasized the collaboration for determining requirements. It also mentioned in the paper that the collaboration resulted in a solid specification for the requirements. Research Type: Experience The paper reported the authors' experience in teaching collaborated software development to students in a distributed environment. The results showed that most of the student teams were able to integrate subsystems where a final project was working at the end of the semester. Form of Study: Laboratory Study The paper described the distributed environment built to support collaboration between the teams. Each team was required to complete a project by delivering high priority requirements to build a system. Result showed that from 6 teams assigned, 5 teams were able to complete although missing several functionalities while the remaining team failed to deliver. Social Techniques: Instant Messaging, Email/Alert, and Wiki There are several social techniques used for communication between developers as mentioned in the paper. The Origo platform support communication includes forum, wikis, and versioning. However, according to the given feedback from the students, most of them use chat, emails, and wiki to support their communication. Social Connectivity: Public The survey conducted using the students that performed the collaboration resulted in the use of chat as the most utilized public tool for communication. Social Interaction: Mixture The survey result did not specify which types of chat were used the most. However, chat or instant messaging can both act as one-to-one social interaction through direct chat and also as many-to-many interaction through group chat. Social Location: Distributed The paper explicitly presents a report of students performing collaboration in a distributed software development. Therefore, the study covers a distributed social location. Honeycomb Framework: Conversation and Sharing Based on the most used social techniques known to the students, we include this paper into two different honeycomb blocks. Conversation and Sharing both represent the communication that occurs between the developers.

244

Paper Title: Analysis of User Comments: An Approach for Software Requirements Evolution Authors : Carreno, L. V. G. and Winbladh, K. Affiliations : University of Delaware, USA Publication : Proceedings of 35th International Conference on Software Engineering, ICSE 2013, San Fransisco, USA Publication Year : 2013 Origin of the Paper : USA Summary: The paper discussed a method to extract feedback requirements given by users through a mobile application. This study aimed to automate topic extraction from user comments by adapting topic modeling and conducting an evaluation on public data sets. The result showed that automatic data extraction generates a good result compared to the manual extraction. Criteria: Areas of Study: Requirements The paper explicitly discussed a method to extract requirements from user feedback through a mobile application. This is to build an automatic data extraction thus minimizing manual data extraction effort. Research Type: Evaluation The paper described evaluation conducted at the automatic data extraction method and at the report generated for the developers. Several public data sets of user comments were used to evaluate the method, together with two other methods for classifying topics. Furthermore, two sets of human subjects were used to evaluate the report. Form of Study: Experiment The paper conducted experiments using three sets of public data retrieved from three different mobile applications. Two types of experiment were performed with each data set. The results were then compared to the manual data extraction. Social Techniques: General Concept The paper did not explicitly mention any method used by the mobile applications to send the user feedback. Several approaches including the concept of email were mentioned. However, we include this paper into general technique. Social Connectivity: Public Considering the assumption that the social technique used in this study is an email, we categorized this paper in the public tool social connectivity. Social Interaction: One-to-one The paper described that the use of the user feedback is to gather requirements for further development. Therefore, the user email sent from the mobile application is specifically directed as feedback. This is included as one-to-one social interaction. Social Location: Distributed The paper did not specifically mention the social location discussed in this paper. However, we consider user as a stakeholder considering that they supply requirement feedback for further development. The mobile application used by the user to send feedback is distributed. Therefore, we include this study in the distributed social location. Honeycomb framework: Sharing In the consideration that users are a part of the stakeholders, feedback sent by users was included in the sharing honeycomb block. With mutual interest, users provide developers with requirements and developers provide users with the latest development that includes the requirements.

245

Paper Title: Authors Affiliations Publication

Awareness 2.0: Staying Aware of Projects, Developers and Tasks using Dashboards and Feeds : Treude, C. and Storey, M. : University of Victoria, Canada : Proceedings of 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010, Cape Town, Africa Publication Year : 2010 Origin of the Paper : Canada Summary: The paper described how the use of dashboard and feeds in software development teams could increase awareness extensively. Description of the dashboard and feeds were discussed in the paper including how they complement each other in supporting software development. The result showed that awareness is often unclear and it could be improve with tools. Criteria: Areas of Study: Management The paper mentioned that previous works has only focused their research in the source code and code management. However this paper emphasized the importance of building awareness between developers. Therefore, we include this paper in the management area of study. Research Type: Evaluation The research in the paper conducted an evaluation of the use of dashboard and feeds to build awareness by collecting data through interviews and web-based surveys. Result of the evaluation is presented in the form of features that dashboards and feeds must have, and the reasons behind using them to support collaboration. Form of Study: Case Study The paper presented the empirical study result of several large development teams, with one detailed study involving 150 developers. The study was performed by collecting data through interviews and web-based surveys. Social Techniques: Dashboard and Feed The paper explicitly described the study of the use of dashboard and feeds to support collaborative software development. Social Connectivity: Designated This paper presented a discussion on the benefit and importance of using dashboard and feeds to support distributed software development teams. The concept of dashboard and feeds presented in this paper was adopted to support tools for communication. Furthermore, this paper did not present any specific tool, however it presented the study of implementing the use of dashboard and feeds. Social Interaction: Mixture Dashboard displays information related to the user, whether updated by the user or by others. Therefore, dashboard applies the many-to-many social interaction due to the various contents and its ability to be seen by other developers. On the other hand, feeds are updated by a developer and can be seen by other developer. Therefore, feeds is a one-to-many social interaction. Social Location: Distributed The observation was conducted to several teams that were located in 15 different locations worldwide. Therefore, the study covered a distributed location. Honeycomb Framework: Identity and Sharing According to the sample dashboard presented in the paper, the concept of dashboard and feed were represented by several honeycomb blocks. Identity represents the user profile provided in the dashboard and Sharing represents the content of the dashboard that contains information.

246

Paper Title: Authors Affiliations Publication

The Role of Emergent Knowledge Structures in Collaborative Software Development : Treude, C. : University of Victoria : Doctoral Symposium in the Proceedings of 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010, Cape Town, Africa (Doctoral symposium: Mature phase) Publication Year : 2010 Origin of the Paper : Canada Summary: This paper described a study of emerging lightweight technologies in supporting collaborative software development projects. The study focused upon the use of tagging and wikis to mediate collaboration. Result showed that informal communication was a highly adopted and adapted tagging mechanism, despite the difficulties in gaining access through formal communication. The study aimed to assist collaboration between managers and developers for decision-making. Criteria: Areas of Study: Maintenance The paper mentioned that the use of tagging currently applies for different kinds of artifacts, including code maintenance, management system, and building awareness. Since the use of tagging is provided the most for maintenance, we include this study in the area of maintenance. Research Type: Opinion The paper discussed various lightweight systems that created emergent knowledge structures. Thus, it proposed two research questions to identify the role of emergent knowledge structures in the collaborative software development. This paper proposed different studies to address the research question and reported of the progress up to date. Form of Study: Observation and Case study The paper explicitly proposed the research method that will be used in conducting the studies. The methods include interviews, surveys, and observations of developers regarding various lightweight technologies. Social Techniques: Tag, Wiki, Blog/Microblog, Feed, Social Networking, and Email/Alert The paper proposed studies to identify features that support the lightweight system. Among the features, tools, and communication features, as mentioned in the social techniques were included. Considering that the paper has only proposed the research method, we include this paper into several social techniques. Social Connectivity: Public The paper presents the proposal for further studies related to lightweight systems. Considering that the use of these features is relatively public, therefore we include this paper in the public tool social connectivity. Social Interaction: Mixture The research in this paper is still in the preliminary stage, wherein it proposed several studies. Therefore, to include various social interactions represented by the social techniques, we include this paper in the mixture social interaction. Social Location: Not acknowledged The paper did not explicitly mention the social location coverage of the lightweight technologies. Honeycomb Framework: Identity, Conversation, Sharing, Relationship, Reputation, and Groups Considering the general content of discussion in this paper, the social techniques described were represented by most of the honeycomb block. Therefore, we include this paper in the honeycomb blocks as mentioned above.

247

Paper Title: Authors Affiliations Publication

A Demonstration of a Distributed Software Design Sketching Tool : Mangano, N., Dempsey, M., Lopez, N., and Hoek, A. V. D. : University of California, Irvine, USA : Proceedings of the 33rd International Conference on Software Engineering, ICSE 2011, Waikiki, Honolulu, USA . Research Demonstrations Publication Year : 2011 Origin of the Paper : USA Summary: The paper presented a distributed design tool that uses sketches to support software designers by adopting the common concept of pen and paper. Several prime features of Calico are also presented in the paper including illustrations on how to use Calico. This paper also provided further discussion of Calico's development. Criteria: Areas of Study: Design The paper explicitly described the use of Calico in supporting distributed software designers in sketching designs. Therefore, we include this paper in the design area of study. Research Type: Solution The paper introduced an improved Calico design tool that integrates several other features compared to the previous Calico. These features include softmode, viewport, and the ability to provide collaboration work. Therefore, this paper is a solution research type. Form of Study: Non-empirical and Literature Review The paper did not provide any empirical research of Calico. This paper only provided an illustration on how to use Calico and described the important features supported by Calico. Social Techniques: Dashboard The paper did not explicitly mention the type of social technique used to support Calico. However, from the distributed use of Calico, we include Calico in the dashboard social technique due to the use of interface for communication. Social Connectivity: Designated The paper presents a collaboration tool for software designers to support design sketching. Calico is specifically built to assist the designers. Therefore, we include this paper in the designated tool social connectivity. Social Interaction: One-to-many The paper described the use of Calico in supporting collaboration software design. From the illustration provided in the paper, we conclude that a designer is able to collaborate with several other designers. This includes Calico in the one-to-many social interaction. Social Location: Distributed The paper explicitly described that the improved version of Calico has the ability to support collaboration between software designers. Furthermore, from the illustration, we identify Calico's ability to collaboration feature by combining sessions in Calico. Honeycomb framework: Sharing and Relationship Calico is used to support collaboration between software designers with the sketching concept. We described Calico in two honeycomb blocks, Sharing and Relationship. Sharing represents the content of information to be exchanged between designers, and relationship represents the link formed between the designers.

248

Paper Title: Authors Affiliations Publication

Exploring, Exposing, and Exploiting Emails to Include Human Factors in Software Engineering : Bacchelli, A. : University of Lugano, Italy : Proceedings of 33rd International Conference on Software Engineering, ICSE 2011, Waikiki, Honolulu, USA Doctoral Symposium Publication Year : 2011 Origin of the Paper : Italy Summary: The paper explored the importance of emails for communication between developers in a collaborated software development environment. The paper focused on methods to explore, expose, and exploit emails by implementing the right tools. The result showed that human factors represented by emails in software development projects contribute to the quality of the project. Criteria: Areas of Study: Management The paper mentioned that the use of emails was related to various kinds of artifacts. Emails consist of valuable information, socially and technically, including code sharing and collaborations. Therefore, we include this study in the management area. Research Type: Evaluation The paper described exploration towards emails in a software development environment. Various methods were applied to extract data from emails and link them to the related projects. Therefore, this study is an evaluation of those methods of email extractions. Form of Study: Case Study and Observation This paper used a case study of an open source system to assess the methods that were used to extract the emails. Detailed descriptions on how the observation was conducted were described in the paper. Social Techniques: Email/Alert The paper explicitly described the main objectives of the study is to explore emails using several extraction methods. Social Connectivity: Public The paper did not explicitly describe any tools used related to the emails. Therefore, we assume that the uses of the emails are from common public tools. Social Interaction: Mixture The paper mentioned the use of email as a direct communication between the developers and it also mentioned email as a part of mailing list that enables a one-to-many communications. Social Location: Not acknowledged The paper did not mention any coverage applied to the email communication. The case study used in the paper is an open source systems but it did not describe the locations of the members. Honeycomb Framework: Identity, Conversation and Sharing According to the paper, developers used emails to communicate with each other. Considering this type of social technique, we include this paper in the Identity, Conversation and Sharing of the honeycomb blocks.

249

Paper Title: Authors Affiliations

How Do Programmers Ask and Answer Questions on the Web? : Treude, C., Barzilay, O., and Storey, M. : University of Victoria, Canada Tel-Aviv University, Israel Publication : Proceedings of 33rd International Conference on Software Engineering, ICSE 2011, Waikiki, Honolulu, USA New Idea Track Publication Year : 2011 Origin of the Paper : Canada and Italy Summary: The paper investigated how programmers ask and answer questions on the web with the concept of crowd sourcing. The study used the date from a social media, Stack overflow, to analyze information exchange between the programmers. The result showed that several particular types of questions were answered more than others. Criteria: Areas of Study: Coding The paper did not explicitly describe the use of crowd sourcing social media to support software development. However, Stack overflow provides a facility to mediate developers to ask and answer questions related to a wide range of topics including coding. Therefore, we include this study in coding environment. Research Type: Evaluation The paper presented a detailed evaluation of questions in Stack overflow. It identified the types of questions that were answered the most and its relationship with the developer who raised the questions. Form of Study: Case Study The paper conducted a case study using the social developer forum, Stack overflow, by creating a script that could collect questions, answers, tags and owners through the API. The result showed that there are certain types of questions that were less favorable to be answered compared to others. Social Techniques: Crowd sourcing Social media used as the main study in this paper applies the concept of crowd sourcing. Any developer can post questions to Stack overflow and expect to receive answer from a known or even random other developers. Social Connectivity: Public Stack overflow is a public website that could be accessed by any developer. This method might provide different perception in developing codes due to the variety in developers involved in Stack overflow. Social Interaction: Many-to-many Crowd sourcing provides many-to-many interaction. Each developer might have more than one question posted on Stack overflow and there are more than one other developer who has access to the question to provide answers. Social Location: Distributed The paper did not explicitly mention the location coverage of Stack overflow. However, since the Stack overflow is a web based application crowd source that is accessible worldwide, we conclude that Stack overflow covers distributed locations. Honeycomb Framework: Identity, Conversation, Sharing, Reputation, and Group The paper conducted a case study to identify the use of crowd sourcing in the social developer forum, Stack overflow. Crowd sourcing was represented in several different blocks of honeycomb. Therefore, we include this paper in the honeycomb blocks as mentioned above.

250

Paper Title: Authors Affiliations Publication

Understanding Broadcast Based Peer Review on Open Source Software Projects : Rigby, P. C. and Storey, M : University of Victoria, Canada : Proceedings of 33rd International Conference on Software Engineering, ICSE 2011, Waikiki, Honolulu, USA

Publication Year Origin of the Paper

: :

2011 Canada

Summary: The paper described a study of code changes for peer review in a collaboration environment. Several empirical studies were conducted to investigate the mechanism and behavior used by the developers to perform reviews. A result was achieved to answer several proposed research questions. Criteria: Areas of Study: Coding The paper studied the peer review for code changes that was broadcast in a collaborative environment for OSS projects. The author and other stakeholders reviewed and discussed the changes until they were accepted or rejected. This method was used to improve the quality of the codes. Research Type: Evaluation and Validation The paper evaluated several environments where the peer reviews were applied. The evaluation result was then validated by a series of interviews and surveys conducted by the developers. Therefore, we include the study in the evaluation and validation research type. Form of Study: Case Study The paper described several case studies used to examine the mechanism and behavior of the developers in conducting peer review. The result was presented clearly in the paper. Social Techniques: Email According to the paper, broadcast messages in conducting peer review were done through emails. An author sends changes in codes through emails to the mailing list where it can then be reviewed by other stakeholders. Social Connectivity: Public The paper did not explicitly describe any specific tool used in the OSS environment to perform the peer review. Therefore, we conclude that the connection used by the stakeholders was performed through public tools. Social Interaction: One-to-many Although email applies as one to one interaction through direct email sending, the main objective of peer review is to obtain reviews from other stakeholders. Therefore, email interaction in this study applies as one-to-many interaction. Social Location: Distributed It is not explicitly describe in the paper on how the peer reviews covers the social location. However, since the case studies used to conduct the examination were in the OSS environment, we conclude that the peer review interaction covers distributed location. Honeycomb Framework: Identity, Conversation and Sharing The paper described the use of email in supporting communication between developers. Conversation and Sharing represents the communication supported by email. Therefore, we include this paper in the identity, conversation and sharing of honeycomb blocks.

251

Paper Title: Authors Affiliations Publication

Influencing the Adoption of Software Engineering Methods Using Social Software : Singer, L. and Schneider, K. : Leibniz Universitat Hannover, Germany : Proceedings of 34th International Conference on Software Engineering, ICSE 2012, Zurich, Switzerland New Ideas Track Publication Year : 2012 Origin of the Paper : Germany Summary: The paper proposed a method to improve software engineering methods by adopting social software. Description of the elements and the effect of social software is given in the paper. For each software method described in the paper, a method of improvement by implementing social software is introduced. Criteria: Areas of Study: Metric and Management The paper discussed several areas of software engineering that could be improved by adopting social software. Two prominent areas discussed were metrics and management. Goal mapping and increasing awareness are part of the management area, and measuring the mechanism performance is part of metrics area. Research Type: Solution The paper presented data taken from other studies to support the main idea of the study. Arguments to strengthen the author's position were also taken from existing literatures. This method was used to introduce the function of adopting social software to the software engineering. Form of Study: Non-empirical There is no empirical research conducted in the paper. Most of the arguments and data presented in the paper were taken from literatures and existing studies. Social Techniques: General Concept The paper did not explicitly mention any social technique used in the methods to improve software engineering by adopting social software. However, it provides several examples of aggregation using several types of social media. Social Connectivity: Adapted The paper explicitly mentioned that the main study was done to improve software engineering by adopting social software. This means that the methods discussed in the paper were adapted from social tools to serve the needs of software engineering. Social Interaction: Many-to-many It was mentioned in the paper that the main purpose of improving software engineering by adopting social software was to increase the quality of the product. From general techniques mentioned in the paper, we conclude that the methods discussed are applicable as many-to-many interaction. Social Location: Distributed It is not specifically mentioned in the paper that the method applied to distributed social location. However, considering the adoption of social software to improve software engineering, the coverage of social software includes distributed location. Honeycomb Framework: Conversations, Sharing, and Relationship The paper did not explicitly describe the type of social technique proposed in the approach. However, the proposal emphasized the relationship that need to be created between users from various different background in a same project team. Furthermore, it described notification system, activity feed and system-derived information that need to be included in the method. Therefore, we include this study in the conversation, sharing, and relationship honeycomb block.

252

Paper Title:

What Makes It Hard To Design Instructional Software? Towards a Collaborative Platform for Stakeholders of Instructional Software Authors : Chimalakonda, S. and Nori, K. V. Affiliations : International Institute of Information Technology, Hyderabad, India Publication : 5th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE), 2012. Proceedings of the 34th International Conference on Software Engineering, ICSE 2012, Zurich, Switzerland Publication Year : 2012 Origin of the Paper : India Summary: The paper presented the author's experience in analyzing instructional software for adult literacy developed in a distributed environment. Different types of stakeholders and the initial facets of their solution (taken from three major dimensions, where one of them involved the use of social networking) were presented in the paper. The result showed that communication, cooperation, and collaboration between stakeholders are important factors for the success of a project. Criteria: Areas of Study: Maintenance The paper provided a description of how the use of social networking tools enhances the communication, cooperation, and collaboration between stakeholders. The main idea behind the exploitation of social network is to gather the stakeholders into social networking, where they can express their knowledge with minimal effort and easily understood by other stakeholders. The social network is used to facilitate information spread of any changes applied to the project. Research Type: Experience The paper presents the author's experience in analyzing customized software development in a distributed environment. The authors then provided solutions to improve the communication, cooperation, and collaboration between developers in a distributed software development environment. One of the solutions is to exploit the use of social networking. Form of Study: Observation The paper did not explicitly describe the form of study applied during the period. However, from the description provided in the paper, we conclude that the author performed observation throughout the entire period. In the end, they propose solutions on how to increase the C3 among distributed developers. Social Techniques: Social Networking and Blog/Microblog The paper explicitly described the use of social networking to increase the communication, cooperation, and collaboration between developers involved in a project. However, we also include this study in blogs/microblogging techniques due to Twitter which was also studied in the paper. Social Connectivity: Adapted Several social techniques mentioned in the paper are public social techniques that were aimed to gain public interest. However, the use of these social techniques in supporting software development means that they were adapted to facilitate the environment. Social Interaction: Many-to-many It is not explicitly described in the paper that the social interaction formed between the developers is a many-to-many interaction. However, considering the types of social techniques used in supporting the development, we conclude that the interaction formed is a many-to-many. Social Location: Localized The paper explicitly described the observation performed was at distributed teams across distributed locations. Honeycomb framework: Identity, Conversations and Groups As described in the paper, the use of social networking is to support software development in a distributed environment. The social networking enables the developers to create groups and perform communication within the groups. Furthermore, identity represents the user profile within the social networking.

253

Paper Title: Creating a Shared Understanding of Testing Culture on a Social Coding Site Authors : Pham, R., Singer, L., Liskin, O., Filho, F. F., and Schneider, K. Affiliations : Leibniz Universitat, Hannover, Germany Publication : Proceedings of the 35th International Conference on Software Engineering, ICSE 2013, San Fransisco, USA Publication Year : 2013 Origin of the Paper : Germany Summary: The paper discussed the broad use of a social coding site to host projects, and its influence upon social interaction regarding testing. The authors performed a study by conducting interviews and validating the results with online questionnaires directed at the members of GitHub. The results showed that there are significant testing behavior influences occurs from the use of social coding site. Criteria: Areas of Study: Software/Program Verification The paper explicitly described the study of testing on a social coding site, GitHub, in order to identify the influence of social coding site to testing behavior. Therefore, we include the study in the software/program verification that includes testing area. Research Type: Evaluation and Validation The paper described both evaluation and validation to identify the influence of a social coding site towards testing. The initial evaluation in the study was conducted in the beginning and the finding result was validated through further research. Form of Study: Case Study The paper uses GitHub, a social coding site, as a case study to investigate the use of social coding site on influencing testing behavior. An initial interview was conducted using various roles such as developers, testers, and a software architect and the result of the interview was validated by an online questionnaire given to a significant amount of members of GitHub. Social Techniques: Crowd sourcing It is explicitly mentioned in the paper that the study was to investigate the use of GitHub social coding site. Social coding site such as GitHub uses the crowd sourcing method to gather members and enable collaborative working. Social Connectivity: Public GitHub is a social coding site that is open to the public. Although the aim of the site is to support developers in software development, it is not designated to facilitate only certain purposes. Social Interaction: Many-to-many The concept of crowd sourcing facilitates many-to-many social interaction. Social Location: Distributed The use of a social coding site enables distributed communication connected by the network. Therefore, this paper is included in the distributed social location. Honeycomb framework: Identity, Conversation, Sharing, Groups The use of social coding site represents several factors in the honeycomb framework. The users have their own profile site that reveals their identity to other users. In the social coding site, the user communicates and shares ideas and codes among themselves in certain groups based on the topic of discussion.

254

Paper Title: Authors Affiliations

Teaching Students Global Software Engineering Skills Using Distributed Scrum : Paasivaara, M., Lassenius, C., Damian, D., Raty, P., and Schroter, A. : Aalto University, Finland University of Victoria, Canada Publication : Proceedings of 35th International Conference on Software Engineering, ICSE 2013, San Fransisco, USA Publication Year : 2013 Origin of the Paper : Finland and Canada Summary: The paper reported the use of Scrum to facilitate global a distributed software development project course between the University of Victoria, Canada and the Aalto University, Finland. An evaluation was conducted to assess the collaboration result. It showed that the Scrum method supports the learning of global software engineering practices. Criteria: Areas of Study: Management The paper presented a report on a global distributed software development course using distributed Scrum. This was to assess the learning competencies of global software engineering, such as communication and teamwork. Therefore, we include this paper in the management area of study. Research Type: Evaluation paper The paper discussed the use of Scrum in supporting global distributed software development. An evaluation of the Daily Scrum is to identify communication pattern that was formed between members of the project challenged by time zone difference. Furthermore, the paper also evaluated teamwork and trust between members. Form of Study: Case Study The paper used a globally distributed project course between two universities to assess the use of Scrum in supporting collaboration. The assessment was conducted to the members of the project through interviews, questionnaires, and analysis of Daily Scrum data. Social Techniques: Email/Alert and Instant Messaging The paper explicitly mentioned that the social techniques used by the members of the project to communicate were through email and instant messaging. It was also as recorded by the Daily Scrum. Social Connectivity: Public The paper did not explicitly mention the kind of email and instant messaging used by the members of the project. However, we assume that public tools were used to facilitate the email and instant messaging communication. Therefore, we include this paper in the public tools social connectivity. Social Interaction: Mixture The social interaction that email and instant messaging represents could be various, starting from direct communication with one-to-one interaction, broadcast messages with one-to-many interaction, and even mailing list or chat group with many-to-many interaction. Therefore, we include this paper in the mixture social interaction. Social Location: Distributed The main objective of the study reported in the paper explicitly mentioned that Scrum is used to facilitate globally distributed software development environment. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversations and Sharing According to the paper, communication formed between the members of the project was used to discuss short questions, meetings, and build awareness. This represents conversation and content sharing that occurs between the members.

255

Paper Title: Authors Affiliations

The Role of Domain Knowledge and Cross-Functional Communication in Soci-Tchnical Coordination : Damian, D., Helms, R., Kwan, I., Marczak, S., and Koelewijn, B. : University o Victoria, Canada Utrecht University, Netherland Oregon State University, USA PUCRS, Brazil Publication : Proceedings of 35th International Conference on Software Engineering, ICSE 2013, San Fransisco, USA Publication Year : 2013 Origin of the Paper : Canada, Netherland, USA, and Brazil Summary: The paper described a study of information flow between different roles in two different projects. The projects contrast with each other in terms of domain knowledge distribution and communication structures. The study showed that various roles communicate more than expected regardless of task dependencies. In communicating, they follow communication structure although they tend to communicate with others who have similar domain knowledge. Criteria: Areas of Study: Coding The paper did not explicitly describe the areas of study related to the investigation. However, we conclude that the communication formed in the study is to support information exchange in software development. Therefore, we include this paper in the coding areas of study. Research Type: Evaluation The study presented in the paper investigated the current communication structure applied in various roles within multiple software projects. The investigation presented the initial result related to the socio-technical communication between team members. Form of Study: Case Study The paper conducted a case study of two different projects within the same software company. Information gathered from both projects was obtained through observation, interview, and survey. Social Techniques: General Concept The paper did not explicitly describe the social techniques used by the member of the projects to communicate. Therefore, we include this paper in the general social technique. Social Connectivity: Public Considering that the paper did not describe any social technique used in the communication, we assumed that the connectivity used to perform the communication was through public tools. Social Interaction: Mixture The paper did not describe any specific social techniques used to support communication. Furthermore, we assumed that the social connectivity was performed through public tool. Therefore, to encompass social interaction occurs in communication, we include the study in the mixture social interaction. Social Location: Distributed Considering the case study used in the study, we include the social location for this study in distributed social location. Honeycomb framework: Conversation, Sharing, and Reputation From the description of information exchange and communication flow in the paper, we include the study in several honeycomb blocks. Conversation and Sharing represents the communication between the team members. Furthermore, Reputation represents the communication structure applied within each project.

256

Paper Title: Wiki-Based Stakeholder Participation in Requirement Engineering Authors : Decker, B., Ras, E., Rech, J., Jaubert, P., and Rieth, M. Affiliations : Fraunhofer Institute for Experimental Software Engineering, Germany Publication : Article in IEEE Software Journal, Volume: 24 Issue: 2, Page 28 - 35 Publication Year : 2007 Origin of the Paper : Germany Summary: The paper discussed an investigation of how to adapt Wiki to provide a flexible platform for supporting active stakeholder participation in Requirement Engineering. The paper presented a list of considerations of utilizing Wiki in requirement engineering. Several application experiences of Wiki implementation were presented in the paper, including challenges in using Wiki and how to overcome them. Criteria: Areas of Study: Requirements/Specifications The paper provided a research of the use of Wiki in supporting stakeholders in determining requirement engineering. The paper also described a proper design of document structure in order to start the requirement elicitation by using Wiki. Therefore, we include this paper in the requirements/specifications area of study. Research Type: Experience The paper presented an overview on how to adapt Wiki into supporting requirement engineering. A list of pros and cons in utilizing Wiki, including challenges occur in implementing Wiki, were presented in the paper. This information resulted from the authors' experience in researching the use of Wiki in requirement engineering. Therefore, we include this paper in the experience paper. Form of Study: Case Study The paper provided several Wiki implementations conducted to different case studies. There were three case studies described in the paper that were used to identify the usefulness of Wiki in supporting requirement engineering. Results from each case study were presented in the paper. Social Techniques: Wiki The paper explicitly described the social technique used in the paper, which was a Wiki. A Wiki was used as a base technology to support variety stakeholders assisting in requirement engineering. Social Connectivity: Designated The paper described the use of adopting Wiki to assist requirement engineering. Although Wiki is adopted from public tool, the tool that utilizes Wiki to provide collaboration between stakeholders was specifically build for this purpose. Therefore, we include this paper in the designated tool. Social Interaction: Many-to-many The paper described the use of Wiki to provide support in requirement engineering. Wiki provides pages of information and places to communicate changes of requirements between developers. Information available in Wiki combined with the number of stakeholders involved represents the many-to-many interaction between stakeholders. Social Location: Distributed The paper did not explicitly describe the location coverage of the Wiki. However, the main aim of conducting research in order to identify the adoptability of Wiki in supporting requirement engineering is to assist distributed environments. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity and Sharing The paper described the adoption of Wiki in supporting requirement engineering. We include the research in this paper in several honeycomb blocks. Identity represents the stakeholder profile that could be identified by other stakeholders. Sharing represents the information exchange using the Wiki, and Presence represents the availability of other developers in providing information in the Wiki as well as conducting the requirement engineering process through the Wiki.

257

Paper Title: Authors Affiliations

Collaboration Tools for Global Software Engineering : Lanubile, F., Ebert, C., Prikladnicki, R., and Vizcaino, A. : University or Bari, Italy Vector Consulting Services, Pontifica Universidade do Rio Grandeso Sul, Brazil University of Castilla-La Mancha, Spain Publication : IEEE Software Journal, Volume: 27, Issue: 2, Pages: 52 - 55 Publication Year : 2010 Origin of the Paper : Italy, Brazil, and Spain Summary: The paper presented a summary of the authors' experience combined with a survey from the IEEE conference to identify the technologies that support collaboration in both global and collocated locations. These technologies enabled effective software development by building a collaborative environment. Several tools categorized by the ability for collaborative development were described in the paper. Criteria: Areas of Study: Requirements/Specification, Design, Coding, Software/Program Verification, Distribution, Maintenance, and Enhancement, and Management The paper presented various tools categorized as both collaborative development tools and specific collaboration tools. Each of the tools represents different functionality for different areas of study within software development. Therefore, we include this paper in the areas of study as mentioned above. Research Type: Experience The paper presented the experience and survey result of the IEEE conference of the collaborative development tool trend. This was to identify which tools were used the most by developers, organization, and companies to improve their software development. Therefore, we include this paper into the experience type. Form of Study: Case Study The paper did not explicitly describe the case study and survey conducted to obtain the trend of the collaboration development tools. However, the paper mentioned that the study resulted from survey conducted to IEEE conference and to companies where the authors' provide consultancy. We include this paper in the case study regarding the conducted survey. Social Techniques: General Concept The tools described in the paper encompass various social techniques used to support collaborative development environment, especially in web2.0 category. Therefore, we include this paper in the general social technique. Social Connectivity: Public, Designated, and Adapted The paper described various existing tools to support collaborative development. Connectivity provided by these tools was also various, including designated tools that were specifically built to support collaborative work, and public or adaptive tools that adopted web2.0 technologies to support collaborative work. Therefore, we include this paper in the social connectivity as mentioned above. Social Interaction: Mixture Considering the social techniques and social connectivity described in the paper, we conclude that the social interaction occurs through these tools was included in the mixture interaction. Various interactions including one-to-one, one-to-many, and many-to-many were adopted to provide communication for collaborative work. Social Location: Mixture The paper explicitly stated that the tools described were to enabled collaborative work in both distributed and collocated location. Therefore, we include this paper in the mixture location. Honeycomb framework: Conversation, and Sharing The paper described several tools that support collaborative development environment. Considering the broad types and kinds of tools described in the paper, we include this study in general honeycomb blocks. Conversation represents the communication that was built and occurs through the tools between developers, and Sharing represents the information exchanged between developers.

258

Paper Title: Authors Affiliations

WIPDash: Work Item and People Dashboard for Software Development Teams : Jakobsen, M. R., Fernandez, R., Czerwinski, M., Inkpen, K., Kulyk, O., and Robertson, G. G. : University of Copenhagen, Denmark Microsoft Research One Microsoft Way, Redmond, WA, USA University of Twente, Enschede, Netherland Publication : Proceeding of the Human-Computer Interaction (INTERACT 2009), 12th IFIP TC 13 International Conference, Uppsala, Sweden Publication Year : 2009 Origin of the Paper : Denmark, USA, and Netherland Summary: The paper introduced a visualization tool to increase awareness of work items and code base activity between developers in a software development team. The initial design of WIPDash was derived from observation and interviews of two development teams. WIPDash was then deployed to both teams to identify the usefulness and the effects that might occur. The design and deployment process, including the results, were presented in the paper. Criteria: Areas of Study: Coding, Distribution, Maintenance, and Enhancement, and Management The paper proposed a tool that visualized work activities based on the artifacts and code changes. WIPDash is aimed to build awareness by presenting an overall view of the project enabling developers to identify activities related to their work. Therefore, we include this paper in the coding, distribution, maintenance, and enhancement, and management areas of study. Research Type: Evaluation, Solution, and Validation The paper proposed a new tool to increase awareness between developers in a software development environment. WIPDash was built to meet the needs of the developers in visualizing the overall project activity. This paper also presented a validation towards the usefulness of WIPDash used by two agile software development teams. Results were presented in the paper. Form of Study: Observation and Experiment The paper described the process of collecting data through observation and interviews in order to build WIPDash. Thus, the author deployed WIPDash to two agile software development teams to identify its usefulness. Through the deployment process, the authors observed WIPDash's performance and conducted interviews afterwards. Results were presented in the paper. Social Techniques: Dashboard The paper explicitly described the technique used by WIPDash to present information of the project overview through visualization. Therefore, we include this paper in the Dashboard technique. Social Connectivity: Designated The paper stated that the main aim of WIPDash is to provide information through visualization in order to increase developers' awareness of the project overview. This means that WIPDash is specifically designed to assist software development teams. Therefore, we include this paper in the designated connectivity. Social Interaction: Many-to-many WIPDash enables visualization of various information related to activities conducted by developers that were involved in a software development teams. We consider the type of social interaction occurs in WIPDash as a many-to-many interaction. Social Location: Localized The paper described a deployment process conducted using two agile software development teams in a localized location. The paper mentioned that the result showed from the deployment needed to be compared to a larger distributed environment. Therefore, we include this paper in the localized location. Honeycomb framework: Identity, Sharing, and Relationship The paper proposed WIPDash to increase awareness in a software development team. We include WIPDash in several honeycomb blocks. Identity represents the user profile shown in the dashboard. Sharing represents the information exchange towards activities of the developers. Relationship represents the link that shown between developers in the Team Panel.

259

Paper Title:

Requirements are Slipping Through the Gaps - A Case Study on Causes & Effects of Communication Gaps in Large-Scale Software Development Authors : Bjarnason, E., Wnuk, K., and Regnell, B. Affiliations : Lund University, Sweden Publication : Proceedings of the 19th IEEE International Requirements Engineering Conference, Trento, Italy Publication Year : 2011 Origin of the Paper : Sweden Summary: The paper reported research identifying communication gaps between members of projects in a large-scale industry, emphasizing the understanding of causes and effects of such gaps. Research was conducted through a case study and was validated through questionnaire. The results identified several significant causes that could lead to several effects e.g. inability to meet customer expectations. Criteria: Areas of Study: Requirements/Specifications The paper explicitly described the importance of communication in supporting management and production efficiency. A continuity of requirements flowing via communication throughout the project lifecycle is more likely to lead to a better result. Research Type: Validation The paper conducted research to identify communication gaps that occur in a large-scale industry. The results identified several causes and effects that could lead to production failure. These results were validated using a number of practitioners. Form of Study: Case Study The paper conducted a case study using a large-scale industry that has a number of distributed teams. The research was performed by interview with a high degree of discussion between the interviewer and the interviewee. Social Techniques: General Concept The paper did not explicitly describe the types of social techniques to overcome the challenges resulting from the research. However, the paper emphasized the importance of communication to bridge the gap and resulted in flowing requirements for management and production. Social Connectivity: Designated The paper did not describe any connectivity involved in the research. However, from the causes of communication gaps identified in the paper, we conclude that a tool that supports communication between members of the project must be a designated tool. A designated tool is specifically designed to support necessary communication, thus fill the existing communication gap. Social Interaction: Mixture From the paper, we conclude that the social interaction that occurs between the members of the project is a mixture from several kind of interactions. Although it is not explicitly described in the paper, we derived this conclusion by analyzing the cause of communication gaps. Social Location: Distributed The paper explicitly described the large-scale industrial set up used as the case study supports the distributed teams. Therefore, we include this paper in the distributed social location. Honeycomb framework: Identity, Conversation, and Sharing Considering that the paper did not describe any social techniques involved in the research, we conclude that the tool required overcoming the communication gaps between members of the projects need to include the identity, conversation, and sharing blocks of honeycomb framework. These blocks are necessary to fill the gap of the identified communication gap mentioned in the paper.

260

Paper Title: Authors Affiliations Publication

Communication is the key – Support Durable Knowledge Sharing in Software Engineering by Microblogging : Reinhard, W. : University of Paderborn, Germany : Proceedings of the International Workshop on Software Engineering within Social Software Environments (SENSE) 2009, Kaiserslautern, Germany Publication Year : 2009 Origin of the Paper : Germany Summary: The paper presented a discussion of communication and knowledge sharing towards social software engineering. Furthermore, the author proposed an approach for supporting communication using social software engineering through microblogging. Description of the prototype and the benefits gained from implementing it were presented in the paper. Criteria: Areas of Study: Coding, Distribution, Maintenance, and Enhancement The paper proposed the use of microblogging to support communication in a software development environment. Microblogging was proposed as a plug-in for an existing Integrated Development Environment (IDE) to provide on screen communication without the developer having to change screen or application. Considering the main use of IDE is to create, compile, and debug codes, we include this paper in the coding, distribution, maintenance, and enhancement areas of study. Research Type: Solution The paper proposed an approach to integrate microblogging with IDE to provide on screen communication for developers to communicate without having to change screen or application. Furthermore, microblogging was proposed to support information recording with the aim to enable downstream search. Form of Study: Experiment The paper described that a prototype of microblogging plug-in has been created based on the Eclipse Rich Client Platform (RCP). The Eclipse provided a specific view interface to enable user to type in messages from the IDE, and it also record the user's Twitter credential account. In order to send messages, the Eclipse uses the Twitter API. Social Techniques: Blog/Microblog The research in this paper explicitly proposed the use of microblogging as a plug-in to support communication within an IDE. Therefore, we include this paper in the microblogging social technique. Social Connectivity: Adapted The paper proposed a microblogging plug-in to support communication within IDE for developer in a software development environment. The microblogging plug-in used in the paper is utilizing a public microblogging application, Twitter. Therefore, we include this approach in the adaptive tools connectivity. Social Interaction: One-to-many Considering the social technique used in the research, a microblogging provides the one-to-many social interaction. Each message posted by a developer through microblogging is available for other developers. Therefore, we include this paper in the one-to-many social interaction. Social Location: Distributed The paper did not explicitly describe the location covered by this approach. However, considering the use of microblogging and its connectivity through internet, we include this paper in the distributed social location. Honeycomb framework: Conversation and Presence The paper proposed an approach by utilizing microblogging as a plug-in to support communication between developers in a software development environment. We include this approach into several honeycomb blocks. Conversation represents the communication that occurs between developers through microblogging, and Presence represents the availability of other developers through messages posted through microblogging.

261

Paper Title: Authors Affiliations Publication

Publication Year Origin of the Paper

Using Social Media to Study the Diversity of Example Usage Among Professional Developer : Barzilay, O., Hazzan, O., and Yehudai, A. : Tel-Aviv University, Israel Technology and Science Technion, Israel : SIGSOFT/FSE'11 19th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-19) and ESEC'11: 13th European Software Engineering Conference (ESEC-13), Szeged, Hungary New Ideas Track : 2011 : Israel

Summary: This paper described how to identify a developer's perception of example code by using the social media such as LinkedIn. In this study, an online survey was conducted to identify how developers use the example code in practices and techniques. The desult showed that some developers only exploit example code a limited amount of times, while some even opposed the use of example codes. However, the research is restricted to several limitations that might threaten the validity of the research itself. Criteria: Areas of Study: Coding This paper discussed the use of social media to identify how developers use example codes to support their work. This is related to the programming environment that supports a developer in delivering its code. Research Type: Evaluation This research is conducted in a specific environment with groups of developers provided by LinkedIn. It is to identify the perception of developers towards the use of example code in supporting the software development. Form of Study: Case Study The research in the paper conducted a case study of a social network, LinkedIn. The data that was collected and analyzed includes a discussion transcript and public profile. The result showed that the highest participants are the ones in the middle related to years of experience. Social Techniques: Social Networking The paper described one particular social networking website, LinkedIn. Therefore, we include this paper in the social networking technique. Social Connectivity: Public LinkedIn is a global business social networking website. Therefore, it is considered as public tools. Social Interaction: Many-to-many In this paper, LinkedIn allows developers to have their own personal account and allows them to join groups that are related to their expertise. The groups facilitate the member in performing discussion by posting and liking comments. For this group discussion, we consider this paper to have a many-to-many social interaction. Social Location: Distributed The paper did not explicitly mention the distribution of the user. However, we conclude from the public use of LinkedIn as discussed above, that the users are widely distributed. Honeycomb Framework: Identity, Conversation, Sharing, Presence, Relationship, Reputation, and Groups The paper discussed one particular social network, LinkedIn, which assists its users to maintain a professional network and relevant discussion. Considering that LinkedIn adopted various mechanisms to support its features, we conclude that LinkedIn is represented by a complete block of honeycomb framework. Therefore, we include this paper in the honeycomb blocks as mentioned above.

262

Paper Title: Authors Affiliations Publication

Collaboration in Distributed Software Development : Lanubile, F. : University of Bari, Italy : Article in Software Engineering Journal: International Summer Schools, ISSSE 2006 - 2008, Salerno, Italy, Revised Tutorial Lectures, 5413, 174 - 193 Publication Year : 2009 Origin of the Paper : Italy Summary: The paper presented a classification of available software engineering tools to support distributed software development, including collaborative distributed development environment from classic platforms to modern environments. Based on the tool and platform classifications, the paper proposed a combination of light and rich media to improve the support and activity for distributed collaboration. A series of empirical studies were conducted, with results that support the proposal. Criteria: Areas of Study: Requirements/Specification The paper presented a classification of existing tools and platforms to support distributed software development. However, the author restricted the research to engage only in requirements elicitation and negotiation activities. Therefore, we include this paper in the requirements/specification area of study. Research Type: Solution The paper described existing tools and platforms for supporting distributed software development. However, based on these descriptions, the author described a proposal to further support collaboration and activity between developers by combining lightweight and rich media. Form of Study: Non-empirical The paper presented a classification of existing tools and platforms used to support distributed software development. Furthermore, the paper also described the use of computer-mediated communication to overcome distance in dispersed development. Based on this classification, the author built a theory in which a tool that combines lightweight and rich media will better improve distributed collaboration. A series of empirical research was presented in the paper to support this theory. Social Techniques: General Concept The paper described several social techniques that could be used to support collaboration in a distributed software development. However, the author did not propose any specific technique to illustrate the theory proposed to improve collaboration software development. The author theorized that a combination of lightweight tool and rich media could increase collaboration and activity. Social Connectivity: Adapted and Designated The author in the paper proposed a combination of lightweight tools with rich media to improve collaboration between developers in a distributed software development. Various combinations of these tools could be in the form of adaptive and designated tools. Social Interaction: Mixture Various existing tools and platform described in the paper together with various possible combinations of tools to increase collaboration between developers encompassed mixture social interaction. Through these tools, different types of social interaction might occur. Therefore, we include this paper in the mixture social interaction. Social Location: Distributed The paper explicitly described the main aim of the existing and future tools are to support collaboration between developers in a distributed software development environment. Therefore, we include this paper in the distributed social location. Honeycomb framework: Conversation, Sharing, and Presence The paper proposed a combination of lightweight with rich media tool to increase support for collaboration in a distributed software development environment. Based on the description presented in the paper, we include this type of tool in several honeycomb blocks. Conversation and Sharing represents the communication and information exchange that occurs between developers. Furthermore, Presence represents the availability of other developers in which gives a higher level in comfort for collaboration.

263

Paper Title: Authors Affiliations

Using Web 2.0 to Improve Software Quality : Black, S. and Jacobs, J. : University of Westminster, London, UK Joanna Jacobs Consulting, London, UK Publication : Proceedings of the 1st International Workshop on Web 2.0 for Software Engineering (Web2SE) 2010, Cape Town, South Africa Publication Year : 2010 Origin of the Paper : UK Summary: The paper provided real world experiences of developers that utilized social media in a distributed software development. It showed how social media was being used in software development industry and how it can enhance and improve the development experience. Several types of social media were identified supported by experience described by developers that utilized them. Thus, the paper presented a measurement using balanced scorecard to show the appropriateness of the use of social media. Criteria: Areas of Study: Requirements/Specifications, Design, Coding, Distribution, Maintenance, and Enhancement, and Metric The paper presented experiences from a number of developers in using social media to support software development in a real world industry. Most of the developers claimed that social media helped them in several areas including the areas of requirements/specifications, design, coding, and distribution, maintenance, and enhancement. Furthermore, the paper provided a measurement of the appropriateness of the social media approaches, as described by the developers using a balanced scorecard. Research Type: Experience The paper presented the authors' experience in conducting a survey using questionnaire to a number of participants invited from Twitter. Several responses were described in the paper as different case studies, to show the importance of social media in supporting software development. Form of Study: Case Study The paper described the survey conducted to developers and were presented as different case studies for each respondent. Respondents were professional software developers accessed through networks of contact of the authors. Social Techniques: Wiki, Blog/Microblog, Instant Messaging, and Crowd sourcing Research in the paper described several social techniques used by the developers to support software development. These techniques were identified as those mentioned above. Social Connectivity: Public The paper did not explicitly describe the types of social techniques used by the developers. However, considering the research was performed in the topic of Web2.0, we include this paper into public connectivity. Social Interaction: Mixture The paper did not describe how the social techniques were used to support communication. It explained that the main aim of the social media was to enhance and improve communication in software development. However, considering the types of social techniques used by the developers, we include this paper in the mixture interaction. Social Location: Distributed The paper explicitly described the survey conducted by the developers, which was done to identify the use of social media in supporting communication between developers in distributed software development. Therefore, we include this paper in the distributed location. Honeycomb framework: Identity, Conversation, Sharing, Presence, Relationship, Reputation and Groups The paper presented experiences of professional developers in using social media to support software development. We consider web2.0 encompass the social aspects of honeycomb framework. Therefore, we include these experiences in the honeycomb blocks as mentioned above.

264

Paper Title: Authors Affiliations Publication

Towards Understanding Twitter Use in Software Engineering: Preliminary Findings, Ongoing Challenges and Future Questions : Bougie, G., Starke, J., Storey, M., and German, D. M. : University of Victoria, Canada : Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering, Web2SE, Waikiki, Honolulu, Hawaii, USA Publication Year : 2011 Origin of the Paper : Canada Summary: The paper presented a report investigating the use of micro blogging (Twitter) in the area of software development. It identified Twitter as supporting tool for conversation and information sharing between distinct Software Engineering groups. Research reported in the paper conducted an evaluation by case study to identify the Twitter's intensity of use. The results were presented in the paper. Criteria: Areas of Study: Coding and Distribution, Maintenance, and Enhancement The paper did not explicitly describe the areas of study that were supported by the use of Twitter in the software development environment. However, it explained how the software developers used micro blogging to support conversation and information sharing related to coding and maintenance, including other social information. Therefore, we include this paper in the coding and distribution, maintenance, and enhancement areas of study. Research Type: Evaluation Research in the paper conducted an evaluation to identify the use of micro blogging by software developers in a distributed software engineering environment. It investigated the intensity of use of Twitter in supporting conversation and information sharing between software developers. Therefore, we include this paper in the evaluation research type. Form of Study: Case Study The paper conducted an evaluation through a case study of a small project that used an open source framework. A number of tweets were collected and analyzed to identify how intensely the software developers used Twitter. A previous study was used as a comparison with the result derived from this evaluation. Results were presented in the paper. Social Techniques: Blog/Microblog The paper explicitly described the research performed in the paper, which was to identify the use of micro blogging, especially Twitter, in a software engineering environment. A previous study mentioned in the paper showed that Twitter was found to be one of the most famous social media used by software developers to communicate. Therefore, we include this paper in the blogs/micro blogging. Social Connectivity: Public The paper explicitly described the social technique discussed in the paper is Twitter, a social media through micro blogging that enables communication and information sharing between users using only 140 characters. We include this paper in the public connectivity. Social Interaction: Mixture Considering the social technique discussed in the paper, combined with prior knowledge of the tool itself, we include this paper in the mixture interaction. Twitter enables a one-to-many interaction for every message posted on-line. However, it also enables many-to-many interaction through discussion grouped by hash tags. Social Location: Distributed The paper explicitly described the research conducted in the paper was to identify the use of micro blogging in supporting conversation and information sharing between software developers in a distinct environment. Therefore, we include this paper in the distributed location. Honeycomb framework: Conversation and Sharing The paper presented a discussion of the use of Twitter in supporting communication between software engineers in a distributed environment. We include Twitter in several honeycomb blocks. Conversation represents the communication that occurs between users in Twitter. Sharing represents the information exchange between users through tweets or re-tweets.

265

Paper Title: Authors Affiliations Publication

Adessowiki On-line Collaborative Scientific Programming Platform : Lotufo, R. A., Machado, R. C., Korbes, A., and Ramos, R. G. : University of Campinas, Brazil : Proceedings of the 5th International Symposium on Wikis and Open Collaboration (WikiSym) , 2009, Orlando, FL, USA Publication Year : 2009 Origin of the Paper : Brazil Summary: The paper introduced an approach to create a collaboration environment for development, documentation, and a knowledge repository for software development. Adessowiki enabled programming code to be embedded as the content of the web page. This would allow a centralized execution of code through the web browser. An overview and features offered by Adessowiki were presented in the paper. Criteria: Areas of Study: Coding, Distribution, Maintenance, and Enhancement, and Management The paper presented an overview of Adessowiki including the offered features. Adessowiki assists software development by enabling programming code to be embedded inside the web content to allow centralized execution. Furthermore, Adessowiki provides space for documentation that includes not only code, but also materials and executable results. Therefore, we include this paper into the areas of study as mentioned above. Research Type: Solution The paper introduced an approach to support collaborative software development by utilizing Wiki. This tool emphasized in documenting programming code, enabled centralize execution, including embedding the result to the wiki content. An overview of this approach is described in the paper. Form of Study: CaseStudy The paper described an overview of Adessowiki including the origin of this approach. Features that were offered by Adessowiki were described in comparison to an existing approach where it provided challenges that could be answered by Adessowiki. We include this paper into the literature review form of study. Social Techniques: Wiki The paper introduced an approach to assist collaborative software development by utilizing Wiki. Documentation storage, centralize execution and embedded results were offered by Adessowiki that also enable distributed environment. Therefore, we include this paper in Wiki social technique. Social Connectivity: Designated The paper described the origin and development of Adessowiki. However, it did not describe which platform used to develop Adessowiki. Therefore, we consider this paper into designated tool. Social Interaction: One-to-many and Many-to-many Considering the nature of the social technique described in the paper, we include this paper into one-to-many and many-to-many interaction. Adessowiki enabled users to publish programming code available for other users. Social Location: Distributed The paper described that Adessowiki enabled distributed work locations due to its ease of use, and that it does not require any installation as the programming code is embedded. Therefore, we include this paper in the distributed location. Honeycomb framework: Sharing The paper introduced Adessowiki as a means of assisting collaborative software development in a distributed environment. We include this paper into a sharing block that represents the information exchanged through the content published on Wiki.

266

Paper Title: Authors Affiliations Publication

Towards Architectural Knowledge Management Practices for Global Software Development : Clerc, V. : VU University Amsterdam, Netherland : Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany Publication Year : 2008 Origin of the Paper : Netherland Summary: This paper discussed the relationship between the importance of architectural knowledge and software development. However, its implementation in the global software development (GSD) environment has become significantly important, and challenges have arisen. The paper tried to identify approaches to overcome the challenges and assessed its applicability. Criteria: Areas of Study: Management The main discussion of the paper is related to architectural knowledge which is used to guide software systems development and evolution. The knowledge integrates and links people from globally dispersed locations into a coherent whole. Research Type: Validation The paper reported initial results from early validation towards architectural knowledge approaches listed to overcome the GSD challenges. However, the validation processes themselves are still ongoing. Form of Study: Observation Initial validation was performed at a number of global software development projects with different sizes. Then, a semi-structured interview was performed to collect feedback on the initial process. Social Techniques: Wiki and Email/Alert In the architectural knowledge approaches listed in the paper, several social techniques were proposed to support collaborative communication. Wikis were used to improve cost effective collaboration while email facilitated personalization communication. Social Connectivity: Public The paper did not explicitly describe the type of connectivity implemented to the wikis and emails. Therefore, we conclude the techniques into public tools. Social Interaction: One-to-many Wikis and emails both facilitate one-to-many social interaction. Single entries or postings are relevant for other individuals. Social Location: Distributed The main focus of the study is the global software development (GSD). Honeycomb Framework: Identity, Conversation and Sharing Considering the social technique studied in this research, we include this paper in the identity, conversation, and sharing blocks of honeycomb framework.

267

Paper Title: What Does Software Engineering Community Microblog About? Authors : Yuan Tian, Palakorn Achananuparp, Ibrahim Nelman Lubis, David Lo, and Ee-Peng Lim Affiliations : Singapore Management University Publication : 9th IEEE Working Conference on MSR Publication Year : 2012 Origin of the Paper : Singapore

Summary:

The authors perform a preliminary study on what the software engineering community microblogs about. They analyze the content of microblogs from Twitter and categorize the types of microblogs that are posted. They investigate the relative popularity of each category of microblogs. They also investigate what kinds of microblogs are diffused more widely in the Twitter network via the “retweet” feature. Criteria: Areas of Study: Design, Coding, Software/Program Verification, Distribution, Maintenance and Enhancements The paper is a preliminary study on what the software engineering community microblogs about, which includes all aspects of software life cycle. Research Type: Evaluation The authors analyze the content of microblogs from Twitter and categorize the types of microblogs that are posted. They investigate the relative popularity of each category of microblogs Form of Study: Document Analysis

The authors perform manual analysis to investigate the contents of the tweets. Social Techniques: Blog/Microblog

The data sources in the paper are retrieved from Twitter. Social Connectivity: Public They use Twitter Streaming API to collect tweets that are marked with hashtags corresponding to at least one of the topics related to software engineering activities. Social Interaction: one-to-many The authors use Twitter capabilities. Social Location: Distributed The authors used Twitter APIs to capture tweets for specific areas of interest software engineering community, which is by

default distributed all around the world. Honeycomb Framework: Identity, Conversation, Sharing, Relationship Considering the social technique studied in this research, we include this paper in the identity, conversation, sharing and relationship blocks of honeycomb framework.

268