A behavioral notion of subtyping
ACM Transactions on Programming Languages and Systems (TOPLAS)
Unreliable failure detectors for reliable distributed systems
Journal of the ACM (JACM)
Developing multi-agent systems with a FIPA-compliant agent framework
Software—Practice & Experience
Dynamic weaving for aspect-oriented programming
AOSD '02 Proceedings of the 1st international conference on Aspect-oriented software development
5th ICSE workshop on component-based software engineering: benchmarks for predictable assembly
Proceedings of the 24th International Conference on Software Engineering
Framework-Based Applications: From Incremental Development to Incremental Reasoning
ICSR-6 Proceedings of the 6th International Conerence on Software Reuse: Advances in Software Reusability
Dynamically reconfigurable parameterized components
Dynamically reconfigurable parameterized components
The spec# programming system: an overview
CASSIS'04 Proceedings of the 2004 international conference on Construction and Analysis of Safe, Secure, and Interoperable Smart Devices
GenQA: automated addition of architectural quality attribute support for Java software?
Proceedings of the 2009 ACM symposium on Applied Computing
| Hi-index | 0.00 |
Software containers present an effective mechanism for decoupling cross-cutting concerns in software. System-wide concerns such as persistence, transaction management, security, fault masking, etc., are implemented as container services. While a lot of effort has been expended in developing effective container implementations, specifications for software containers are largely presented in informal natural language, which hampers predictable reasoning about the behavior of components deployed within containers. In this paper, we present a formal model for reasoning about the behavior of software containers. Our model allows developers to reason precisely about how the behaviors of software components deployed within a container are modified by the container. We further present the specifications of a few examples of container services that are found in different container implementations, and use our formal model to prove the correctness of the behavioral transformations that these services cause.