The Experts below are selected from a list of 219 Experts worldwide ranked by ideXlab platform
Iman Poernomo - One of the best experts on this subject based on the ideXlab platform.
-
QoS-aware model driven architecture through the UML and CIM
Information Systems Frontiers, 2007Co-Authors: Kenneth Chan, Iman PoernomoAbstract:The specification of Quality of Service (QoS) constraints over software design requires measures that ensure such requirements are met by the delivered product. Achieving this goal is non-trivial, as it involves, at least, identifying how QoS constraint specifications should be checked at the runtime. In this paper we present an implementation of a Model Driven Architecture (MDA) based framework for the runtime monitoring of QoS properties. We incorporate the UML2 superstructure and the UML profile for Quality of Service to provide abstract descriptions of component-and-connector systems. We then define transformations that refine the UML2 models to conform with the Distributed management Taskforce (DMTF) Common Information Model (CIM) (Distributed management Task Force Inc. 2006 ), a schema standard for management and instrumentation of hardware and software. Finally, we provide a mapping the CIM metamodel to a .NET-based metamodel for implementation of the monitoring infrastructure utilising various .NET features including the windows management instrumentation (WMI) interface.
-
EDOC - QoS-Aware Model Driven Architecture through the UML and CIM
2006 10th IEEE International Enterprise Distributed Object Computing Conference (EDOC'06), 2006Co-Authors: Kenneth Chan, Iman PoernomoAbstract:The specification of quality of service (QoS) constraints over software design requires measures that ensure such requirements are met by the delivered product. Achieving this goal is non-trivial, as it involves, at least, identifying how QoS constraint specifications should be checked at the runtime. In this paper we present an implementation of a model driven architecture (MDA) based framework for the runtime monitoring of QoS properties. We incorporate the UML2 superstructure and the UML profile for quality of service to provide abstract descriptions of component-and-connector systems. We then define transformations that refine the UML2 models to conform with the distributed management taskforce (DMTF) common information model (CIM) (2006), a schema standard for management and instrumentation of hardware and software. Finally, we provide a mapping the CIM metamodel to a .NET-based metamodel for implementation of the monitoring infrastructure utilising various .NET features including the windows management instrumentation (WML) interface
-
QoSA/SOQUA - A model-oriented framework for runtime monitoring of nonfunctional properties
Lecture Notes in Computer Science, 2005Co-Authors: Kenneth Chan, Heinz Schmidt, Iman Poernomo, James JayaputeraAbstract:It is now recognized that nonfunctional properties are important to practical software development and maintenance. Many of these properties involve involving time and probabilities – for example, reliability and availability. One approach to ensuring conformance to nonfunctional requirements is the use of runtime monitoring. Currently, such monitoring is done in one of two ways: 1) monitoring through use of a generic tool or 2) by adding instrumentation code within system software and writing a tool to manage resulting datasets. The first approach is often not flexible while the second approach can lead to a higher development cost. In this paper, we present a flexible framework for runtime verification of timed and probabilistic nonfunctional properties of component-based architectures. We describe a Microsoft .NET-based implementation of our framework built upon the windows management instrumentation (WMI) infrastructure and the Distributed management Task Force’s Common Information Model standard. We use a language for contracts based on Probabilistic Computational Tree Logic (PCTL). We provide a formal semantics for this language based on possible application execution traces. The semantics is generic over the aspects of an application that are represented by states and transitions of traces. This enables us to use the language to define a wide range of nonfunctional properties.
-
EUROMICRO - Runtime verification of timing and probabilistic properties using WMI and .NET
2004Co-Authors: James Jayaputera, Iman Poernomo, Heinz SchmidtAbstract:Reliability and availability are key issues to distributed service-oriented systems. We present a methodology for run-time verification of reliability and availability properties for distributed architectures. Our approach generalizes the concept of design-by-contract to contracts involving time and probabilities. We define a language for contracts based on probabilistic real time computational tree logic (PCTL). We provide a formal semantics for this language based on possible execution traces of a system. Then we describe a .NET-based system for monitoring contracts, built upon the windows management instrumentation (WMI) framework.
Kenneth Chan - One of the best experts on this subject based on the ideXlab platform.
-
QoS-aware model driven architecture through the UML and CIM
Information Systems Frontiers, 2007Co-Authors: Kenneth Chan, Iman PoernomoAbstract:The specification of Quality of Service (QoS) constraints over software design requires measures that ensure such requirements are met by the delivered product. Achieving this goal is non-trivial, as it involves, at least, identifying how QoS constraint specifications should be checked at the runtime. In this paper we present an implementation of a Model Driven Architecture (MDA) based framework for the runtime monitoring of QoS properties. We incorporate the UML2 superstructure and the UML profile for Quality of Service to provide abstract descriptions of component-and-connector systems. We then define transformations that refine the UML2 models to conform with the Distributed management Taskforce (DMTF) Common Information Model (CIM) (Distributed management Task Force Inc. 2006 ), a schema standard for management and instrumentation of hardware and software. Finally, we provide a mapping the CIM metamodel to a .NET-based metamodel for implementation of the monitoring infrastructure utilising various .NET features including the windows management instrumentation (WMI) interface.
-
EDOC - QoS-Aware Model Driven Architecture through the UML and CIM
2006 10th IEEE International Enterprise Distributed Object Computing Conference (EDOC'06), 2006Co-Authors: Kenneth Chan, Iman PoernomoAbstract:The specification of quality of service (QoS) constraints over software design requires measures that ensure such requirements are met by the delivered product. Achieving this goal is non-trivial, as it involves, at least, identifying how QoS constraint specifications should be checked at the runtime. In this paper we present an implementation of a model driven architecture (MDA) based framework for the runtime monitoring of QoS properties. We incorporate the UML2 superstructure and the UML profile for quality of service to provide abstract descriptions of component-and-connector systems. We then define transformations that refine the UML2 models to conform with the distributed management taskforce (DMTF) common information model (CIM) (2006), a schema standard for management and instrumentation of hardware and software. Finally, we provide a mapping the CIM metamodel to a .NET-based metamodel for implementation of the monitoring infrastructure utilising various .NET features including the windows management instrumentation (WML) interface
-
QoSA/SOQUA - A model-oriented framework for runtime monitoring of nonfunctional properties
Lecture Notes in Computer Science, 2005Co-Authors: Kenneth Chan, Heinz Schmidt, Iman Poernomo, James JayaputeraAbstract:It is now recognized that nonfunctional properties are important to practical software development and maintenance. Many of these properties involve involving time and probabilities – for example, reliability and availability. One approach to ensuring conformance to nonfunctional requirements is the use of runtime monitoring. Currently, such monitoring is done in one of two ways: 1) monitoring through use of a generic tool or 2) by adding instrumentation code within system software and writing a tool to manage resulting datasets. The first approach is often not flexible while the second approach can lead to a higher development cost. In this paper, we present a flexible framework for runtime verification of timed and probabilistic nonfunctional properties of component-based architectures. We describe a Microsoft .NET-based implementation of our framework built upon the windows management instrumentation (WMI) infrastructure and the Distributed management Task Force’s Common Information Model standard. We use a language for contracts based on Probabilistic Computational Tree Logic (PCTL). We provide a formal semantics for this language based on possible application execution traces. The semantics is generic over the aspects of an application that are represented by states and transitions of traces. This enables us to use the language to define a wide range of nonfunctional properties.
James Jayaputera - One of the best experts on this subject based on the ideXlab platform.
-
QoSA/SOQUA - A model-oriented framework for runtime monitoring of nonfunctional properties
Lecture Notes in Computer Science, 2005Co-Authors: Kenneth Chan, Heinz Schmidt, Iman Poernomo, James JayaputeraAbstract:It is now recognized that nonfunctional properties are important to practical software development and maintenance. Many of these properties involve involving time and probabilities – for example, reliability and availability. One approach to ensuring conformance to nonfunctional requirements is the use of runtime monitoring. Currently, such monitoring is done in one of two ways: 1) monitoring through use of a generic tool or 2) by adding instrumentation code within system software and writing a tool to manage resulting datasets. The first approach is often not flexible while the second approach can lead to a higher development cost. In this paper, we present a flexible framework for runtime verification of timed and probabilistic nonfunctional properties of component-based architectures. We describe a Microsoft .NET-based implementation of our framework built upon the windows management instrumentation (WMI) infrastructure and the Distributed management Task Force’s Common Information Model standard. We use a language for contracts based on Probabilistic Computational Tree Logic (PCTL). We provide a formal semantics for this language based on possible application execution traces. The semantics is generic over the aspects of an application that are represented by states and transitions of traces. This enables us to use the language to define a wide range of nonfunctional properties.
-
EUROMICRO - Runtime verification of timing and probabilistic properties using WMI and .NET
2004Co-Authors: James Jayaputera, Iman Poernomo, Heinz SchmidtAbstract:Reliability and availability are key issues to distributed service-oriented systems. We present a methodology for run-time verification of reliability and availability properties for distributed architectures. Our approach generalizes the concept of design-by-contract to contracts involving time and probabilities. We define a language for contracts based on probabilistic real time computational tree logic (PCTL). We provide a formal semantics for this language based on possible execution traces of a system. Then we describe a .NET-based system for monitoring contracts, built upon the windows management instrumentation (WMI) framework.
Alain Lissoir - One of the best experts on this subject based on the ideXlab platform.
-
The WMI Events Scripting
Understanding WMI Scripting, 2003Co-Authors: Alain LissoirAbstract:This chapter examines the various event types available, how they are organized, and how to take full advantage of this technology from the scripting world. This chapter examines windows management instrumentation (WMI) events by explaining the different event types available from WMI and the type of system classes they use. Beside the WMI scripting API used in a script managing WMI events, WMI events can be received only by formulating the right WMI query language (WQL) event query. Without being able to formulate a WQL event query, it is impossible to work with the WMI events. This chapter explores that the event providers and the classes that they implement have an influence at three levels: the way the WQL query is formulated, the retrieved properties from the event, and the instance subject to the event.
-
The WMI Query Language
Understanding WMI Scripting, 2003Co-Authors: Alain LissoirAbstract:This chapter reviews the possibilities of WMI query language (WQL). windows management instrumentation (WMI) query language (WQL) is one of the key elements required to work with WMI. In most cases, WQL is a primary input to execute WMI tasks. The difficulty in learning WQL is that one has to work with some WMI elements. However, because WMI is a mix of various features interacting with each other, it is necessary to start from somewhere. With WMI, the learning phase starts at the level of the common information model (CIM) repository with WQL. Learning the CIM object model is necessary in order to understand the kind of information available from a WMI system. Learning WQL is essential to be able to formulate inputs to gather data from the CIM repository. When working with WMI event scripting, WQL is the primary input to formulate event queries.
-
Scripting with WMI
Understanding WMI Scripting, 2003Co-Authors: Alain LissoirAbstract:This chapter examines the windows management instrumentation (WMI) architecture, WMI-related tools, and WMI query language (WQL). Scripting on top of WMI implies the use of WMI COM objects. A script uses two types of objects: the objects obtained from the various class definitions located in the CIM repository (instances) and the objects exposed by the WMI scripting API (COM objects). The WMI scripting API is a collection of COM objects usable from most programming languages and scripting languages. In order to use the WMI COM objects they must first be instantiated. In addition, the CIM repository classes must also be instantiated as objects in order to reference the manageable entities of the real world. They are two instantiation types: the instantiation of the WMI scripting COM objects and the instantiation of the manageable entities. Both object types must be located in the system or in the CIM repository based on their nature. This chapter discovers the techniques for using WMI scripting objects.
-
Advanced WMI Scripting Techniques
Understanding WMI Scripting, 2003Co-Authors: Alain LissoirAbstract:This chapter reveals that the windows management instrumentation (WMI) scripting API offers many possibilities for performing various operations. Its versatility adds to its complexity in the sense that there are so many ways to perform an operation that it can sometimes be confusing. This chapter recommends that one should practice this technology to get a better working knowledge of the WMI scripting API. Throughout examination of WMI scripting, one has seen that it is possible to instantiate CIM classes or real-world manageable entities by using a moniker, or a series of WMI scripting APls. Moreover, the security can be set at different object levels of the WMI scripting API. In addition to these two aspects, it is also possible to combine the WMI scripting API with WMI query language (WQL) queries. The execution of the WMI operation can be performed synchronously or asynchronously. This provides many features and possibilities that can work together or separately. The ability to execute some WMI scripting API operations asynchronously is an important WMI feature because it enhances the responsiveness of a script.
-
Starting with WMI
Understanding WMI Scripting, 2003Co-Authors: Alain LissoirAbstract:This chapter reviews windows management instrumentation (WMI). It explains the basic foundation of WMI. Some of the WMI features available were used to illustrate the possibilities offered by this management instrumentation without programming. WMI refers to some standards defined by a committee called the distributed management task force (DMTF). The DMTF started many unifying management initiatives while focusing on distributed management. These initiatives are: desktop management interface (DMI), Web-based enterprise management (WBEM), common information model (CIM), directory-enabled networks (DEN), service incident standard (SIS) and solution exchange standard (SES), and alert standard forum (ASF). These components are themselves manageable in various ways. Although computers from various manufacturers may differ, they all have some common characteristics. Every computer has network devices, hard disks, controllers, tapes, memory, and processors, regardless of the manufacturer. In the same way, operating systems also have common characteristics, such as the memory available to run applications, the processes running, disk space available, users configured in the system, print queues and print jobs, and network adapters status.
Heinz Schmidt - One of the best experts on this subject based on the ideXlab platform.
-
QoSA/SOQUA - A model-oriented framework for runtime monitoring of nonfunctional properties
Lecture Notes in Computer Science, 2005Co-Authors: Kenneth Chan, Heinz Schmidt, Iman Poernomo, James JayaputeraAbstract:It is now recognized that nonfunctional properties are important to practical software development and maintenance. Many of these properties involve involving time and probabilities – for example, reliability and availability. One approach to ensuring conformance to nonfunctional requirements is the use of runtime monitoring. Currently, such monitoring is done in one of two ways: 1) monitoring through use of a generic tool or 2) by adding instrumentation code within system software and writing a tool to manage resulting datasets. The first approach is often not flexible while the second approach can lead to a higher development cost. In this paper, we present a flexible framework for runtime verification of timed and probabilistic nonfunctional properties of component-based architectures. We describe a Microsoft .NET-based implementation of our framework built upon the windows management instrumentation (WMI) infrastructure and the Distributed management Task Force’s Common Information Model standard. We use a language for contracts based on Probabilistic Computational Tree Logic (PCTL). We provide a formal semantics for this language based on possible application execution traces. The semantics is generic over the aspects of an application that are represented by states and transitions of traces. This enables us to use the language to define a wide range of nonfunctional properties.
-
EUROMICRO - Runtime verification of timing and probabilistic properties using WMI and .NET
2004Co-Authors: James Jayaputera, Iman Poernomo, Heinz SchmidtAbstract:Reliability and availability are key issues to distributed service-oriented systems. We present a methodology for run-time verification of reliability and availability properties for distributed architectures. Our approach generalizes the concept of design-by-contract to contracts involving time and probabilities. We define a language for contracts based on probabilistic real time computational tree logic (PCTL). We provide a formal semantics for this language based on possible execution traces of a system. Then we describe a .NET-based system for monitoring contracts, built upon the windows management instrumentation (WMI) framework.
