The Experts below are selected from a list of 66396 Experts worldwide ranked by ideXlab platform

Schahram Dustdar - One of the best experts on this subject based on the ideXlab platform.

  • Monitoring performance related qos properties in service oriented systems a pattern based architectural decision model
    European Conference on Pattern Languages of Programs, 2011
    Co-Authors: Ernst Oberortner, Uwe Zdun, Stefan Sobernig, Schahram Dustdar
    Abstract:

    In service-oriented systems, service-level agreements (SLA) are specified as contracts between service providers and service consumers. SLAs stipulate --- among other things --- the provided services' performance. A service provider must fulfill the agreements stated in SLAs, e.g., to avoid paying penalties. Service consumers must verify whether the service quality as purchased is delivered. We present an architectural design decision model (ADDM) covering the design of a QoS Monitoring Infrastructure. The ADDM collects design decisions about measuring, storing, and evaluating performance-related quality-of-service (QoS) agreements. The model includes various requirements and puts forth design solutions by referring to established architectural, remoting, and design patterns. We evaluate the ADDM to build the architecture of a QoS Monitoring Infrastructure in a case study. The model guides through the decision-making process of designing a QoS Monitoring Infrastructure.

  • EuroPLoP - Monitoring performance-related QoS properties in service-oriented systems: a pattern-based architectural decision model
    Proceedings of the 16th European Conference on Pattern Languages of Programs - EuroPLoP '11, 2011
    Co-Authors: Ernst Oberortner, Uwe Zdun, Stefan Sobernig, Schahram Dustdar
    Abstract:

    In service-oriented systems, service-level agreements (SLA) are specified as contracts between service providers and service consumers. SLAs stipulate --- among other things --- the provided services' performance. A service provider must fulfill the agreements stated in SLAs, e.g., to avoid paying penalties. Service consumers must verify whether the service quality as purchased is delivered. We present an architectural design decision model (ADDM) covering the design of a QoS Monitoring Infrastructure. The ADDM collects design decisions about measuring, storing, and evaluating performance-related quality-of-service (QoS) agreements. The model includes various requirements and puts forth design solutions by referring to established architectural, remoting, and design patterns. We evaluate the ADDM to build the architecture of a QoS Monitoring Infrastructure in a case study. The model guides through the decision-making process of designing a QoS Monitoring Infrastructure.

  • DEBS - An event view model and DSL for engineering an event-based SOA Monitoring Infrastructure
    Proceedings of the Fourth ACM International Conference on Distributed Event-Based Systems - DEBS '10, 2010
    Co-Authors: Emmanuel Mulo, Uwe Zdun, Schahram Dustdar
    Abstract:

    An event-based solution that uses events to convey information to a Monitoring tool is well suited to implementing a non-intrusive Monitoring Infrastructure. This enables an SOA system's stakeholders to observe the system aspects of interest to them. However, implementation of SOA today, let alone the Monitoring Infrastructure, is a complex task due to the heterogeneous environment consisting of multiple technologies, platforms and components. We propose an approach for implementing such an event-based SOA Monitoring Infrastructure, that introduces a dedicated event view model and an eventing domain-specific language in a model-driven framework. The event view model captures SOA artifacts and links them with the event domain, while the eventing domain-specific language enables a system developer to specify instances of the event view model. With our model-driven approach, most of the runtime Monitoring Infrastructure is generated. These two ingredients (view model and domain-specific language) focus implementation efforts on the concern of eventing, thereby helping to manage complexity. We apply and evaluate our approach in the context of a case study.

Eddie Al-shakarchi - One of the best experts on this subject based on the ideXlab platform.

  • A Case Study into Using Common Real-Time Workflow Monitoring Infrastructure for Scientific Workflows
    Journal of Grid Computing, 2013
    Co-Authors: Karan Vahi, Ian Harvey, Taghrid Samak, Daniel Gunter, Kieran Evans, David Rogers, Ian Taylor, Monte Goode, Fabio Silva, Eddie Al-shakarchi
    Abstract:

    Scientific workflow systems support various workflow representations, operational modes, and configurations. Regardless of the system used, end users have common needs: to track the status of their workflows in real time, be notified of execution anomalies and failures automatically, perform troubleshooting, and automate the analysis of the workflow results. In this paper, we describe how the Stampede Monitoring Infrastructure was integrated with the Pegasus Workflow Management System and the Triana Workflow Systems, in order to add generic real time Monitoring and troubleshooting capabilities across both systems. Stampede is an Infrastructure that provides interoperable Monitoring using a three-layer model: (1) a common data model to describe workflow and job executions; (2) high-performance tools to load workflow logs conforming to the data model into a data store; and (3) a common query interface. This paper describes the integration of Stampede Monitoring architecture with Pegasus and Triana and shows the new analysis capabilities that Stampede provides to these workflow systems. The successful integration of Stampede with these workflow engines demonstrates the generic nature of the Stampede Monitoring Infrastructure and its potential to provide a common platform for Monitoring across scientific workflow engines.

Ernst Oberortner - One of the best experts on this subject based on the ideXlab platform.

  • Monitoring performance related qos properties in service oriented systems a pattern based architectural decision model
    European Conference on Pattern Languages of Programs, 2011
    Co-Authors: Ernst Oberortner, Uwe Zdun, Stefan Sobernig, Schahram Dustdar
    Abstract:

    In service-oriented systems, service-level agreements (SLA) are specified as contracts between service providers and service consumers. SLAs stipulate --- among other things --- the provided services' performance. A service provider must fulfill the agreements stated in SLAs, e.g., to avoid paying penalties. Service consumers must verify whether the service quality as purchased is delivered. We present an architectural design decision model (ADDM) covering the design of a QoS Monitoring Infrastructure. The ADDM collects design decisions about measuring, storing, and evaluating performance-related quality-of-service (QoS) agreements. The model includes various requirements and puts forth design solutions by referring to established architectural, remoting, and design patterns. We evaluate the ADDM to build the architecture of a QoS Monitoring Infrastructure in a case study. The model guides through the decision-making process of designing a QoS Monitoring Infrastructure.

  • EuroPLoP - Monitoring performance-related QoS properties in service-oriented systems: a pattern-based architectural decision model
    Proceedings of the 16th European Conference on Pattern Languages of Programs - EuroPLoP '11, 2011
    Co-Authors: Ernst Oberortner, Uwe Zdun, Stefan Sobernig, Schahram Dustdar
    Abstract:

    In service-oriented systems, service-level agreements (SLA) are specified as contracts between service providers and service consumers. SLAs stipulate --- among other things --- the provided services' performance. A service provider must fulfill the agreements stated in SLAs, e.g., to avoid paying penalties. Service consumers must verify whether the service quality as purchased is delivered. We present an architectural design decision model (ADDM) covering the design of a QoS Monitoring Infrastructure. The ADDM collects design decisions about measuring, storing, and evaluating performance-related quality-of-service (QoS) agreements. The model includes various requirements and puts forth design solutions by referring to established architectural, remoting, and design patterns. We evaluate the ADDM to build the architecture of a QoS Monitoring Infrastructure in a case study. The model guides through the decision-making process of designing a QoS Monitoring Infrastructure.

Karan Vahi - One of the best experts on this subject based on the ideXlab platform.

  • A Case Study into Using Common Real-Time Workflow Monitoring Infrastructure for Scientific Workflows
    Journal of Grid Computing, 2013
    Co-Authors: Karan Vahi, Ian Harvey, Taghrid Samak, Daniel Gunter, Kieran Evans, David Rogers, Ian Taylor, Monte Goode, Fabio Silva, Eddie Al-shakarchi
    Abstract:

    Scientific workflow systems support various workflow representations, operational modes, and configurations. Regardless of the system used, end users have common needs: to track the status of their workflows in real time, be notified of execution anomalies and failures automatically, perform troubleshooting, and automate the analysis of the workflow results. In this paper, we describe how the Stampede Monitoring Infrastructure was integrated with the Pegasus Workflow Management System and the Triana Workflow Systems, in order to add generic real time Monitoring and troubleshooting capabilities across both systems. Stampede is an Infrastructure that provides interoperable Monitoring using a three-layer model: (1) a common data model to describe workflow and job executions; (2) high-performance tools to load workflow logs conforming to the data model into a data store; and (3) a common query interface. This paper describes the integration of Stampede Monitoring architecture with Pegasus and Triana and shows the new analysis capabilities that Stampede provides to these workflow systems. The successful integration of Stampede with these workflow engines demonstrates the generic nature of the Stampede Monitoring Infrastructure and its potential to provide a common platform for Monitoring across scientific workflow engines.

Paul Grünbacher - One of the best experts on this subject based on the ideXlab platform.

  • VaMoS - Variability Management for a Runtime Monitoring Infrastructure
    Proceedings of the Ninth International Workshop on Variability Modelling of Software-intensive Systems - VaMoS '15, 2015
    Co-Authors: Rick Rabiser, Michael Vierhauser, Paul Grünbacher
    Abstract:

    Many software systems today are systems of systems (SoS), which are difficult to analyze due to their size, complexity, heterogeneity, and variability. For instance, unexpected behavior of SoS is often caused by the complex interactions between the involved systems and their environment at runtime. Monitoring Infrastructures (MIs) provide support for engineers and support staff analyzing the behavior of SoS during development and operation. Variability plays an important role in MIs, however, while some approaches exist, managing variability of MIs remains challenging. In this paper, we describe how we applied a variability management approach to support the reconfiguration of a SoS Monitoring Infrastructure (MI) at runtime. Our approach provides configuration support for setting up the MI to reflect system variability. It also supports runtime reconfiguration of the MI to reflect the different Monitoring tasks of users and to support evolution. We motivate our work using the case of Monitoring a real-world SoS from the domain of industrial automation and discuss variability-related challenges in four Monitoring scenarios. We evaluate the feasibility of our approach by applying it to these scenarios. We also demonstrate that our approach reduces manual reconfiguration effort and helps to reduce the overhead of the MI.

  • a requirements Monitoring Infrastructure for very large scale software systems
    Requirements Engineering: Foundation for Software Quality, 2014
    Co-Authors: Michael Vierhauser, Rick Rabiser, Paul Grünbacher
    Abstract:

    [Context and motivation] Approaches for requirements Monitoring check the compliance of systems with their requirements during operation. [Question/problem] Despite many advances, requirements Monitoring remains challenging particularly for very-large-scale software systems VLSS with system-of-systems architectures. [Principal ideas/results] In this research preview we describe key characteristics of industrial VLSS and discuss implications for requirements Monitoring. Furthermore, we report on our ongoing work of developing a requirements Monitoring Infrastructure addressing these characteristics. [Contribution] Our Infrastructure supports runtime Monitoring of requirements across systems; variability management of requirements-based monitors; and the integration of Monitoring data from different sources in a VLSS.

  • REFSQ - A Requirements Monitoring Infrastructure for Very-Large-Scale Software Systems
    Requirements Engineering: Foundation for Software Quality, 2014
    Co-Authors: Michael Vierhauser, Rick Rabiser, Paul Grünbacher
    Abstract:

    [Context and motivation] Approaches for requirements Monitoring check the compliance of systems with their requirements during operation. [Question/problem] Despite many advances, requirements Monitoring remains challenging particularly for very-large-scale software systems VLSS with system-of-systems architectures. [Principal ideas/results] In this research preview we describe key characteristics of industrial VLSS and discuss implications for requirements Monitoring. Furthermore, we report on our ongoing work of developing a requirements Monitoring Infrastructure addressing these characteristics. [Contribution] Our Infrastructure supports runtime Monitoring of requirements across systems; variability management of requirements-based monitors; and the integration of Monitoring data from different sources in a VLSS.

  • COMPSAC Workshops - Goal-Driven Adaptation of Service-Based Systems from Runtime Monitoring Data
    2011 IEEE 35th Annual Computer Software and Applications Conference Workshops, 2011
    Co-Authors: Xavier Franch, Paul Grünbacher, Deepak Dhungana, Marc Oriol, Benedikt Burgstaller, Lidia López, Jordi Marco, João Pimentel
    Abstract:

    Service-based systems need to provide flexibility to adapt both to evolving requirements from multiple, often conflicting, ephemeral and unknown stakeholders, as well as to changes in the runtime behavior of their component services. Goal-oriented models allow representing the requirements of the system whilst keeping information about alternatives. We present the MAESoS approach which uses i* diagrams to identify quality of service requirements over services. The alternatives are extracted and kept in a variability model. A Monitoring Infrastructure identifies changes in runtime behavior that can propagate up to the level of stakeholder goals and trigger the required adaptations. We illustrate the approach with a scenario of use.