No abstract

We address in this paper the need to develop appropriate notations for the QoSaware specification of the ODP (Open Distributed Processing) enterprise viewpoint. The Unified Modelling Language (UML) is currently emerging as de facto standard for formal object-oriented modelling. Several approaches are being used in the field of the formalization ofUML. For several reasons, we use the metamodelling approach in our work. We analyze the QoS concepts defined in QoS foundation modelling concepts part and in the QoS in enterprise specification part. The result is an UML meta-model of the core QoS concepts and their relationships, which is considered as the abstract syntax of a concrete language for QoS-aware ODP enterpn•se specifications.

No abstract

Abstract:-In this work we raise two issues that we came across when aiming to formalize both interaction signatures and action templates within the ODP computational viewpoint. We discuss these two concepts and present a way to formalize them by introducing a new term to formal descriptions of interaction signatures. In the same spirit as other works, our aim is to address issues concerning how concepts of the ODP computational viewpoint are currently defined as we present some solutions to their formalisation. If required, our work aim to serve as a step to help improve or change the current process of formalizing the ODP computational viewpoint concepts using the UML language.

Monitoring telecommunications systems is of a crucial importance. Nowadays, PBX software packages can be configured to allow the storage of Call Detail Records in a database. There is a permanent need to analyze those records and allow business owners to detect PBX misuse from inside and outside the company. The word "misuse" covers an employee making too many personal phone calls, a salesman making fewer phone calls than expected, a client making an excessive number of phone calls, and other suspicious calls. A data-mining package or any other analytical tool would not be as efficient because it would report what happened when it is too late to take action. In this article, we integrate Asterisk with a rule-based engine called InRule. Asterisk will consult InRule whenever a call is about to be made and thus take appropriate actions.