Xavier Franch Universitat Politècnica de Catalunya Barcelona, Spain e-mail: franch@essi.upc.edu Lidia López Universitat Politècnica de Catalunya Barcelona, Spain e-mail: llopez@essi.upc.edu Carlos Cares Universidad de la Frontera Temuco, Chile e-mail: carlos.cares@ceisufro.cl Daniel Colomer Universitat Politècnica de Catalunya Barcelona, Spain e-mail: dncolomer32@gmail.com The i* Framework for Goal-Oriented Modeling Xavier Franch, Lidia López, Carlos Cares, Daniel Colomer Abstract i* is a widespread framework in the software engineering field that sup- ports goal-oriented modeling of socio-technical systems and organizations. At its heart lies a language offering concepts such as actor, dependency, goal and decom- position. i* models resemble a network of interconnected, autonomous, collabora- tive and dependable strategic actors. Around this language, several analysis tech- niques have emerged, e.g. goal satisfaction analysis and metrics computation. In this work, we present a consolidated version of the i* language based on the most adopted versions of the language. We define the main constructs of the language and we articulate them in the form of a metamodel. Then, we implement this version and a concrete technique, goal satisfaction analysis based on goal propagation, us- ing ADOxx. Throughout the chapter, we used an example based on open source software adoption to illustrate the concepts and test the implementation. 1. Introduction Goal-oriented methods are well-known in the software engineering field since the early nineties. They are used both in broad areas as requirements engineering (van Lamsweerde 2001) and organizational modelling (Kavakli 2004), and in more spe- cific scopes as adaptive system modelling (Bencomo and Belaggoun 2013) and soft- ware architecture representation (Grau and Franch 2007). For instance, if we consider goal-oriented requirements engineering, it is recog- nized that goals play a crucial role for domain understanding and elicitation of stake- holders’ intentions (Mylopoulos et al 1999). Goals can be formulated at different levels of abstraction, from strategic concerns to technical issues, and are less volatile than requirements (van Lamsweerde 2001). Therefore, they can be considered as an essential artefact in the early phases of requirements engineering, when still alter- natives are considered and stakeholder intentions do need further discussion. Goal- oriented methods allow analyzing consequences of decisions, making interrogative questions and explore solution spaces.