Abstract

Problem statement: There are many different model checkers that have been developed. Each of the model checkers is based on different input languages and they are suitable for model checking different types of systems. Thus it is important for us to choose the right model checker or modeling and verifying a given system. However, moving from one model checker to another is not an easy task since we have to deal with different input languages. Approach: In order to solve the problem we propose a common modeling language that is based on UML state chart. Some translation rules for translating the model described in the common modeling language into the input languages of model checkers are also presented. Results: The result of the case study shows that our approach has been successfully applied in modeling the control system through the process of transformation and translation. Conclusion: Common modeling language can be used as a front end to help users to properly model a system before it is translated into input language of model checkers.

Highlights

  • Model checking is an automatic technique for checking properties of software and hardware systems (Clarke, 1997; Berard et al, 2010)

  • The translation from Common Modeling language (CM) to input language of model checkers starts by modeling the behavior of a system into a statechart diagram

  • The result of of the case study shows that the proposed method for translating the model described in CM into the input languages of SMV and PRISM is feasible

Read more

Summary

Introduction

Model checking is an automatic technique for checking properties of software and hardware systems (Clarke, 1997; Berard et al, 2010). The first step is to specify the properties of the system to be checked. The verification process is carried out by the model checker. Once verification process is completed, the system will produce either true if model satisfied the property, or false if it does not. Most model checkers will produce a counterexample if the property is not satisfied by the model. This counterexample is a state sequence that violates the model of the system. This implies that, a model checker will check whether a model satisfies a given property by exploring all possible behaviors of the system

Methods
Results
Discussion
Conclusion

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.