Reconciling system requirements and runtime behavior

Feather, Martin S.; Fickas, Stephen; Lamsweerde, Axel van; Ponsard, Christophe

doi:10.1109/iwssd.1998.667919

Cited by 131 publications

(114 citation statements)

References 17 publications

Supporting

Mentioning

114

Contrasting

Order By: Relevance

“…Monitoring infrastructure A monitoring infrastructure is required to continuously observe and analyze emitted events to check compliance. Runtime requirementsmonitoring systems, such as proposed by Feather et al [10] and Skene and Emmerich [3], can be integrated with MORSE and used for the compliance checking. If a violation occurs, the model responsible for the violation can easily be identified using the identifier contained in the event(s) that caused the violation.…”

Section: A Model-aware Service Environment In Compliance Monitoring Amentioning

confidence: 99%

“…In this section we refer and relate to work in the areas of runtime requirements-monitoring and model management in form of model repositories. 36 x + 3.38 Feather et al [10] discuss an architecture and a development process for monitoring system requirements at runtime. It builds on work on goal-driven requirements engineering [21] and runtime requirements monitoring [22].…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Monitoring and Analyzing Service-Based Internet Systems through a Model-Aware Service Environment

Holmes

Zdun

Daniel

et al. 2010

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

As service-based Internet systems get increasingly complex they become harder to manage at design time as well as at runtime. Nowadays, many systems are described in terms of precisely specified models, e.g., in the context of model-driven development. By making the information in these models accessible at runtime, we provide better means for analyzing and monitoring the service-based systems. We propose a model-aware repository and service environment (MORSE) to support model access and evolution at both design time and runtime. MORSE focuses on enabling us to monitor, interpret, and analyze the monitored information. In an industrial case study, we demonstrate how compliance monitoring can benefit from MORSE to monitor violations at runtime and how MORSE can ease the root cause analysis of such violations. Performance and scalability evaluations show the applicability of our approach for the intended use cases and that models can be retrieved during execution at low cost.

show abstract

Section: A Model-aware Service Environment In Compliance Monitoring Amentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Monitoring and Analyzing Service-Based Internet Systems through a Model-Aware Service Environment

Holmes

Zdun

Daniel

et al. 2010

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

show abstract

“…Feather et al [2] address system behaviour deviations from requirements specifications; they introduce an architecture (and a development process) to reconcile requirements with behaviour. This process is enacted by jointly anticipating deviations at specification time and solving unpredicted situations at runtime, and examine the latter option using the requirements monitoring framework FLEA [16].…”

Section: Related Workmentioning

confidence: 99%

“…Deviations of system behavior from requirements specifications have been discussed in [2], where the authors suggest an architecture (and a development process) to reconcile requirements with system behavior. Reconciliation is enacted by anticipating deviations at specification time and solving unpredicted circumstances at runtime.…”

Section: Introductionmentioning

confidence: 99%

An Architecture for Requirements-Driven Self-reconfiguration

Dalpiaz

Giorgini

Mylopoulos

2009

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

Abstract. Self-reconfiguration is the capability of a system to autonomously switch from one configuration to a better one in response to failure or context change. There is growing demand for software systems able to self-reconfigure, and specifically systems that can fulfill their requirements in dynamic environments. We propose a conceptual architecture that provides systems with selfreconfiguration capabilities, enacting a model-based adaptation process based on requirements models. We describe the logical view on our architecture for selfreconfiguration, then we detail the main mechanisms to monitor for and diagnose failures. We present a case study where a self-reconfiguring system assists a patient perform daily tasks, such as getting breakfast, within her home. The challenge for the system is to fulfill its mission regardless of the context, also to compensate for failures caused by patient inaction or other omissions in the environment of the system.

show abstract

“…When a change in stakeholder requirements is detected at runtime (e.g., by using the approach in [2]), goal models can be used to re-evaluate the system behaviour alternatives with respect to the new requirements and to determine if system reconfiguration is needed. For instance, if a change in stakeholder requirements affected a particular goal in the model, it is easy to see how this goal is decomposed and which components/autonomic elements implementing the goal are in turn affected.…”

Section: The Role Of Goal Modelsmentioning

confidence: 99%

Requirements-driven design of autonomic application software

Lapouchnian

Liaskos

et al. 2006

Proceedings of the 2006 Conference of the Center for Advanced Studies on Collaborative Research - CASCON '06

View full text Add to dashboard Cite

Autonomic computing systems reduce software maintenance costs and management complexity by taking on the responsibility for their configuration, optimization, healing, and protection. These tasks are accomplished by switching at runtime to a different system behaviour -the one that is more efficient, more secure, more stable, etc. -while still fulfilling the main purpose of the system. Thus, identifying the objectives of the system, analyzing alternative ways of how these objectives can be met, and designing a system that supports all or some of these alternative behaviours is a promising way to develop autonomic systems. This paper proposes the use of requirements goal models as a foundation for such software development process and demonstrates this on an example.

show abstract

Reconciling system requirements and runtime behavior

Cited by 131 publications

References 17 publications

Monitoring and Analyzing Service-Based Internet Systems through a Model-Aware Service Environment

Monitoring and Analyzing Service-Based Internet Systems through a Model-Aware Service Environment

An Architecture for Requirements-Driven Self-reconfiguration

Requirements-driven design of autonomic application software

Contact Info

Product

Resources

About