Sebastian Smith ○ Lance Hutchinson ○ Ben Damonte ○ Jennifer Knowles ○ Dr. Monica Nicolescu ○ Dr. Sergiu Dascalu Department of Computer Science and Engineering,

Slides:



Advertisements
Similar presentations
TSpaces Services Suite: Automating the Development and Management of Web Services Presenter: Kevin McCurley IBM Almaden Research Center Contact: Marcus.
Advertisements

Chapter 13 Review Questions
An evolutionary approach to G-MPLS ensuring a smooth migration of legacy networks Ben Martens Alcatel USA.
8.
Computer Science – Game DesignUC Santa Cruz Today Publish/Subscribe Design Pattern Delegates Sprite movement Particles.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering Vahid Jalali Amirkabir university of technology, Department of computer.
Delegates & Events Observer and Strategy Patterns Game Design Experience Professor Jim Whitehead January 30, 2009 Creative Commons Attribution 3.0 creativecommons.org/licenses/by/3.0.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
PROGRESS project: Internet-enabled monitoring and control of embedded systems (EES.5413)  Introduction Networked devices make their capabilities known.
MERTIS: Modifiable, Extensible, Real-Time, Interactive Simulation Leandro Basallo ◦ Ryan Leigh ◦ Sam Talaie ◦ Regan Snyder with Dr. Sergiu Dascalu and.
Establishing the overall structure of a software system
V-FIRE: Virtual Fire In Realistic Environments Michael Penick ◦ Grant Kelly ◦ Juan Quiroz with Dr. Fred Harris, Dr. Sergiu Dascalu, and Brian Westphal.
Abstract The University Class Scheduler (U.C.S) is an innovative scheduling tool. It is intended to be used by major Universities to schedule classes into.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Towards.
Architectural Design, Distributed Systems Architectures
Course Instructor: Aisha Azeem
Distributed Systems: Client/Server Computing
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Ricerca Distribuita Semantica Protocolli opensource per la condivisione di risorse online.
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
SensIT PI Meeting, January 15-17, Self-Organizing Sensor Networks: Efficient Distributed Mechanisms Alvin S. Lim Computer Science and Software Engineering.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 13Slide 1 Architectural Design u Establishing the overall structure of a software system.
1 CMPT 275 High Level Design Phase Architecture. Janice Regan, Objectives of Design  The design phase takes the results of the requirements analysis.
An Introduction to Software Architecture
POAD Distributed System Case Study: A Medical Informatics System Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Architectural Design portions ©Ian Sommerville 1995 Establishing the overall structure of a software system.
A Spring 2005 CS 426 Senior Project By Group 15 John Studebaker, Justin Gerthoffer, David Colborne CSE Dept., University of Nevada, Reno Advisors (CSE.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
9 September 2008CIS 340 # 1 Topics reviewTo review the communication needs to support the architectures variety of approachesTo examine the variety of.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
©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.
Distributed Systems and Algorithms Sukumar Ghosh University of Iowa Spring 2011.
Software Engineering CSC 342/Dr. Ghazy Assassa Chapter 10, Architectural Design “Sommerville +.. “ Slide 1 CSC 342 Semester II: H ( G)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
 Repository Model  Client-Server Model  Layered Model  Modular decomposition styles  Object Models  Function Oriented Pipelining  Control Styles.
A Software Solution for the Control, Acquisition, and Storage of CAPTAN Network Topologies Ryan Rivera, Marcos Turqueti, Alan Prosser, Simon Kwan Electronic.
Dale Roberts Object Oriented Programming using Java - Introduction Dale Roberts, Lecturer Computer Science, IUPUI Department.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 11 Slide 1 Architectural Design.
CSC480 Software Engineering Lecture 10 September 25, 2002.
INTRODUCTION GORT is a virtual 3D modeling environment for computer programmers. Its main area of focus is to aid in the education of programmers learning.
1 Object Oriented Logic Programming as an Agent Building Infrastructure Oct 12, 2002 Copyright © 2002, Paul Tarau Paul Tarau University of North Texas.
©Ian Sommerville, Robin Abraham 2004CS 361, Summer 2004 Slide 1 Architectural Design.
The Mediator Pattern (Behavioral) ©SoftMoore ConsultingSlide 1.
Chapter 14 Advanced Architectural Styles. Objectives Describe the characteristics of a distributed system Explain how middleware supports distributed.
RIA to visualize the health of a project Team #4 Midterm presentation February 28,2008.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
Lecture VIII: Software Architecture
CS223: Software Engineering Lecture 14: Architectural Patterns.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
An Architecture-Centric Approach for Software Engineering with Situated Multiagent Systems PhD Defense Danny Weyns Katholieke Universiteit Leuven October.
Slide 1 Chapter 8 Architectural Design. Slide 2 Topics covered l System structuring l Control models l Modular decomposition l Domain-specific architectures.
Chapter 9: Relationships Chapter 10: Inheritance and Polymorphism [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of Nevada,
Efficient Opportunistic Sensing using Mobile Collaborative Platform MOSDEN.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Roslyn: A Tour Guide Robot Jared Rhizor, Timothy Sweet, Nishok Yadav Advisor: Dr. David Feil-Seifer Instructor: Dr. Sergiu Dascalu Department of Computer.
Dr D. Greer, Queens University Belfast ) Software Engineering Chapter 7 Software Architectural Design Learning Outcomes Understand.
An evolutionary approach to G-MPLS ensuring a smooth migration of legacy networks Ben Martens Alcatel USA.
Where are we ? Setup Sprites Input Collision Drawing Sprites
IS301 – Software Engineering Dept of Computer Information Systems
A Framework for Object-Based Event Composition in Distributed Systems
Part 3 Design What does design mean in different fields?
Princess Nourah bint Abdulrahman University
An Introduction to Software Architecture
Computer Networking A Top-Down Approach Featuring the Internet
Distributed Systems and Algorithms
Presentation transcript:

Sebastian Smith ○ Lance Hutchinson ○ Ben Damonte ○ Jennifer Knowles ○ Dr. Monica Nicolescu ○ Dr. Sergiu Dascalu Department of Computer Science and Engineering, University of Nevada, Reno This project was developed in 2005/2006 as part of the course CS426/CPE426 Senior Projects Abstract The behavior-based robot control paradigm is a mature method for implementing intelligent robot controllers. This technique uses the interactions of simple behaviors to produce complex emergent behaviors - behaviors that are observed externally that were not explicitly programmed into the system. While highly flexible, behavior-based systems are often difficult to implement. Society was designed to ease the workload of developers by abstracting away the creation of behavior networks through application of the publish/subscribe communication paradigm. Conclusions Future Work Behavior Network and System Diagram Behavior Networks Behavior-based systems are a proven method of robot control that uses the interactions of simple behaviors to produce complex emergent behaviors that were not explicitly programmed into the system. The term “behavior” is abstract, and may be defined as any simple function of a robot. Complexity arises from simple behaviors when they are interconnected into a network. Since each behavior is a distinct computational unit, behavior-based systems lend themselves to distribution. The top diagram within the leftmost figure above depicts a traditional behavior network. Publish/Subscribe Publish/Subscribe is a communication paradigm in which subscribers register interest in an event and are notified as it is generated by a publisher. Since events serve as the communication medium between publishers and subscribers, neither requires knowledge of the underlying network topology. Rather, both communicate through an event notification system that routes packets between publishers and subscribers. Because of this loosely coupled nature the publish/subscribe communication paradigm is highly scalable, easily distributed, and high-performance. Society Society merges behavior-based control and the publish/subscribe communication paradigm. It utilizes a centralized server to route event data from producer behaviors to subscriber behaviors via the transmission control protocol. It provides an easy-to-use client application program interface that allows developers to rapidly develop complex behavior networks, and coordinate multi-agent robot teams. The leftmost figure above depicts the contrast between a traditional and Society-based behavior network. The rightmost figure above is a system diagram of Society. Behavior-based systems and the publish/subscribe communication paradigm are structurally complimentary. The distributed, loosely coupled nature of behavior-based systems closely models the publisher and subscriber roles of the publish/subscribe paradigm. While early in its development cycle, Society promises a robust feature set that will allow researchers to easily coordinate multi-agent robot teams, better utilize computing resources, and practice extensive code reuse. The high-performance nature of the publish/subscribe paradigm will also allow behavior networks to scale to currently unreachable degrees of complexity. Society will be developed as part of Sebastian Smith’s graduate work at the University of Nevada, Reno. As the project becomes stable it will be released free under the GNU Public License. Future features will include an advanced emergency response subsystem, dynamic distribution of behaviors via network interface, user datagram protocol support, stream control transmission protocol support, and an advanced diagnostics suite. The Society framework will also be used in multi-robot applications to demonstrate its advantages over existing coordination/communication approaches.