TOWARDS ADVANCED GOAL MODEL ANALYSIS WITH JUCMNAV Daniel Amyot, Azalia Shamsaei, Jason Kealey, Etienne Tremblay, Andrew Miga, Gunter Mussbacher, and Mohammad Alhaj, Rasha Tawhid, Edna Braun, and Nick Cartwright 1

Introduction  Goal modeling is an important part of various types of activities  Requirements engineering, business management, and compliance assessment  Capture stakeholder and business objectives  Positive/negative impacts on various quality aspects  Guides the decision-making process 2

URN (User Requirements Notation )  Is an international standard (ITU-T)  Combines and integrates  Goal modeling (with GRL), and  Scenario/process modeling (with UCM)  URN models are graphical  Created, managed and analyzed with jUCMNav, a free, Eclipse-based open source tool 3

GRL in a Nutshell  Goal-oriented Requirement Language  Rooted in i* and the NFR Framework  Actors, intentional elements, and their links  Connects requirements to business objectives  Interesting features  Qualitative, quantitative, and hybrid evaluations  Strategy definitions  Extensibility (metadata, URN links, groupings…)  Integration with a scenario/process view  Indicators (real-world values  GRL satisfaction values)

GRL in jUCMNav 5

GRL Strategy 6

Our Objective 7  Recent applications of GRL to a regulatory context highlighted several analysis issues  Investigated issues related to the computation of  Strategy and model differences  Management of complexity and uncertainty  Sensitivity analysis  Various domain-specific considerations during analysis  Solutions proposed and implemented in jUCMNav

Limitation 1: Strategy Differences 8  Problem:  Many strategies are defined for a model to explore different global alternatives  Tradeoffs in a decision support context, to represent as-is and to-be contexts  Highlight differences within the graphical model to provide more immediate feedback  Solution  Compare strategies and visualize this comparison  Comparison is computed between a base strategy and a current strategy on a per element basis

(a) Base Strategy (b) New Strategy (c) Difference: New Strategy – Base Strategy Strategy Differences Color feedback! (in a [-200, 200] scale) Actor feedback (got worse by 30) Goal feedback (got better by 200)

Limitation 2: Model Evolution 10  Problem:  How can we highlight, understand, and control model evolution Solution (with EMF Compare)

Limitation 3: Complexity / Uncertainty Management 11  Problem:  How should we manage large collections of strategies?  How can we handle different contributions? Either because we are not sure of the right contribution level Or because some contributions are “secret”  Solution:  A parent-child inclusion relationship between strategies  Contribution contexts that can override some contributions  Contribution contexts can also include other contexts

Limitation 4: Sensitivity Analysis 12  Problem:  How localized changes to a satisfaction/contribution level impact other high-level goals?  Solution:  Support ranges of values for strategy evaluations and for contribution changes in GRL strategies  Sensitivity analysis in jUCMNav is currently limited to one dimension only From strategy definition

Limitation 5: Domain Considerations During Analysis 13  Problem:  The standard GRL satisfaction range ([– ]) is really counter-intuitive to many people  A goal with a negative satisfaction and a negative contribution to another intentional element leads to a positive evaluation value for that element  Solution:  New [0..100] scale for satisfaction Still allows [ for contributions]  Color feedback updated (0 is red, as opposed to -100)

Limitation 6: Support Models in Multiple Languages 14  Problem:  Can we support models in multiple languages without having different models, to avoid maintenance issues?  Solution:  The modeler can switch between model languages and provide alternative names and descriptions for model elements Note the [0..100] range used For satisfaction values here! En français svp!

Limitation 7: Handle Strategies Separately from Model 15  Problem:  Store strategies independently from models  Not having sufficient privileges to access strategies used to evaluate the model  Solution  Import/export of strategies as CSV files  Split strategy definitions from the model

Conclusion and Future Work 16  Presented many concrete issues with the applicability of goal modeling (GRL/jUCMNav)  Implemented a collection of advanced analysis and management features  Usefulness and validity of these new features requires further experiment (other domains)  Some of the language extensions become part of a future release of URN  Strategy inclusion, contribution contexts, and indicators standardized by ITU-T (verdict in mid-October 2012!)

Thank You! 17  Many more jUCMNav goodies at ! Azalia Shamsaei