As part of Requirements Engineering, “Elicitation” is the phase where an analyst collects informa... more As part of Requirements Engineering, “Elicitation” is the phase where an analyst collects information from the stakeholders, clarifies the problems and the needs of the customers and users, tries to find the best solutions, and makes its planning on what software system will be developed. During elicitation, to get well-defined requirements, a consensus among the different stakeholders is needed. There are several elicitation techniques in the literature; however every technique faces the same problem: each stakeholder has different requirements and priorities, which potentially produces conflicting situations. Therefore, this situation points out Requirements Prioritization as a relevant research area to define the requirements’ level of importance. Nevertheless, often the strategies implemented to solve conflicts among stakeholders are inadequate; for example, weighting requirements can be problematic because sometimes weights are inconsistent and lead to confusion about which are the most essential customer requirements. The prioritizing process must hold stakeholder satisfaction considering high-priority requirements first. However, practical experience shows that prioritizing requirements is not as straightforward task as the Literature suggests. In any case, clearly defining a way of balancing preferences on requirements is essential to the elicitation process. The remainder of this chapter is structured as follows. Section 2 describes a conceptual framework to describe several prioritization proposals, which are characterized in Section 3. Future trends are presented afterwards.
Prioritizing software requirements includes negotiation among people involved in the process as w... more Prioritizing software requirements includes negotiation among people involved in the process as well as an acceptance of the prioritization criteria. The analysis includes negotiation as an important issue, which becomes extremely difficult, as clients often do not know exactly what they need. To overcome this situation, aiming at improving stakeholder's negotiation, we propose reducing the gap of misunderstanding between them by the use of cognitive science. In this paper, we introduce a case study showing that cognitive profiles may affect requirement prioritization. A controlled experiment shows that elicitation techniques should be carefully selected according to cognitive skills to improve prioritization results.
El objetivo de los foros de discusión es el de compartir experiencias y soluciones a problemas de... more El objetivo de los foros de discusión es el de compartir experiencias y soluciones a problemas de tópicos diversos. También funcionan como una importante fuente de información a la hora de realizar consultas y búsquedas de problemas particulares. De esta manera, cuando un usuario tiene una dificultad, realiza una pregunta sobre su problema, que suele ser respondida por diferentes usuarios, quienes proponen diversas soluciones, todo ello realizado en forma asíncrona. Bajo este prisma, los foros de discusión técnicos actúan como plataformas colaborativas para compartir soluciones que luego pueden ser reutilizadas en situaciones similares por otras personas.
Resumen Si bien los foros de discusión son consultados asiduamente en la Web para resolver proble... more Resumen Si bien los foros de discusión son consultados asiduamente en la Web para resolver problemas, muchas veces la información contenida en ellos no está bien organizada o no es la adecuada en términos de solución, razón por la cual se vuelve indispensable poder definir algunos criterios de calidad de la información existente en dichos foros. La propuesta es utilizar los foros como sistemas de recupero de información (SRI), con capacidad para almacenar, mantener y recuperar información. La información resultante estará ordenada de acuerdo a alguna prioridad generada considerando varias caracteŕısticas de calidad. En esta propuesta se definen algunas métricas para medir la calidad de la información contenida en hilos de discusión técnicos, y se analizan las métricas propuestas para especificar un ranking en la información recuperada, se ejemplifica a través de un caso de estudio.
As part of Requirements Engineering, “Elicitation” is the phase where an analyst collects informa... more As part of Requirements Engineering, “Elicitation” is the phase where an analyst collects information from the stakeholders, clarifies the problems and the needs of the customers and users, tries to find the best solutions, and makes its planning on what software system will be developed. During elicitation, to get well-defined requirements, a consensus among the different stakeholders is needed. There are several elicitation techniques in the literature; however every technique faces the same problem: each stakeholder has different requirements and priorities, which potentially produces conflicting situations. Therefore, this situation points out Requirements Prioritization as a relevant research area to define the requirements’ level of importance. Nevertheless, often the strategies implemented to solve conflicts among stakeholders are inadequate; for example, weighting requirements can be problematic because sometimes weights are inconsistent and lead to confusion about which are the most essential customer requirements. The prioritizing process must hold stakeholder satisfaction considering high-priority requirements first. However, practical experience shows that prioritizing requirements is not as straightforward task as the Literature suggests. In any case, clearly defining a way of balancing preferences on requirements is essential to the elicitation process. The remainder of this chapter is structured as follows. Section 2 describes a conceptual framework to describe several prioritization proposals, which are characterized in Section 3. Future trends are presented afterwards.
Prioritizing software requirements includes negotiation among people involved in the process as w... more Prioritizing software requirements includes negotiation among people involved in the process as well as an acceptance of the prioritization criteria. The analysis includes negotiation as an important issue, which becomes extremely difficult, as clients often do not know exactly what they need. To overcome this situation, aiming at improving stakeholder's negotiation, we propose reducing the gap of misunderstanding between them by the use of cognitive science. In this paper, we introduce a case study showing that cognitive profiles may affect requirement prioritization. A controlled experiment shows that elicitation techniques should be carefully selected according to cognitive skills to improve prioritization results.
El objetivo de los foros de discusión es el de compartir experiencias y soluciones a problemas de... more El objetivo de los foros de discusión es el de compartir experiencias y soluciones a problemas de tópicos diversos. También funcionan como una importante fuente de información a la hora de realizar consultas y búsquedas de problemas particulares. De esta manera, cuando un usuario tiene una dificultad, realiza una pregunta sobre su problema, que suele ser respondida por diferentes usuarios, quienes proponen diversas soluciones, todo ello realizado en forma asíncrona. Bajo este prisma, los foros de discusión técnicos actúan como plataformas colaborativas para compartir soluciones que luego pueden ser reutilizadas en situaciones similares por otras personas.
Resumen Si bien los foros de discusión son consultados asiduamente en la Web para resolver proble... more Resumen Si bien los foros de discusión son consultados asiduamente en la Web para resolver problemas, muchas veces la información contenida en ellos no está bien organizada o no es la adecuada en términos de solución, razón por la cual se vuelve indispensable poder definir algunos criterios de calidad de la información existente en dichos foros. La propuesta es utilizar los foros como sistemas de recupero de información (SRI), con capacidad para almacenar, mantener y recuperar información. La información resultante estará ordenada de acuerdo a alguna prioridad generada considerando varias caracteŕısticas de calidad. En esta propuesta se definen algunas métricas para medir la calidad de la información contenida en hilos de discusión técnicos, y se analizan las métricas propuestas para especificar un ranking en la información recuperada, se ejemplifica a través de un caso de estudio.
Uploads