An empirical evaluation of requirement engineering techniques for collaborative systems

Abstract

A collaborative system is a distributed software which allows several users to work together and carry out collaboration, communication and coordination tasks. To actions, usually by means of a set of awareness techniques. When we are defining a collaborative system, the awareness techniques can be considered as non-functional requirements bounded to some quality factors, such as usability. However, serious flaws can be found during the specification of these systems if we use the usual Requirement Engineering techniques available, because their expressiveness limitations when dealing with non-functional requirements. In this paper an empirical evaluation is introduced to determine if these techniques are really appropriate to model groupware requirements and which is the best approach to specify this kind of systems. With this aim, a collaborative text editor is used to evaluate whether the current techniques for Requirement Engineering are appropriated or not, exploiting the relation between awareness capabilities and standard quality factors.

Improving collaborative and Post-WIMP systems through requirements specification

“…With this aim, Use Cases [19], Viewpoints [8] and GO [21] were empirically evaluated, concluding that GO approaches were the most adequate to specify CSCW requirements [41]. This results led us to analyze the most widely adopted GO proposals, NFR Framework [3], KAOS [21], i* [56], in order to identify which one was the most suitable for CSCW systems.…”

Towards a new requirements’ definition methodology using ontologies for Pervasive Games Based Learning Systems

“…al. [20] studied the applicability of three Requirement Engineering (RE) techniques (Use Cases [21], Viewpoints [22], and GoalOriented [23]) for the specification of collaborative systems and paying special attention to the awareness requirements. In order to carry out their study, they specify some awareness requirements of a real system (Google Docs) [24].…”

Evaluating the use of Pareto Efficiency to Optimize Non-Functional Requirements Satisfaction in i* Modeling

“…En lo que respecta a la ingeniería de requisitos orientada a objetivos (goal-oriented requirements engineering), existen algunos trabajos que resaltan la importancia de la evaluación de este tipo de enfoques, Al Subaie y Maibaum [23] presentan una evaluación cualitativa del método KAOS y su respectiva herramienta Objectiver, este tipo de evaluación es subjetiva debido a que la información cualitativa de KAOS y Objectiver se basa en las observaciones de los evaluadores, usaron KAOS y Objectiver para abordar un problema objetivo para obtener informes y observaciones con el fin de evaluar la pertinencia, la exactitud, la trazabilidad y la comprensibilidad del enfoque. En cambio, en Teruel et al [24] estudiaron la aplicabilidad de tres técnicas utilizadas en la ingeniería de requisitos (casos de uso, orientados a objetivos y viewpoints) para especificar sistemas colaborativos, realizaron un análisis empírico para comparar las técnicas por medio de una variación del método DESMET [25], utilizado para evaluar métodos y herramientas en ingeniería de software. En Morandini et al [26] se presentó un informe sobre la evaluación empírica de Tropos4AS (Tropos para Sistemas Adaptativos) sobre la eficacia de los modelos de Tropos4AS, en dos experimentos los participantes que tuvieron que realizar varias tareas y dar sus opiniones personales.…”