A well-defined boundary of components allows to encapsulate internal state and to dis tinguish between internal calls that remain inside the component and external calls that have target objects outside the component. From a static point of view, such boundaries define the programmer's interface to the component. In particular, they define the methods that can be called on the component. From a dynamic point of view, the boundaries separate the component state and those parts of the program state outside the component. In this tutorial paper, we investigate encapsulated components that are realized based on object-oriented concepts. We define a semantics that captures a flexible notion of hierarchical encapsulation with confined references. The semantics generalizes the encapsulation concepts of ownership types. It is used as a foundation for modular behavioral component specifications. In particular, it allows to provide a simple semantics for invariants and an alternative solution for the frame problem. We demonstrate this new specification methodology by typical programming patterns. © Springer-Verlag Berlin Heidelberg 2006.
CITATION STYLE
Poetzsch-Heffter, A., & Schäfer, J. (2006). Modular specification of encapsulated object-oriented components. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 4111 LNCS, pp. 313–341). Springer Verlag. https://doi.org/10.1007/11804192_15
Mendeley helps you to discover research relevant for your work.