Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework

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...

Full description

Autores:: Buitrón Ruiz, Sandra Lorena
Flores Rios, Brenda Leticia
Pino Correa, Francisco Jose

Tipo de recurso:: Article of journal

Fecha de publicación:: 2018

Institución:: Universidad de Medellín

Repositorio:: Repositorio UDEM

Idioma:: spa

id	REPOUDEM2_01fcc0e56f84b765854cbb0406f63c1e
oai_identifier_str	oai:repository.udem.edu.co:11407/5502
network_acronym_str	REPOUDEM2
network_name_str	Repositorio UDEM
repository_id_str
dc.title.eng.fl_str_mv	Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework
dc.title.por.fl_str_mv	Elicitação de requisitos não funcionais baseada na gestão de conhecimento: o referencial de trabalho Merlinn
dc.title.spa.fl_str_mv	Elicitación de requisitos no funcionales basada en la gestión de conocimiento: el marco de trabajo Merlinn
title	Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework
spellingShingle	Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework Requirements engineering Requirements tendering Knowled-ge management Non-functional requirements Case study Engenharia de requisitos Elicitação de requisitos Gestão de conhecimento Requisitos não funcionais Estudo de caso Ingeniería de requisitos Elicitación de requisitos Gestión de conocimiento Requisitos no funcionales Estudio de caso
title_short	Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework
title_full	Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework
title_fullStr	Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework
title_full_unstemmed	Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework
title_sort	Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework
dc.creator.fl_str_mv	Buitrón Ruiz, Sandra Lorena Flores Rios, Brenda Leticia Pino Correa, Francisco Jose
dc.contributor.author.none.fl_str_mv	Buitrón Ruiz, Sandra Lorena Flores Rios, Brenda Leticia Pino Correa, Francisco Jose
dc.subject.eng.fl_str_mv	Requirements engineering Requirements tendering Knowled-ge management Non-functional requirements Case study
topic	Requirements engineering Requirements tendering Knowled-ge management Non-functional requirements Case study Engenharia de requisitos Elicitação de requisitos Gestão de conhecimento Requisitos não funcionais Estudo de caso Ingeniería de requisitos Elicitación de requisitos Gestión de conocimiento Requisitos no funcionales Estudio de caso
dc.subject.por.fl_str_mv	Engenharia de requisitos Elicitação de requisitos Gestão de conhecimento Requisitos não funcionais Estudo de caso
dc.subject.spa.fl_str_mv	Ingeniería de requisitos Elicitación de requisitos Gestión de conocimiento Requisitos no funcionales Estudio de caso
description	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.
publishDate	2018
dc.date.created.none.fl_str_mv	2018-07-04
dc.date.accessioned.none.fl_str_mv	2019-11-07T15:00:32Z
dc.date.available.none.fl_str_mv	2019-11-07T15:00:32Z
dc.type.eng.fl_str_mv	Article
dc.type.coar.fl_str_mv	http://purl.org/coar/resource_type/c_2df8fbb1
dc.type.coarversion.fl_str_mv	http://purl.org/coar/version/c_970fb48d4fbd8a85
dc.type.coar.none.fl_str_mv	http://purl.org/coar/resource_type/c_6501
dc.type.local.spa.fl_str_mv	Artículo científico
dc.type.driver.none.fl_str_mv	info:eu-repo/semantics/article
format	http://purl.org/coar/resource_type/c_6501
dc.identifier.issn.none.fl_str_mv	1692-3324
dc.identifier.uri.none.fl_str_mv	http://hdl.handle.net/11407/5502
dc.identifier.doi.none.fl_str_mv	https://doi.org/10.22395/rium.v17n32a8
dc.identifier.eissn.none.fl_str_mv	2248-4094
dc.identifier.reponame.spa.fl_str_mv	reponame:Repositorio Institucional Universidad de Medellín
dc.identifier.repourl.none.fl_str_mv	repourl:https://repository.udem.edu.co/
dc.identifier.instname.spa.fl_str_mv	instname:Universidad de Medellín
identifier_str_mv	1692-3324 2248-4094 reponame:Repositorio Institucional Universidad de Medellín repourl:https://repository.udem.edu.co/ instname:Universidad de Medellín
url	http://hdl.handle.net/11407/5502 https://doi.org/10.22395/rium.v17n32a8
dc.language.iso.none.fl_str_mv	spa
language	spa
dc.relation.uri.none.fl_str_mv	https://revistas.udem.edu.co/index.php/ingenierias/article/view/2068
dc.relation.citationvolume.none.fl_str_mv	17
dc.relation.citationissue.none.fl_str_mv	32
dc.relation.citationstartpage.none.fl_str_mv	155
dc.relation.citationendpage.none.fl_str_mv	182
dc.relation.references.spa.fl_str_mv	[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.
dc.relation.ispartofjournal.spa.fl_str_mv	Revista Ingenierías Universidad de Medellín
dc.rights.coar.fl_str_mv	http://purl.org/coar/access_right/c_abf2
dc.rights.uri.*.fl_str_mv	http://creativecommons.org/licenses/by-nc-sa/4.0/
dc.rights.creativecommons.*.fl_str_mv	Attribution-NonCommercial-ShareAlike 4.0 International
rights_invalid_str_mv	http://creativecommons.org/licenses/by-nc-sa/4.0/ Attribution-NonCommercial-ShareAlike 4.0 International http://purl.org/coar/access_right/c_abf2
dc.format.extent.spa.fl_str_mv	p. 155-182
dc.format.medium.spa.fl_str_mv	Electrónico
dc.format.mimetype.none.fl_str_mv	application/pdf
dc.coverage.none.fl_str_mv	Lat: 06 15 00 N degrees minutes Lat: 6.2500 decimal degreesLong: 075 36 00 W degrees minutes Long: -75.6000 decimal degrees
dc.publisher.spa.fl_str_mv	Universidad de Medellín
dc.publisher.faculty.spa.fl_str_mv	Facultad de Ingenierías
dc.publisher.place.spa.fl_str_mv	Medellín
dc.source.spa.fl_str_mv	Revista Ingenierías Universidad de Medellín; Vol. 17 Núm. 32 (2018): Enero-Junio; 155-182
institution	Universidad de Medellín
repository.name.fl_str_mv	Repositorio Institucional Universidad de Medellin
repository.mail.fl_str_mv	repositorio@udem.edu.co
_version_	1814159169391951872
spelling	Buitrón Ruiz, Sandra LorenaFlores Rios, Brenda LeticiaPino Correa, Francisco JoseBuitrón Ruiz, Sandra Lorena; Universidad del Cauca Grupo IDISFlores Rios, Brenda Leticia; Universidad Autónoma de Baja CaliforniaPino Correa, Francisco Jose; Universidad del Cauca Grupo IDIS2019-11-07T15:00:32Z2019-11-07T15:00:32Z2018-07-041692-3324http://hdl.handle.net/11407/5502https://doi.org/10.22395/rium.v17n32a82248-4094reponame:Repositorio Institucional Universidad de Medellínrepourl:https://repository.udem.edu.co/instname:Universidad de MedellínRequirements 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.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.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.p. 155-182Electrónicoapplication/pdfspaUniversidad de MedellínFacultad de IngenieríasMedellínhttps://revistas.udem.edu.co/index.php/ingenierias/article/view/20681732155182[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.Revista Ingenierías Universidad de Medellínhttp://creativecommons.org/licenses/by-nc-sa/4.0/Attribution-NonCommercial-ShareAlike 4.0 Internationalhttp://purl.org/coar/access_right/c_abf2Revista Ingenierías Universidad de Medellín; Vol. 17 Núm. 32 (2018): Enero-Junio; 155-182Requirements engineeringRequirements tenderingKnowled-ge managementNon-functional requirementsCase studyEngenharia de requisitosElicitação de requisitosGestão de conhecimentoRequisitos não funcionaisEstudo de casoIngeniería de requisitosElicitación de requisitosGestión de conocimientoRequisitos no funcionalesEstudio de casoNon-Functional Requirements Tendering Based on Knowledge Management: the Merlinn FrameworkElicitação de requisitos não funcionais baseada na gestão de conhecimento: o referencial de trabalho MerlinnElicitación de requisitos no funcionales basada en la gestión de conocimiento: el marco de trabajo MerlinnArticlehttp://purl.org/coar/resource_type/c_6501http://purl.org/coar/resource_type/c_2df8fbb1Artículo científicoinfo:eu-repo/semantics/articlehttp://purl.org/coar/version/c_970fb48d4fbd8a85Comunidad Universidad de MedellínLat: 06 15 00 N degrees minutes Lat: 6.2500 decimal degreesLong: 075 36 00 W degrees minutes Long: -75.6000 decimal degrees11407/5502oai:repository.udem.edu.co:11407/55022021-05-14 14:29:37.139Repositorio Institucional Universidad de Medellinrepositorio@udem.edu.co

Non-Functional Requirements Tendering Based on Knowledge Management: the Merlinn Framework

Publicaciones similares