Jasmine: A Tool for Model-Driven Runtime Verification with UML Behavioral Models

Author(s):  
Zhou Zhou ◽  
Linzhang Wang ◽  
Zhanqi Cui ◽  
Xin Chen ◽  
Jianhua Zhao
IET Software ◽  
2011 ◽  
Vol 5 (2) ◽  
pp. 142 ◽  
Author(s):  
X. Li ◽  
X. Qiu ◽  
L. Wang ◽  
X. Chen ◽  
Z. Zhou ◽  
...  

Author(s):  
Marjan Sirjani ◽  
Luciana Provenzano ◽  
Sara Abbaspour Asadollah ◽  
Mahshid Helali Moghadam ◽  
Mehrdad Saadatmand

AbstractSoftware systems are complicated, and the scientific and engineering methodologies for software development are relatively young. Cyber-physical systems are now in every corner of our lives, and we need robust methods for handling the ever-increasing complexity of their software systems. Model-Driven Development is a promising approach to tackle the complexity of systems through the concept of abstraction, enabling analysis at earlier phases of development. In this paper, we propose a model-driven approach with a focus on guaranteeing safety using formal verification. Cyber-physical systems are distributed, concurrent, asynchronous and event-based reactive systems with timing constraints. The actor-based textual modeling language, Rebeca, with model checking support is used for formal verification. Starting from structured requirements and system architecture design the behavioral models, including Rebeca models, are built. Properties of interest are also derived from the structured requirements, and then model checking is used to formally verify the properties. This process can be performed in iterations until satisfaction of desired properties are ensured, and possible ambiguities and inconsistencies in requirements are resolved. The formally verified models can then be used to develop the executable code. The Rebeca models include the details of the signals and messages that are passed at the network level including the timing, and this facilitates the generation of executable code. The natural mappings among the models for requirements, the formal models, and the executable code improve the effectiveness and efficiency of the approach.


2005 ◽  
Vol 1 (2) ◽  
pp. 147-164 ◽  
Author(s):  
Joseph Cautilli ◽  
T. Chris Riley-Tillman ◽  
Saul Axelrod ◽  
Phil Hineline

2013 ◽  
pp. 98-110
Author(s):  
M. Likhachev

Behavioral models are considered in the paper as the link between the description of the institutional structure of the economic system and the formation of macro-aggregates, reflecting the results of its operations. The degree of homogeneity of the private sector’s economic environment and complementary goals of private entities and government regulation are noted as basic characteristics of behavioral models. The author examines the differences in the estimates of these characteristics as one of the most important factors underpinning the architecture of modern macroeconomic models and their practical implications.


2009 ◽  
Vol 38 (38) ◽  
pp. 119-130
Author(s):  
Erika Asnina

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.


Sign in / Sign up

Export Citation Format

Share Document