Combining Requirements, Use Case Maps and AADL Models for Safety-Critical Systems Design

Good requirements engineering practices are essentialfor developing correct safety-critical systems. In this paper, we report our experience in combining existing rich modelinglanguages such as AADL (Architecture Analysis and DesignLanguage), URN (User Requirements Notation) and RDAL(Requirements Definition and Analysis Language) to supporta requirements engineering and design process as promotedby the FAA Requirements Engineering Management Handbook(REMH). Each of the combined language is well suited for thecapture of specific concerns of the REMH practices allowingreusing the capability from the individual languages but alsofrom their combined use. Our approach has been applied to thespecification and analysis of a medical device example from theREMH and shows several benefits due to the early discovery oferrors resulting from each modeling language and from theircombination. This experience also identifies important needs for automated model management not covered by current state-of the-art modeling techniques.

[1]  Dominique Blouin,et al.  Defining an annex language to the architecture analysis and design language for requirements engineering activities support , 2011, 2011 Model-Driven Requirements Engineering Workshop.

[2]  Dominique Blouin,et al.  Model-Driven Requirements Engineering for Embedded Systems Development , 2013, 2013 39th Euromicro Conference on Software Engineering and Advanced Applications.

[3]  Lawrence D. Pohlmann,et al.  Customer‐Centered Products – Creating Successful Products through Smart Requirements Management , 2001 .

[4]  Silvia Mara Abrahão,et al.  A systematic review of the use of requirements engineering techniques in model-driven development , 2010, MODELS'10.

[5]  John Mylopoulos,et al.  Specifying and analyzing early requirements in Tropos , 2004, Requirements Engineering.

[6]  Axel van Lamsweerde,et al.  Requirements Engineering: From System Goals to UML Models to Software Specifications , 2009 .

[7]  Julien Delange,et al.  Architecture Fault Modeling with the AADL Error-Model Annex , 2014, 2014 40th EUROMICRO Conference on Software Engineering and Advanced Applications.

[8]  Jörgen Hansson,et al.  System Architecture Virtual Integration: An Industrial Case Study , 2009 .

[9]  Ivan Kurtev,et al.  Generation and validation of traces between requirements and architecture based on formal trace semantics , 2014, J. Syst. Softw..

[10]  Christophe Ponsard,et al.  Towards a Model-Driven Approach for Mapping Requirements on AADL Architectures , 2009, 2009 14th IEEE International Conference on Engineering of Complex Computer Systems.

[11]  Kristin A. Farry,et al.  Customer Centered Products: Creating Successful Products Through Smart Requirements Management (Продукты для клиента: создание успешных продуктов с помощью грамотного управления требованиями) , 2000 .

[12]  Dominique Blouin Modeling languages for requirements engineering and quantitative analysis of embedded systems , 2013 .

[13]  Axel van Lamsweerde,et al.  From Object Orientation to Goal Orientation: A Paradigm Shift for Requirements Engineering , 2002, RISSEF.