Abstract
Abstract 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, whilst making difficult a better understanding of what is actually described. In this paper, we adopt software architecture principles for structuring middleware specifications together with LOTOS 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..
Highlights
The number of open specifications of middleware systems [5][27] is rapidly increasing
We present an approach for structuring the middleware architecture using software architecture principles [22]
This paper has illustrated how to adopt software architecture concepts together with the formal description technique LOTOS in order to describe the behaviour of middleware systems
Summary
The number of open specifications of middleware systems [5][27] is rapidly increasing. Developers who want to implement those services have a hard task to produce a final product by interpreting what the specifications describe. In this context, we present an approach for structuring the middleware architecture using software. The Z notation and High Level Petri Nests have been adopted for specifying CORBA services [3], Naming service [13], Event service [4] and Security service [2] All those works, do not adopt software architecture principles for structuring the service descriptions. The last section presents the conclusions and some directions for future work
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.