Maritta Heisel

Prof. Dr. Maritta Heisel
Raum BB 919
Tel. : +49 203 379 3465
Fax : +49 379 4490
E-Mail : maritta.heisel[at]uni-duisburg-essen.de

Research
  • Compliance [Veröffentlichungen]
  • Formal Methods [Veröffentlichungen]
  • Methodology [Veröffentlichungen]
  • Patterns [Veröffentlichungen]
  • Privacy [Veröffentlichungen]
  • Requirements Engineering [Veröffentlichungen]
  • Safety
    Veröffentlichungen:

    QuickSearch:   Number of matching entries: 0.

    YearTitleAuthorJournal/ProceedingsPublisher
    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 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/}
    }
    
    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}
    }
    

    Created by JabRef on 13/03/2018.

  • Security [Veröffentlichungen]
  • Software Architecture [Veröffentlichungen]
  • Software Quality [Veröffentlichungen]
  • Test [Veröffentlichungen]