BibSonomy publications for /concept/tag/reticollab0708Wed Nov 14 18:51:47 CET 2007Los Alamitos, CA, USAicgse71-80On Coordination Mechanisms in Global Software Development02007reticollab0708 Sat Nov 10 21:36:14 CET 2007Sheffield, EnglandProceedings of the 15th International Conference on Conceptual StructuresJulyAnalysis of the Publication Sharing Behaviour in {BibSonomy}2007reticollab0708 behaviour analysis concept bibsonomy BibSonomy is a web-based social resource sharing system which allows users to organise and share bookmarks and publications in a collaborative manner. In this paper we present the system, followed by a description of the insights in the structure of its bibliographic data that we gained by applying techniques we developed in the area of Formal Concept Analysis.Thu Oct 18 23:20:44 CEST 2007New York, NY, USAACM Trans. Web27Visualizing tags over time12007folksonomy RDF tags semanticweb reticollab0708 Mon Oct 08 00:33:51 CEST 2007Los Alamitos, CA, USAicgse81-90Awareness in the Wild: Why Communication Breakdowns Occur02007communication reticollab0708 awareness GSD Mon Oct 08 00:32:51 CEST 2007Los Alamitos, CA, USAicgse91-102Of Deadlocks and Peopleware - Collaborative Work Practices in Global Software Development02007reticollab0708 collaborative GSD Mon Oct 08 00:31:36 CEST 2007Los Alamitos, CA, USAicgse204-216A 3-Dimensional Relevance Model for Collaborative Software Engineering Spaces02007collaborative reticollab0708 GSD Mon Oct 08 00:29:05 CEST 2007Los Alamitos, CA, USAicgse71-80On Coordination Mechanisms in Global Software Development02007GSD reticollab0708 coordination Wed Oct 03 18:59:29 CEST 2007Information and Software TechnologyNovember111006--1024Using an experimental study to develop group awareness support for real-time distributed collaborative writing482006writing distributed reticollab0708 group collaborative awareness Supporting group awareness is vital for the success of real-time, distributed, collaborative writing systems. Many awareness mechanisms have been introduced, but highly effective solutions are few. The research presented in this paper focuses on the development of awareness mechanisms using an experimental study of synchronous distributed collaborative writing. Our study has made two major contributions to research on group awareness. First, the study compares the importance of different awareness elements in supporting group awareness for collaborative writing. The results of our Wilcoxon test on awareness elements identify the five most important elements, including "Being able to comment on what other users have done," "Knowing what actions other users are currently taking," "Providing a communication tool when audio is not available," "Knowing other user's working areas in the document," and "Knowing other user's tasks." Second, the research proposes mechanisms corresponding to the above-mentioned five awareness elements. The mechanisms include Dynamic Task List (DTL), Modification Director (MD), Advanced Chat (AC) and Split Window View (SWV). These mechanisms provide support for various aspects of group awareness, and add many enhanced features to existing awareness mechanisms. For example, DTL presents high-level information about authors' responsibilities and the correlation between their work allocations. MD notifies users instantaneously whenever their work is modified by other authors. AC enhances communication between users by allowing them to attach document objects such as text and diagrams to a conversation message. And, SWV provides the views of other authors' working areas and viewing areas simultaneously.Wed Oct 03 16:52:26 CEST 2007Proceedings of the 1st International Symposium on Empirical Software Engineering and Metrics (ESEM'07)September275-284A Comparative Case Study on the Impact of Test-Driven Development on Program Design and Test Coverage2007design reticollab0708 test tdd xp Test-driven development (TDD) is a programming technique in which the tests are written prior to the source code. It is proposed that TDD is one of the most fundamental practices enabling the development of software in an agile and iterative manner. Both the literature and practice suggest that TDD practice yields several benefits. Essentially, it is claimed that TDD leads to an improved software design, which has a dramatic impact on the maintainability and further development of the system. The impact of TDD on program design has seldom come under the researchers’ focus. This paper reports the results from a comparative case study of three software development projects where the effect of TDD on program design was measured using objectoriented metrics. The results show that the effect of TDD on program design was not as evident as expected, but the test coverage was significantly superior to iterative test-last development.Wed Oct 03 16:45:30 CEST 2007Proceedings of the 1st International Symposium on Empirical Software Engineering and Metrics (ESEM'07)September265-274A Replicate Empirical Comparison Between Software Development with Inspection and Pair Development2007inspection development comparison pair reticollab0708 In 2005, we studied the development effort and effect of quality comparisons between software development with Fagan’s inspection and pair development. Three experiments were conducted in Thailand: two classroom experiments and one industry experiment. We found that in the classroom experiments, the pair development group had less average development effort than the inspection group with the same or higher level of quality. The industry experiment’s result showed pair development to have a bit more effort but about 40% fewer major defects. However, since this set of experiments was conducted in Thailand, the results may be different if we conducted the experiment in other countries due to the impact of cultural differences. To investigate this we conducted another experiment with Computer Science graduate students at USC in Fall 2006. Unfortunately, the majority of the graduate students who participated in the experiment were from India, a country in which the culture is not much different from Thailand [18], [19]. As a result, we cannot compare the impact of cultural differences in this paper. However, the results showed that the experiment can be replicated in other countries where the cultures are similar.Wed Oct 03 16:36:11 CEST 2007Proceedings of the 1st International Symposium on Empirical Software Engineering and Metrics (ESEM'07)September255-264Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study2007reticollab0708 development agile Agile development methodologies have been gaining acceptance in the mainstream software development community. While there are numerous studies of Agile development in academic and educational settings, there has been little detailed reporting of the usage, penetration and success of Agile methodologies in traditional, professional software development organizations. We report on the results of an empirical study conducted at Microsoft to learn about Agile development and its perception by people in development, testing, and management. We found that one-third of the study respondents use Agile methodologies to varying degrees, and most view it favorably due to improved communication between team members, quick releases and the increased flexibility of Agile designs. The Scrum variant of Agile methodologies is by far the most popular at Microsoft. Our findings also indicate that developers are most worried about scaling Agile to larger projects (greater than twenty members), attending too many meetings and the coordinating Agile and non-Agile teams.Wed Oct 03 15:59:16 CEST 2007Special Issue Section: Distributed Software DevelopmentInformation and Software Technology#sep#9781--794Essential communication practices for Extreme Programming in a global software development team482006communication teams agile xp reticollab0708 distributed We conducted an industrial case study of a distributed team in the USA and the Czech Republic that used Extreme Programming. Our goal was to understand how this globally-distributed team created a successful project in a new problem domain using a methodology that is dependent on informal, face-to-face communication. We collected quantitative and qualitative data and used grounded theory to identify four key factors for communication in globally-distributed XP teams working within a new problem domain. Our study suggests that, if these critical enabling factors are addressed, methodologies dependent on informal communication can be used on global software development projects.Wed Oct 03 13:42:30 CEST 2007HICSSconf/hicss/2006Improving Group Communication Outcomes with Collaborative Software: The Impact of Group Size, Media Richness, and Social Presence.2006reticollab0708 media-richness Project groups are becoming a mainstay in today’s work environment. This coupled with globalization has distributed many teams. This makes communication among team members vital to project success. This study evaluates the impact of group size and social presence upon group communication. It compares key communication factors for three different social presence treatments (Face-to-Face without CS support; Face-to- Face with CS support; and distributed with CS support). In addition, it evaluates these impacts with two different group sizes. The results indicate that smaller and higher social presence groups maintain higher levels of communication than larger groups and groups with lower social presence. These results should alert project managers to the difficulty of communication between project team members in distributed global environmentsTue Oct 02 16:25:21 CEST 2007New York, NY, USACHI '07: Proceedings of the SIGCHI conference on Human factors in computing systems1313--1322FASTDash: a visual dashboard for fostering awareness in software teams2007teams dashboard reticollab0708 awareness software collaboration Software developers spend significant time gaining and maintaining awareness of fellow developers' activities. FASTDash is a new interactive visualization that seeks to improve team activity awareness using a spatial representation of the shared code base that highlights team members' current activities. With FASTDash, a developer can quickly determine which team members have source files checked out, which files are being viewed, and what methods and classes are currently being changed. The visualization can be annotated, allowing programmers to supplement activity information with additional status details. It provides immediate awareness of potential conflict situations, such as two programmers editing the same source file. FASTDash was developed through user-centered design, including surveys, team interviews, and in situ observation. Results from a field study show that FASTDash improved team awareness, reduced reliance on shared artifacts, and increased project-related communication. Additionally, the team that participated in our field study continues to use FASTDash.Tue Oct 02 16:23:52 CEST 2007Software Engineering Conference, 2007. ASWEC 2007. 18th Australian399-408NextMove: A Framework for Distributed Task Coordination2007teams collaboration coordination reticollab0708 distributed This paper presents NextMove, a framework that assists project managers in allocating and managing tasks in an agile, distributed development environment. In such environments, managing tasks dynamically is difficult because of the lack of available informal, lightweight communication mechanisms. The framework simulates the project manager's thought processes involved in prioritizing and allocating tasks, by aggregating the variables involved in a software project, such as schedules, feature priorities and team-member attributes, using multi-criteria decision-resolution methodologies. We implemented the framework as a distributed client-server application using Java and MySQL. In addition, we built a simulator to evaluate the effectiveness of the framework. Preliminary simulation results show that, when compared with randomized selection of tasks, NextMove is more efficiently allocates tasks, so in a way that the project is completed sooner.Tue Oct 02 16:18:43 CEST 2007Software Engineering, IEEE Transactions on226- 237On the effectiveness of the test-first approach to programming312005test-first reticollab0708 testing xp agile tdd Test-driven development (TDD) is based on formalizing a piece of functionality as a test, implementing the functionality such that the test passes, and iterating the process. This paper describes a controlled experiment for evaluating an important aspect of TDD: in TDD, programmers write functional tests before the corresponding implementation code. The experiment was conducted with undergraduate students. While the experiment group applied a test-first strategy, the control group applied a more conventional development technique, writing tests after the implementation. Both groups followed an incremental process, adding new features one at a time and regression testing them. We found that test-first students on average wrote more tests and, in turn, students who wrote more tests tended to be more productive. We also observed that the minimum quality increased linearly with the number of programmer tests, independent of the development strategy employed.Tue Oct 02 16:00:41 CEST 2007Washington, DC, USAADC '05: Proceedings of the Agile Development Conference80--89An Environment for Collaborative Iteration Planning2005face-to-face planning collaboration reticollab0708 meeting Existing project planning software for agile development processes offers limited support for face-to-face, synchronous collaboration. In this paper, we describe an environment, AgilePlanner, that supports team collaboration during planning meetings. Our approach utilizes advanced technologies of pen computing and digital tabletops to create a collaborative work environment to emulate project planning using index cards. It combines the benefits of paper index cards with those of traditional desktop planning solutions. AgilePlanner is intended as an integral resource in the planning process.Tue Oct 02 15:51:22 CEST 2007Washington, DC, USAAGILE '06: Proceedings of the conference on AGILE 200635--46Executable Acceptance Tests for Communicating Business Requirements: Customer Perspective2006reticollab0708 agile testing acceptance requirements Using an experimental method, we found that customers, partnered with an IT professional, are able to use executable acceptance test (storytest)-based specifications to communicate and validate functional business requirements. However, learnability and ease of use analysis indicates that an average customer may experience difficulties learning the technique. Several additional propositions are evaluated and usage observations made.Mon Oct 01 20:36:55 CEST 2007Innsbruck, AustriaBridging the Gap between Semantic Web and Web 2.0, workshop at ESWC 20076Organizing Resources on Tagging Systems using T-ORG2007reticollab0708 organizing tagging resources Mon Oct 01 20:36:14 CEST 2007Los Alamitos, CA, USAhicss85bThe Social Structure of Tagging Internet Video on del.icio.us002007structure social reticollab0708 tagging internet video del.icio.us