How To Understand The Organizational Model Of A Multiagent System



Similar documents
Chapter 8 The Enhanced Entity- Relationship (EER) Model

Enterprise Architecture at Work

Towards a Common Metamodel for the Development of Web Applications

SEARCH The National Consortium for Justice Information and Statistics. Model-driven Development of NIEM Information Exchange Package Documentation

Representing XML Schema in UML A Comparison of Approaches

Table of Contents. CHAPTER 1 Web-Based Systems 1. CHAPTER 2 Web Engineering 12. CHAPTER 3 A Web Engineering Process 24

Requirements Engineering Process

Data Modeling Basics

1. Visual Paradigm for UML

CS 487. Week 8. Reference: 1. Software engineering, roger s. pressman. Reading: 1. Ian Sommerville, Chapter 3. Objective:

SysML Modelling Language explained

How To Develop A Multi Agent System (Mma)

Design Authorization Systems Using SecureUML

Use Cases. Massimo Felici. Massimo Felici Use Cases c

Skills for Employment Investment Project (SEIP)

Quiz Examination in Software Engineering Theory

An Investigation of Agent Oriented Software Engineering Methodologies to Provide an Extended Methodology

AN ONTOLOGICAL APPROACH TO WEB APPLICATION DESIGN USING W2000 METHODOLOGY

Modeling the User Interface of Web Applications with UML

Software Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville

Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model

Course Outline. Business Analysis & SAP BI (SAP Business Information Warehouse)

Development of Enterprise Architecture of PPDR Organisations W. Müller, F. Reinert

i. Node Y Represented by a block or part. SysML::Block,

Modeling Turnpike: a Model-Driven Framework for Domain-Specific Software Development *

Agent-Oriented Software Engineering PORTO Methodology AIAD 2013/2014. António Castro and Eugénio Oliveira

UML Modeling of Five Process Maturity Models

Application Of Business Intelligence In Agriculture 2020 System to Improve Efficiency And Support Decision Making in Investments.

IRA 423/08. Designing the SRT control software: Notes to the UML schemes. Andrea Orlati 1 Simona Righini 2

SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) SERVICE-ORIENTED BUSINESS INTEGRATION MODEL LANGUAGE SPECIFICATIONS

The Tropos and MaSE Agent-Oriented Software Engineering Methodologies. Msury Mahunnah, Tallinn University of Technology

11 Tips to make the requirements definition process more effective and results more usable

Java (12 Weeks) Introduction to Java Programming Language

Structure of Presentation. The Role of Programming in Informatics Curricula. Concepts of Informatics 2. Concepts of Informatics 1

Adapted from slides by John Musser

An Automatic Tool for Checking Consistency between Data Flow Diagrams (DFDs)

Meta-Model specification V2 D

Business Modeling with UML

Tool Support for Software Variability Management and Product Derivation in Software Product Lines

MBSE Practices in Telescope Modeling. Section I: Introduction. Project Description

IV. The (Extended) Entity-Relationship Model

Generating Aspect Code from UML Models

Architecture. Reda Bendraou

How To Design An Information System

Chap 1. Introduction to Software Architecture

UML PROFILING AND DSL

Work Breakdown Structure (WBS) Emanuele Della Valle

ARIS Education Package Process Design & Analysis

Role Engineering: The Cornerstone of Role- Based Access Control DECEMBER 2009

UML-based Test Generation and Execution

Chapter 10. Practical Database Design Methodology. The Role of Information Systems in Organizations. Practical Database Design Methodology

An Enterprise Architecture and Data quality framework

An Agent Based Etl System: Towards an Automatic Code Generation

Clarifying a vision on certification of MDA tools

Software Development in the Large!

Overview

Administering Active Directory. Administering Active Directory. Reading. Review: Organizational Units. Review: Domains. Review: Domain Trees

ProGUM-Web: Tool Support for Model-Based Development of Web Applications

Section C. Requirements Elicitation

GECKO Software. Introducing FACTORY SCHEMES. Adaptable software factory Patterns

UML FOR OBJECTIVE-C. Excel Software

Requirements Management mit HP Quality Center / ALM

Developing Business Architecture with TOGAF

UML TUTORIALS THE USE CASE MODEL

Database Design Methodology

Co-Creation of Models and Metamodels for Enterprise. Architecture Projects.

Common Warehouse Metamodel (CWM): Extending UML for Data Warehousing and Business Intelligence

A pragmatic approach to modeling large systems

Lecture Slides for Managing and Leading Software Projects. Chapter 5: Project Planning Techniques

Agile PASSI. 1 The Agile PASSI Skeleton

White Paper What Solutions Architects Should Know About The TOGAF ADM

Software Requirements Specification of A University Class Scheduler

Architecture Description of <Architecture Name> for <System of Interest>

Enterprise Architect for an Enterprise Architecture

Design principles in Test Suite Architecture

Object-Oriented Systems Analysis and Design

Advanced Service Creation: Bridging the Gap Between Requirements Elicitation and Service Design

An Ontological Approach to Oracle BPM

Background: Business Value of Enterprise Architecture TOGAF Architectures and the Business Services Architecture

How To Write A Diagram

CDC UNIFIED PROCESS PRACTICES GUIDE

AC : ENGINEERING MANAGEMENT PROGRAM ACCREDI- TATION: COMPARING AACSB AND ABET

ATV Data Link Simulator: A Development based on a CCSDS Layers Framework

4. Multiagent Sys stems Design. Part 2: The PROMETHEUS methodology.

A Methodology for the Development of New Telecommunications Services

Ultimus and Microsoft Active Directory

Transcription:

A UML-Based Notation for Representing MAS Organizations WOA 2011 Dodicesimo Workshop Nazionale "Dagli Oggetti agli Agenti" M. C O S S E N T I N O, C. L O D A T O, S. L O P E S, P. R I B I N O I C A R I N S T I T U T E N A T I O N A L R E S E A R C H C O U N C I L O F I T A L Y V. S E I D I T A, A. C H E L L A D I P. D I I N G. C H I M. G E S T. I N F. M E C C. U N I V E R S I T À D E G L I S T U D I D I P A L E R M O

A UML-Based Notation for Representing MAS Organizations A notation for representing agents organizations to be implemented using Moise+ and Jason. An UML profile was defined for representing the elements of Moise+ organizational model such as role, mission and group

Overview Organizations play a relevant role in multi-agent systems design; They can be seen as the set of constraints ruling the agent s behavior in MAS. Moise+ describes the organization in a MAS by employing three main views: Structural Functional Normative

Moise+ The structural and functional dimensions defined in Moise+ are almost independent. The normative dimension is used to establish a link between them. Moise+ is complemented with the possibilities of quickly and easily programming MAS by means of J-Moise+. J-Moise+ is a Jason extension allowing developers to use Jason for programming agents and their organizations

Moise+ (2) Structural viewpoint: An organization can be seen as a set of Roles linked by Relations and clustered into Groups. Functional viewpoint: Social Schemes define global objectives and the plans for reaching them. The functionalities of the organization are represented as Goals grouped into Missions. Normative viewpoint: A Mission is linked to a Role by means of norms. Norms can be seen as the backbone connecting the functional and structural aspects of an organization.

Objectives The creation of a specific notation for representing the organizational model proposed by Moise+. Advantages: Graphical notations are more readable and understandable than any coding language. It is usually easier to explain a graphical notation to stakeholders involved in the designer than to read the application code with them. The possibility of involving stakeholders like system users enables the adoption of agile development approaches and improves the flexibility of conventional ones.

Notation elements

Notation elements Group may contain several structural elements (Roles) and other grouping elements (sub-groups). The root group represents the entire organization.

Notation elements Group may contain several structural elements (Roles) and other grouping elements (sub-groups). The root group represents the entire organization. Role has properties represented in the form of class attributes. An abstract role is identified using an italic font.

Notation elements Group may contain several structural elements (Roles) and other grouping elements (sub-groups). The root group represents the entire organization. Role has properties represented in the form of class attributes. An abstract role is identified using an italic font. Goal achievement and maintenance.

Notation elements Group may contain several structural elements (Roles) and other grouping elements (sub-groups). The root group represents the entire organization. Role has properties represented in the form of class attributes. An abstract role is identified using an italic font. Goal achievement and maintenance. Mission has the minimum and the maximum commitments to the mission.

Notation elements Group may contain several structural elements (Roles) and other grouping elements (sub-groups). The root group represents the entire organization. Role has properties represented in the form of class attributes. An abstract role is identified using an italic font. Goal achievement and maintenance. Mission has the minimum and the maximum commitments to the mission. Social Scheme where goals and missions are grouped

Relations among organizational elements - Dependency << Stereotype>> Dependency ( ) a generic relationship, with an UML stereotypes that defines the type of dependency.

Relations among organizational elements - Generalization Generalization( ) a relationship between roles in which specialized roles inherit features of the general role.

Relations among organizational elements - Association << Stereotype>> Association ( ) a link between elements of the Moise+ model with an UML stereotypes that attributes a semantic. Used for representing Organizational links Compatibility links Norms

Relations among organizational elements - Association: Organizational links Organizational links define the way in which social exchanges between agent roles occur. Authority Acquaintance Communication <<type of Org. Link>>

Relations among organizational elements - Association: Compatibility links Compatibility links show the possibility of an agent to adopt both roles at the same time <<compatibility>>

Relations among organizational elements - Association: Norms Norms regulates the way a Role performs a Mission Obligations Permissions <<type of Norm>>

Relations among organizational elements - Aggregation Aggregation ( ) a link defining the membership of a goal to a mission

Adopted Diagrams Organizational Diagram OD Scheme Structural Diagram SSD Scheme Functional Diagram SFD

Adopted Diagrams Organizational Diagram OD An UML class diagram for representing the structural and normative specification. The Organizational Diagram focuses on Moise+ elements such as Group, Roles, Missions and different kinds of relationships. Scheme Structural Diagram SSD Scheme Functional Diagram SFD

Adopted Diagrams Organizational Diagram OD An UML class diagram for representing the structural and normative specification. The Organizational Diagram focuses on Moise+ elements such as Group, Roles, Missions and different kinds of relationships. Scheme Structural Diagram SSD An UML class diagram for modeling the social schemes of the organization. Scheme Functional Diagram SFD

Adopted Diagrams Organizational Diagram OD An UML class diagram for representing the structural and normative specification. The Organizational Diagram focuses on Moise+ elements such as Group, Roles, Missions and different kinds of relationships. Scheme Structural Diagram SSD An UML class diagram for modeling the social schemes of the organization. Scheme Functional Diagram SFD An UML activity diagram for representing how a goal can be decomposed in sub-goals.

Organizational Diagram

Scheme Structural Diagram

Scheme Functional Diagram

Future works Conversion the diagrams in a XMI file and then in other kind of code.

Thanks!