Best practices for requirements identification, specification, and validation to guide software implementation and maintenance processes for applications in an electricity supply company

Main Article Content

Gloria Yolanda López Herrera
Juan Carlos Jiménez Sanz

Abstract

The objective of this project is to identify and adapt the best practices for the identification, specification, and validation of requirements that guide the software implementation and maintenance processes in applications of an electric company. We performed this identification through the study and analysis of the actual state of the topic in Colombia, particularly within electric companies and supported by the theoretical examples of requirements engineering. Both the examples and the methodological models identified as best practices —such as RUP, agile development (focused on Scrum), CMMI, use cases and use cases 2.0, PMI —focused on the management of the scope and stakeholders—, and BABOK support the understanding of this topic. The result is a process that collects models to improve the requirements for new developments and for the handling of change requests and incidents/emergencies, obtaining positive evaluations by expert judgement in a pilot experiment.

Article Details

Section
Discussion papers
Author Biographies

Gloria Yolanda López Herrera, Universidad Autónoma de Manizales

Systems Engineer, Specialist in Software Engineering from the Universidad Autónoma de Manizales (Colombia). She works for an electricity supply company in its TI area implementing, maintaining and managing information systems

Juan Carlos Jiménez Sanz, Universidad Autónoma de Manizales

Ingeniero de Sistemas con especializaciones en Informática/Computación y Desarrollo Gerencial, MBA en administración con énfasis en proyectos.

References

Agudelo, L. (2015, February 12). Buenas retrospectivas = equipos en mejoramiento constante. Retrieved from: http://agilescolombia.org/2015/02/12/buenas-retrospectivas-equipos-en-mejoramiento-constante/

Arteaga, D. (2010, September 7). Referencia rápida del CMMI para desarrollo. Retrieved form: http://cmmi-en-castellano.blogspot.com.co/2009/07/implementar-cmmi.html

International Institute of Business Analysis [IIBA]. (2012). Guía sobre los fundamentos del conocimiento del análisis de negocio [Guía Babok]. Whitby, ON: IIBA.

Jacobson, I., Spence, I., & Bittner, K. (2013, August). Casos de uso 2.0. La guía para ser exitoso con los casos de uso. Retrieved from https://www.ivarjacobson.com/sites/default/files/field_iji_file/article/use_case_2.0_-_spanish_translation.pdf

Marcos, E. (2002). Investigación en ingeniería del software vs. desarrollo software. Retrieved from: http://gidis.inf.pucp.edu.pe/recursos/InvIngSWvsDS.pdf

Martinez, A., & Martinez, R. (2014, September 6). Guía a rational unified process. Retrieved from: https://anaylenlopez.files.wordpress.com/2011/03/trabajo-guia20rup.pdf

Pow-Sang, J. (2003). La especificación de requisitos con casos de uso: buenas y malas prácticas. In II Simposio Internacional de Sistemas de Información e Ingeniería de Software en la Sociedad del Conocimiento-SISOFT. Retrieved from:
http://inform.pucp.edu.pe/~jpowsang/papers/japowsang-sisoft03.pdf

Project Management Institute [PMI]. (2013). Guía de los fundamentos para la dirección de proyectos (5a ed.). Newtown Square, PA: PMI

Schwaber, K. & Sutherland, J. (2013, july). La guía de scrum: La guía definitiva de scrum, las reglas del juego. Retrieved from: http://www.scrumguides.org/docs/scrumguide/v1/Scrum-Guide-ES.pdf#zoom=100