Isabella A. da Silva
ABSTRACT
Despite the fact that software development is an inherently collaborative activity, a great deal of software development is spent with developers in isolation, working on their own parts of the system. In these situations developers are unaware of parallel changes being made by others, often resulting in conflicts. One common approach to deal with this issue is called conflict resolution, which means that changes have already been checked-in and developers must use merge tools to resolve conflicts and then retest the code to ensure its correctness. Unfortunately, this process becomes more difficult the longer the conflicts go undetected. In order to address these issues, have been proposed conflict avoidance approaches that detect conflicts as soon as they occur. In this paper, we present Lighthouse, an Eclipse plug-in that takes the conflict avoidance approach to coordinate developers. Lighthouse distinguishes itself by utilizing a concept called emerging design, an up to date design representation of the code, to alert developers of potentially conflicting implementation changes as they occur, indicating where the changes have been made and by whom.
- Allen, L., Fernandez, G., Kane, K., Leblang, D. B., Minard, D., and Posner, J. 1995. ClearCase MultiSite: Supporting Geographically-Distributed Software Development. In Selected Papers From the ICSE SCM-4 and SCM-5 Workshops on Software Configuration Management, LKNCS 1005. Springer-Verlag, 194--214. Google Scholar
Digital Library
- McCrickard, D. S., Chewar, C. M., Somervell, J. P., and Ndiwalana, A. 2003. A model for notification systems evaluation---assessing user goals for multitasking activity. ACM Trans. Comput.-Hum. Interact. 10(4), 312--338. Google ScholarDigital Library
- Eclipse, Eclipse, http://www.eclipse.orgGoogle Scholar
- Hupfer, S., Cheng, L., Ross, S., and Patterson, J. 2004. Introducing collaboration into an application development environment. In Proceedings of the 2004 ACM Conference on Computer Supported Cooperative Work, 2004, 21--24. Google ScholarDigital Library
- Perry, D. E., Siy, H. P., and Votta, L. G. 2001. Parallel changes in large-scale software development: an observational case study. ACM TOSEM. 10(3), 308--337. Google ScholarDigital Library
- Sarma, A., Noroozi, Z., and van der Hoek, A. 2003. Palantír: raising awareness among configuration management workspaces. Twenty-fifth international Conference on Software Engineering, 444--454. Google ScholarDigital Library
- Sarma, A., van der Hoek, A. 2004. A conflict detected earlier is a conflict resolved easier. Fourth Workshop on Open Source Software Engineering".Google Scholar
- Speier, C., Valacich, J. S., and Vessey, I. 1997. The effects of task interruption and information presentation on individual decision making. Eighteenth International Conference on Information Systems, 21--36. Google ScholarDigital Library
- Subclipse, Subclipse, http://subclipse.tigris.org/Google Scholar
- Subversion, Subversion, http://subversion.tigris.org/Google Scholar
- Van der Hoek, A., Redmiles, D., Dourish P., Sarma, A., Silva Filho R., and De Souza, C. 2004. Continuous coordination: a new paradigm for collaborative software engineering tools. Workshop on Directions in Software Engineering EnvironmentsGoogle ScholarCross Ref
- Van der Westhuizen, C., Chen, P. H., and van der Hoek, A. 2006. Emerging design: new roles and uses for abstraction. 2006 International Workshop on Role of Abstraction in Software Engineering, 23--2. Google ScholarDigital Library
Index Terms
- Lighthouse: coordination through emerging design
Recommendations
A Novel Deadlock Avoidance Algorithm and Its Hardware Implementation
CODES+ISSS '04: Proceedings of the international conference on Hardware/Software Codesign and System Synthesis: 2004This paper proposes a novel Deadlock Avoidance Algorithm (DAA) and its hardware implementation, the Deadlock Avoidance Unit (DAU), as an Intellectual Property (IP) core that provides a mechanism for very fast and automatic deadlock avoidance in ...
Reduced Hardware NOrec: A Safe and Scalable Hybrid Transactional Memory
ASPLOS'15Because of hardware TM limitations, software fallbacks are the only way to make TM algorithms guarantee progress. Nevertheless, all known software fallbacks to date, from simple locks to sophisticated versions of the NOrec Hybrid TM algorithm, have ...
Reduced Hardware NOrec: A Safe and Scalable Hybrid Transactional Memory
ASPLOS '15: Proceedings of the Twentieth International Conference on Architectural Support for Programming Languages and Operating SystemsBecause of hardware TM limitations, software fallbacks are the only way to make TM algorithms guarantee progress. Nevertheless, all known software fallbacks to date, from simple locks to sophisticated versions of the NOrec Hybrid TM algorithm, have ...
Comments