DeSoftIn: A methodological proposal for individual software development
DOI:
https://doi.org/10.19053/01211129.v26.n45.2017.6061Keywords:
Agile Methods, Development Methodology, Software Quality, Software EngineeringAbstract
Different Computer Engineering undergraduate programs over the world are demanding the students to present individual works and, particularly, to present a degree project, which in most cases is related to software development. However, when planning the projects, students find themselves with the problem of choosing a method to develop the software, since existent methods involve team work, but the degree project is supposed to be done individually, in order to evaluate the student’s acquired knowledge. This difficulty leads to projects that fail either to achieve the proposed objectives or to finish on the expected time, among other difficulties. This paper presents a methodological proposal for the development of individual software projects, mainly in academia, named "DeSoftIn", which will contribute to accomplish the project objectives, and will allow the students to approach development methodologies since the beginning of their studies.
Downloads
References
J. S. González-Sanabria, "Propuesta metodológica para el desarrollo individual de proyectos de software," Thesis Master in Software Engineering and Information System, Universidad Internacional de La Rioja, La Rioja, Spain, 2017.
J. P. Gamboa, and A. Rosado, “Diseño de un método ágil de desarrollo de software basado en XP, SCRUM, OPENUP y validado con la herramienta de análisis 4-DAT,” Ingenio, vol. 8, pp. 19-31, 2015.
E. Gottberg, G. Noguera, and M. A. Noguera, “Propuesta pedagógica: Una metodología de desarrollo de software para la enseñanza universitaria,” Universidades, vol. LXI (50), pp. 49-57, 2011.
C. J. Madariaga-Fernández, Y. Rivero-Peña, and A. R. Leyva-Téllez, “Propuesta metodológica para desarrollo de software educativo en la Universidad de Holguín,” Ciencias Holguín, vol. XXII (4), pp. 1-17, 2016.
J. Cervantes, and M. C. Gómez, “Taxonomía de los modelos y metodologías de desarrollo de software más utilizados,” Universidades, vol. LXII (52), pp. 37-47, 2012.
E. Parra, “Propuesta de metodología de desarrollo de software para objetos virtuales de aprendizaje -MESOVA,” Revista Virtual Universidad Católica del Norte, nº 34, pp. 113-137, 2011.
A. F. Loboguerrero, L. Castañeda Bueno, and H. F. Arboleda, “Metodología Ágil para equipos pequeños usando plataformas Microsoft,” Sistemas & Telemática, vol. 9 (18), pp. 83-99, Sep. 2011. DOI: http://doi.org/10.18046/syt.v9i18.1078. DOI: https://doi.org/10.18046/syt.v9i18.1078
I. Marcano, and G. Benigni, “Análisis de alternativas metodológicas para el desarrollo de software educativo,” SABER - Revista Multidisciplinaria del Consejo de Investigación de la Universidad de Oriente, vol. 26 (3), pp. 297-304, 2014.
J. Texier, M. De Guisti, and S. Gordillo, “El desarrollo de software dirigido por modelos en los repositorios institucionales,” Dyna, vol. 81 (184), pp. 186-192, Apr. 2014. DOI: http://doi.org/10.15446/dyna.v81n184.37164. DOI: https://doi.org/10.15446/dyna.v81n184.37164
O. Pérez, and Y. Zulueta, “Proceso para gestionar riesgos en proyectos de desarrollo de software,” Revista Cubana de Ciencias Informáticas, vol. 7 (2), pp. 206-221, 2013.
J. Bernardo-Quintero, and J. F. Duitama-Muñoz, “Reflexiones acerca de la adopción de enfoques centrados en modelos en el desarrollo de software,” Ingeniería y Universidad, vol. 15 (1), pp. 219-243, 2011.
L. F. Botero, and M. E. Álvarez, “Last planner, un avance en la planificación y control de proyectos de construcción Estudio del caso de la ciudad de Medellín,” Ingeniería y Desarrollo, nº 17, pp. 148-159, 2005.
A. Alarcón-Aldana, J. S. González-Sanabria, and S. L. Rodriguez-Torres, “Guía para pymes desarrolladoras de software, basada en la norma ISO/IEC 15504,” Revista Virtual Universidad Católica del Norte, nº 34, pp. 285-313, 2011.
E. Avila-Domenech, A. Abad, and V. De la Cruz, “Delfdroid: metodología ágil de desarrollo de software para dispositivos móviles,” Revista Ingeniería UC, vol. 20 (3), pp. 59-70, 2013.
A. Qumer, and B. Henderson-Sellers, “Measuring agility and adoptability of agile methods: a 4-Dimensional Analytical Tool,” in IADIS International Conference Applied Computing, San Sebastián, Spain, 2006.
A. Qumer, and B. Henderson-Sellers, “Comparative evaluation of XP and SCRUM using the 4d analytical tool (4-DAT),” in European and Mediterranean Conference on Information Systems (EMCIS), Costa Blanca, Alicante, Spain, 2006.
Published
How to Cite
Issue
Section
License
All articles included in the Revista Facultad de Ingeniería are published under the Creative Commons (BY) license.
Authors must complete, sign, and submit the Review and Publication Authorization Form of the manuscript provided by the Journal; this form should contain all the originality and copyright information of the manuscript.
The authors who publish in this Journal accept the following conditions:
a. The authors retain the copyright and transfer the right of the first publication to the journal, with the work registered under the Creative Commons attribution license, which allows third parties to use what is published as long as they mention the authorship of the work and the first publication in this Journal.
b. Authors can make other independent and additional contractual agreements for the non-exclusive distribution of the version of the article published in this journal (eg, include it in an institutional repository or publish it in a book) provided they clearly indicate that the work It was first published in this Journal.
c. Authors are allowed and recommended to publish their work on the Internet (for example on institutional or personal pages) before and during the process.
review and publication, as it can lead to productive exchanges and a greater and faster dissemination of published work.
d. The Journal authorizes the total or partial reproduction of the content of the publication, as long as the source is cited, that is, the name of the Journal, name of the author (s), year, volume, publication number and pages of the article.
e. The ideas and statements issued by the authors are their responsibility and in no case bind the Journal.