Research Topics
Research Topic Safety
Publications:| Year | Title | Author | Journal/Proceedings | Publisher | |
|---|---|---|---|---|---|
| 2019 | Integration of Development Interface Agreement, Supplier Safety Assessment and Safety Management for Driver Assistance Systems | Frese, T., Côté, I., Hatebur, D. & Heisel, M. | Mobilität in Zeiten der Veränderung | Springer | |
BibTeX:
@incollection{mobi19,
year = {2019},
title = {Integration of Development Interface Agreement, Supplier Safety Assessment and Safety Management for Driver Assistance Systems},
booktitle = {Mobilit{\"{a}}t in Zeiten der Ver{\"{a}}nderung},
author = {Frese, Thomas and C{\^{o}}t{\'{e}}, Isabelle and Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
pages = {241 -- 251},
url = {www.springer.com}
}
|
|||||
| 2019 | Combining Safety and Security in Autonomous Cars Using Blockchain Technologies | Davi, L., Hatebur, D., Heisel, M. & Wirtz, R. | Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
BibTeX:
@proceedings{,
year = {2019},
title = {Combining Safety and Security in Autonomous Cars Using Blockchain Technologies},
booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Davi, Lucas and Hatebur, Denis and Heisel, Maritta and Wirtz, Roman},
publisher = {Springer},
url = {www.springer.com}
}
|
|||||
| 2018 | Functional Safety Processes and Driver Assistance Systems: Evolution or Revolution? | Frese, T., Hatebur, D., Côté, I. & Heisel, M. | Mobilität und digitale Transformation - Technische und betriebswirtschaftliche Aspekte | Springer | |
BibTeX:
@incollection{mobi2018,
year = {2018},
title = {Functional Safety Processes and Driver Assistance Systems: Evolution or Revolution?},
booktitle = {Mobilit{\"{a}}t und digitale Transformation - Technische und betriebswirtschaftliche Aspekte},
author = {Frese, Thomas and Hatebur, Denis and C{\^{o}}t{\'{e}}, Isabelle and Heisel, Maritta},
publisher = {Springer},
pages = {199 - 216},
url = {www.springer.com}
}
|
|||||
| 2017 | A structured and systematic model-based development method for automotive systems, considering the OEM/supplier interface | Beckers, K., Côté, I., Frese, T., Hatebur, D. & Heisel, M. | Reliability Engineering & System Safety | ||
| Abstract: Abstract The released ISO 26262 standard for automotive systems requires to create a hazard analysis and risk assessment and to create safety goals, to break down these safety goals into functional safety requirements in the functional safety concept, to specify technical safety requirements in the safety requirements specification, and to perform several validation and verification activities. Experience shows that the definition of technical safety requirements and the planning and execution of validation and verification activities has to be done jointly by OEMs and suppliers. In this paper, we present a structured and model-based safety development approach for automotive systems. The different steps are based on Jackson's requirement engineering. The elements are represented by UML notation extended with stereotypes. The UML model enables a rigorous validation of several constraints. We make use of the results of previously published work to be able to focus on the OEM/supplier interface. We illustrate our method using a three-wheeled-tilting control system (3WTC) as running example and case study. | |||||
BibTeX:
@article{Beckers2016-4,
year = {2017},
title = {A structured and systematic model-based development method for automotive systems, considering the OEM/supplier interface},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
journal = {Reliability Engineering \& System Safety},
volume = {158},
pages = {172 - 184},
note = {Special Sections : Reliability and Safety Certification of Software-Intensive Systems},
url = {http://www.sciencedirect.com/science/article/pii/S0951832016304057},
doi = {10.1016/j.ress.2016.08.018}
}
|
|||||
| 2017 | A structured hazard analysis and risk assessment method for automotive systems—A descriptive study | Beckers, K., Holling, D., Côté, I. & Hatebur, D. | Reliability Engineering & System Safety | ||
| Abstract: Abstract The 2011 release of the first version of the ISO 26262 standard for automotive systems demand the elicitation of safety goals following a rigorous method for hazard and risk analysis. Companies are struggling with the adoption of the standard due to ambiguities, documentation demands and the alignment of the standards demands to existing processes. We previously proposed a structured engineering method to deal with these problems developed in applying action research together with an OEM. In this work, we evaluate how applicable the method is for junior automotive software engineers by a descriptive study. We provided the method to 8 members of the master course Automotive Software Engineering (ASE) at the Technical University Munich. The participants have each been working in the automotive industry for 1–4 years in parallel to their studies. We investigated their application of our method to an electronic steering column lock system. The participants applied our method in a first round alone and afterwards discussed their results in groups. Our data analysis revealed that the participants could apply the method successfully and the hazard analysis and risk assessment achieved a high precision and productivity. Moreover, the precision could be improved significantly during group discussions. | |||||
BibTeX:
@article{Beckers2016-5,
year = {2017},
title = {A structured hazard analysis and risk assessment method for automotive systems—A descriptive study},
author = {Beckers, Kristian and Holling, Dominik and C{\^{o}}t{\'{e}}, Isabelle and Hatebur, Denis},
journal = {Reliability Engineering & System Safety},
volume = {158},
pages = {185 - 195},
note = {Special Sections : Reliability and Safety Certification of Software-Intensive Systems},
url = {http://www.sciencedirect.com/science/article/pii/S0951832016305002},
doi = {10.1016/j.ress.2016.09.004}
}
|
|||||
| 2017 | Deriving Safety Requirements according to ISO 26262 for complex systems: A method applied in the automotive industrie | Frese, T., Heisel, M., Hatebur, D. & Côté, I. | Innovative Produkte und Dienstleisungen in der Mobilität | ||
BibTeX:
@article{mobi2017,
year = {2017},
title = {Deriving Safety Requirements according to ISO 26262 for complex systems: A method applied in the automotive industrie},
author = {Frese, Thomas and Heisel, Maritta and Hatebur, Denis and C{\^{o}}t{\'{e}}, Isabelle},
journal = {Innovative Produkte und Dienstleisungen in der Mobilit{\"{a}}t},
volume = {Wissenschaftsforum Mobilit{\"{a}}t 8},
pages = {211-222}
}
|
|||||
| 2017 | Performing a More Realistic Safety Analysis by Means of the Six-Variable Model | Ulfat-Bunyadi, N., Hatebur, D. & Heisel, M. | Automotive - Safety & Security 2017 | GI | |
| Abstract: Safety analysis typically consists of hazard analysis and risk assessment (HARA) as well as fault tree analysis (FTA). During the first, possible hazardous events are identified. During the latter, failure events that can lead to a hazardous event are identified. Usually, the focus of FTA is on identifying failure events within the system. However, a hazardous event may also occur due to invalid assumptions about the system’s environment. If the possibility that environmental assumptions turn invalid is considered during safety analysis, a more realistic and complete safety analysis is performed than without considering them. Yet, a major challenge consists in eliciting first the ‘real’ environmental assumptions. Developers do not always document assumptions, and often they are not aware of the assumptions they make. In previous work, we defined the Six-Variable Model which provides support in making the ‘real’ environmental assumptions explicit. In this paper, we define a safety analysis method based on the Six-Variable Model. The benefit of our method is that we make the environmental assumptions explicit and consider them in safety analysis. In this way, assumptions that are too strong and too risky can be identified and weakened or abandoned if necessary. | |||||
BibTeX:
@inproceedings{UHH-ASS2017,
year = {2017},
title = {Performing a More Realistic Safety Analysis by Means of the Six-Variable Model},
booktitle = {Automotive - Safety & Security 2017},
author = {Ulfat-Bunyadi, Nelufar and Hatebur, Denis and Heisel, Maritta},
publisher = {GI},
volume = {P-269},
series = {Lecture Notes in Informatics},
pages = {135-148},
url = {https://dl.gi.de/handle/20.500.12116/152}
}
|
|||||
| 2015 | A Structured Validation and Verification Method for Automotive Systems considering the OEM/Supplier Interface | Beckers, K., Côté, I., Frese, T., Hatebur, D. & Heisel, M. | Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: The released ISO 26262 standard for automotive systems requires several validation and verification activities. These validation and verification activities have to be planned and performed jointly by the OEMs and the suppliers. In this paper, we present a systematic, structured and model-based method to plan the required validation and verification activities and collect the results. Planning and the documentation of performed activities are represented by a UML notation extended with stereotypes. The UML model supports the creation of the artifacts required by ISO 26262, enables document generation and a rigorous check of several constraints expressed in OCL. We illustrate our method using the example of an electronic steering column lock system. | |||||
BibTeX:
@inproceedings{fs2015,
year = {2015},
title = {A Structured Validation and Verification Method for Automotive Systems considering the OEM/Supplier Interface},
booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
volume = {9337},
pages = {90 - 107},
url = {www.springer.com}
}
|
|||||
| 2014 | Systematic Derivation of Functional Safety Requirements for Automotive Systems | Beckers, K., Côté, I., Frese, T., Hatebur, D. & Heisel, M. | Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: The released ISO 26262 standard for automotive systems requires breaking down safety goals from the hazard analysis and risk assessment into functional safety requirements in the functional safety concept. It has to be justi ed that the de ned functional safety requirements are suitable to achieve the stated safety goals. In this paper, we present a systematic, structured and model-based method to de ne functional safety requirements using a given set of safety goals. The rationale for safety goal achievement, the relevant attributes of the functional safety requirements, and their relationships are represented by a UML notation extended with stereotypes. The UML model enables a rigorous validation of several constraints expressed in OCL. We illustrate our method using an example electronic steering column lock system. |
|||||
BibTeX:
@inproceedings{safecomp2014,
year = {2014},
title = {{Systematic Derivation of Functional Safety Requirements for Automotive Systems}},
booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 8666},
pages = {65--80},
url = {https://link.springer.com/}
}
|
|||||
| 2013 | A Structured and Model-Based Hazard Analysis and Risk Assessment Method for Automotive Systems | Beckers, K., Frese, T., Hatebur, D. & Heisel, M. | Proceedings of the 24th IEEE International Symposium on Software Reliability Engineering | IEEE Computer Society | |
| Abstract: The released ISO 26262 standard requires a hazard analysis and risk assessment for automotive systems to determine the necessary safety measures to be implemented for a certain feature. In this paper, we present a structured and model-based hazard analysis and risk assessment method for automotive systems. The hazard analysis and risk assessment are based on a requirements engineering process using problem frames. Their elements are represented by a UML notation extended with stereotypes. The UML model enables a rigorous validation of several constraints expressed in OCL. We illustrate our method using an electronic steering column lock system. |
|||||
BibTeX:
@inproceedings{Beckers2013-issre,
year = {2013},
title = {A Structured and Model-Based Hazard Analysis and Risk Assessment Method for Automotive Systems},
booktitle = {Proceedings of the 24th IEEE International Symposium on Software Reliability Engineering},
author = {Beckers, Kristian and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
publisher = {IEEE Computer Society},
pages = {238-247},
url = {http://www.ieee.org/}
}
|
|||||
| 2012 | Pattern- and Component-based Development of Dependable Systems | Hatebur, D. | School: University of Duisburg-Essen | Deutscher Wissenschafts-Verlag (DWV) Baden-Baden | |
BibTeX:
@phdthesis{Hatebur2012,
year = {2012},
title = {Pattern- and Component-based Development of Dependable Systems},
author = {Hatebur, Denis},
publisher = {Deutscher Wissenschafts-Verlag (DWV) Baden-Baden},
school = {University of Duisburg-Essen},
url = {http://www.dwverlag.de/index.php?art=Pattern-+and+Component-based+Development+of+Dependable+Systems&mod=Onlineshop&view=Artikel&abid=166}
}
|
|||||
| 2010 | A UML Profile for Requirements Analysis of Dependable Software | Hatebur, D. & Heisel, M. | Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: At Safecomp 2009, we presented a foundation for requirements analysis of dependable software. We defined a set of patterns for expressing and analyzing dependability requirements, such as confidentiality, integrity, availability, and reliability. The patterns take into account random faults as well as certain attacks and therefore support a combined safety and security engineering. In this paper, we demonstrate how the application of our patterns can be tool supported. We present a UML profile allowing us to express the different dependability requirements using UML diagrams. Integrity conditions are expressed using OCL. We provide tool support based on the Eclipse development environment, extended with an EMF-based UML tool, e.g., Papyrus UML. We illustrate how to use the profile to model dependability requirements of a cooperative adaptive cruise control system. |
|||||
BibTeX:
@inproceedings{HateburHeisel2010b,
year = {2010},
title = {A {UML} Profile for Requirements Analysis of Dependable Software},
booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 6351},
pages = {317--331},
url = {https://link.springer.com/}
}
|
|||||
| 2009 | A Foundation for Requirements Analysis of Dependable Software | Hatebur, D. & Heisel, M. | Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: We present patterns for expressing dependability requirements, such as confidentiality, integrity, availability, and reliability. The paper considers random faults as well as certain attacks and therefore supports a combined safety and security engineering. The patterns - attached to functional requirements - are part of a pattern system that can be used to identify missing requirements. The approach is illustrated on a cooperative adaptive cruise control system. |
|||||
BibTeX:
@inproceedings{HH09b,
year = {2009},
title = {A Foundation for Requirements Analysis of Dependable Software},
booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 5775},
pages = {311--325},
url = {https://link.springer.com/}
}
|
|||||
| 2007 | Enhancing Dependability of Component-Based Systems | Lanoix, A., Hatebur, D., Heisel, M. & Souquières, J. | Reliable Software Technologies -- Ada Europe 2007 | Springer | |
| Abstract: We present an approach for enhancing dependability of component- based software. Functionality related to security, safety and reliability is encapsulated in specific components, allowing the method to be applied to off-the-shelf components. Any set of components can be extended with dependability features by wrapping them with special components, which monitor and filter input and outputs. This approach is supported by a rigorous development methodology based on UML and the B method and is introduced on the level of software architecture. |
|||||
BibTeX:
@inproceedings{LHH+2007,
year = {2007},
title = {Enhancing Dependability of Component-Based Systems},
booktitle = {Reliable Software Technologies -- Ada Europe 2007},
author = {Lanoix, Arnaud and Hatebur, Denis and Heisel, Maritta and Souqui{\`{e}}res, Jeanine},
publisher = {Springer},
series = {LNCS 4498},
pages = {41--54},
url = {https://link.springer.com/}
}
|
|||||
| 2006 | Security Engineering using Problem Frames | Hatebur, D., Heisel, M. & Schmidt, H. | Proceedings of the International Conference on Emerging Trends in Information and Communication Security (ETRICS) | Springer | |
| Abstract: We present a method for security engineering, which is based on two special kinds of problem frames that serve to structure, characterize, analyze, and finally solve software development problems in the area of software and system security. Both kinds of problem frames constitute patterns for representing security problems, variants of which occur frequently in practice.We present security problem frames, which are instantiated in the initial step of our method. They explicitly distinguish security problems from their solutions. To prepare the solution of the security problems in the next step, we employ concretized security problem frames capturing known approaches to achieve security. Finally, the last step of our method results in a specification of the system to be implemented given by concrete security mechanisms and instantiated generic sequence diagrams. We illustrate our approach by the example of a secure remote display system. |
|||||
BibTeX:
@inproceedings{HHS2006a,
year = {2006},
title = {Security Engineering using Problem Frames},
booktitle = {Proceedings of the International Conference on Emerging Trends in Information and Communication Security (ETRICS)},
author = {Hatebur, Denis and Heisel, Maritta and Schmidt, Holger},
publisher = {Springer},
volume = {3995/2006},
pages = {238--253},
url = {https://link.springer.com/}
}
|
|||||
| 2005 | A Model-Based Development Process for Embedded Systems | Heisel, M. & Hatebur, D. | Proc. Workshop on Model-Based Development of Embedded Systems | ||
| Abstract: We present a development process for embedded systems which emerged from industrial practice. This process covers hardware and software components for systems engineering, but the main focus is on embedded software components and the modeling of problems, specications, tests and architectures. Each step of the process has validation conditions associated with it that help to detect errors as early as possible. |
|||||
BibTeX:
@inproceedings{HH2005a,
year = {2005},
title = {A Model-Based Development Process for Embedded Systems},
booktitle = {Proc. Workshop on Model-Based Development of Embedded Systems},
author = {Heisel, Maritta and Hatebur, Denis},
publisher = {Technical University of Braunschweig},
number = {TUBS-SSE-2005-01},
note = {Available at {\tt http://www.sse.cs.tu-bs.de/publications/MBEES-Tagungsband.pdf}}
}
|
|||||
| 2001 | Specifying Safety-Critical Embedded systems with Statecharts and Z: An Agenda for Cyclic Software Components | Grieskamp, W., Heisel, M. & Dörr, H. | Science of Computer Programming | ||
| Abstract: The application of formal techniques can contribute much to the quality of software, which is of utmost importance for safety-critical embedded systems. These techniques, however, are not easy to apply. In particular, methodological guidance is often unsatisfactory. We address this problem by the concept of an agenda. An agenda is a list of activities to be performed for solving a task in software engineering. Agendas used to support the application of formal specification techniques provide detailed guidance for specifiers, templates of the used specification language that only need to be instantiated, and application independent validation criteria. We apply the agenda approach to a particular class of embedded safety-critical systems, the formal specification of which has been investigated in the case-studies of the German Espress project during the last two years. | |||||
BibTeX:
@article{Grieskamp2001,
year = {2001},
title = {Specifying Safety-Critical Embedded systems with {S}tatecharts and {Z}: An Agenda for Cyclic Software Components},
author = {Grieskamp, Wolfgang and Heisel, Maritta and D{\"{o}}rr, Heiko},
journal = {Science of Computer Programming},
volume = {40},
pages = {31--57}
}
|
|||||
| 1999 | Modeling Safety-Critical Systems with Z and Petri Nets | Heiner, M. & Heisel, M. | Proceedings of the 18th International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: We show how to combine the specification notation Z with Petri nets for modeling safety-critical systems. The combination preserves the strengths of the two formalisms, while ameliorating their drawbacks. We illustrate our approach by modeling a part of a production cell and validating that model with respect to safety-related properties. | |||||
BibTeX:
@inproceedings{Heiner1999,
year = {1999},
title = {Modeling Safety-Critical Systems with {Z} and {P}etri Nets},
booktitle = {Proceedings of the 18th International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Heiner, Monika and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 1698},
pages = {361--374},
url = {http://www.springerlink.com/}
}
|
|||||
| 1999 | Combining Z and Petri Nets for Modeling Safety-Critical Systems | Heiner, M. & Heisel, M. | Sicherheit und Zuverlässigkeit software-basierter Systeme | ||
| Abstract: to be inserted | |||||
BibTeX:
@inproceedings{Heiner1999a,
year = {1999},
title = {Combining {Z} and {P}etri Nets for Modeling Safety-Critical Systems},
booktitle = {Sicherheit und {Z}uverl{\"{a}}ssigkeit software-basierter {S}ysteme},
author = {Heiner, Monika and Heisel, Maritta},
publisher = {Institut f{\"{u}}r Sicherheitstechnologie},
series = {Bericht ISTec-A-367},
pages = {249--251},
note = {{ISBN} 3-00-004872-3}
}
|
|||||
| 1999 | Specifying the Safety Controllers of Traffic Light Systems in Z and Statecharts | Winter, K., Santen, T. & Heisel, M. | Sicherheit und Zuverlässigkeit software-basierter Systeme | ||
| Abstract: to be inserted | |||||
BibTeX:
@inproceedings{Winter1999,
year = {1999},
title = {Specifying the Safety Controllers of Traffic Light Systems in {Z} and {S}tatecharts},
booktitle = {Sicherheit und {Z}uverl{\"{a}}ssigkeit software-basierter {S}ysteme},
author = {Winter, Kirsten and Santen, Thomas and Heisel, Maritta},
publisher = {Institut f{\"{u}}r Sicherheitstechnologie},
series = {Bericht ISTec-A-367},
pages = {126--137},
note = {{ISBN} 3-00-004872-3}
}
|
|||||
| 1998 | Specifying safety-critical embedded systems with Statecharts and Z: An Agenda for Cyclic Software Components | Grieskamp, W., Heisel, M. & Dörr, H. | Proc. ETAPS-FASE'98 | Springer | |
| Abstract: The application of formal techniques can contribute much to the quality of software, which is of utmost importance for safety-critical embedded systems. These techniques, however, are not easy to apply. In particular, methodological guidance is often unsatisfactory. We address this problem by the concept of an agenda. An agenda is a list of activities to be performed for solving a task in software engineering. Agendas used to support the application of formal specification techniques provide detailed guidance for specifiers, templates of the used specification language that only need to be instantiated, and application independent validation criteria. We apply the agenda approach to a particular class of embedded safety-critical systems, the formal specification of which has been investigated in the case-studies of the German Espress project during the last two years. | |||||
BibTeX:
@inproceedings{Grieskamp1998,
year = {1998},
title = {Specifying safety-critical embedded systems with {S}tatecharts and {Z}: An Agenda for Cyclic Software Components},
booktitle = {Proc.\ {ETAPS-FASE'98}},
author = {Grieskamp, Wolfgang and Heisel, Maritta and D{\"{o}}rr, Heiko},
publisher = {Springer},
series = {LNCS 1382},
pages = {88--106},
url = {http://www.springerlink.com/}
}
|
|||||
| 1998 | Agendas -- A Concept to Guide Software Development Activites | Heisel, M. | Proc. Systems Implementation 2000 | ||
| Abstract: We present the concept of an agenda. This concept serves to represent process knowledge in the area of software development. An agenda consists of a list of steps to be performed when developing a software artifact. Each activity may have associated a schematic expression of the language in which the artifact is expressed and some validation conditions that help detect errors. We present example agendas and discuss the distinguishing features of the agenda concept in detail. Agendas provide methodological support to their users, make development knowledge explicit and thus comprehensible, and contribute to a standardization of software development activities and products. Agendas are flexible and useful in many different contexts and lay the basis for powerful machine support in software development. | |||||
BibTeX:
@inproceedings{Heisel1998a,
year = {1998},
title = {Agendas -- A Concept to Guide Software Development Activites},
booktitle = {Proc.\ Systems Implementation 2000},
author = {Heisel, Maritta},
publisher = {Chapman \& Hall London},
pages = {19--32}
}
|
|||||
| 1998 | An Agenda for Event-Driven Software Components with Complex Data Models | Winter, K., Santen, T. & Heisel, M. | Proceedings of the 17th International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: We present a method to specify software for a special kind of safetycritical embedded systems, where sensors deliver low-level values that must be abstracted and pre-processed to express functional and safety requirements adequately. These systems are characterized by a reference architecture. The method is expressed as an agenda, which is a list of activities to be performed for setting up the software specification, complemented by validation conditions that help detect and correct errors. The specification language we use is a combination of the formal notation Z and the diagrammatic notation statecharts. Our approach not only provides detailed guidance to specifiers, but it is also part of a more general engineering concept for engineering safety-critical embedded systems that was developed in the ESPRESS project, a joint project of academia and industry. | |||||
BibTeX:
@inproceedings{Winter1998,
year = {1998},
title = {An Agenda for Event-Driven Software Components with Complex Data Models},
booktitle = {Proceedings of the 17th International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Winter, Kirsten and Santen, Thomas and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 1516},
pages = {16--31},
url = {http://www.springerlink.com/}
}
|
|||||
| 1997 | Methodological Support for Formally Specifying Safety-Critical Software | Heisel, M. & Sühl, C. | Proceedings 16th International Conference on Computer Safety, Reliability and Security (SAFECOMP) | Springer | |
| Abstract: We present the concept of an agenda and apply this concept to the formal specification of software for safety-critical applications. An agenda describes a list of activities to solving a task in software engineering, and validations of the results of the activities. Agendas used to support the application of formal specification techniques provide detailed guidance for specifiers, schematic expressions of the used specification language that only need to be instantiated, and application independent validation criteria. We present an agenda for a frequently used design of safety-critical systems and illustrate its usage by an example. Using agendas to systematically develop formal specifications for safety-critical software contributes to system safety because, first, the specifications are developed in a standardized way, making them better comprehensible for other persons. Secondly, using a formal language yields specifications with an unambiguous semantics as the starting point of further design and implementation. Thirdly, the recommended validation criteria draw the specifier’s attention to common mistakes and thus enhance the quality of the resulting specification. |
|||||
BibTeX:
@inproceedings{Heisel1997c,
year = {1997},
title = {Methodological Support for Formally Specifying Safety-Critical Software},
booktitle = {Proceedings 16th International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Heisel, Maritta and S{\"{u}}hl, Carsten},
publisher = {Springer},
pages = {295--308},
url = {https://link.springer.com/}
}
|
|||||
| 1996 | An Approach to Develop Provably Safe Software | Heisel, M. | High Integrity Systems | ||
| Abstract: We present a process model for the development of provably safe software. It is based on well-established tools and techniques to set up formal specifications in the specification language Z and a program synthesis system designed by the author. The model provides a guideline for the specification and implementation of safe software consisting of a number of steps that are complemented by proof obligations. The parts of the process specific to software safety are given special consideration. The approach is exemplified by the specification and partial implementation of a program controlling the pump of a steam boiler. Finally we relate software safety to correctness and reliability. | |||||
BibTeX:
@article{Heisel1996a,
year = {1996},
title = {An Approach to Develop Provably Safe Software},
author = {Heisel, Maritta},
journal = {High Integrity Systems},
volume = {1},
number = {6},
pages = {501--512}
}
|
|||||
| 1995 | Six Steps Towards Provably Safe Software | Heisel, M. | Proceedings of the 14th International Conference on Computer Safety, Reliability and Security (SAFECOMP) | ||
| Abstract: We present an approach to the specification and implementation of provably safe software. It uses well-established tools and techniques that are usually employed to ensure correctness rather than safety of software. The approach comprises six steps each of which is complemented by some proof obligations. For each step the safety-related aspects are clearly elaborated. Thus designers of safety-critical systems are given guidance that helps to avoid potentially dangerous gaps in the specification of the system´s safety properties. | |||||
BibTeX:
@inproceedings{Heisel1995b,
year = {1995},
title = {Six Steps Towards Provably Safe Software},
booktitle = {Proceedings of the 14th International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
author = {Heisel, Maritta},
publisher = {Springer London},
pages = {191--205}
}
|
|||||
Created by JabRef on 11/09/2019.