Results 1 -
5 of
5
Simulation-based Validation and Defect Localization for Evolving, Semi-Formal Requirements Models
- Proceedings of the 12th AsiaPacific Software Engineering Conference (APSEC 2005
, 2005
"... When requirements models are developed in an iterative and evolutionary way, requirements validation becomes a major problem. In order to detect and fix problems early, the specification should be validated as early as possible, and should also be revalidated after each evolutionary step. In this pa ..."
Abstract
-
Cited by 5 (2 self)
- Add to MetaCart
(Show Context)
When requirements models are developed in an iterative and evolutionary way, requirements validation becomes a major problem. In order to detect and fix problems early, the specification should be validated as early as possible, and should also be revalidated after each evolutionary step. In this paper, we show how the ideas of continuous integration and automatic regression testing in the field of coding can be adapted for simulation-based, automatic revalidation of requirements models after each incremental step. While the basic idea is fairly obvious, we are confronted with a major obstacle: requirements models under development are incomplete and semi-formal most of the time, while classic simulation approaches require complete, formal models. We present how we can simulate incomplete, semi-formal models by interactively recording missing behavior or functionality. However, regression simulations must run automatically and do not permit interactivity. We therefore have developed a technique where the simulation engine automatically resorts to the interactively recorded behavior in those cases where it does not get enough information from the model during a regression simulation run. Finally, we demonstrate how the information gained from model evolution and regression simulation can be exploited for locating defects in the model. 1
Simulation-Driven Creation, Validation and Evolution of Behavioral Requirements Models
"... Abstract: Requirements models for large systems cannot be developed in a single step; they evolve in a sequence of iterations. We have developed a simulationdriven process that supports iterative, evolutionary modeling of behavioral requirements. We start with modeling type scenarios (i.e. use cases ..."
Abstract
-
Cited by 5 (0 self)
- Add to MetaCart
(Show Context)
Abstract: Requirements models for large systems cannot be developed in a single step; they evolve in a sequence of iterations. We have developed a simulationdriven process that supports iterative, evolutionary modeling of behavioral requirements. We start with modeling type scenarios (i.e. use cases) and simulate these interactively. The simulation runs yield exemplary system behavior, which is documented in message sequence charts (MSCs). The modeler can then generalize this recorded partial behavior into statecharts. The resulting model is simulated again for validating that the modeled behavior matches the previously recorded behavior. The validated model is then used in the next incremental step for eliciting new, yet unspecified behavior by simulating new scenarios. 1
A Requirements Modeling Language for the Component Behavior of Cyber Physical Robotics Systems
- In Modelling and Quality in Requirements Engineering
, 2012
"... Abstract. Software development for robotics applications is a sophisticated endeavor as robots are inherently complex. Explicit modeling of the architecture and behavior of robotics application yields many advantages to cope with this complexity by identifying and separating logically and physically ..."
Abstract
-
Cited by 4 (3 self)
- Add to MetaCart
(Show Context)
Abstract. Software development for robotics applications is a sophisticated endeavor as robots are inherently complex. Explicit modeling of the architecture and behavior of robotics application yields many advantages to cope with this complexity by identifying and separating logically and physically independent components and by hierarchically structuring the system under development. On top of component and connector models we propose modeling the requirements on the behavior of robotics software components using I/O ω automata [1]. This approach facilitates early simulation of requirements model, allows to subject these to formal analysis and to generate the software from them. In this paper, we introduce an extension of the architecture description language MontiArc to model the requirements on components with I/O ω automata, which are defined in the spirit of Martin Glinz ’ Statecharts for requirements modeling [2]. We furthermore present a case study based on a robotics application generated for the Lego NXT robotic platform. “In der Robotik dachte man vor 30 Jahren, dass man heute alles perfekt beherrschen würde”, Martin Glinz [3] 1
Aspect-Oriented Modeling with Integrated Object Models
- Proc. Modellierung 2006
, 2006
"... Abstract: With the advent of aspect-oriented programming, the need for adequate techniques for handling aspect-oriented artifacts in the early phases of the software engineering process has emerged. In this paper, we present an aspect-oriented lan-guage extension for an integrated modeling language ..."
Abstract
-
Cited by 3 (2 self)
- Add to MetaCart
(Show Context)
Abstract: With the advent of aspect-oriented programming, the need for adequate techniques for handling aspect-oriented artifacts in the early phases of the software engineering process has emerged. In this paper, we present an aspect-oriented lan-guage extension for an integrated modeling language based on object models. We present the way aspect constructs can be handled in requirements and architectural models, and identify the impact on existing modeling languages and models. 1
ABSTRACT Scenario-Driven Modeling and Validation of Requirements Models
"... Requirements models for large systems typically cannot be developed in a single step, but evolve in a sequence of iterations. We have developed such an iterative modeling process which is based on the interactive simulation of yet incomplete and semi-formal models. Missing parts are completed intera ..."
Abstract
- Add to MetaCart
(Show Context)
Requirements models for large systems typically cannot be developed in a single step, but evolve in a sequence of iterations. We have developed such an iterative modeling process which is based on the interactive simulation of yet incomplete and semi-formal models. Missing parts are completed interactively by the user simulating the model. We start by modeling type scenarios (i.e. use cases) and simulate these interactively before having specified any system behavior. Such simulation runs yield exemplary system behavior in form of message sequence charts (MSCs). The modeler can then generalize this recorded partial behavior into statecharts. The resulting model is simulated again, (i) for validating that the modeled behavior matches the previously recorded behavior, and (ii) for recording new yet unspecified behavior in a next iteration step. Thus, recording MSCs by playing-through the scenarios and transforming MSCs to statecharts stimulate and drive each other. In this paper we focus on two elements of our approach: firstly, we describe the syntax and semantics of our scenario language. Secondly, we give an example how our modeling process works.
