Elicitación de requisitos no funcionales basada en la gestión de conocimiento: el marco de trabajo Merlinn

  • Sandra Lorena Buitrón Ruiz Universidad del Cauca Grupo IDIS
  • Brenda Leticia Flores Rios Universidad Autónoma de Baja California
  • Francisco Jose Pino Correa Universidad del Cauca Grupo IDIS
Palabras clave: Ingeniería de requisitos, Elicitación de requisitos, Gestión de conocimiento, Requisitos no funcionales, Estudio de caso

Resumen

La elicitación de requisitos se considera la base para las etapas siguientes del desarrollo del software, e involucra, entre otras, recopilar y analizar requisitos funcionales y no funcionales (RNF). A través de la literatura se evidencia que: (i) hay falta de mecanismos de elicitación de RNF y, (ii) existe un desconocimiento de RNF por los interesados. En este sentido, este artículo presenta el marco de trabajo para la elicitación de requisitos no funcionales basada en la gestión de conocimiento (denominado Merlinn) que busca la visualización de los RNF y una participación activa de los interesados. La evaluación de Merlinn se realizó mediante un estudio de caso en una empresa desarrolladora de software. Los resultados de la evaluación muestran que Merlinn puede ser idóneo y adaptable para apoyar el proceso de elicitación de RNF de la organización, de manera que impacta en la calidad del producto software.

Descargas

La descarga de datos todavía no está disponible.
  • Referencias

    [1] D. Pandey, U. Suman, and A. K. Ramani, “An Effective Requirement Engineering Process Model for Software Development and Requirements Management,” pp. 287-291, 2010.

    [2] H. F. Hofmann and F. Lehner, “Requirements engineering as a success factor in software projects,” IEEE software, vol. 18, p. 58, 2001.

    [3] D. Zowghi and C. Coulin, “Requirements elicitation: A survey of techniques, approaches, and tools,” in Engineering and managing software requirements, ed: Springer, 2005, pp. 19-46.

    [4] I. C. S. S. E. S. Committee and I.-S. S. Board, “IEEE Recommended Practice for Software Requirements Specifications,” 1998.

    [5] L. Chung and J. C. S. do Prado Leite, “On non-functional requirements in software engineering,” in Conceptual modeling: Foundations and applications, ed: Springer, 2009, pp. 363-379.

    [6] A. Casamayor, D. Godoy, and M. Campo, “Identification of non-functional requirements in textual specifications: A semi-supervised learning approach,” Information and Software Technology, vol. 52, pp. 436-445, 2010.

    [7] X. Franch and P. Botella, “Putting non-functional requirements into software architecture,” in Proceedings of the 9th international Workshop on Software Specification and Design, 1998, p. 60.

    [8] L. M. Cysneiros and E. Yu, “Non-functional requirements elicitation,” in Perspectives on software requirements, ed: Springer, 2004, pp. 115-138.

    [9] É. Serna-Montoya, “Estado actual de la investigación en requisitos no funcionales,” Ingeniería y Universidad, vol. 16, pp. 225-246, 2012.

    [10] M. Mijanur Rahman and S. Ripon, “Elicitation and Modeling Non-Functional Requirements – A POS Case Study,” International Journal of Future Computer and Communication, pp. 485-489, 2013.

    [11] H. Hu, Q. Ma, T. Zhang, Y. Tan, H. Xiang, C. Fu, and Y. Feng, “Semantic modelling and automated reasoning of non-functional requirement conflicts in the context of softgoal interdependencies,” IET Software, vol. 9, pp. 145-156, 2015.

    [12] W. Hu, J. C. Carver, V. K. Anu, G. S. Walia, and G. Bradshaw, “Detection of requirement errors and faults via a human error taxonomy: a feasibility study,” in Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement, 2016, p. 30.

    [13] E. Serna, O. Bachiller, and A. Serna, “Knowledge meaning and management in requirements engineering,” International Journal of Information Management, vol. 37, pp. 155-161, 2017.

    [14] F. J. Pino, M. Piattini, and G. Horta Travassos, “Managing and developing distributed research projects in software engineering by means of action-research,” Revista Facultad de Ingeniería Universidad de Antioquia, pp. 61-74, 2013.

    [15] R. K. Yin, “Case study research: Design and methods, Newbury Park,” Cal.: SAGE Publications, 1994.

    [16] K. Petersen, R. Feldt, S. Mujtaba, and M. Mattsson, “Systematic mapping studies in software engineering,” in 12th international conference on evaluation and assessment in software engineering, 2008.

    [17] I. Nonaka, R. Toyama, and N. Konno, “SECI, Ba and leadership: a unified model of dynamic knowledge creation,” Long range planning, vol. 33, pp. 5-34, 2000.

    [18] K. Dalkir and J. Liebowitz, Knowledge management in theory and practice: MIT press, 2011.

    [19] SEI, “Improving Processes in Small Settings (IPSS) A White Paper,” Software Engineering Institute, Pittsburgh, PA, 2017.

    [20] S. L. Buitrón, B. L. Flores-Rios, and F. J. Pino, “Elicitación de requisitos no funcionales basada en la gestión de conocimiento de los stakeholders,” Ingeniare. Revista chilena de ingeniería, vol. 26, pp. 142-156, 2018.

    [21] P. Brereton, B. Kitchenham, D. Budgen, and Z. Li, “Using a protocol template for case study planning,” in Proceedings of the 12th International Conference on Evaluation and Assessment in Software Engineering. University of Bari, Italy, 2008.

    [22] T. H. Al Balushi, P. R. F. Sampaio, and P. Loucopoulos, “Eliciting and prioritizing quality requirements supported by ontologies: a case study using the ElicitO framework and tool,” Expert Systems, vol. 30, pp. 129-151, 2013.

    [23] A. L. de Araújo, L. M. Cysneiros, and V. M. B. Werneck, “NDR-Tool: Uma Ferramenta de Apoio ao Reuso de Conhecimento em Requisitos Não Funcionais.”

    [24] N. Larburu, R. G. Bults, and H. J. Hermens, “Making medical treatments resilient to technological disruptions in telemedicine systems,” in IEEE-EMBS International Conference on Biomedical and Health Informatics (BHI), 2014, pp. 285-288.

    [25] Y. Terawaki, “Supporting of requirements elicitation for ensuring services of information systems used for education,” in Symposium on Human Interface, 2011, pp. 58-65.

    [26] L. Teixeira, V. Saavedra, C. Ferreira, J. Simões, and B. S. Santos, “Requirements Engineering Using Mockups and Prototyping Tools: Developing a Healthcare Web-Application,” in International Conference on Human Interface and the Management of Information, 2014, pp. 652-663.

    [27] P. Loucopoulos, J. Sun, L. Zhao, and F. Heidari, “A systematic classification and analysis of NFRs,” 2013.

    [28] D. Ameller, C. Ayala, J. Cabot, and X. Franch, “How do software architects consider non-functional requirements: An exploratory study,” in 2012 20th IEEE International Requirements Engineering Conference (RE), 2012, pp. 41-50.

    [29] J. Helming, M. Koegel, F. Schneider, M. Haeger, C. Kaminski, B. Bruegge, and B. Berenbach, “Towards a unified requirements modeling language,” in Requirements Engineering Visualization (REV), 2010 Fifth International Workshop on, 2010, pp. 53-57.

    [30] B. Wei, Z. Jin, and L. Liu, “A Formalism for Extending the NFR Framework to Support the Composition of the Goal Trees,” pp. 23-32, 2010.

    [31] X. Song, Z. Duan, and C. Tian, “Non-functional requirements elicitation and incorporation into class diagrams,” in International Conference on Intelligent Information Processing, 2010, pp. 72-81.

    [32] R. Veleda and L. M. Cysneiros, “An Initial Approach to Reuse Non-Functional Requirements Knowledge,” in iStar, 2015, pp. 25-30.
Publicado
2018-07-04
Cómo citar
Buitrón Ruiz, S., Flores Rios, B., & Pino Correa, F. (2018, julio 4). Elicitación de requisitos no funcionales basada en la gestión de conocimiento: el marco de trabajo Merlinn. Revista Ingenierías Universidad De Medellín, 17(32), 155-182. https://doi.org/https://doi.org/10.22395/rium.v17n32a8
Sección
Artículos