Mostrar el registro sencillo del ítem

dc.contributor.authorServant-Cortés, Francisco Javier 
dc.contributor.authorJones, James A.
dc.contributor.authorVan der Hoek, Andre
dc.date.accessioned2024-10-25T06:41:14Z
dc.date.available2024-10-25T06:41:14Z
dc.date.issued2010
dc.identifier.citationCASI: preventing indirect conflicts through a live visualization. In Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering (CHASE '10). Association for Computing Machinery, New York, NY , USA, 39–46. DOI: https://doi.org/10.1145/1833310.1833317es_ES
dc.identifier.urihttps://hdl.handle.net/10630/34900
dc.descriptionCorreo 25/10/24
dc.description.abstractSoftware development is a collaborative activity that may lead to conflicts when changes are performed in parallel by several developers. Direct conflicts arise when multiple developers make changes in the same source code entity, and indirect conflicts are produced when multiple developers make changes to source code entities that depend on each other. Previous approaches of code analysis either cannot predict all kinds of indirect conflicts, since they can be caused by syntactic or semantic changes, or they produce so much information as to make them virtually useless. Workspace awareness techniques have been proposed to enhance software configuration management systems by providing developers with information about the activity that is being performed by other developers. Most workspace awareness tools detect direct conflicts while only some of them warn about potential indirect conflicts. We propose a new approach to the problem of indirect conflicts. Our tool CASI informs developers of the changes that are taking place in a software project and the source code entities influenced by them. We visualize this influence together with directionality and severity information to help developers decide whether a concrete situation represents an indirect conflict. We introduce our approach, explain its implementation, discuss its behavior on an example, and lay out several steps that we will be taking to improve it in the future.es_ES
dc.description.sponsorshipFundación Caja Madrides_ES
dc.language.isoenges_ES
dc.publisherAssociation for Computing Machinery (ACM)es_ES
dc.rightsinfo:eu-repo/semantics/openAccesses_ES
dc.rights.urihttp://creativecommons.org/licenses/by-nc-nd/4.0/*
dc.subjectProgramación de ordenadoreses_ES
dc.subjectSoporte lógico - Mantenimientoes_ES
dc.subjectSoporte lógico - Desarrolloes_ES
dc.subject.otherProgramming environmentses_ES
dc.subject.otherSoftware maintenancees_ES
dc.subject.otherSoftware designes_ES
dc.subject.otherSoftware comprehensiones_ES
dc.subject.otherSoftware evolutiones_ES
dc.titleCASI: Preventing Indirect Conflicts through a Live Visualization.es_ES
dc.typeinfo:eu-repo/semantics/conferenceObjectes_ES
dc.relation.eventtitleICSE Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)es_ES
dc.relation.eventplaceCape Town, South Africaes_ES
dc.relation.eventdateMayo 2010es_ES
dc.identifier.doi10.1145/1833310.1833317
dc.rights.ccAttribution-NonCommercial-NoDerivatives 4.0 Internacional*


Ficheros en el ítem

Este ítem aparece en la(s) siguiente(s) colección(ones)

Mostrar el registro sencillo del ítem

Attribution-NonCommercial-NoDerivatives 4.0 Internacional
Excepto si se señala otra cosa, la licencia del ítem se describe como Attribution-NonCommercial-NoDerivatives 4.0 Internacional