Silvia Abrahão
Emilio Insfran
ABSTRACT
Context. Several early requirements approaches focus on modeling objectives, interest or benefits of related stakeholders. However, as they can be used for different purposes as identifying problems, exploring system solutions, evaluating alternatives, etc., there are no clear guidelines on how to build these models, which constructs of the language must be used in each case, and most importantly, how to use these models downstream to the software requirements and design artifacts. Background. In a previous work, we proposed a specialization of the GRL language (value@GRL) to specify stakeholders' goals when dealing with early requirements in the context of incremental software development. Goal/Method. This paper reports on a controlled experiment aimed at comparing the goal model quality and the productivity, perceived ease of use, and perceived usefulness of participants when using value@GRL and i* languages. Results. The results showed that value@GRL obtained better results than i* as a goal modeling language indicating that it can be considered as a promising emerging approach in this area. Conclusions. Value@GRL allows obtaining goal models with good quality that may be later used downstream software development activities.
- J. Cohen, Statistical Power Analysis for the Behavioral Sciences 2nd edn, Elsevier, 1988.Google Scholar
- F. D. Davis, Perceived usefulness, perceived ease of use, and user acceptance of information technology, MIS quarterly 13(3), 1989. Google ScholarDigital Library
- H. Estrada, K. Najera, B. Vázquez, A. Martínez, J. C. Téllez, J. J. Hierro, Applying Tropos Modeling for Smart Mobility App Based on the FIWARE Platform, iStar Workshop, 2016, pp. 85--90.Google Scholar
- W. B. Frakes, R. Baeza-Yates, Information Retrieval: Data Structures & Algorithms, Prentice-Hall, Inc., 1992. Google ScholarDigital Library
- J. Horkoff, T. Li, F. L. Li, M. Salnitri, E. Cardoso, P. Giorgini, J. Mylopoulos, Using goal models downstream: A systematic roadmap and literature review. IJISMD 6(2), 1--42, 2015.Google Scholar
- E. Insfran, S. Abrahão, R.P. Oliveira, F. González, M. Fernández, C. Cano, Specifying Value in GRL for Guiding BPMN Activities Prioritization, 26<sup>th</sup> Int. Conf. on Information Systems Development (ISD), Larnaca, Cyprus, 2017.Google Scholar
- ITU-T. Recommendation Z.151 (09/08): User Requirements Notation (URN)-Language definition, 2008. 206 p.Google Scholar
- K. Maxwell, Applied Statistics for Software Managers, Software Quality Institute Series, Prentice Hall, 2002.Google Scholar
- M. Serrano, J. C. S. do Prado Leite, Development of Agent-Driven Systems: from i* Architectural Models to Intentional Agents Code, iStar Workshop 2011, pp. 55--60.Google Scholar
- E. Yu, Towards Modelling and Reasoning Support for Early-phase Requirements Engineering, RE conference, 1997, pp. 226--235. Google ScholarDigital Library
Index Terms
- Comparing the effectiveness of goal-oriented languages: results from a controlled experiment
Recommendations
Assessing the effectiveness of goal-oriented modeling languages: A family of experiments
Abstract ContextSeveral goal-oriented languages focus on modeling stakeholders’ objectives, interests or wishes. However, these languages can be used for various purposes (e.g., exploring system solutions or evaluating alternatives),...
Towards extending the goal-oriented requirements language with emotion-oriented goals to support socio-technical systems
MODELS '22: Proceedings of the 25th International Conference on Model Driven Engineering Languages and Systems: Companion ProceedingsRequirements engineers focus mostly on gathering and modeling functional and quality (i.e., non-functional) requirements, with a marginal consideration of emotion-oriented requirements, which describe how stakeholders already feel, or would like to feel,...
Specifying privacy requirements with goal-oriented modeling languages
SBES '18: Proceedings of the XXXII Brazilian Symposium on Software EngineeringContext: Privacy of personal data is a growing concern regarding users of software systems. In this sense, the literature reports that in order to avoid privacy breaches, there must be systematic approaches to specify privacy requirements from the early ...
Comments