PRISE: A process to support iStar extensions

Abstract iStar is a goal-based requirement modelling language, being used both in industrial and academic projects of different domains. Often the language is extended to incorporate new constructs related to an application domain or to adjust it to practical situations during requirements modelling. These iStar extensions have been proposed in an ad hoc way resulting in many problems of incompleteness, inconsistency and conflicts. Recently, the language was standardised, but it continues being extended. Thus, we consider that this is an adequate moment to study how to support the proposals of the next iStar extensions. In this paper, we define PRISE, a process to support the creation of iStar extensions which is driven by model-based development concepts, reuse of existing iStar extensions and guidelines of experts. This process can be customised. We illustrate the usage of PRISE by recreating five existing iStar extensions. Finally, we evaluated PRISE with interviews and a survey with experts; and, we performed an interview to analyse the opinion about the usage of the PRISE to create a new iStar extension by a novice. The evaluation and validation indicate good results to avoid problems and increase the quality of the proposals and well receptivity by the experts and novice.

[1]  Stéphane Faulkner,et al.  An Exploratory Study of Topic Importance in Requirements Elicitation Interviews , 2014, CAiSE.

[2]  João Araújo,et al.  Towards Extension Mechanisms in iStar 2.0 , 2018, iSTAR@CAiSE.

[3]  Paul Ralph,et al.  Grounded Theory in Software Engineering Research: A Critical Review and Guidelines , 2016, 2016 IEEE/ACM 38th International Conference on Software Engineering (ICSE).

[4]  Márcia Lucena STREAM: a systematic process to derive architectural models from requirements models , 2010 .

[5]  John Mylopoulos,et al.  From object-oriented to goal-oriented requirements analysis , 1999, CACM.

[6]  Xavier Franch,et al.  iStar 2.0 Language Guide , 2016, ArXiv.

[7]  Fausto Giunchiglia,et al.  Tropos: An Agent-Oriented Software Development Methodology , 2004, Autonomous Agents and Multi-Agent Systems.

[8]  Sharan B. Merriam,et al.  Qualitative Research: A Guide to Design and Implementation , 2009 .

[9]  Anna Perini,et al.  Engineering requirements for adaptive systems , 2015, Requirements Engineering.

[10]  Anna Perini,et al.  Exploring the Effectiveness of Normative i* Modelling: Results from a Case Study on Food Chain Traceability , 2008, CAiSE.

[11]  Eric Yu,et al.  Modeling Strategic Relationships for Process Reengineering , 1995, Social Modeling for Requirements Engineering.

[12]  Richard F. Paige,et al.  A tutorial on metamodelling for grammar researchers , 2014, Sci. Comput. Program..

[13]  Haralambos Mouratidis,et al.  Model Based Process to Support Security and Privacy Requirements Engineering , 2012, Int. J. Secur. Softw. Eng..

[14]  Nicolas Mayer,et al.  Improving Risk-Based Security Analysis with /* , 2011, Social Modeling for Requirements Engineering.

[15]  Vic Chung Considering role-based conflicts of interest in analyzing and designing e-health systems with goal-oriented methodologies , 2006, PST.

[16]  John W. Creswell,et al.  A Concise Introduction to Mixed Methods Research , 2014 .

[17]  Eric S. K. Yu,et al.  A vulnerability-centric requirements engineering framework: analyzing security attacks, countermeasures, and requirements based on vulnerabilities , 2010, Requirements Engineering.

[18]  Mariela Inés Cortés,et al.  MAS-ML 2.0: Supporting the modelling of multi-agent systems with different agent architectures , 2015, J. Syst. Softw..

[19]  Daniel L. Moody,et al.  The “Physics” of Notations: Toward a Scientific Basis for Constructing Visual Notations in Software Engineering , 2009, IEEE Transactions on Software Engineering.

[20]  Miguel Goulão,et al.  How to reach a usable DSL? Moving toward a systematic evaluation , 2012 .

[21]  Claes Wohlin,et al.  Experimentation in Software Engineering , 2012, Springer Berlin Heidelberg.

[22]  Xavier Franch,et al.  A Metamodelling Approach for i* Model Translations , 2011, CAiSE.

[23]  John Mylopoulos,et al.  Goal-oriented requirements engineering: an extended systematic mapping study , 2017, Requirements Engineering.

[24]  Daniel Amyot,et al.  Legal goal-oriented requirement language (legal GRL) for modeling regulations , 2014, MiSE 2014.

[25]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[26]  David Garlan,et al.  Acme: an architecture description interchange language , 2010, CASCON.

[27]  Xavier Franch,et al.  On the joint use of i∗ with other modelling frameworks: A vision paper , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[28]  Jaelson Castro,et al.  Using empirical studies to mitigate symbol overload in iStar extensions , 2019, Software and Systems Modeling.

[29]  Munindar P. Singh,et al.  Xipho: extending tropos to engineer context-aware personal agents , 2014, AAMAS.

[30]  João Araújo,et al.  A Systematic Literature Review of iStar extensions , 2018, J. Syst. Softw..

[31]  Patrick Heymans,et al.  Visual notation design 2.0: Towards user comprehensible requirements engineering notations , 2013, 2013 21st IEEE International Requirements Engineering Conference (RE).

[32]  Natalia Juristo Juzgado,et al.  Basics of Software Engineering Experimentation , 2010, Springer US.

[33]  Jaelson Castro,et al.  CATIE: A Catalogue of iStar Extensions , 2018 .

[34]  José Miguel Morales,et al.  TRiStar: an i* extension for teleo-reactive systems requirements specifications , 2015, SAC.

[35]  Pär J. Ågerfalk,et al.  Ontological and linguistic metamodelling revisited: A language use approach , 2013, Inf. Softw. Technol..

[36]  Miguel Goulão,et al.  Addressing Symbol Redundancy Representations in iStar Extensions , 2019, iStar@ER.

[37]  B. Boehm Software risk management: principles and practices , 1991, IEEE Software.

[38]  Eric S. K. Yu,et al.  Reflective Analysis of the Syntax and Semantics of the i* Framework , 2008, ER Workshops.

[39]  Jéssyka Vilela,et al.  iStar4Safety: Uma Extensão de iStar para Modelagem de Requisitos de Segurança em Sistemas Críticos , 2019, WER.

[40]  Colin Atkinson,et al.  Model-Driven Development: A Metamodeling Foundation , 2003, IEEE Softw..

[41]  João Araújo,et al.  iStar4RationalAgents: Modeling Requirements of Multi-agent Systems with Rational Agents , 2019, ER.

[42]  Haralambos Mouratidis,et al.  A framework to support selection of cloud providers based on security and privacy requirements , 2013, J. Syst. Softw..

[43]  Paolo Giorgini,et al.  Goal-oriented requirement analysis for data warehouse design , 2005, DOLAP '05.

[44]  Peter Norvig,et al.  Artificial Intelligence: A Modern Approach , 1995 .

[45]  Pamela Zave Classification of research efforts in requirements engineering , 1997, ACM Comput. Surv..

[46]  Jaelson Brelaz de Castro,et al.  Systematic Integration Between Requirements and Architecture , 2004, SELMAS.

[47]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[48]  Haralambos Mouratidis,et al.  Secure Tropos: a Security-Oriented Extension of the Tropos Methodology , 2007, Int. J. Softw. Eng. Knowl. Eng..

[49]  Shari Lawrence Pfleeger,et al.  Principles of survey research: part 1: turning lemons into lemonade , 2001, SOEN.

[50]  Joaquín Pérez Ortega,et al.  A Methodology for Modeling Ambient Intelligence Applications using i* Framework , 2016, iStar.

[51]  Haralambos Mouratidis,et al.  Secure Tropos framework for software product lines requirements engineering , 2014, Comput. Stand. Interfaces.