Show simple item record

XP/Architecture: Un modelo Ágil para Escalar XP

dc.contributor.authorMuñoz, Luis F.spa
dc.contributor.authorHurtado Alegría, Julio Arielspa
dc.date.accessioned2020-10-27T00:20:29Z
dc.date.available2020-10-27T00:20:29Z
dc.date.issued2012-12-01
dc.identifier.issn2539-2115
dc.identifier.issn1657-2831
dc.identifier.urihttp://hdl.handle.net/20.500.12749/8919
dc.description.abstractXP es uno de los métodos ágiles más usados por la industria del software y la comunidad científica. Sin embargo, la literatura reporta problemas para escalarlo cuando el equipo crece y el producto es complejo. El SEI propone prácticas de arquitectura como mecanismos para resolver asuntos de complejidad y organización de las soluciones para alcanzar los atributos de calidad más relevantes. Aprovechando la capacidad de los métodos de arquitecturas y para separar preocupaciones a gran escala, en este artículo se propone un método de desarrollo de software en que varios equipos de desarrollo XP trabajan coordinadamente alrededor de un equipo que incorpora en forma ágil prácticas arquitectónicas. El método ha sido aplicado en un estudio de caso en dos proyectos académicos, mostrando la capacidad del modelo para escalar grupos trabajo, organizados en equipos XP en proyectos de mediana complejidad.spa
dc.format.mimetypeapplication/pdfspa
dc.language.isospaspa
dc.publisherUniversidad Autónoma de Bucaramanga UNAB
dc.relationhttps://revistas.unab.edu.co/index.php/rcc/article/view/2128/1896
dc.relation.urihttps://revistas.unab.edu.co/index.php/rcc/article/view/2128
dc.rightsDerechos de autor 2012 Revista Colombiana de Computación
dc.rights.urihttp://creativecommons.org/licenses/by-nc-sa/4.0/*
dc.rights.urihttp://creativecommons.org/licenses/by-nc-nd/2.5/co/
dc.sourceRevista Colombiana de Computación; Vol. 13 Núm. 2 (2012): Revista Colombiana de Computación; 124-140
dc.subjectIngeniería del Software
dc.subjectProcesos Software
dc.subjectMétodos Agiles
dc.subjectArquitectura del Software
dc.titleXP/Architecture: Un modelo Ágil para Escalar XPspa
dc.title.translatedXP/Architecture: An Agile Model for Scaling XPeng
dc.type.driverinfo:eu-repo/semantics/article
dc.type.localArtículospa
dc.type.coarhttp://purl.org/coar/resource_type/c_7a1f
dc.subject.keywordsSoftware Engineeringeng
dc.subject.keywordsSoftware Processeseng
dc.subject.keywordsAgile Methodseng
dc.subject.keywordsSoftware Architectureeng
dc.subject.keywordsTechnological innovationseng
dc.subject.keywordsTechnological developmenteng
dc.subject.keywordsComputer's scienceeng
dc.subject.keywordsInformation technology and communicationeng
dc.subject.keywordsResearcheng
dc.identifier.instnameinstname:Universidad Autónoma de Bucaramanga UNABspa
dc.type.hasversioninfo:eu-repo/semantics/acceptedVersion
dc.rights.accessrightsinfo:eu-repo/semantics/openAccessspa
dc.relation.referencesFedesoft. (2011) Noticias TIC. [Online]. Available: http://www.fedesoft.org
dc.relation.referencesP. L. José Hilario Canós and C. Penadés, “Metodologías Agiles en el Desarrollo de Software,” Tech. Rep., 2003.
dc.relation.referencesR. J. Costello and D.-B. Liu, Metrics for Requirements Engineering. Journal of Systems and Software 1995, 1995.
dc.relation.referencesK. Beck and C. Andres, Extreme Programming Explained: Embrace Change (2nd Edition). Addison-Wesley Professional, 2004.
dc.relation.referencesP. C. Pendharkar, Rodger, and J. A., “The Relationship Between Software Development Team Size and Software Development Cost,” Commun. ACM, vol. 52, no. 1, pp. 141–144, Jan. 2009.
dc.relation.referencesR. L. Nord, Tomayko, and J. E., “Software Architecture-Centric Methodsand Agile Development,” IEEE Software, vol. 23, no. 2, pp. 47–53, Mar.2006.
dc.relation.referencesE. Hadar and G. M. Silberman, “Agile architecture Methodology: Long Term Strategy Interleaved with Short Term Practics,” in Companion tothe 23rd ACM SIGPLAN conference on Objectoriented programmingsystems languages and applications, ser. OOPSLA Companion '08.New York, NY, USA: ACM, 2008, pp. 641–652.
dc.relation.referencesO. S. P Abrahamsson and J. Ronkainen, Agile Software Development Methods: Review and Analysis. VTT Electronics, 2002.
dc.relation.referencesA. Kornstadt and J. Sauer, “Tackling Offshore Communication Challenges with Agile Architecture-Centric Development,” in Proceedingsof the Sixth Working IEEE/IFIP Conference on Software Architecture,ser. WICSA '07. Washington, DC, USA: IEEE Computer Society,2007, pp.
dc.relation.referencesP. S. Rolf Njor Jensen, Thomas Maller and G. Tarnehaj, Architectureand Design in eXtreme Programming; Introducing Developer Stories.Lecture Notes in Computer Science, 2006.
dc.relation.referencesD. J. Reifer, F. Maurer, and M. H. Erdogmus, “Scaling Agile Methods,”IEEE Software, vol. 20, no. 4, pp. 12–14, 2003.
dc.relation.referencesL. Layman, L. Williams, and L. Cunningham, “Exploring ExtremeProgramming in Context: An Industrial Case Study,” in Proceedingsof the Agile Development Conference, ser. ADC '04. Washington, DC,USA: IEEE Computer Society, 2004, pp. 32–41.
dc.relation.referencesF. Maurer and S. Martel, “On the Productivity of Agile Software Practices:An Industrial Case study,” International Workshop on Economics-Driven Software Engineering Researh(EDSER, Tech. Rep., 2002.
dc.relation.referencesD. Wells, “Extreme Programming a Gentle Introduction,” 2012. [Online]. Available: http://www.extremeprogramming.org
dc.relation.referencesK. Beck, M. Beedle, A. V. Bennekum, A. Cockburn, and W. Cunningham, Manifesto for Agile Software Development. URL: http://agilemanifesto.org/l, 2009.
dc.relation.referencesR. Wojcik, F. Bachmann, L. Bass, P. Clements, P. Merson, R. Nord,and B. Wood, Attribute-Driven Design (ADD), Version 2.0. SoftwareEngineering Institute, 2006, no.CMU/SEI-2006-TR023.
dc.relation.referencesM. R. Barbacci, R. J. Ellison, A. J. Lattanze, J. A. Stafford, C. B.Weinstock, and W. G. Wood, “Quality Attribute Workshops QAW -Third Edition,” Carnegie Mellon, Technical Report CMU/SEI-2003-TR-016, Oct. 2003.
dc.relation.referencesM. Freddy and H. Julio, “XP/Architecture,” Tech. Rep. IDIS-TR002, 2011.
dc.contributor.googlescholarHurtado Alegría, Julio Ariel [DyxZTSMAAAAJ]spa
dc.subject.lembInnovaciones tecnológicasspa
dc.subject.lembDesarrollo tecnológicospa
dc.subject.lembCiencias de la computaciónspa
dc.subject.lembTecnología de la información y la comunicaciónspa
dc.subject.lembInvestigaciónspa
dc.identifier.repourlrepourl:https://repository.unab.edu.co
dc.description.abstractenglishXP is one of the most used agile methods by the software industry and the scientific community. However, the literature reports problems scale it when the team grows and the product is complex. The SEI proposes architectural practices as mechanisms for resolving issues of complexity and organization of solutions to achieve the attributes of most relevant quality. Taking advantage of the capacity of the methods of architectures and to separate large-scale concerns, this article will proposes a method of software development in which several teams of XP development work in coordination around a team that incorporates in an agile architectural practices. The method has been applied in a study of case in two academic projects, showing the capacity of the model to scale work groups, organized in XP teams in medium-sized projects complexity.eng
dc.subject.proposalIngeniería del softwarespa
dc.subject.proposalProcesos softwarespa
dc.subject.proposalMétodos agilesspa
dc.subject.proposalArquitectura del softwarespa
dc.type.redcolhttp://purl.org/redcol/resource_type/CJournalArticle
dc.rights.creativecommonsAttribution-NonCommercial-ShareAlike 4.0 International*


Files in this item

Thumbnail
Name:
2012_Articulo_XP Architecture ...
Size:
1.076Mb
Format:
PDF
Description:
Artículo
View/Open

This item appears in the following Collection(s)

Show simple item record

Attribution-NonCommercial-ShareAlike 4.0 International
Except where otherwise noted, this item's license is described as Attribution-NonCommercial-ShareAlike 4.0 International