+ All Categories
Home > Documents > WP 6: Tool Suite . WP6: Tool Suite CSICURJUPVTotal WP6: Tool suite (Leader: V.Botti – UPV) 365416...

WP 6: Tool Suite . WP6: Tool Suite CSICURJUPVTotal WP6: Tool suite (Leader: V.Botti – UPV) 365416...

Date post: 02-Jan-2016
Category:
Upload: dorcas-hill
View: 216 times
Download: 0 times
Share this document with a friend
Popular Tags:
16
WP 6: Tool Suite www.agreement-technologies.org
Transcript

WP 6: Tool Suite

www.agreement-technologies.org

WP6: Tool Suite

CSIC URJ UPV Total

WP6: Tool suite (Leader: V.Botti – UPV)

36 54 162

252

Task 6.1: Design of a MAS methodology based on organizational concepts (Leader: C. Iglesias)

6 48 72 126

Task 6.2: MAS Development Environment (Leader: V.Julián)

30 6 90 126

WP8: Tool Suite : Goal

– Methodology that

• integrates software engineering principles for the correct management of complex and large-scale systems; and

• provides specific support to new requirements.

– Development environment for open MAS.

From an organisational perspective (WP3)

Carlos A. [email protected]

Task 6.1 Design of a MAS Methodology based on Organisational Concepts

www.agreement-technologies.org

MAS Methodology: Motivation

• Agents are SW, so it is need engineering'

• Why another new MAS methodology?– Because most of them are “old” in a SW engineering

sense• Lack of a pragmatic approach to agent engineering• Need to include current trends, such as XP, DDD, MDA,

Testing, Mashups, ...• Need to research specifically on engineering with TA and

social/organisational aspects• Need to research on how, when and why TA, can be

integrated in current SW development

MAS Methodology: Objectives

I. Define a methodology for “open MAS”

Agents, TA, model-based engineering

graphical/textual notations, worksheets, documents structure

Life-cycle model, process model, guidelines, elicitation techniques

IDE, T6.2

Case studies, application projects

MAS Methodology: Activities

• Process development (Methods)– D6.1.1. Process development report (M18)

• Formalisation process / guidelines

• Meta-models (World View + Theory)– Early draft should be available (M9)

• Review internal/external proposals (M2)• Define context / purpose of the methodology (M3)• Define use cases (M5)• Define models / theory (M9)

– D6.1.2 Report on meta-models (M24)• Iterative refinement / formalisation

Vicente JulianGTI-IA. UPV.

Task 6.2. MAS Development Environment

www.agreement-technologies.org

Task 6.2. MAS Development Environment

•WP6: Tool suite (Leader: V.Botti – UPV)•Task 6.1: Design of a MAS methodology based on organizational concepts (Leader: C. Iglesias)•Task 6.2: MAS Development Environment (Leader: V.Julián)

Task 6.2. MAS Development Environment

• Motivation– Lack of development tools and environments

that support the development of open MAS– Necessity of a sw tool which integrates all

the project work proposals

Task 6.2. MAS Development Environment

• Description– The goal of this task is to build an application

development environment (ADE) that allows users to develop and execute open MAS populated with agents with agreement capabilities

– There exists some previous works (EIDE, MAST, TOAST and RICAJ) which can facilitate the kick-off

Task 6.2. MAS Development Environment

• Activities– Study of available development tools– Definition of rules and mechanisms for

translating models– Tool Development and Integration

Task 6.2. Schedule

M12

Definition of rules and mechanisms for translating models

M24 M36 M48 M60

Tool Development and Integration

Study of available development tools

M0

Task 6.2. MAS Development Environment

• Milestones– D6.2.1 Survey on development tools for MAS.

Month 6 – D6.2.2 Rules and mechanisms for translating

models. Month 24 – D6.2.3 Tool and Integrated Application

development environment. Month 24, 40, 48, 60

Task 6.2. MAS Development Environment

• Open Issues/Challenges– Started Work

• Related work study. First version available

– In this year• Related work ended. Analysis and elicitation of requirements

for our proposal. • Temptative: to start the transformation of the proposed

models to obtain a basic non-completely functional prototype.

WP 6: Tool Suite

www.agreement-technologies.org


Recommended