Scenario Development: A Model-Driven Engineering Perspective

Abstract

Scenario development starts with capturing scenarios from the users and leads to the design and the development of the simulation environment to execute these scenarios. This paper proposes a scenario development process adopting a Model-Driven Engineering (MDE) perspective. It takes scenario development and the use of scenarios in simulation environment development put forth in IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) as a starting point. It then constructs a basic vocabulary including the definitions of operational, conceptual, and executable scenarios. Following MDE principles, scenario development is viewed as a series of model transformations. Operational scenarios, mostly defined in a natural language, are first transformed into conceptual scenarios, which conform to a formal metamodel. Then conceptual scenarios can be transformed into executable scenarios specified using a specific scenario definition language. Furthermore, it is also possible to generate the constructs of simulation environment design and development using model transformations. In this regard, a conceptual scenario metamodel is proposed adopting the Base Object Model metamodel as an example. Then this metamodel is used to present the proposed process with a sample operational scenario and conceptual scenario excerpts. Samples are shown how model transformation can be employed for developing a Federation Object Model and an executable scenario file.

Formal Scenario Definition Language for Aviation: Aircraft Landing Case Study

“…The work presented by Durak et al 3 laid down the foundation for the research presented in this paper. It proposed a scenario development process adopting a Model-Driven Engineering (MDE) perspective.…”

“…These classes were integrated with the BOM framework developed by Durak et al 3 The details of some of the important classes in this model have been explained here.…”

“…It is an extensive process beginning with the stakeholders' descriptions of the scenario and finishing with the generation of the corresponding executable specification. 3 This work targets aviation scenario generation by proposing a Domain-Specific Language (DSL) for the aviation domain, called the Aviation Scenario Definition Language (ASDL). ASDL aims at providing a standard scenario specification that will lead to a common mechanism for verifying and executing aviation scenarios, effective sharing of scenarios among various simulation environments, improve the consistency among different simulators and simulations and enable the reuse of scenario specifications.…”

Exploring scenario development – a case study of two collaborative research projects

“…The fact that scenarios can be many things to many people makes it a non-trivial task to summarize its relevance, history and application. Although scenarios, and methods for their development and utilization, have a rich history as tools used by individuals, businesses and governments there still exists a lack of common standardized development practices (Urwin et al, 2011, Schwarz, 2008, Durak et al, 2014.…”

OWL Ontology To Ecore Metamodel Transformation for Designing a Domain Specific Language To Develop Aviation Scenarios

“…The steps followed for this were obtained from the framework provided by Durak et al (2014): (1) define the classes required to accurately represent the model, (2) determine the attributes used to describe the classes, (3) define the structure and relationships between the classes, (4) create an Ecore model based on the entities identified, (5) integrate this model of aviation entities into the BOM framework, (6) generate Java code for the model, and (7) create a runtime instance and use it to define and edit an aviation scenario. The first four steps here were part of Stage 1 of the project and the next three were part of Stage 2.…”