iStarML: principles and implications

iStarML is an XML-based format for enabling i* interoperability. A relevant difference with any other interoperability proposal is that iStarML is founded under the assumption that there is not a common ontology guiding this communication proposal. The different i* variants and even particular applications proposing new language constructors forced to confront a theoretical approach for supporting an interoperability approach in an evolving and variable semantic scenario. In this paper we focused on the theories behind the iStarML proposal, which include sociological, cybernetics and linguistics approaches. Finally, we apply what these theories predict to the case of the i* framework and its research community.Peer ReviewedPostprint (published version

A metamodelling approach for i* model translations

The i* (i-star) framework has been widely adopted by the information systems community. Since the time it was proposed, different variations have arisen. Some of them just propose slight changes in the language definition, whilst others introduce constructs for particular usages. This flexibility is one of the reasons that makes i* attractive, but it has as counterpart the impossibility of automatically porting i* models from one context of use to another. This lack of interoperability makes difficult to build a repository of models, to adopt directly techniques defined for one variation, or to use i* tools in a feature-oriented instead of a variant-oriented way. In this paper, we explore in more detail the interoperability problem from a metamodel perspective. We analyse the state of the art concerning variations of the i* language, from these variations and following a proposal from Wachsmuth, we define a supermetamodel hosting identified variations, general enough so as to embrace others yet to exist. We present a translation algorithm oriented to semantic preservation and we use the XML-based iStarML interchange format to illustrate the interconnection of two tools.Peer ReviewedPostprint (author's final draft

Perspectives about paradigms in software engineering

There is a broad use of the term “paradigm” in Software Engineer-ing. Concepts such as structured paradigm, cascade paradigm or agent-oriented paradigm are very frequent in software engineering research proposals. In this essay we distinguish between functional and scientific paradigm and we show that the common use of paradigm in Software Engineering is about the func-tional or engineering paradigm rather than scientific paradigm. We distinguish among four possible perspectives and, in this context, we sustain that the scien-tific perspective is intrinsic and hence very difficult to properly identify and de-scribe. We argue that a discussion about the scientific paradigm in Software Engineering could help us to evaluate and improve the research practice in the discipline.Peer ReviewedPostprint (published version

Definition and uses of the i* metamodel

The clear definition of a metamodel can be considered helpful for any conceptual modeling approach, and the i* framework is not an exception. Agreeing on a metamodel for i* can be considered even more convenient than ever when we are aware of the different dialects and variations that the commu-nity proposed, and keep proposing, over the seminal i* definition. In this paper we present the revised version of the i* metamodel proposed by the GESSI re-search group at 2005 and we report some current contexts of use: 1) definition of a data interchange format; 2) definition of the inheritance construct; 3) defi-nition of a modularity construct; and 4) definition of a metrics framework.Peer ReviewedPostprint (published version

Goal-driven agent-oriented software processes

The quality of software processes is acknowledged as a critical factor for delivering quality software systems. Any initiative for improving the quality of software processes requires their explicit representation and management. A current representational metaphor for systems is agent orientation, which has become one of the recently recognized engineering paradigms. In this article, we argue for the convenience of representing the software process using an agent-oriented language to model it and a goal-driven procedure to design it. Particularly we propose using the i* framework which is both an agent- and a goal-oriented modeling language. We review the possibilities of i* as a software process modeling language, and we also show how success factors can be made explicit in i* representations of the software processes. Finally, we illustrate the approach with an example based on the development of a set of ergonomic and safety software tools.Peer ReviewedPostprint (published version

MASISCo—Methodological Approach for the Selection of Information Security Controls

As cyber-attacks grow worldwide, companies have begun to realize the importance of being protected against malicious actions that seek to violate their systems and access their information assets. Faced with this scenario, organizations must carry out correct and efficient management of their information security, which implies that they must adopt a proactive attitude, implementing standards that allow them to reduce the risk of computer attacks. Unfortunately, the problem is not only implementing a standard but also determining the best way to do it, defining an implementation path that considers the particular objectives and conditions of the organization and its availability of resources. This paper proposes a methodological approach for selecting and planning security controls, standardizing and systematizing the process by modeling the situation (objectives and constraints), and applying optimization techniques. The work presents an evaluation of the proposal through a methodology adoption study. This study showed a tendency of the study subjects to adopt the proposal, perceiving it as a helpful element that adapts to their way of working. The main weakness of the proposal was centered on ease of use since the modeling and resolution of the problem require advanced knowledge of optimization techniques.This research was funded by Universidad de La Frontera, research direction, research project DIUFRO DI22-0043

Tool interoperability using iStarML

iStarML is an XML-based format for enabling interoperability among i* tools. Its main design focus was to support data interchange even when involved tools implement different i* variants. In this paper, we present a summary of the format, we briefly describe the ccistarml Java library, and we show an application of it. We finally summarize the requirements for representing new i* concepts in order to generate a revised version of iStarML.Postprint (published version

Análisis comparativo de lenguajes de modelado orientados a objetivos basados en i*

Los modelos orientados a objetivos son usados frecuentemente en disciplinas tales como la ingeniería de requisitos o el modelado de procesos en organizaciones. i* es una de las notaciones más empleadas para construir este tipo de modelos. Desafortunadamente, no existe una definición única de i* sino diferentes versiones y variantes que, con frecuencia, no están totalmente definidas dificultando su comprensión y utilización. En este artículo, se presenta un estudio comparativo de las tres variantes más utilizadas de i*: la propuesta original de Eric Yu, el lenguaje GRL y el lenguaje utilizado en el método TROPOS. A continuación, se formula un modelo conceptual genérico como marco de referencia de las variantes estudiadas, se muestra cómo a partir de este modelo genérico pueden generarse los modelos específicos de cada una, y se evidencia que también puede usarse para clasificar algunas variantes puntuales que encontramos en la literatura.Peer ReviewedPostprint (author's final draft

From the i* diversity to a common interoperability framework

Since the i* framework emerged in the requirements engineering community in the mid-90s, different research groups have proposed variations to the modelling language proposed in the i* framework (¿the i* language¿). There are basically two reasons behind this fact: ¿ The definition of the i* language is loose in some parts, and some groups have opted by different solutions or proposed slight changes to the original definition. ¿ Some groups have used the i* framework with very different purposes, thus different concepts have become necessary, many of them have added their own modelling constructs. As a consequence, several i* variations at different maturity levels have been produced. The adaptability of i* to different needs is part of its own nature, therefore these variations are not to be considered pernicious, on the contrary, flexibility may be considered one of the framework¿s key success features. In this context, the objective of this thesis is to tackle the i* Interoperability Problem: to propose a framework to understand the variations of the i* modelling language and, considering this framework, to generate a proposal to support the interoperability and integration of these variations. To do so, the PhD thesis has identified and solved up to ten research questions related to the following categories: 1) The i* variants have been identified and characterized. Metamodels have been used to align these variants and identify an appropriate kernel. A critical look on the ¿why¿ this happened has been conducted from several perspectives. 2) An interoperability framework in terms of metamodel alignment has been formulated. This interoperability framework has come from the adaptation of a solution to metamodel evolution and model co-adaptation formulated in the domain of model-driven engineering. 3) An XML-based interoperability format implementing the framework, iStarML, has been deployed. 4) The solution has been validated in terms of community acceptance by means of an empirical study, and from a practical point of view by the interconnection of different existing tools. The set of related publications shows the research path, starting from the identification and characterization of the interoperability problem, pass trhought a theoretical explanation that sustaints a technical proposal, and ends illustrating inteoperation cases and its community acceptation

iStarML: principles and implications

iStarML is an XML-based format for enabling i* interoperability. A relevant difference with any other interoperability proposal is that iStarML is founded under the assumption that there is not a common ontology guiding this communication proposal. The different i* variants and even particular applications proposing new language constructors forced to confront a theoretical approach for supporting an interoperability approach in an evolving and variable semantic scenario. In this paper we focused on the theories behind the iStarML proposal, which include sociological, cybernetics and linguistics approaches. Finally, we apply what these theories predict to the case of the i* framework and its research community.Peer Reviewe