R EFLECTIVE A NALYSIS OF THE S YNTAX AND S EMANTICS OF THE i* F RAMEWORK Jennifer Horkoff, Golnaz Elahi, Samer Abdulhadi, Eric Yu Department of Computer.

Slides:



Advertisements
Similar presentations
1 © 2006 Curriculum K-12 Directorate, NSW Department of Education and Training Implementing English K-6 Using the syllabus for consistency of teacher judgement.
Advertisements

The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
Project Proposal.
Chapters 7 & 9 System Scope
Soft Systems Methodology
1 Ch. 3: Interaction Introduction – 3.1 (Reading Assignment – RA) Introduction – 3.1 (Reading Assignment – RA) Models – 3.2, 3.3 (RA) Models – 3.2, 3.3.
Classification of Business Documents DITA BusDocs Subcommittee Meeting 21 January 2008 Presentation with Notes from the Focus Group Meeting of 14 Jan 2008.
S OCIAL S CIENCE R ESEARCH HPD 4C W ORKING WITH S CHOOL – A GE C HILDREN AND A DOLESCENTS M RS. F ILINOV.
OASIS Reference Model for Service Oriented Architecture 1.0
Using the ICF as a Framework for Washington Group Measures Barbara M. Altman Jennifer Madans Elizabeth Rasch National Center for Health Statistics.
Use-case Modeling.
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering Vahid Jalali Amirkabir university of technology, Department of computer.
Pittsburgh, PA Copyright 2004, Carnegie Mellon University. All rights reserved. Concepts for Writing Effective Process Guidance Suzanne Garcia.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Goal.
End-to-End Design of Embedded Real-Time Systems Kang G. Shin Real-Time Computing Laboratory EECS Department The University of Michigan Ann Arbor, MI
ECE122 L17: Method Development and Testing April 5, 2007 ECE 122 Engineering Problem Solving with Java Lecture 17 Method Development and Testing.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Interdisciplinary role of English in the field of medicine: integrating content and context Nataša Milosavljević, Zorica Antić University of Niš, Faculty.
The chapter will address the following questions:
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
USE Case Model.
Dr. MaLinda Hill Advanced English C1-A Designing Essays, Research Papers, Business Reports and Reflective Statements.
Jeanne M. Clerc, Ed.D. Western Illinois University (WIU) October 14, 2011.
Arunee Wiriyachitra, Chiang Mai University
Evaluating Goal Achievement in Enterprise Modeling – An Interactive Procedure and Experiences Jennifer Horkoff 1 Eric Yu 2 1 Department of Computer Science,
Systems Analysis and Design in a Changing World, Fifth Edition
Helping Your Department Advance and Implement Effective Assessment Plans Presented by: Karen Froslid Jones Director, Institutional Research.
SWE 316: Software Design and Architecture – Dr. Khalid Aljasser Objectives Lecture 11 : Frameworks SWE 316: Software Design and Architecture  To understand.
Visualizations to Support Interactive Goal Model Analysis Jennifer Horkoff 1 Eric Yu 2 Department of Computer Science 1 Faculty of Information 2
Understanding User Requirements. Documenting Use Cases 2 At this stage of the exploration, the participants should be thinking of essential use cases.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Planning and Integrating Curriculum: Unit 4, Key Topic 1http://facultyinitiative.wested.org/1.
Project Based Learning - An Emergent Framework for Designing Courses Ulf Melin, Karin Axelsson and Tommy Wedlund Information Systems and Management, Department.
1 A Conceptual Framework of Data Mining Y.Y. Yao Department of Computer Science, University of Regina Regina, Sask., Canada S4S 0A2
RHS 303. TRANSITION OF THEORY AND TREATMENT nature of existence and gives meaning to and guides the action Philosophical Base: Philosophy of occupational.
Illustrations and Answers for TDT4252 exam, June
Information Security - City College1 Access Control in Collaborative Systems Authors: Emis Simo David Naco.
Morten Blomhøj and Paola Valero Our agenda: 1.The journal NOMAD’s mission, review policy and process 2.Two reviews of a paper 3.Frequent comments in reviews.
A Lightweight GRL Profile for i* Modeling Presenter: Alexei Lapouchnian Daniel Amyot, Jennifer Horkoff, Daniel Gross, and Gunter Mussbacher {damyot,
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Qualitative Research January 19, Selecting A Topic Trying to be original while balancing need to be realistic—so you can master a reasonable amount.
A Goal Based Methodology for Developing Domain-Specific Ontological Frameworks Faezeh Ensan, Weichang Du Faculty of Computer Science, University of New.
Using Meta-Model-Driven Views to Address Scalability in i* Models Jane You Department of Computer Science University of Toronto.
Dr. Bea Bourne 1. 2 If you have any troubles in seminar, please do call Tech Support at: They can assist if you get “bumped” from the seminar.
Finding Solutions in Goal Models: An Interactive Backward Reasoning Approach Jennifer Horkoff 1 Eric Yu 2 Department of Computer Science 1 Faculty of Information.
Human Computer Interaction
Interactive Goal Model Analysis Applied - Systematic Procedures versus Ad hoc Analysis Jennifer Horkoff 1 Eric Yu 2 Arup Ghose 1 Department of Computer.
Terada Pinyo. I NTRODUCTION The world has witnessed the progressive social and economic change, and has stepped into the era of knowledge economy. Thailand.
1 Structuring Knowledge for a Security Trade-offs Knowledge Base Golnaz Elahi Department of Computer Science Eric Yu Faculty of Information Study University.
1 Model-based Development and Evolution of Information Systems Quality of models and modeling languages John Krogstie Professor, IDI, NTNU UPC,
1 What the body knows: Exploring the benefits of embodied metaphors in hybrid physical digital environments Alissa N. Antle, Greg Corness, Milena Droumeva.
COURSE AND SYLLABUS DESIGN
Chapter 6 Guidelines for Modelling. 1. The Modelling Process 1. Modelling as a Transformation Process 2. Basic Modelling Activities 3. Types of Modelling.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Expanding the Notion of Links DeRose, S.J. Expanding the Notion of Links. In Proceedings of Hypertext ‘89 (Nov. 5-8, Pittsburgh, PA). ACM, New York, 1989,
Of 24 lecture 11: ontology – mediation, merging & aligning.
SYSE 802 John D. McGregor Module 0 Session 3 Systems Engineering QuickView.
Cognitive Dimensions  Developed by Thomas Green and Alan Blackwell  Enhanced by Marian Petre Marian PetreMarian Petre  Descriptions of aspects, attributes,
Measuring the Disability Continuum in a Policy Context Barbara M. Altman, PhD Disability Statistics Consultant Stephen P. Gulley, PhD Brandeis University.
ECE362 Principles of Design The System Engineering Process
Literature review Methods
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Presentation transcript:

R EFLECTIVE A NALYSIS OF THE S YNTAX AND S EMANTICS OF THE i* F RAMEWORK Jennifer Horkoff, Golnaz Elahi, Samer Abdulhadi, Eric Yu Department of Computer Science and Faculty of Information University of Toronto, Canada RIGiM’08

M ODELING L ANGUAGES : I NTENTION VS. U SE Modeling languages are introduced to serve a variety of purposes, including: Facilitating communication Making tacit information explicit Storing knowledge Aiding analysis (Sometimes the intention of a language is not explicitly expressed) 2

M ODELING L ANGUAGES : I NTENTION VS. U SE As a language is adopted and used, it may be used in ways which the language creators did not anticipate It is useful to reflect on the intentions of the language versus its use in practice We focus on the intentions of the syntax and semantics of a language 3 Reflective Analysis of intention vs. use can help to answer: What were the original intentions of the language syntax and semantics? How are the syntax and semantics being commonly used? Why are users prone to deviate from the original language description? Do these variations matter? Should the language be modified? Or, should an effort be made to increase training? Reflective Analysis of intention vs. use can help to answer: What were the original intentions of the language syntax and semantics? How are the syntax and semantics being commonly used? Why are users prone to deviate from the original language description? Do these variations matter? Should the language be modified? Or, should an effort be made to increase training?

R EFLECTIVE A NALYSIS OF THE i* F RAMEWORK We analyze the intention vs. use of the i* Framework i* is a goal and agent-oriented framework which was intended to be used in the early requirements stage to capture agents, their inter-relationships, and their goals Aimed at helping to discover and compare high-level system design alternatives 4

i* E VOLVING A good candidate for reflective analysis 5 The i* Framework was left open to interpretation and modification i* has been applied to many areas for differing purposes We compare i* usage to current U of T Style i* is used in system analysis courses i* Adapted Surveyed student i* assignments, research papers and presentations

S URVEY M ETHOD Survey subjects looking for variations from U of T style: 15 student project assignments from a graduate level system analysis course 15 academic papers and presentations using i* drawn from various sources. All models in each document were surveyed Variations were only counted once per document The models covered diverse application domains, including health care, banking, and education systems. An analysis of the motivations behind the variations was also performed Was the modeler confused about the syntax? Was the modeler using a syntactic shortcut? Does the variation indicate issues within i*? 6

T HE i* F RAMEWORK : U OF T F LAVOUR 7 Elements Links between Elements Actors and Actor Boundaries Actor Association Links Hard Soft

T HE i* F RAMEWORK : U OF T F LAVOUR 8 Syntax Restrictions Include: Goals decompose only with means- ends links to tasks Decomposition links are only used from tasks Dependums are needed Dependency links must go outside actors Actors are not nested Contribution links only go to softgoals Contribution links only inside actors Actor Associations are restricted between certain actors

S URVEY R ESULTS Variations were grouped together in two ways: By syntax category By perceived motivation 9

10 S URVEY R ESULTS : V ARIATION I NSTANCES BY S YNTAX C ATEGORY Number of Variations in Category

D ECOMPOSITION L INKS V ARIATIONS 11 Decomposition links are drawn directly from goals to tasks Decomposition links are used between goals Softgoals are decomposed to tasks Goals are means- ends decomposed to softgoals Decomposition links extend outside actors' boundaries Decomposition links are used between resources Goals are decomposed to resources Decomposition links are used between Softgoals

S URVEY R ESULTS Variations Grouped by perceived motivations: 12 Perceived Motivation The Nature of “Hard” Elements and Softgoals Means-Ends vs. Decomposition The Nature of Actor Boundaries Potentially Ambiguous Dependencies Understanding Associations Intermediate Model Stages Resource Refinement Association Links vs. Inclusion Dependums Incomplete Evaluation Total Number of Variations Instances

E XAMPLE V ARIATION : N ATURE OF “H ARD ” E LEMENTS AND S OFTGOALS G OAL (M EANS -E NDS ) D ECOMPOSED TO S OFTGOAL (7 I NSTANCES ) Syntax not permitted in the U of T style of i* Semantics: The nature of soft and hard goals implies that a softgoal should not be sufficient to satisfy a hard goal Something qualitative satisfies something concrete However… In i* a task can be decomposed to a softgoal The softgoal represents a quality the task should encompass 13

E XAMPLE V ARIATION : N ATURE OF “H ARD ” E LEMENTS AND S OFTGOALS G OAL (M EANS -E NDS ) D ECOMPOSED TO S OFTGOAL Possible Responses: Discontinue decomposition of tasks to sofgoals But how do we associate a quality with a task? Create an alternative way to associate qualitative aspects to tasks, other than through decomposition Could also be used for goals? 14 Alternative Syntax

S URVEY R ESULTS Variations Grouped by perceived motivations: 15 Perceived Motivation The Nature of “Hard” Elements and Softgoals Means-Ends vs. Decomposition The Nature of Actor Boundaries Potentially Ambiguous Dependencies Understanding Associations Intermediate Model Stages Resource Refinement Association Links vs. Inclusion Dependums Incomplete Evaluation Total Number of Variations Instances

E XAMPLE V ARIATION : M EANS -E NDS VS. D ECOMPOSITION G OAL D ECOMPOSITION (16 INSTANCES ) Syntax: Goal decomposition is not permitted in the U of T i* style Semantics: Tasks versus goals Goals can be accomplished in different ways Task is a particular way of doing something Syntax restriction promotes the discovery of alternatives 16

E XAMPLE V ARIATION : T HE N ATURE OF A CTOR B OUNDARIES C ONTRIBUTION L INKS O UTSIDE B OUNDARIES (6 I NSTANCES ) Syntax: Only dependency links should be used outside actor boundaries Semantics: Emphasize actors’ autonomy Actors should not have knowledge of the internal motivations of other actors 17

P OSSIBLE R ESPONSES Strict and loose versions of i* syntax: Strict syntax follows the U of T style restrictions Loose syntax relaxes a select set of rules based on common variations: Means-ends for tasks, decomposition for goals Contribution links across actors Omitting dependums The notion of syntactical shortcuts 18 Shortcut for

S URVEY R ESULTS : S TUDENTS V S R ESEARCHERS Students are more likely to: Have more difficulties understanding the difference between soft and “hard” elements Have incomplete models (models with un-decomposed goals) Misuse association links Researchers are more likely to adapt the Framework as they see fit: More likely to use non-dependency links outside of actor boundaries 19

C ONCLUSIONS AND F UTURE W ORK Based on an analysis of several variations we were able to suggest: Areas where the syntax of i* could be modified We would like to explore the notion of “loose” and “strict” versions of i* syntax Recognized syntactic shortcuts Associating softgoals with hard elements Areas where more training is needed Soft vs. “hard” elements Association links Consistent interpretation of standard syntax shortcuts Future work can: Expand our survey pool and include analysis of further variations Experiment with the utility of modified i* syntax 20

T HANK Y OU Jennifer Horkoff Golnaz Elahi Samer Abdulhadi Eric Yu i* Wiki 21

T HREATS TO V ALIDITY The selection of academic papers and presentations was not completely random The surveyor was less interested in papers without variations Student assignments were longer than academic works, and had more examples But not all variations were higher for student assignments The qualitative analysis of the variations was performed by the authors Variation intentions could be misinterpreted However, misinterpretation could indicate a general source of confusion 22

T HE N ATURE OF “H ARD ” E LEMENTS AND S OFTGOALS Variation# Instances Decomposition links are used between softgoals3 Softgoals are decomposed to tasks2 Means-ends links are used between softgoals1 Softgoal dependency is met by a goal5 Softgoal dependency is met by a task2 Goals are means-ends decomposed to softgoals2 Goals are decomposed to softgoals5 Contribution links are drawn from softgoals to tasks4 Contribution links are drawn from softgoals to goals2 Contribution links are used between goals1 Contribution links are drawn from resources to tasks1 Softgoal should be goal10 Goal should be softgoal15 Task should be softgoal8 Softgoal should be task7 Total70 We select one category of perceived motivation to examine in detail 23 Goal (means-ends) decomposed to softgoal

S URVEY R ESULTS : D ECOMPOSITION L INKS E XAMPLE B REAKDOWN 24 VariationAssignmentsAcademic WorkTotal Instances Decomposition links are drawn directly from goals to tasks 549 Decomposition links are used between goals 426 Goals are means-ends decomposed to softgoals 235 Decomposition links extend outside actors' boundaries 134 Decomposition links are used between Softgoals 213 Softgoals are decomposed to tasks 202 Decomposition links are used between resources 101 Goals are decomposed to resources 011 Resources to tasks are decomposed to tasks 000 Total

S URVEY R ESULTS Variations Grouped by perceived motivations: 25 Number of Variations in Category Total Instances per Category