Improving the development process for teleo-reactive programming through advanced composition

J. Hawthorne, R. Anthony, Miltiadis Petridis

Research output: Chapter in Book/Conference proceeding with ISSN or ISBNConference contribution with ISSN or ISBNpeer-review

Abstract

Teleo-Reactive programming as applied to autonomic systems is both a viable and exciting prospect as it inherently recovers from errors and unexpected events whilst proceeding towards its goal. It does this without the need to know in advance, the specific events which might occur, thus greatly reducing the human maintenance element. Whilst the benefits of this technique are great once the program has been composed, the challenge of validation attached to these programs also increases. We aim to ease the composition process needed when constructing T-R programs by building new abilities in to our existing Teleo-Reactive framework. Firstly, these new abilities will make it possible to detect validation issues at design time, thus reducing the likelihood of problems and increasing the ease of detecting them. Secondly, it will be possible for programs to be automatically composed from existing elements, thus further reducing the cost of validation issues. These ideas can even be extended to allow for dynamic composition and runtime changes to goals and actions.
Original languageEnglish
Title of host publicationThe Seventh International Conference on Autonomic and Autonomous Systems
Place of PublicationVenice/Mestre, Italy
PublisherIARIA
Pages75-80
Number of pages6
ISBN (Print)9781612081342
Publication statusPublished - 22 May 2011
EventThe Seventh International Conference on Autonomic and Autonomous Systems - Venice, Italy, 22-27 May, 2011
Duration: 22 May 2011 → …

Conference

ConferenceThe Seventh International Conference on Autonomic and Autonomous Systems
Period22/05/11 → …

Fingerprint

Dive into the research topics of 'Improving the development process for teleo-reactive programming through advanced composition'. Together they form a unique fingerprint.

Cite this