{"id":7741,"date":"2021-04-29T08:07:03","date_gmt":"2021-04-29T06:07:03","guid":{"rendered":"https:\/\/www.iese.fraunhofer.de\/blog\/?p=7741"},"modified":"2024-01-22T12:21:49","modified_gmt":"2024-01-22T11:21:49","slug":"safety-engineering","status":"publish","type":"post","link":"https:\/\/www.iese.fraunhofer.de\/blog\/safety-engineering\/","title":{"rendered":"Model-Based Safety Engineering \u2013 easily explained"},"content":{"rendered":"

Model-based development offers many advantages such as improved maintainability, reusability, quality, and efficiency. Addressing these aspects is also possible for Safety Engineering if model-based approaches are introduced. In a four-part series of blog posts, we will give an overview of typical safety engineering methods and techniques and how they can be realized in a model-based way. In Part 1, we will start with a general definition and a presentation of the advantages and challenges of Model-Based Safety Engineering (MBSE).<\/p>\n

What is Safety Engineering about?<\/strong><\/h3>\n

When developing safety-critical systems, ensuring functional safety is essential. For this purpose, different analyses and development artifacts must be produced in accordance with the requirements of relevant standards (e.<\/span><\/span>g.,\u00a0<\/span><\/span>ISO 12100, IEC 61508, ISO 13849, EN 50128, ISO 26262, ISO 25119). In this respect, hazard\u00a0<\/span><\/span>analyses\u00a0<\/span><\/span>and risk\u00a0<\/span><\/span>assessments<\/span><\/span>, safety analyses, safety requirements, safety concepts<\/span><\/span>,<\/span><\/span>\u00a0and\u00a0<\/span><\/span>safety c<\/span><\/span>ases<\/span><\/span>\u00a0<\/span><\/span>must be included<\/span><\/span>. In practice, these artifacts are usually created and managed using document processing and spreadsheet tools such as Microsoft Word, Excel<\/span><\/span>\u00a0<\/span><\/span>or\u00a0<\/span><\/span>Visio<\/span><\/span>.\u00a0<\/span><\/span>As<\/span><\/span>\u00a0the complexity of the systems continues to increase, there are limits here, as important characteristics such as maintainability<\/span><\/span>\u00a0<\/span><\/span>and\u00a0<\/span><\/span>traceability<\/span><\/span>\u00a0<\/span><\/span>cannot be\u00a0<\/span><\/span>adequately\u00a0<\/span><\/span>guaranteed.\u00a0<\/span><\/span>This ultimately<\/span><\/span>\u00a0results in problems with the efficiency and quality<\/span><\/span>\u00a0of the\u00a0<\/span><\/span>development<\/span><\/span>\u00a0artifacts and, consequently, of the whole system,<\/span><\/span>\u00a0<\/span><\/span>which in the best case only costs money and, in the worst case, human lives.<\/span><\/span>\u00a0<\/span><\/p>\n

 <\/p>\n