The object constraint language: precise modeling with UML
The object constraint language: precise modeling with UML
N degrees of separation: multi-dimensional separation of concerns
Proceedings of the 21st international conference on Software engineering
Model checking
Achieving Extensibility Through Product-Lines and Domain-Specific Languages: A Case Study
ICSR-6 Proceedings of the 6th International Conerence on Software Reuse: Advances in Software Reusability
Assume-Guarantee Model Checking of Software: A Comparative Case Study
Proceedings of the 5th and 6th International SPIN Workshops on Theoretical and Practical Aspects of SPIN Model Checking
Implementing Layered Designs with Mixin Layers
ECCOP '98 Proceedings of the 12th European Conference on Object-Oriented Programming
Modular Model Checking of Software
TACAS '98 Proceedings of the 4th International Conference on Tools and Algorithms for Construction and Analysis of Systems
COMPOS'97 Revised Lectures from the International Symposium on Compositionality: The Significant Difference
Model Checking and Modular Verification
CONCUR '91 Proceedings of the 2nd International Conference on Concurrency Theory
Interface Compatibility Checking for Software Modules
CAV '02 Proceedings of the 14th International Conference on Computer Aided Verification
Handling Consistency of Software Evolution in an Efficient Way
IWPSE '04 Proceedings of the Principles of Software Evolution, 7th International Workshop
| Hi-index | 0.00 |
Open systems capable of handling unanticipated future changes are very desirable. A common approach towards open systems is based on components. There are some essential issues of the component-based software paradigm. First, the most challenging analysis issue is about component consistency – namely a component does not violate some property in another when composed. The paper presents a formal approach to the issue by including consistency semantic to component specification. Based on this semantic information, components can be efficiently cross-checked for the consistency among components. The second issue is on how components are realized from the formal specification. The layered architecture is recommended for component-based system design in which component specifications are separated into layers. Subsequently, each layer can be then respectively implemented by a corresponding module via aspect-oriented programming. The target system simply involves composing those modules together in a well-defined order.