Software systems are getting larger and more complex, while the requirements are becoming vaguer and more rapidly changing. These trends make current software development more and more likely a team work. To integrate multiple developers into a coherent structured management process and make team software development a positive-sum game for both higher productivity and better quality, many team soft ware development methodologies have been proposed and practised. An emerging methodology is collaborative programming, which allows a group of programmers to work together on the same source code for design, implementation of individual components, and integration of individual components. Compared with other team software methodologies that only address needs in some phases or situations, collaborative programming is more adaptive to the variety of different phases or situations in a team software development process. A core technical component in collaborative programming is collaborative editing, which allows a group of programmers to view and edit the same source code. To support different phases or situations in an Internet-based collaborative programming process, collaborative editing must meet the requirements of supporting unconstrained, responsive, real-time collaborative editing; unconstrained, syncretic, non-real-time collaborative editing; and smooth, flexible switching between real-time and non-real-time collaborative editing. This thesis research contributes several novel techniques to address these requirements, and an Internet-based collaborative programming environment to integrate those techniques. These research contributions have advanced state-of-the-art technologies on col laborative editing for supporting Internet-based collaborative programming. First, we contribute a collaborative highlighting gestural communication technique for unconstrained, responsive, real-time collaborative editing. This technique is particularly effective in improving the quality of real-time interaction on text-based source code documents. The contribution to the operational transformation technology is the extension of the technology to support group awareness. It includes a package of operational transformation functions and transformation control algorithms for consistency maintenance in collaborative highlighting, and a flexible undo solution that has the capability of undoing any highlighting operation at any time. Second, we contribute a flexible operation-based merging technique for unconstrained, syncretic, non-real-time collaborative editing, which is efficient and has the capability of textually integrating all changes, and automatically detecting and resolving syntactic conflicts according to application-dependent user-specified policies. The contribution to the operational transformation technology is the extension of the technology to support unconstrained, syncretic, non-real-time collaborative editing. Its includes a log compression algorithm, a textual merging algorithm, and a syntactic merging algorithm. Moreover, we contribute a flexible notification technique to support flexible collaborative editing: unconstrained, responsive, real-time collaborative editing; uncon strained, syncretic, non-real-time collaborative editing; and smooth, flexible switching between them. The contribution to the operational transformation technology is the extension of the technology to support flexible collaborative editing. It includes a new transformation control algorithm that has a linear time complexity, two notification algorithms that support propagation and acceptance of any notifications at any time, and a notification propagation protocol that is efficient for both real-time and non-real-time collaborative editing.

Extreme programming is an agile software development process, which has gained a lot of publicity the last couple of years. It has also brought Pair Programming into new light. Research and experiments have shown that the usage of Pair Programming can increase the quality in software development. People who used Pair Programming are usually satisfied using it and they are also more confident in their solutions. Having a pair colleague is not redundancy, people bring the best out of each other and they produce better solutions. Wages for employees are today heavy costs for companies but quality and time aspects in software development become more and more important. A quantitative survey has been conducted among professionals and students, both with and without Pair Programming experience. People surveyed have very low resistance from the start when using Pair Programming. They actually find benefits from it compared to being singles, but they think it should not be used on every task and at every time. This report investigates if Pair Programming is a technique to increase quality and productivity within software development. We also address business related aspects compared to the usage of Pair Programming as well as management aspects to see if we can find other synergy effects from the use of Pair Programming. / Denna rapport undersöker om Parprogrammering är en teknik för att höja kvalitén och produktiviteten inom mjukvaruutvecklingen. Vi belyser även relaterade areor och jämför dessa med Parprogrammering för att se om vi kan finna synergieffekter från användandet av Parprogrammering. Vi har gjort en undersökning både bland professionella och studenter, både med och utan Parprogrammeringserfarenhet. De som svarat har väldigt lågt motstånd till att använda Parprogrammering. De anser att det finns fördelar med att använda Parprogrammering jämfört med att arbeta själv, men de anser att tekniken inte kan användas hela tiden på alla delmoment. / Nöjesv 6 294 77 Sölvesborg 0708-422240

Programming practices are used to improve various attributes of the coding process. Pair and Mob Programming are two practices that involve multiple developers collaboratively working on the same tasks and share multiple advantages and disadvantages. The aim of this project is to identify common advantages and disadvantages of the two practices as well as some attributes that differentiate the two and help in the process of deciding which programming practice should be used for a task. The first method used to answer the research questions was a literature review that should find and list the pros and cons of Mob and Pair Programming. A second method used were interviews with industry practitioners, whose perspectives and experiences will validate the previous results, add new attributes to the practices and identify differences and factors that encourage the use of one or the other practice. The findings of the project consist of positive and negative aspects of using any of the two programming practices and a set of attributes that should be considered when deciding whether to adopt Mob or Pair Programming for the task at hand.