1 4 January 2016 Architectural Design of a Distributed Application with Autonomic Quality Requirements DEAS St. Louis, USA, May 21 th, 2005 Danny Weyns,

Slides:



Advertisements
Similar presentations
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
Advertisements

SDN and Openflow.
Effective Coordination of Multiple Intelligent Agents for Command and Control The Robotics Institute Carnegie Mellon University PI: Katia Sycara
A Summary of the Article “Intelligence Without Representation” by Rodney A. Brooks (1987) Presented by Dain Finn.
University of Jyväskylä An Observation Framework for Multi-Agent Systems Joonas Kesäniemi, Artem Katasonov * and Vagan Terziyan University of Jyväskylä,
Introduction and Overview “the grid” – a proposed distributed computing infrastructure for advanced science and engineering. Purpose: grid concept is motivated.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
ATSN 2009 Towards an Extensible Agent-based Middleware for Sensor Networks and RFID Systems Dirk Bade University of Hamburg, Germany.
MultiAgent Systems. Distributed Artificial Intelligence MultiAgent Systems Characteristics of MAS Challenges of MAS Networking Remote Method Invocation.
Essential Software Architecture Ian Gorton CS590 – Winter 2008.
RETSINA: A Distributed Multi-Agent Infrastructure for Information Gathering and Decision Support The Robotics Institute Carnegie Mellon University PI:
May-June 2001 ISISTAN Research Institute – Tandil, Argentina Software Design Methodologies: UML in Action Dr. Mohamed Fayad, J.D. Edwards Professor Department.
A Colored Petri Net for a Multi-Agent Application Aarhus, Denmark - August 27, 2002 MOCA ‘02 Danny Weyns & Tom Holvoet K.U.Leuven - Belgium.
Course Instructor: Aisha Azeem
Adaptive Traffic Light Control with Wireless Sensor Networks Presented by Khaled Mohammed Ali Hassan.
Abstraction and Control of Transport Networks (ACTN) BoF
Adapting Environment-Mediated Self-Organizing Emergent Systems by Exception Rules Holger Kasinger, Bernhard Bauer, Jörg Denzinger and Tom Holvoet.
January 13, 2012 Oscar Lin Steve Leung School of Computing and Information Systems Faculty of Science and Technology Athabasca University, Canada.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
1 18 August 2015 AGV Simulation Tutorial Nelis Boucké Alexander Helleboogh.
What is Software Architecture?
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
Topic 2: Multi-Agent Systems a practical example categories of MAS examples definitions: agents and MAS conclusion.
International Workshop on Web Engineering ACM Hypertext 2004 Santa Cruz, August 9-13 An Engineering Perspective on Structural Computing: Developing Component-Based.
A Framework for Distributed Model Predictive Control
International Conference on Software Engineering 2007
L 9 : Collaborations Why? Terminology Coherence Coordination Reference s :
Architectural Design To explain the advantages and disadvantages of different distributed systems architectures To discuss client-server and distributed.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
1 8 October 2015 Coordination middleware for decentralized applications in dynamic networks Kurt Schelfthout, Tom Holvoet.
Travis Steel. Objectives What is the Agent Paradigm? What is Agent-Oriented Design and how is it different than OO? When to apply AOD techniques? When.
1 Software Design Reference: Software Engineering, by Ian Sommerville, Ch. 12 & 13, 5 th edition and Ch. 10, 6 th edition.
Distributed Software Engineering Lecture 1 Introduction Sam Malek SWE 622, Fall 2012 George Mason University.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
NAVEEN AGENT BASED SOFTWARE DEVELOPMENT. WHAT IS AN AGENT? A computer system capable of flexible, autonomous (problem-solving) action, situated in dynamic,
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Architectural Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Chapter 6 Architectural Design.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Refining middleware functions for verification purpose Jérôme Hugues Laurent Pautet Fabrice Kordon
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
Bio-Networking: Biology Inspired Approach for Development of Adaptive Network Applications 21 May 2005Ognen Paunovski Bio-Networking: Biology Inspired.
VII Applications Mike Schagrin, VII Applications Manager ITS Joint Program Office Research & Innovative Technology Administration USDOT Mike Schagrin,
VII Applications Mike Schagrin, VII Applications Manager ITS Joint Program Office Research & Innovative Technology Administration USDOT Mike Schagrin,
1 Object Oriented Logic Programming as an Agent Building Infrastructure Oct 12, 2002 Copyright © 2002, Paul Tarau Paul Tarau University of North Texas.
Multiagent System Katia P. Sycara 일반대학원 GE 랩 성연식.
Energy-Aware Resource Adaptation in Tessellation OS 3. Space-time Partitioning and Two-level Scheduling David Chou, Gage Eads Par Lab, CS Division, UC.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Extraction Tools and Relational Database Schemas for CVS, SVN, and Bazaar Revision Control Systems.
Self-Organizing Architectures SOAR 2010 International Conference on Autonomic Computing and Communication, ICAC Washington DC, USA June 7, 2010.
Satellite MAS Position Statement FOSE-MAS 2008 – Danny Weyns.
NCP Info DAY, Brussels, 23 June 2010 NCP Information Day: ICT WP Call 7 - Objective 1.3 Internet-connected Objects Alain Jaume, Deputy Head of Unit.
Chapter : 9 Architectural Design
April 25, 2006Parag Mhashilkar, Fermilab1 Resource Selection in OSG & SAM-On-The-Fly Parag Mhashilkar Fermi National Accelerator Laboratory Condor Week.
An Architecture-Centric Approach for Software Engineering with Situated Multiagent Systems PhD Defense Danny Weyns Katholieke Universiteit Leuven October.
UCI Large-Scale Collection of Application Usage Data to Inform Software Development David M. Hilbert David F. Redmiles Information and Computer Science.
HRM A: Tutorial job analysis © ETH Zürich | Taskforce Kommunikation.
Database Development (8 May 2017).
Selected ICT-based Wide-Area Monitoring Protection and Control Systems (WAMPAC) applications
IS301 – Software Engineering Dept of Computer Information Systems
CHAPTER 3 Architectures for Distributed Systems
Algorithm Design.
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Decomposing the System
Software Architecture
Design Yaodong Bi.
Chapter 6: Architectural Design
Design.
Presentation transcript:

1 4 January 2016 Architectural Design of a Distributed Application with Autonomic Quality Requirements DEAS St. Louis, USA, May 21 th, 2005 Danny Weyns, Kurt Schelfthout and Tom Holvoet University of Leuven, Belgium

2 4 January 2016 A challenging application AGV transportation system

3 4 January 2016 Traditional approach Centralized architecture oServer assigns transports to AGVs oServer plans routes etc. oVehicles are controlled by central server oLow level control AGVs is handled by E’nsor software Main non-functional properties oConfigurability (server is central configuration point) oPredictability (server manages execution of functionality)

4 4 January 2016 Aiming for new quality requirements AGVs are expected to be flexible and adapt their behavior autonomously with changing circumstances oExploit opportunities  Switch jobs when driving to a load when a more interesting transport pops up oAnticipate possible difficulties  Prefer jobs near to a battery charging station when battery needs to be charged in the near future oCope with particular situations  Choose the farthest load in the corridor

5 4 January 2016 Aiming for new quality requirements System is expected to deal with openness oAGVs leave/enter the system, e.g. for maintenance oCustomers intervene during execution of the system We investigate the feasibility of a decentralized architecture aiming to cope with these new quality requirements Joint R&D project between AgentWise research group and Egemin This talk: overview basic architecture of the system

6 4 January 2016 Overview Situated multiagent systems for the AGV transportation system A trace through the architectural design Round-up

7 4 January 2016 Situated multiagent systems What is a situated multiagent system (MAS)? oSet of autonomous entities (agents) explicitly situated in a shared structure (an environment) oAgents select actions “here and now”, they do not use long term planning (locality in time and space) oInteraction is at the core of problem solving (rather than individual capabilities) Decentralized control Adaptive behavior Collective behavior

8 4 January 2016 A situated MAS for the AGV transportation system Motivations for situated MAS Matching quality properties Situated MAS are a promising approach to build flexible, adaptable, open systems Matching characteristics  Locality in time and space: order assignment to idle AGV near to load, collision avoidance, etc.  Interaction at the core of problem solving: load manipulation, collision avoidance, etc.

9 4 January 2016 Reference architecture as a guidance for architectural design oEmbodies knowledge and experiences acquired during 4 years of research oServes as a reusable architectural design artifact oWe developed design guidelines for specific modules, e.g., decision making with free-flow architectures Reference architecture for situated MASs

10 4 January 2016 High-level overview of the reference architecture

11 4 January 2016 Overview Situated multiagent systems for the AGV transportation system A trace through the architectural design Round-up

12 4 January 2016 Deployment view of the decentralized architecture

13 4 January 2016 Top level module decomposition: situated MAS

14 4 January 2016 Module view of the environment: layers  Separate functionality, support reuse

15 4 January 2016 Virtual environment is a distributed entity

16 4 January 2016 Physical Environment

17 4 January 2016 Virtual Environment

18 4 January 2016 The virtual environment Offers a medium to agents to exchange information and coordinate their behavior Synchronizing state of the virtual environment oVirtual environment as software entity does not exist  Virtual environment is necessary distributed over the AGVs  ObjectPlaces middleware keeps state of local virtual environment synchronized with virtual environments of local AGVs

19 4 January 2016 AGV agents: data repository  Separation of concerns, loose coupling

20 4 January 2016 AGV agents: blackboard with sequential processing  Decision making at different levels of abstraction, separation of concerns  Feedback for flexible decision making

21 4 January 2016 Overview Situated multiagent systems for the AGV transportation system A trace through the architectural design Round-up

22 4 January 2016 The challenge continues Project status (after 1.2 of 2 years) o2 real AGVs manipulate loads, drive around and avoid collisions in an industrial test set-up (basics for deadlock prevention) oThe same for n AGvs in a simulated setup Current work oMethodological evaluation of software architecture: ATAM planned June oOrder assignment and deadlock avoidance Next challenges oExplore and validate flexibility, adaptability, scalability oGive guarantees about global behavior

23 4 January 2016 Lessons learned oWe learned the real value of our research by applying it in real-world application  We experienced what “application-driven research” is about oThe reference architecture serves as an excellent guidance for the architectural design oStakeholders not involved in the daily development tend to overestimate the agent metaphor