iStar 2.0 Language Guide

iStar 2.0 Language Guide

Fabiano Dalpiaz Utrecht University, The Netherlands    Xavier Franch Universitat Politècnica de Catalunya, Spain    and Jennifer Horkoff City University London, United Kingdom
f.dalpiaz@uu.nl,franch@essi.upc.edu,horkoff@city.ac.uk
Endorsers: Okhaide Akhigbe, Fatma Başak Aydemir, Juan Pablo Carvallo, Jaelson Castro, Luiz Marcio Cysneiros, Sepideh Ghanavati, Alicia Grubb, Giancarlo Guizzardi, Renata Guizzardi, Matthias Jarke, Alexei Lapouchnian, Tong Li, Lin Liu, Lidia López, Alejandro Maté, John Mylopoulos, Soroosh Nalchigar, Elda Paja, Angelo Susi, Juan Carlos Trujillo Mondéjar, Eric Yu, Jelena Zdravkovic.
Abstract

The i* modeling language was introduced to fill the gap in the spectrum of conceptual modeling languages, focusing on the intentional (why?), social (who?), and strategic (how? how else?) dimensions. i* has been applied in many areas, e.g., healthcare, security analysis, eCommerce. Although i* has seen much academic application, the diversity of extensions and variations can make it difficult for novices to learn and use it in a consistent way. This document introduces the iStar 2.0 core language, evolving the basic concepts of i* into a consistent and clear set of core concepts, upon which to build future work and to base goal-oriented teaching materials. This document was built from a set of discussions and input from various members of the i* community. It is our intention to revisit, update and expand the document after collecting examples and concrete experiences with iStar 2.0.

Version History

Version Date Implemented Changes
3 June 17, 2016 New integrity rules: at most one actor link between a pair of actors; contribution and qualification cannot connect the same two elements.
2 June 3, 2016 Fixed typos in the original version
1 May 26, 2016 -
Comments 0
Request Comment
You are adding the first comment!
How to quickly get a good reply:
  • Give credit where it’s due by listing out the positive aspects of a paper before getting into which changes should be made.
  • Be specific in your critique, and provide supporting evidence with appropriate references to substantiate general statements.
  • Your comment should inspire ideas to flow and help the author improves the paper.

The better we are at sharing our knowledge with each other, the faster we move forward.
""
The feedback must be of minimum 40 characters and the title a minimum of 5 characters
   
Add comment
Cancel
Loading ...
242188
This is a comment super asjknd jkasnjk adsnkj
Upvote
Downvote
""
The feedback must be of minumum 40 characters
The feedback must be of minumum 40 characters
Submit
Cancel

You are asking your first question!
How to quickly get a good answer:
  • Keep your question short and to the point
  • Check for grammar or spelling errors.
  • Phrase it like a question
Test
Test description