How does the AUTOSAR Ecosystem Impact Requirement Engineering?

AUTOSAR aims at facilitating reuse of standardized software components in automotive software development. For this, it defines three layers: the application components (with standardized interfaces between components), the (standardized) runtime environment, and the basic software (which abstracts the hardware and contains the driver modules). Despite this standardization, the combination of application components, runtime and basic software should still offer differentiating functionality for cars. In an exploratory study, we found this situation challenging for Requirements Engineering practice, where standard requirements implied by the AUTOSAR standard should be treated differently from OEM specific requirements targeted towards differentiation or innovation features.

We will discuss our preliminary findings at the 23rd IEEE International Requirements Conference 2015 in Ottawa, Canada during the poster and tool demo session as well as our method in the 5th IEEE International Workshop on Empirical Requirements Engineering.

Continue reading

Panel on Empirical Requirements Engineering, EmpiRE@RE’12

Yesterday, I participated in the workshop on empirical requirements engineering. My notes on the talks will follow shortly, but I want to highlight the excellent panel that concluded the workshop. The panelists where Nan Niu, Jörg Dörr and Neil Maiden. Note, that the panelists were required to be provocative in their statements. Also note that I will add more links and references to this article later. Continue reading