Results 21 - 30
of
34
Runtime Goal Models
"... Abstract—Goal models capture stakeholder requirements for a system-to-be, but also circumscribe a space of alternative specifications for fulfilling these requirements. Recent proposals for self-adaptive software systems rely on variants of goal models to support monitoring and adaptation functions. ..."
Abstract
-
Cited by 2 (2 self)
- Add to MetaCart
(Show Context)
Abstract—Goal models capture stakeholder requirements for a system-to-be, but also circumscribe a space of alternative specifications for fulfilling these requirements. Recent proposals for self-adaptive software systems rely on variants of goal models to support monitoring and adaptation functions. In such cases, goal models serve as mechanisms in terms of which systems reflect upon their requirements during their operation. We argue that existing proposals for using goal models at runtime are using design artifacts for purposes they were not intended, i.e., for reasoning about runtime system behavior. In this paper, we propose a conceptual distinction between Design-time Goal Models (DGMs)—used to design a system—and Runtime Goal Models (RGMs)—used to analyze a system’s runtime behavior with respect to its requirements. RGMs extend DGMs with additional state, behavioral and historical information about the fulfillment of goals. We propose a syntactic structure for RGMs, a method for deriving them from DGMs, and runtime algorithms that support their monitoring. Keywords—Runtime goal models; Requirements at runtime; Goal reasoning; Self-adaptive systems. I.
N.: Adaptation in Cyber-Physical Systems: from System Goals to Architecture Configurations
, 2014
"... Abstract: Design of self-adaptive Cyber-Physical Systems (CPS) operating in not fully anticipated environments is a significant challenge, especially if the design is to provide for a sufficient level of dependability. This stems partly from the fact that the concerns of self-adaptivity and dependab ..."
Abstract
-
Cited by 2 (2 self)
- Add to MetaCart
(Show Context)
Abstract: Design of self-adaptive Cyber-Physical Systems (CPS) operating in not fully anticipated environments is a significant challenge, especially if the design is to provide for a sufficient level of dependability. This stems partly from the fact that the concerns of self-adaptivity and dependability are to certain extent contradictory. In this paper, we present an extension to IRM (Invariant Refinement Method) – a design method and associated formally grounded model targeting CPS – that addresses self-adaptivity while preserving the dependability aspects. Specifically, we extend IRM to provide traceability between system requirements, distinct situations in the environment, and predefined configurations of system architecture. Additionally, based on this traceability, we propose a method for adaptation at runtime that allows coping with unanticipated situations. As a proof of concept, we implemented the proposed method for the DEECo component model, based on dynamic ensembles of components.
Managing testing complexity in dynamically adaptive systems: a model-driven approach
- Proc. 3rd Int’l Conf. Software Testing, Verification, and Validation Workshops, IEEE
"... Abstract-Autonomous systems are increasingly conceived as a means to allow operation in changeable or poorly understood environments. However, granting a system autonomy over its operation removes the ability of the developer to be completely sure of the system's behaviour under all operating ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
Abstract-Autonomous systems are increasingly conceived as a means to allow operation in changeable or poorly understood environments. However, granting a system autonomy over its operation removes the ability of the developer to be completely sure of the system's behaviour under all operating contexts. This combination of environmental and behavioural uncertainty makes the achievement of assurance through testing very problematic. This paper focuses on a class of system, called an m-DAS, that uses run-time models to drive run-time adaptations in changing environmental conditions. We propose a testing approach which is itself model-driven, using model analysis to significantly reduce the set of test cases needed to test for emergent behaviour. Limited testing resources may therefore be prioritised for the most likely scenarios in which emergent behaviour may be observed.
Aspect-Oriented Modeling to Support Dynamic Adaptation
"... Since software systems need to be continuously available under varying conditions, their ability to evolve at runtime is increasingly seen as one key issue. Modern programming frameworks already provide support for dynamic adaptations. However the high-variability of features in Dynamically Adapti ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
Since software systems need to be continuously available under varying conditions, their ability to evolve at runtime is increasingly seen as one key issue. Modern programming frameworks already provide support for dynamic adaptations. However the high-variability of features in Dynamically Adaptive Systems (DAS) introduces an explosion of possible runtime system configurations (often called modes) and mode transitions. Designing these configurations and their transitions is tedious and error-prone, making the system feature evolution difficult. This demo presents a tool-chain developed by the DiVA project, which combines AOM and Model-Driven Engineering to tame the combinatorial explosion of DAS modes. Using AOM techniques, we derive a wide range of modes by weaving aspects into an explicit model reflecting the runtime system. We use these generated modes to automatically adapt the system using MDE techniques.
137 PUBLICATIONS 1,197 CITATIONS SEE PROFILE
"... All in-text references underlined in blue are linked to publications on ResearchGate, letting you access and read them immediately. ..."
Abstract
- Add to MetaCart
(Show Context)
All in-text references underlined in blue are linked to publications on ResearchGate, letting you access and read them immediately.
Towards Flexible Evolution of Dynamically Adaptive Systems
"... Abstract—Modern software systems need to be continuously available under varying conditions. Their ability to dynamically adapt to their execution context is thus increasingly seen as a key to their success. Recently, many approaches were proposed to design and support the execution of Dynamically A ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract—Modern software systems need to be continuously available under varying conditions. Their ability to dynamically adapt to their execution context is thus increasingly seen as a key to their success. Recently, many approaches were proposed to design and support the execution of Dynamically Adaptive Systems (DAS). However, the ability of a DAS to evolve is limited to the addition, update or removal of adaptation rules or reconfiguration scripts. These artifacts are very specific to the control loop managing such a DAS and runtime evolution of the DAS requirements may affect other parts of the DAS. In this paper, we argue to evolve all parts of the loop. We suggest leveraging recent advances in model-driven techniques to offer an approach that supports the evolution of both systems and their adaptation capabilities. The basic idea is to consider the control loop itself as an adaptive system.
Noname manuscript No. (will be inserted by the editor) RELAX: A Language to Address Uncertainty in Self-Adaptive Systems Requirements
, 2009
"... Abstract Self-adaptive systems have the capability to autonomously modify their behavior at run-time in response to changes in their environment. Self-adaptation is particularly necessary for applications that must run continuously, even under adverse conditions and changing requirements; sample dom ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract Self-adaptive systems have the capability to autonomously modify their behavior at run-time in response to changes in their environment. Self-adaptation is particularly necessary for applications that must run continuously, even under adverse conditions and changing requirements; sample domains include automotive systems, telecommunications, and environmental monitoring systems. While a few techniques have been developed to support the monitoring and analysis of requirements for adaptive systems, limited attention has been paid to the actual creation and specification of requirements of self-adaptive systems. As a result, self-adaptivity is often constructed in an ad-hoc manner. In order to support the rigorous specification of adaptive systems requirements, this paper introduces RELAX, a new requirements language for selfadaptive systems that explicitly addresses uncertainty inherent in adaptive systems. We present the formal semantics for RELAX in terms of fuzzy logic, thus enabling a rigorous treatment of requirements that include uncertainty. RELAX enables developers to identify uncertainty in the requirements, thereby facilitating the design of systems that are, by definition, more flexible and amenable to adaptation in a systematic fashion. We illustrate the use of RELAX on smart home applications, including an adaptive assisted living system. 1
(Dagstuhl Seminar Organizer Authors)
"... Software’s ability to adapt at run-time to changing user needs, system intrusions or faults, changing operational environment, and resource variability has been proposed as a means to cope with the complexity of today’s softwareintensive systems. Such self-adaptive systems can configure and reconfig ..."
Abstract
- Add to MetaCart
(Show Context)
Software’s ability to adapt at run-time to changing user needs, system intrusions or faults, changing operational environment, and resource variability has been proposed as a means to cope with the complexity of today’s softwareintensive systems. Such self-adaptive systems can configure and reconfigure themselves, augment their functionality, continually optimize themselves, protect themselves, and recover themselves, while keeping most of their complexity hidden from the user and administrator. In this paper, we present research road map for software engineering of selfadaptive systems focusing on four views, which we identify as essential: requirements, modelling, engineering, and assurances.
Requirements-aware Systems for Self-adaptation under Uncertainty Research Statement
"... The development of software-intensive systems is driven by their requirements. Traditional requirements engineering (RE) methods focus on resolving ambiguities in requirements and advocate specifying require-ments in sufficient detail so that the implementation can be checked against them for confor ..."
Abstract
- Add to MetaCart
(Show Context)
The development of software-intensive systems is driven by their requirements. Traditional requirements engineering (RE) methods focus on resolving ambiguities in requirements and advocate specifying require-ments in sufficient detail so that the implementation can be checked against them for conformance. In an ideal world, this way of thinking can be very effective. Requirements can be specified clearly, updated as necessary, and evolutions of the software design can be made with the requirements in mind. Increasingly, however, it is not sufficient to fix requirements statically because they will change at runtime as the operating environment changes. Furthermore, as software systems become more pervasive, there is growing uncertainty about the environment and so requirements changes cannot be predicted at design-time [12, 24, 39, 1, 20]. It is considerations such as these that have led to the development of self-adaptive systems (SASs) [11], which have the ability to dynamically and autonomously reconfigure their behavior to respond to changing external conditions. Consider a scenario involving a robot vacuum cleaner for domestic apartments. The vacuum cleaner has goals clean apartment, avoid tripping hazard and minimize energy costs. Further, it has the domain assumption energy is cheapest at night. To satisfy the avoid tripping hazard goal, a requirement is derived that it should stop operating as soon as any human activity is detected. Night operation satisfies the
From Goals to Reliable Service Compositions∗
"... A key feature of modern enterprises lies in the availabil-ity of software systems able to adapt themselves to the fre-quent changes in the business processes. Services have al-ready proven their ability to provide flexible solutions, but so far the focus has been mainly on the technological in-frast ..."
Abstract
- Add to MetaCart
(Show Context)
A key feature of modern enterprises lies in the availabil-ity of software systems able to adapt themselves to the fre-quent changes in the business processes. Services have al-ready proven their ability to provide flexible solutions, but so far the focus has been mainly on the technological in-frastructure. Oftentimes user requirements have been ne-glected and also the reliability of proposed solutions has been traded for flexibility and dynamism. These are the mo-tivations for the research proposal presented in this paper. Starting from the actual user requirements, we aim to pro-vide a complete solution to (semi) automatically derive co-herent, complete, and reliable service compositions. The proposal uses a goal model to represent the business goals and supervision directives to oversee and enforce the relia-bility of obtained compositions. Execution and supervision are supported through a flexible run-time infrastructure. 1 Research Problem It is already proven that service-based IT solutions pro-vide different advantages [2]: quick reaction and adapta-tion to new needs, easy integration of heterogenous com-ponents, and reduced development costs. So far, these so-lutions have been mainly addressed from a technological perspective, but, in contrast, they should come from the ac-tual requirements of the different stakeholders. Besides the technological achievements, we need methods and tools to precisely relate requirements to services and service com-positions (also known as processes). The business dimension imposes frequently changing re-quirements, while the distributed nature makes them intrin-sically unreliable: network failures may happen, partner services can be down or unavailable, or they can change in-