Understanding DCE
Middleware: a model for distributed system services
Communications of the ACM
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Software engineering and middleware: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Formal specification of CORBA services: experience and lessons learned
OOPSLA '00 Proceedings of the 15th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
A formal specification of the CORBA event service
Fourth International Conference on Formal methods for open object-based distributed systems IV
Safe 'composability' of middleware services
Communications of the ACM - Adaptive middleware
On the role of middleware in architecture-based software development
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
Managing Complexity: Middleware Explained
IT Professional
A Formal Analysis of the CORBA Security Service
ZB '02 Proceedings of the 2nd International Conference of B and Z Users on Formal Specification and Development in Z and B
Formal Specification of CORBA Services using Object-Z
ICFEM '98 Proceedings of the Second IEEE International Conference on Formal Engineering Methods
A formal approach to software architecture
A formal approach to software architecture
An architecture for next generation middleware
Middleware '98 Proceedings of the IFIP International Conference on Distributed Systems Platforms and Open Distributed Processing
A formal framework for middleware behavioural specification
ACM SIGSOFT Software Engineering Notes
A LOTOS framework for middleware specification
FORTE'06 Proceedings of the 26th IFIP WG 6.1 international conference on Formal Techniques for Networked and Distributed Systems
| Hi-index | 0.00 |
The number of open specifications of middleware systems and middleware services is increasing. Despite their complexity, they are traditionally described through APIs (the operation signatures) and informal prose (the behaviour). This fact often leads to ambiguities and makes difficult a better understanding of what is really described. In this paper, we adopt software architecture principles for structuring middleware together the LOTOS language for formalising their behaviour. The adoption of software architecture principles makes explicit structural aspects of the middleware. Meanwhile, the formalisation enables us to check behavioural properties of the middleware. In order to illustrate our approach, we present a LOTOS specification of the well-known object-oriented middleware CORBA and its transaction service.