Skip to main content

3.1 Self-* Software Architectures and Component Middleware in Pervasive Environments

George Edwards, University of Southern California
Chiyoung Seo,
University of Southern California
Daniel Popescu,
University of Southern California
Sam Malek, George Mason University
Nenad Medvidovic,
University of Southern California

Abstract

Software systems that execute in embedded and pervasive environments are frequently required to be self-monitoring, self-adapting, and self-healing. However, supporting these self-* capabilities in pervasive environments creates a number of unique engineering challenges. This paper first describes the challenges that we believe to be the most significant based on our experience developing real-world pervasive software applications with self-* capabilities. We then discuss each challenge in the context of four strategies commonly employed in self-* systems: dynamic software update, service discovery, transparent replication, and logical mobility. Finally, we explain how each strategy is implemented in our architectural middleware platform, Prism-MW.

ACM Copyright Notice Copyright © by the Association for Computing Machinery, Inc. Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, to republish, to post on servers, or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from Publications Dept, ACM Inc., fax +1 (212) 869-0481, or permissions@acm.org.

Comments

Popular posts from this blog

Best Paper

Update: Sorry about that -- didn't realize this got posted initially with no content. As Steve pointed out in comments, the votes were close. After tallying the online voting with in-attendance votes (from those who didn't make the online poll before it closed), Todor made a strong comeback but Ian Wakeman et. al. finally triumphed with a 9-7 edge. Congratulations to them, and we look forward to seeing you all again next year.

Posting abstracts for papers ..

The workshop is just over ten days away. In preparation for the discussions, and also to get the attendees more conversant with the researchers and papers to be presented, we will be posting the abstracts for accepted papers (one per blog item) over the next few days. If you are the author of a paper, and want to add links in to related research or a personal website for more information, please feel free to do so. For convenience, the blog posting will be prefixed with a number of the form S.P, where S is the session number (1, 2 or 3) and P is the paper number within that session. Each session will conclude with a panel focussed on discussion around the papers presented. In that context, if you have specific questions for authors, or have comments on the topic -- feel free to post them against the relevant blog items.. Update: I'm just waiting on some clarifications from ACM before I release the abstracts... do check back. Update: ACM granted us permissions -- the abstracts will...

About the "1 minute madness" ...

As you may have noticed in the workshop program , we have a final 30-minute plenary discussion to close out the workshop. In order to make this as interactive and useful as possible, we decided to preface this with a 20-minute session called "1-minute madness". Some of you may have seen this forum before at other workshops. Basically, this is a soapbox of sorts -- anyone (presenters, organizers, attendees) is welcome to participate and provide fodder for the follow-up discussion. The idea is to make a 1-minute pitch about a topic of interest. You may elect to use slides or not - if the former, a single slide is ideal but you can use your discretion here. For convenience, here are some possible 'themes' for the pitch. These are suggestions only: Research in a nutshell . What problem are you trying to solve? Why is it important? What makes your solution novel? Hot Topics . What should the MPAC community's next big research challenge be? Why? Experience Lessons . S...