Abstract

Software systems in safety-critical industrial automation systems, such as power plants and steel mills, become increasingly large, complex, and distributed. For assessing risks, like low product quality and project cost and duration overruns, to trustworthy services provided by software as part of automation systems there are established risk analysis approaches based on data collection from project participants and data models. However, in multi-disciplinary engineering projects there are often semantic gaps between the software tools and data models of the participating engineering disciplines, e.g., mechanic, electrical, and software engineering. In this paper we discuss current limitations to risk assessment in (software+) engineering projects and introduce the SEMRISK approach for risk assessment in projects with semantically heterogeneous software tools and data models. The SEMRISK approach provides the knowledge engineering foundation to allow an end-to-end view for service-relevant data elements such as signals, by providing a project domain ontology and mappings to the tool data models of the involved engineering disciplines. We empirically evaluate the effectiveness and efficiency of the approach based on a real-world industrial use case from the safety-critical power plant domain. Major results are that the approach was effective and considerably more efficient than the current approach at the industry partner.

Full Text
Paper version not known

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.