Abstract

at "components" and "frameworks" might entail. Otherwise, we have little hope of getting a useful model because the prevailing component architectures in software engineering are not suitable for embedded systems. Most frameworks have four service categories: . Ontology. A framework defines what it means to be a component. Is a component a subroutine? A state transformation? A process? An object? An aggregate of components may or may not be a component. Certain semantic properties of components also flow from the definition. Is a component active or passive---can it autonomously initiate interactions with other components or does it simply react to stimulus? . Epistemology. A framework defines states of knowledge. What does the framework know about the components? What do components know about one another? Can components interrogate one another to obtain information (that is, is there reflection or introspection)? What do components know<F1

Citations

1008	A Model of Concurrent Computation in Distributed Systems - Agha - 1986
725	the Ordering of Events in a Distributed System - Time - 1978
378	The theory of hybrid automata - Henzinger - 1996
244	Formalizing architectural connection - Allen, Garlan - 1994
208	A framework for comparing models of computation - Lee, Sangiovanni-Vincentelli - 1998
99	Hierarchical finite state machines with multiple concurrency models - Girault, Lee, et al. - 1999
78	Guernic, “Hybrid Dynamical Systems Theory and the Signal Language - Benveniste, Le - 1990
70	Combinatorics and partially ordered sets - Trotter - 1992
42	et al. STATEMATE: A Working Environment for the Development of Complex Reactive Systems - Harel - 1990
21	Scripting: Higher Level Programming for the 21st - Ousterhout - 1998
5	Constructive Mathematics and Computer - Martin-Löf - 1980
2	Orbit—A Framework for High Assurance System Design and Analysis - Abu-Ghazaleh - 1998