1 From GORE (not the US presidential candidate) to AORE (Agent-Oriented Requirements Engineering) Eric Yu University of Toronto November 2000.

Slides:



Advertisements
Similar presentations
1 GRL Introduction Lin Liu University of Toronto April 2001.
Advertisements

Intelligence Step 5 - Capacity Analysis Capacity Analysis Without capacity, the most innovative and brilliant interventions will not be implemented, wont.
Centralize or Decentralize? A Requirements Engineering Perspective on Internet-Scale Architectures Eric Yu University of Toronto July 2000.
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
© Eric Yu Strategic Actor Relationships Modelling with i* Eric Yu University of Toronto December 13-14, 2001 IRST, Trento, Italy.
Some questions o What are the appropriate control philosophies for Complex Manufacturing systems? Why????Holonic Manufacturing system o Is Object -Oriented.
1/10 POSDATA Team EVR:MAKING USE Hou, Kyu Cho, Eun Young Jeung, Min Ho Jung,Hee Joon.
Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University 1 Pittsburgh, PA Dennis Smith, David Carney and Ed Morris DEAS.
Strategic Modelling for Enterprise Integration Eric Yu University of Toronto 14th World Congress International Federation of Automatic Control July 5-9,
Unit-III Requirements Engineering
Olivia Smith Angus Amy. Lewis Hopkins, the author of this selection, is the Professor of Urban and Regional Planning emeritus. In addition to his work.
Developing MAS The GAIA Methodology A Brief Summary by António Castro and Prof. Eugénio Oliveira.
Modeling Issues Modeling Enterprises
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Requirements.
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering Vahid Jalali Amirkabir university of technology, Department of computer.
Agent Mediated Grid Services in e-Learning Chun Yan, Miao School of Computer Engineering Nanyang Technological University (NTU) Singapore April,
Software engineering for supply chains:
Introduction to Software Architecture. What is Software Architecture?  It is the body of methods and techniques that help us to manage the complexities.
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering درس مهندسی نیازمندی ها استاد دکتر عبداله زاده دانشجو خیرالنسا مرچانت.
12.1 Frameworks for comparing ISD methodologies IMS Information Systems Development Practices.
1 درس مهندسي نيازمندي استاد دكتر عبداله زاده دانشجو خيرالنسا مرچانت RE in The Year 00: A Research Perspective.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Goal.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Towards.
Copyright c 2006 Oxford University Press 1 Chapter 4 Group Tasks and Activities Wide variety of synonyms and metaphors for groups and teams Crosses context.
TRUST TRADE-OFF ANALYSIS FOR SECURITY REQUIREMENTS ENGINEERING Authors: Golnaz Elahi, PhD student at the University of Toronto, Canada Eric Yu, full professor.
Chapter 9 Architecture Alignment. 9 – Architecture Alignment 9.1 Introduction 9.2 The GRAAL Alignment Framework  System Aspects  The Aggregation.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
A Research Agenda for Accelerating Adoption of Emerging Technologies in Complex Edge-to-Enterprise Systems Jay Ramanathan Rajiv Ramnath Co-Directors,
Challenge the future Delft University of Technology Agent-based Modeling and Simulation for the Social Scientist MAIA Amineh Ghorbani, Virginia Dignum,
ARTIFICIAL INTELLIGENCE [INTELLIGENT AGENTS PARADIGM]
Evaluating Goal Achievement in Enterprise Modeling – An Interactive Procedure and Experiences Jennifer Horkoff 1 Eric Yu 2 1 Department of Computer Science,
Multi-Agent Systems University “Politehnica” of Bucarest Spring 2003 Adina Magda Florea
A knowledge-based Assistant for real-time Planning and Execution of PSS Engineering Change Processes Michael Abramovici, Youssef Aidi IT in Mechanical.
Visualizations to Support Interactive Goal Model Analysis Jennifer Horkoff 1 Eric Yu 2 Department of Computer Science 1 Faculty of Information 2
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course Lecture 5: i*modelling.
Project design & Planning The Logical Framework Approach An Over View Icelandic International Development Agency (ICEIDA) Iceland United Nations University.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
1 An Agent-Oriented Methodology for Requirements Elicitation Luiz Marcio Cysneiros Dept. of Math and Stat Information Technology Program York University.
1 Introduction to Software Architectures Lecture - 3.
© Eric Yu Strategic Actor Relationships Modelling with i* Eric Yu University of Toronto December 13-14, 2001 IRST, Trento, Italy.
1 A Methodology for Eliciting Requirements/Re-engineering Processes Using i* Luiz Marcio Cysneiros Eric Yu Department of Computer Science – University.
Lecture 7: Requirements Engineering
© Eric Yu Agent Oriented Software Development References
Goal and Requirement Change Management in Enterprise Architecture Abelneh Teka 13, June 2012.
Presentation on Issues and Challenges in Evaluation of Agent-Oriented Software Engineering Methodologies By: kanika singhal.
1 Evolving System Architecture to Meet Changing Business Goals An Agent and Goal-Oriented Approach Daniel Gross & Eric Yu Faculty of Information Studies.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
Using Meta-Model-Driven Views to Address Scalability in i* Models Jane You Department of Computer Science University of Toronto.
Agent Oriented Software Development
© Eric Yu Business Processes (from Steve Easterbrook RE slides)  Business Process Automation  Leave existing business processes as they are 
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
2006 Technology Foresight Training Programme Module 1: Technology Foresight for Organizers 1 Ozcan Saritas Scope and Focus of Foresight Exercises – 2 Dr.
International Atomic Energy Agency Regulatory Review of Safety Cases for Radioactive Waste Disposal Facilities David G Bennett 7 April 2014.
1 Structuring Knowledge for a Security Trade-offs Knowledge Base Golnaz Elahi Department of Computer Science Eric Yu Faculty of Information Study University.
Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 8-1 Chapter 8 Participative Management and Leading Teams.
 2001 John Mylopoulos STRAW’ Software Architectures as Social Structures John Mylopoulos University of Toronto First ICSE Workshop titled “From.
Requirements Analysis
Management: Arab World Edition Robbins, Coulter, Sidani, Jamali Chapter 9: Organizational Structure and Design Lecturer: [Dr. Naser Al Khdour]
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Engineering as Social Experimentation “To undertake a great work, and especially a work of a novel type, means carrying out an experiment. It means taking.
Models of the OASIS SOA Reference Architecture Foundation Ken Laskey Chair, SOA Reference Model Technical Committee 20 March 2013.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
Page 1 An Overview of The COTS-Aware Requirements Engineering and Software Architecting Project (CARE/SA) The University of Texas at Dallas Department.
Object-Oriented Software Engineering Using UML, Patterns, and Java,
SNS College of Engineering Coimbatore
Grade 6 Outdoor School Program Curriculum Map
TDT4252 Modelling of Information Systems Advanced Course
Requirements I Peter Dolog dolog [at] cs [dot] aau [dot] dk
Dept. of Computation, UMIST
Presentation transcript:

1 From GORE (not the US presidential candidate) to AORE (Agent-Oriented Requirements Engineering) Eric Yu University of Toronto November 2000

2 From GORE to AORE 1.GORE is gathering momentum 2.Why Agent-Oriented RE ? 3.What kind of Agent-Oriented RE ?

3 Goal-Oriented Requirements Engineering CSD – Feather 87… KAOS – van Lamsweerde, … Inquiry Cycle – Potts, Anton EKD – Bubenko, Rolland, Loucopoulos Win-Win – Boehm NFR – Chung, Mylopoulos, … MOMENTUM >>> Z.URN proposal to ITU-T (Nov. 2000)  GRL

4 Benefits of GORE van Lamsweerde (ICSE 2000) Systematic derivation of requirements from goals Goals provide rationales for requirements Goal refinement structure provides a comprehensible structure for the requirements document Alternative goal refinements and agent assignments allow alternative system proposals to be explored Goal formalization allows refinements to be proved correct and complete.

5 From GORE to AORE 1.GORE is gathering momentum 2.Why Agent-Oriented RE ? 3.What kind of Agent-Oriented RE ?

6 The Changing Needs of Requirements Modelling 1.Technology as enabler  Goals are discovered; may be bottom-up 2.Networked systems and organizations  Composite systems, but dispersed, fluid, contingent, ephemeral  Same for responsibilities, accountability, authority, ownership,… 3.Increased inter-dependency and vulnerability  Dependencies among stakeholders (inc. system elements)  Impact of changes 4.Limited knowledge and control  No single designer with full knowledge and control 5.Openness and uncertainties  Can’t anticipate all eventualities / prescribe responses in advance 6.Cooperation  Beyond vocabulary of “interaction” (behavioural)  Reason about benefits of cooperation – goals, beliefs, conflicts

7 The Changing Needs of Requirements Modelling (cont’d) 7. Boundaries, Locality, and Identity  Can transcend physical boundaries  Want “logical” criteria for locality, identity – e.g., authority, autonomy, reach of control, knowledge  Negotiated boundaries  Reasoning about boundary re-alignment and implications

8 Development-World model refers to and reasons about… Operational-World models Alt-1 Alt-2 To-be As-is

9 GORE & AORE research challenges (framework components) Ontology Formalization Analysis and reasoning Methodologies Knowledge Based Support  Generic knowledge, e.g., common NFR goals, refinements, solution techniques (e.g., for security, safety,…)  Larger patterns Tools Evaluation, Validation, Empirical studies Heterogeneous modelling frameworks

10 i* - agent-oriented modelling Actors are semi-autonomous, partially knowable Strategic actors, intentional dependencies Meeting Scheduling Example “Strategic Dependency” Model

11 Revealing goals, finding alternatives Asking “Why”, “How”, “How else”

12 Scheduling meeting …with meeting scheduler Consider 1.Technology as enabler 2.Networked systems and organizations 3.Increased inter-dependency and vulnerability 4.Limited knowledge and control 5.Openness and uncertainties 6.Cooperation 7.Boundaries, locality, identity

13 “Strategic Rationale” Model with Meeting Scheduler SR2

14 From GORE to AORE 1.GORE is gathering momentum 2.Why Agent-Oriented RE ? 3.What kind of Agent-Oriented RE ?

15 Agent Orientation as a Software Paradigm Situated  sense the environment and perform actions that change the environment Autonomous  have control over their own actions and internal states  can act without direct intervention from humans Flexible  responsive to changes in environment, goal-oriented, opportunistic, take initiatives Social  interact with other artificial agents and humans to complete their tasks and help others Jennings, Sycara, Wooldridge (1998)

16 Analysis and Design of Agent-Oriented Systems e.g., Wooldridge Jennings Kinny (JAAMAS 2000) “GAIA” Analysis level  Roles and Interactions Permissions Responsibilities »liveness properties »safety properties Activities Protocols Design level  Agent types  Services  Acquaintances Modelling concepts being driven from programming again?!! Structured Analysis from Structured Programming OOA from OOD, OOP AOA from AOP ??

17 What are the important concepts for Agent Orientation as a Modelling Paradigm ? Intentionality Autonomy Sociality Identity & Boundaries Strategic Reflectivity Rational Self-Interest

18 Agent Orientation as a Modelling Paradigm Intentionality  Agents are intentional.  Agent intentionality is externally attributed by the modeller.  Agency provides localization of intentionality.  Agents can relate to each other at an intentional level. Autonomy Sociality Identity & Boundaries Strategic Reflectivity Rational Self-Interest

19 Agent Orientation as a Modelling Paradigm Intentionality Autonomy  An agent has its own initiative, and can act independently. Consequently, for a modeller and from the viewpoint of other agents: its behaviour is not fully predictable. It is not fully knowable, nor fully controllable.  The behaviour of an agent can be partially characterized, despite autonomy, using intentional concepts. Sociality Identity & Boundaries Strategic Reflectivity Rational Self-Interest

20 Agent Orientation as a Modelling Paradigm Intentionality Autonomy Sociality  An agent is characterized by its relationships with other agents, and not by its intrinsic properties alone.  Relationships among agents are complex and generally not reducible.  Conflicts among many of the relationships that an agent participates in are not easily resolvable.  Agents tend to have multi-lateral relationships, rather than one- way relationships.  Agent relationships form an unbounded network  Cooperation among agents cannot be taken for granted.  Autonomy is tempered by sociality. Identity & Boundaries Strategic Reflectivity Rational Self-Interest

21 Agent Orientation as a Modelling Paradigm Intentionality Autonomy Sociality Identity & Boundaries  Agents can be abstract, or physical.  The boundaries, and thus the identity, of an agent are contingent and changeable.  Agent, both physical and abstract, may be created and terminated.  Agent behaviour may be classified, and generalized. Strategic Reflectivity Rational Self-Interest

22 Agent Orientation as a Modelling Paradigm Intentionality Autonomy Sociality Identity & Boundaries Strategic Reflectivity  Agents can reflect upon their own operations.  Development world deliberations and decisions are usually strategic with respect to the operational world.  The scope of reflectivity is contingent. Rational Self-Interest

23 Agent Orientation as a Modelling Paradigm Intentionality Autonomy Sociality Identity & Boundaries Strategic Reflectivity Rational Self-Interest  An agent strives to meet its goals.  Self-interest is in a context of social relations.  Rationality is bounded and partial.

24 Beyond RE Agent-Oriented Software Development  Tropos – a full-fledge development framework driven by AORE concepts Agent-Oriented Software Engineering  Goal and agent modelling support for SE activities  e.g., traceability for maintenance, AO as scoping, limiting propagation of change, assigning responsibilities in software eng. organizations, software processes, … Business Goals/Arch. System Goals/Arch.  Business strategy modelling & analysis Intellectual Property management  Security and Trust