Abstract
Model-based software engineering is a promising approach for controlling complex automation systems. Automation engineers, unfortunately, do not routinely model the expected behavior, especially if they are not trained in software engineering. They rather focus only on the implementation. In this paper, we analyze potential causes for the low adoption of service sequences within IEC 61499, which define behavioral constraints for building blocks of control applications. We propose a methodology for mining constraints of software components, which are then classified by an engineer. Furthermore, we suggest extending the language to allow for forbidden and mandatory scenarios. Our approach facilitates the constraint definition for legacy software, where the effort of manual specification is extremely high. Tool support for all described extensions and modeling techniques is provided as part of the open source IDE Eclipse 4diac to facilitate applying the approach in practice.
Sign-in/Register to access full text options 
Free) 
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
