Knowledge transfer measurement methodology for Software Requirements, a case study

The purpose of this work is to present a proposal methodology for knowledge transfer measurement in software requirements. To obtain results, a methodology composed of four stages was defined: i) review of the knowledge transfer background in software engineering, in order to identify existing effor...

Full description

Autores:
Camacho Vargas, José Jairo
Tipo de recurso:
Fecha de publicación:
2015
Institución:
Universidad Nacional de Colombia
Repositorio:
Universidad Nacional de Colombia
Idioma:
spa
OAI Identifier:
oai:repositorio.unal.edu.co:unal/54019
Acceso en línea:
https://repositorio.unal.edu.co/handle/unal/54019
http://bdigital.unal.edu.co/48801/
Palabra clave:
0 Generalidades / Computer science, information and general works
62 Ingeniería y operaciones afines / Engineering
Knowledge management
Knowledge transfer
Software engineering
Software requirements
Software requirements metrics
Knowledge transfer measurement
Gestión de conocimiento
Transferencia de conocimiento
Ingeniería de software
Requisitos de software
Métricas de requisitos de software
Medición de transferencia de conocimiento
Rights
openAccess
License
Atribución-NoComercial 4.0 Internacional
Description
Summary:The purpose of this work is to present a proposal methodology for knowledge transfer measurement in software requirements. To obtain results, a methodology composed of four stages was defined: i) review of the knowledge transfer background in software engineering, in order to identify existing efforts in knowledge transfer measurement, ii) characterization of the software requirements process from the knowledge transfer point of view, thus, finding common factors regarding variables and indicators suitable for measuring purposes, iii) define a proposal methodology based on variables and indicators found, data gathering methods, statistical tools and helping documentation, iv) testing the proposal in order to provide feedback, using a case study. Principal results are: seven groups of factors mapping software requirements process stages against knowledge transfer steps, resulting in 115 indicators and 24 variables; 2 variables definition for knowledge transfer initialization stage and software requirements elicitation step mapping, which didn’t had any variable or indicator. Likewise, it was identified that exists a correlation between knowledge transfer and software requirements, the better knowledge transfer the better software requirements. Furthermore, the feed back gathered indicates that motivation variable defined is the more influential variable in the software requirements process according 41.67% of respondents, over other variables as: abstraction, methodology and time access availability, each one with 16.67% of respondents, and understandability with 8.33% of respondents. Last, this work allows analyzing the influence of knowledge transfer indicators in software requirements quality attributes.