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

• Autores: Sandra L. Buitrón, Brenda Flores, Francisco J. Pino Correa
• Localización: Revista de Ingenierías: Universidad de Medellín, ISSN 1692-3324, Vol. 17, Nº. 32, 2018 (Ejemplar dedicado a: Enero-Junio), págs. 155-182
• Idioma: español
• DOI: 10.22395/rium.v17n32a8
• Títulos paralelos:
  • Elicitação de requisitos não funcionais baseada na gestão de conhecimento: o referencial de trabalho Merlinn
  • Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework
• Enlaces
  • Texto completo (pdf)
• Resumen
  • español

    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.

  • English

    Requirements solicitation is considered the basis for the next stages of software development, and involves, among others, collecting and analyzing functional and non-functional requirements (FNR). The literature shows that: (i) there is a lack of NFR elicitation mechanisms and (ii) there is a lack of awareness of NFR by stakeholders. In this sense, this article presents the framework for the tendering of non-functional requirements based on knowledge management (called Merlinn) that seeks the visualization of NFRs and the active participation of stakeholders.

    Merlinn’s evaluation was conducted through a study case in a software development company. The results of the evaluation show that Merlinn can be ideal and adaptable to support the organization’s NRF tendering process, so that it impacts the quality of the software product.

  • português

    A elicitação de requisitos é considerada a base para as etapas seguintes do desenvolvimento do software e envolve, entre outras, recopilar e analisar requisitos funcionais e não funcionais (RNF). Por meio da literatura, evidencia-se que (i) há falta de mecanismos de elicitação de RNF e (ii) existe um desconhecimento de RNF pelos interessados. Nesse sentido, este artigo apresenta o referencial de trabalho para a elicitação de RNF baseada na gestão de conhecimento (denominado Merlinn), que busca a visualização dos RNF e uma participação ativa dos interessados. A avaliação de Merlinn foi realizada mediante um estudo de caso numa empresa que desenvolve software. Os resultados da avaliação mostram que Merlinn pode ser idôneo e adaptável para apoiar o processo de elicitação de RNF da organização, de maneira que impacta na qualidade do produto software.

• Referencias bibliográficas
  • [1] D. Pandey, U. Suman, and A. K. Ramani, “An Effective Requirement Engineering Process Model for Software Development and Requirements Management,”...
  • [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...
  • [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...
  • [6] A. Casamayor, D. Godoy, and M. Campo, “Identification of non-functional requirements in textual specifications: A semi-supervised learning...
  • [7] X. Franch and P. Botella, “Putting non-functional requirements into software architecture,” in Proceedings of the 9th international Workshop...
  • [8] L. M. Cysneiros and E. Yu, “Non-functional requirements elicitation,” in Perspectives on software requirements, ed: Springer, 2004, pp....
  • [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...
  • [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...
  • [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:...
  • [13] E. Serna, O. Bachiller, and A. Serna, “Knowledge meaning and management in requirements engineering,” International Journal of Information...
  • [14] F. J. Pino, M. Piattini, and G. Horta Travassos, “Managing and developing distributed research projects in software engineering by means...
  • [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...
  • [17] I. Nonaka, R. Toyama, and N. Konno, “SECI, Ba and leadership: a unified model of dynamic knowledge creation,” Long range planning, vol....
  • [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...
  • [21] P. Brereton, B. Kitchenham, D. Budgen, and Z. Li, “Using a protocol template for case study planning,” in Proceedings of the 12th International...
  • [22] T. H. Al Balushi, P. R. F. Sampaio, and P. Loucopoulos, “Eliciting and prioritizing quality requirements supported by ontologies: a case...
  • [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...
  • [24] N. Larburu, R. G. Bults, and H. J. Hermens, “Making medical treatments resilient to technological disruptions in telemedicine systems,”...
  • [25] Y. Terawaki, “Supporting of requirements elicitation for ensuring services of information systems used for education,” in Symposium on...
  • [26] L. Teixeira, V. Saavedra, C. Ferreira, J. Simões, and B. S. Santos, “Requirements Engineering Using Mockups and Prototyping Tools: Developing...
  • [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,”...
  • [29] J. Helming, M. Koegel, F. Schneider, M. Haeger, C. Kaminski, B. Bruegge, and B. Berenbach, “Towards a unified requirements modeling language,”...
  • [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...
  • [32] R. Veleda and L. M. Cysneiros, “An Initial Approach to Reuse Non-Functional Requirements Knowledge,” in iStar, 2015, pp. 25-30.