Software Engineering Institute | Carnegie Mellon University
Software Engineering Institute | Carnegie Mellon University

Digital Library

Javascript is currently disabled for your browser. For an optimal search experience, please enable javascript.

Advanced Search

Basic Search

Content Type

Topics

Publication Date

Presentation

Using Hazard Analysis to Make Early Architecture Decisions for an Autonomous Automotive Application

  • April 2015
  • By Joakim Fröberg (Mälardalen University)
  • This session shows how use cases, activity diagrams, and overview function block diagrams can be defined early and act as input to a preliminary hazard analysis, which in turn provides valuable input to early decisions about partitioning and redundancy.
  • Publisher: Software Engineering Institute
  • This presentation was created for a conference series or symposium and does not necessarily reflect the positions and views of the Software Engineering Institute.
  • Abstract

    Developing a producible autonomous vehicle requires addressing functional safety compliance, an effort that can be considerable. The computer system has a much larger scope than does a traditional automotive system, and many of the functions are critical to avoiding hazardous events, which increases the design and development effort. Some architectural decisions must be made early in the design process and include issues of redundancy, system separation, and functionality limitations. These decisions could greatly influence the effort to achieve the required level of safety at a later stage, and an early analysis of their effects can help avoid unexpected compliance problems later.

    We performed systems engineering tasks on a case of an autonomous hauler for quarry-type work sites. We defined system use cases, developed an overview functional architecture, and performed a preliminary hazard analysis for the intended application. Our proposed method combines common systems and safety engineering tasks that can be conducted early in the life cycle, and we illustrate how the outcome can be analyzed to inform early design decisions.  

    Issues of system partitioning and redundancy have a potentially high impact on the effort to achieve functional safety compliance, and some of those decisions are highly architectural and need addressing relatively early in a design process. Use cases, activity diagrams, and overview function block diagrams can be defined early and act as input to a preliminary hazard analysis, which in turn provides valuable input to early decisions about partitioning and redundancy.

  • Slides

Part of a Collection

SATURN 2015 Presentations