Towards the model-driven engineering of security requirements for embedded systems

Yves Roudier, Muhammad Sabir Idrees, Ludovic Apvrille

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

This paper discusses why and how security requirements engineering must be adapted to the model-driven approach usually adopted to design and develop embedded systems. In particular, we discuss to what extent the elicitation of security requirements and the Y-chart partitioning approach, a central design methodology in embedded systems, can mutually enrich each other. We also show how SysML, which is already commonly used to engineer requirements in embedded systems, can also represent security requirements, assets, and threats with only a few extensions and thus support a more comprehensive requirements engineering methodology. We illustrate the use of our overall methodology and toolkit with examples from the automotive embedded system field in order to demonstrate the relevance of our approach.

Original languageEnglish
Title of host publication2013 3rd International Workshop on Model-Driven Requirements Engineering, MoDRE 2013 - Proceedings
Pages55-64
Number of pages10
DOIs
Publication statusPublished - 21 Oct 2013
Externally publishedYes
Event2013 3rd International Workshop on Model-Driven Requirements Engineering, MoDRE 2013 - Rio de Janeiro, Brazil
Duration: 15 Jul 201315 Jul 2013

Publication series

Name2013 3rd International Workshop on Model-Driven Requirements Engineering, MoDRE 2013 - Proceedings

Conference

Conference2013 3rd International Workshop on Model-Driven Requirements Engineering, MoDRE 2013
Country/TerritoryBrazil
CityRio de Janeiro
Period15/07/1315/07/13

Keywords

  • Communication System Security
  • Component Architectures
  • Computer Security
  • Design methodology
  • Embedded Systems
  • Security Requirements Engineering
  • System-level design

Fingerprint

Dive into the research topics of 'Towards the model-driven engineering of security requirements for embedded systems'. Together they form a unique fingerprint.

Cite this