WP 6: Tool Suite www.agreement-technologies.org. WP6: Tool Suite CSICURJUPVTotal WP6: Tool suite (Leader: V.Botti – UPV) 365416 2 252 Task 6.1: Design.

Slides:



Advertisements
Similar presentations
Cultural Heritage in REGional NETworks REGNET WP2: Implementation of the System and Preparation of Services and Product Generation Structure and deliverables.
Advertisements

Software Quality Assurance Plan
Workpackage 2: Norms
GTI-IA-MIP-GRPS Universidad Politécnica de Valencia (UPV)
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Stepan Potiyenko ISS Sr.SW Developer.
Introduction to Knowledge Engineering
Chapter 6: Design of Expert Systems
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Requirements.
Lesson-12 Information System Development-2
Secure Middleware (?) Patrick Morrison 3/1/2006 Secure Systems Group.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
CATEGORIES OF INFORMATION There are three main categories of business information,and these are related to the purpose for which the information is utilized.
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Software Engineering General Project Management Software Requirements
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Information Systems Development : Overview. Information systems development practice Concept and role of a systems development methodology Approaches.
Chapter 4 Capturing the Requirements 4th Edition Shari L. Pfleeger
PRIME Economics WP Sub-contractors Meeting Thursday 16th December, – In Den Rustwat.
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
IIIAURJCUPV Task 7.1 Software architecture and computation model E. Marcos C. Acuña Task 7.2 Multiagent System Platform A. Espinosa Task.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
CSI315 Web Applications and Technology Overview of Systems Development (342)
What is Software Engineering?. Software engineering Multi-person construction of multi-version software (David Parnas) An engineering discipline whose.
Requirements Analysis
Towards an activity-oriented and context-aware collaborative working environments Presented by: Ince T Wangsa Supervised by:
ITEC224 Database Programming
TC Methodology Massimo Cossentino (Italian National Research Council) Radovan Cervenka (Whitestein Technologies)
Introduction to Software Engineering
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Content The system development life cycle
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
SysML Reference Model Definition Model Based System Development in the Joint Strike Missile project Svein-Erik Søgård KDS/Missile Division.
Systems Analysis and Design in a Changing World, Fourth Edition
HCI Design Process CS774 Human-Computer Interaction Spring 2004.
Lecture 2 –Approaches to Systems Development Method 10/9/15 1.
Teaching material for a course in Software Project Management & Software Engineering – part V.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
ECIMF meeting, Brussels Copyright WebGiro AB, All rights reserved. ECIMF CWA Overview Andrzej Bialecki WebGiro, Chief System Architect.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
EMI INFSO-RI Guidelines and SQA Process Maria Alandes Pradillo (CERN) SA2.2 Task Leader.
Task 2.1: Software Specifications Markus Kissler-Patig.
Stand Up Comedy Project/Product Management
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Petter Nielsen Information Systems/IFI/UiO 1 Systems development Methodologies IN364.
On-To-Knowledge review Juan-Les-Pins/France, October 06, 2000 Hans Akkermans, VUA Hans-Peter Schnurr, AIFB Rudi Studer, AIFB York Sure, AIFB KMKMMethodology.
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
Quality Milestones Elaborate quality system developed over the years “Joint Agenda Building” (JAB) group “Strategic Quality” – Progress report CA/80/04.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
L ECTURE 1 Introduction Getting started with software engineering.
1 Requirements Elicitation – 2 Lecture # Requirements Engineering Process Requirements Elicitation Requirements Analysis and Negotiation Requirements.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
Requirement Engineering Management Amna Shifia Nisafani Feby Artwodini M. Department of Information Systems Subject : Requirement Engineering.
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
The Systems Engineering Context
Chapter 6: Design of Expert Systems
Seminar 1 Design of Informatics Systems
CS 790M Project preparation (I)
Lecture Software Process Definition and Management Chapter 3: Descriptive Process Models Dr. Jürgen Münch Fall
User requirements modelling: Motivation
Dept. of Computation, UMIST
CS 426 CS 791z Topics on Software Engineering
CS 426 CS 791z Topics on Software Engineering
Presentation transcript:

WP 6: Tool Suite

WP6: Tool Suite CSICURJUPVTotal 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)

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. Iglesias Task 6.1 Design of a MAS Methodology based on Organisational Concepts

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)‏ –D 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 Julian GTI-IA. UPV. Task 6.2. MAS Development Environment

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