1 from gore (not the us presidential candidate) to aore (agent-oriented requirements engineering)...

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

Upload: stuart-rich

Post on 12-Jan-2016

215 views

Category:

Documents


2 download

TRANSCRIPT

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

1

From GORE (not the US presidential candidate)

to AORE (Agent-Oriented Requirements Engineering)

Eric YuUniversity of TorontoNovember 2000

Page 2: 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 ?

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

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

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

4

Benefits of GOREvan 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.

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

5

From GORE to AORE

1. GORE is gathering momentum

2. Why Agent-Oriented RE ?

3. What kind of Agent-Oriented RE ?

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

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

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

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

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

8

Development-World model refers to and reasons about…

Operational-World models

Alt-1 Alt-2 To-beAs-is

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

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

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

10

i* - agent-oriented modelling

•Actors are semi-autonomous, partially knowable

•Strategic actors, intentional dependencies

Meeting Scheduling Meeting Scheduling ExampleExample

“Strategic Dependency” Model

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

11

Revealing goals, finding alternatives

•Asking “Why”, “How”, “How else”

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

12

Scheduling meeting …with meeting scheduler

ConsiderConsider

1.1. Technology as enablerTechnology as enabler

2.2. Networked systems and organizationsNetworked systems and organizations

3.3. Increased inter-dependency and Increased inter-dependency and vulnerabilityvulnerability

4.4. Limited knowledge and controlLimited knowledge and control

5.5. Openness and uncertaintiesOpenness and uncertainties

6.6. CooperationCooperation

7.7. Boundaries, locality, identityBoundaries, locality, identity

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

13

“Strategic Rationale” Model with Meeting Scheduler

•SR2

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

14

From GORE to AORE

1. GORE is gathering momentum

2. Why Agent-Oriented RE ?

3. What kind of Agent-Oriented RE ?

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

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 othersJennings, Sycara, Wooldridge

(1998)

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

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 ??

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

17

What are the important concepts for

Agent Orientation as a Modelling Paradigm ?

• Intentionality

•Autonomy

•Sociality

• Identity & Boundaries

•Strategic Reflectivity

•Rational Self-Interest

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

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

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

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

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

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

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

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

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

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

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

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.

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

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