How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature
Descripción del Articulo
Software development outsourcing is a frequent practice, a widely used modality is the software factory (SWF) model, by which a company hires one or more specialized companies, for a considerable period, to take care of its software development need, both to create new software systems and maintain...
Autor: | |
---|---|
Formato: | artículo |
Fecha de Publicación: | 2022 |
Institución: | Universidad Nacional Mayor de San Marcos |
Repositorio: | Revistas - Universidad Nacional Mayor de San Marcos |
Lenguaje: | español |
OAI Identifier: | oai:ojs.csi.unmsm:article/24856 |
Enlace del recurso: | https://revistasinvestigacion.unmsm.edu.pe/index.php/rpcsis/article/view/24856 |
Nivel de acceso: | acceso abierto |
Materia: | software maintenance outsourcing Third-Party Application Maintenance eSourcing externalización del desarrollo de software externalización del mantenimiento de software |
id |
REVUNMSM_d29772c2e37a4134a6ba2f183ef6a1ce |
---|---|
oai_identifier_str |
oai:ojs.csi.unmsm:article/24856 |
network_acronym_str |
REVUNMSM |
network_name_str |
Revistas - Universidad Nacional Mayor de San Marcos |
repository_id_str |
|
spelling |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literatureCómo definir el alcance de una externalización de desarrollo de aplicaciones mediante un modelo de software factory : Una revisión sistemática de la literaturaAzabache, AlbertAzabache, Albertsoftware maintenance outsourcingThird-Party Application MaintenanceeSourcingexternalización del desarrollo de softwareexternalización del mantenimiento de softwareSoftware development outsourcing is a frequent practice, a widely used modality is the software factory (SWF) model, by which a company hires one or more specialized companies, for a considerable period, to take care of its software development need, both to create new software systems and maintain the existing ones; The model provides important advantages to the contracting organization, but its implementation requires rigorous planning to correctly define the scope of outsourcing, and an adequate implementation plan, among other fundamental aspects. In this article, a systematic review of the literature has been carried out to identify and analyze models, frameworks, guides, or other contributions that propose a way to define the scope of outsourcing that uses the SWF model or similar. We found few studies that address this issue and these only do so tangentially, considering its implementation, but only recommending generic practices to achieve it. Here there is a space to be filled with future works that propose specific recommendations, especially in the technical aspects to be considered.La externalización de desarrollo del software es una práctica frecuente, una modalidad muy usada es el modelo de software factory (SWF), por el cual una compañía contrata una o más empresas especializadas, por un periodo considerable, para que se haga cargo de sus necesidades de desarrollo, tanto para crear nuevos sistemas de software como mantener los existentes; el modelo brinda importantes ventajas a la organización contratante pero su implementación requiere de una planificación rigurosa para definir correctamente el alcance de la externalización, un adecuado plan de implementación, entre otros aspectos fundamentales. En este artículo se ha realizado una revisión sistemática de la literatura para identificar y analizar modelos, frameworks, guías u otros aportes que propongan una forma de definir el alcance de externalizaciones que usan el modelo de SWF o similares. Encontramos pocos estudios que abordan esta cuestión y sólo lo hacen tangencialmente considerando su realización, pero sólo recomendando prácticas genéricas para lograrlo. Aquí hay un espació por llenar con trabajos futuros que propongan recomendaciones específicas sobre todo en los aspectos técnicos a considerar.Universidad Nacional Mayor de San Marcos, Facultad de Ingeniería de Sistemas e Informática2022-12-31info:eu-repo/semantics/articleinfo:eu-repo/semantics/publishedVersionapplication/pdfhttps://revistasinvestigacion.unmsm.edu.pe/index.php/rpcsis/article/view/2485610.15381/rpcs.v4i2.24856Revista Peruana de Computación y Sistemas; Vol. 4 No. 2 (2022); 53-64Revista peruana de computación y sistemas; Vol. 4 Núm. 2 (2022); 53-642617-2003reponame:Revistas - Universidad Nacional Mayor de San Marcosinstname:Universidad Nacional Mayor de San Marcosinstacron:UNMSMspahttps://revistasinvestigacion.unmsm.edu.pe/index.php/rpcsis/article/view/24856/19363Derechos de autor 2022 Albert Azabachehttps://creativecommons.org/licenses/by/4.0info:eu-repo/semantics/openAccessoai:ojs.csi.unmsm:article/248562023-07-13T16:22:35Z |
dc.title.none.fl_str_mv |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature Cómo definir el alcance de una externalización de desarrollo de aplicaciones mediante un modelo de software factory : Una revisión sistemática de la literatura |
title |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature |
spellingShingle |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature Azabache, Albert software maintenance outsourcing Third-Party Application Maintenance eSourcing externalización del desarrollo de software externalización del mantenimiento de software |
title_short |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature |
title_full |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature |
title_fullStr |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature |
title_full_unstemmed |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature |
title_sort |
How to define the scope of an application development outsourcing through a software factory model?: A systematic review of the literature |
dc.creator.none.fl_str_mv |
Azabache, Albert Azabache, Albert |
author |
Azabache, Albert |
author_facet |
Azabache, Albert |
author_role |
author |
dc.subject.none.fl_str_mv |
software maintenance outsourcing Third-Party Application Maintenance eSourcing externalización del desarrollo de software externalización del mantenimiento de software |
topic |
software maintenance outsourcing Third-Party Application Maintenance eSourcing externalización del desarrollo de software externalización del mantenimiento de software |
description |
Software development outsourcing is a frequent practice, a widely used modality is the software factory (SWF) model, by which a company hires one or more specialized companies, for a considerable period, to take care of its software development need, both to create new software systems and maintain the existing ones; The model provides important advantages to the contracting organization, but its implementation requires rigorous planning to correctly define the scope of outsourcing, and an adequate implementation plan, among other fundamental aspects. In this article, a systematic review of the literature has been carried out to identify and analyze models, frameworks, guides, or other contributions that propose a way to define the scope of outsourcing that uses the SWF model or similar. We found few studies that address this issue and these only do so tangentially, considering its implementation, but only recommending generic practices to achieve it. Here there is a space to be filled with future works that propose specific recommendations, especially in the technical aspects to be considered. |
publishDate |
2022 |
dc.date.none.fl_str_mv |
2022-12-31 |
dc.type.none.fl_str_mv |
info:eu-repo/semantics/article info:eu-repo/semantics/publishedVersion |
format |
article |
status_str |
publishedVersion |
dc.identifier.none.fl_str_mv |
https://revistasinvestigacion.unmsm.edu.pe/index.php/rpcsis/article/view/24856 10.15381/rpcs.v4i2.24856 |
url |
https://revistasinvestigacion.unmsm.edu.pe/index.php/rpcsis/article/view/24856 |
identifier_str_mv |
10.15381/rpcs.v4i2.24856 |
dc.language.none.fl_str_mv |
spa |
language |
spa |
dc.relation.none.fl_str_mv |
https://revistasinvestigacion.unmsm.edu.pe/index.php/rpcsis/article/view/24856/19363 |
dc.rights.none.fl_str_mv |
Derechos de autor 2022 Albert Azabache https://creativecommons.org/licenses/by/4.0 info:eu-repo/semantics/openAccess |
rights_invalid_str_mv |
Derechos de autor 2022 Albert Azabache https://creativecommons.org/licenses/by/4.0 |
eu_rights_str_mv |
openAccess |
dc.format.none.fl_str_mv |
application/pdf |
dc.publisher.none.fl_str_mv |
Universidad Nacional Mayor de San Marcos, Facultad de Ingeniería de Sistemas e Informática |
publisher.none.fl_str_mv |
Universidad Nacional Mayor de San Marcos, Facultad de Ingeniería de Sistemas e Informática |
dc.source.none.fl_str_mv |
Revista Peruana de Computación y Sistemas; Vol. 4 No. 2 (2022); 53-64 Revista peruana de computación y sistemas; Vol. 4 Núm. 2 (2022); 53-64 2617-2003 reponame:Revistas - Universidad Nacional Mayor de San Marcos instname:Universidad Nacional Mayor de San Marcos instacron:UNMSM |
instname_str |
Universidad Nacional Mayor de San Marcos |
instacron_str |
UNMSM |
institution |
UNMSM |
reponame_str |
Revistas - Universidad Nacional Mayor de San Marcos |
collection |
Revistas - Universidad Nacional Mayor de San Marcos |
repository.name.fl_str_mv |
|
repository.mail.fl_str_mv |
|
_version_ |
1795238282108338176 |
score |
13.958958 |
Nota importante:
La información contenida en este registro es de entera responsabilidad de la institución que gestiona el repositorio institucional donde esta contenido este documento o set de datos. El CONCYTEC no se hace responsable por los contenidos (publicaciones y/o datos) accesibles a través del Repositorio Nacional Digital de Ciencia, Tecnología e Innovación de Acceso Abierto (ALICIA).
La información contenida en este registro es de entera responsabilidad de la institución que gestiona el repositorio institucional donde esta contenido este documento o set de datos. El CONCYTEC no se hace responsable por los contenidos (publicaciones y/o datos) accesibles a través del Repositorio Nacional Digital de Ciencia, Tecnología e Innovación de Acceso Abierto (ALICIA).