Honeysuckle logo

Links:


A number of papers have been published, from 2001 onwards, that discuss either motivations for or aspects of Honeysuckle. Where copyright permits, a link is provided to a copy ofeach paper (Adobe PDF).

East, I. R.: 2001, Towards a Successor to occam, Proceedings of Communicating Process Architecture 2001, University of Bristol, UK, A. Chalmers et al. (Eds.), pp. 231-241. IOS Press. ISBN 1-58603-202-X.

A review of the strengths and weaknesses in the occam process-oriented programming language, with regard to commercial exploitation for embedded systems development. The inefficiency of copying large data structures between processes, and weak data abstraction, are identified as chief weaknesses. The threat of deadlock, and other pathological behaviour, are also identified as by far the most serious disincentives towards communicating-process architecture.

East, I. R.: 2002, Programming Prioritized Alternation, Proceedings of The 2002 International Conference on Parallel and Distributed Processing Techniques and Applications (PDPTA ‘02), Las Vegas, H. A. Arabnia (Ed.), pp. 531-537. CSREA Press. ISBN 1-892512-88-2.

Arguments are presented in favour of a new prioritized alternation programming construct that expresses pre-emptive response to external events. Semantics are discussed with regard to existing operators in Hoare's CSP.

East, I. R.: 2003, The “Honeysuckle” Programming Language: An Overview, IEE Proc. Software, 150, 2, pp. 95-107.

A comprehensive overview of Honeysuckle, though the syntax has evolved slightly since publication (refer to Draft Manual). The concern here is strictly the programming language. Little is said about its formal foundation.

East, I. R.: 2004, Prioritised Service Architecture, Proceedings of Communicating Process Architecture 2004, Oxford Brookes University, Ian East et al. (Eds.), pp. 55-69. IOS Press. ISBN 1-58603-458-8.

An account of the formal foundation of Honeysuckle, including the formal conditions that define service protocol and a service network component, and the formal design rule which excludes deadlock and livelock.

East, I. R.: 2004, Towards a Semantics for Prioritized Alternation, Proceedings of Communicating Process Architecture 2004, Oxford Brookes University, Ian East et al. (Eds.), pp. 55-69. IOS Press. ISBN 1-58603-458-8.

Discusses the problem of attributing a formal semantics to prioritized alternation, including the capture of prioritized parallel composition in Timed CSP, and a recently proposed alternative semantics for (untimed) CSP.

East, I. R.: 2005, Interfacing with Honeysuckle by Formal Contract, Proceedings of Communicating Process Architecture 2005, Technische Universiteit Eindhoven, The Netherlands, Jan F. Broenink et al. (Eds.). pp. 1-12. IOS Press. ISBN 1-58603-561-4.

Presents a syntax for expressing a service interface to a component process, and discusses sharing in consuption, distribution of provision, and mutual exclusion.

East, I. R.: 2007, Concurrent/Reactive System Design with Honeysuckle, Proceedings of Communicating Process Architecture 2007, University of Surrey, A. A. McEwan, S. Schneider et al. (Eds.). pp. 15-25.  IOS Press.

Shows how design and implementation may be separated using Honeysuckle. A syntax is presented for the expression of design using the prioritized service model for communicating-process architecture.

East, I. R.: 2008, Prioritized Service Architecture: Refinement and Visual Design, Proceedings of Communicating Process Architecture 2008, University of York, Susan Stepney, Fiona Polack, Alistair McEwan, Peter Welch, and Wilson Ifill (Eds.). IOS Press.

Prioritized service architecture is refined to enable verification of design rule that guarantees deadlock freedom independent of any implementation. A visual design language is presented with a one-to-one correspondence with the textual one.

 

 

Home

Progress

Draft manual

Publications

Tutorial

Tools

    Contact : Dr Ian East

Page last modified: 3rd September 2008
Pages copyright: Dr Ian Robert East