loading...
Reactive Types for Dataflow-Oriented Software Architectures
Oslo, Norway June 12-June 15
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/WICSA.2004.1310704Fourth Working IEEE/IFIP Conference o ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Barry Norton, University of Sheffield, UK
Matt Fairtlough, University of Sheffield, UK
Digital signal-processing (DSP) tools, such as Ptolemy, LabView and iConnect, allow application developers to assemble reactive systems by connecting pre-defined components in generalised dataflow graphs and by hierarchically building new components by encapsulating sub-graphs. We follow the literature in calling this approach dataflow-oriented development. Our previous work has shown how a new process calculus, uniting ideas from previous systems within a compositional theory, can be formally shown to capture the properties of such systems. This paper first re-casts the graphical dataflow-oriented style of design into an underlying textual architecture design language (ADL) and then shows how the previous modelling approach can be seen as a system of process-algebraic behavioural types for such a language, so that type-checking is the mechanism used to statically diagnose the reactivity of applications. We show how both the existing notion of behavioural equivalence and a new behavioural pre-order are involved in this judgement.
Citation:
Barry Norton, Matt Fairtlough, "Reactive Types for Dataflow-Oriented Software Architectures," wicsa, pp.211, Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA'04), 2004
Usage of this product signifies your acceptance of the Terms of Use.


Suggestions