Survey of Concerns in Embedded Systems Requirements Engineering

2013 ◽  
Vol 7 (1) ◽  
pp. 1-13 ◽  
Author(s):  
Daniel Aceituna
Keyword(s):  
Embedded Systems ◽  
Requirements Engineering ◽  
Systems Requirements

Debugging Embedded Systems Requirements Before The Design Begins

2017 ◽  
Vol 36 (2) ◽  
pp. 58-59
Author(s):  
Fabien Gaucher ◽  
Yves Génevaux
Keyword(s):  
Embedded Systems ◽  
Systems Requirements

scholarly journals Industrial Examples of Formal Specifications for Test Case Generation

10.29007/z9ph ◽  
2018 ◽  
Author(s):  
Hendrik Roehm ◽  
Rainer Gmehlich ◽  
Thomas Heinz ◽  
Jens Oehlerking ◽  
Matthias Woehrle
Keyword(s):  
Embedded Systems ◽  
Requirements Engineering ◽  
Automotive Industry ◽  
Test Case Generation ◽  
Test Case ◽  
Formal Specifications ◽  
Discrete Events ◽  
The Past ◽  
Formal Representations

While requirements engineering has received considerable attention inacademia over the past years, formalization of requirements for physicallyinfluenced systems is still a difficult task in practice. In this paper, we giveformal representations of some typical requirement classes arising in theautomotive industry. We divide these patterns into three main classes:those mostly referring to properties of continuous signals, those mostlyreferring to discrete events and those referring to similarity to a referencesignal. We discuss these patterns on concrete examples from automotiveembedded systems, where specifications are used for test case generation.

Requirements Engineering

2011 ◽  
pp. 1-20 ◽  
Author(s):  
Päivi Parviainen ◽  
Maarit Tihinen ◽  
Marco Lormanms ◽  
Rini van Solingen
Keyword(s):  
Requirements Engineering ◽  
Sociotechnical Systems ◽  
Software Requirements ◽  
Main Process ◽  
Vast Number ◽  
Complex Process ◽  
System Requirements ◽  
Systems Requirements ◽  
Continuous Activities ◽  
Requirements Development

This chapter introduces requirements engineering for sociotechnical systems. Requirements engineering for sociotechnical systems is a complex process that considers product demands from a vast number of viewpoints, roles, responsibilities, and objectives. This chapter explains the requirements engineering terminology and describes the requirements engineering process in detail, with examples of available methods for the main process activities. The main activities described include system requirements development, requirements allocation and flow-down, software requirements development, and continuous activities, including requirements documentation, requirements validation and verification, and requirements management. As requirements engineering is the process with the largest impact on the end product, it is recommended to invest more effort in both industrial application as well as research to increase understanding and deployment of the concepts presented in this chapter.

Guiding requirements engineering for software-intensive embedded systems in the automotive industry

2010 ◽  
Vol 29 (1) ◽  
pp. 21-43 ◽  
Author(s):  
Peter Braun ◽  
Manfred Broy ◽  
Frank Houdek ◽  
Matthias Kirchmayr ◽  
Mark Müller ◽  
...  
Keyword(s):  
Embedded Systems ◽  
Requirements Engineering ◽  
Automotive Industry ◽  
Software Intensive

4.3.2 Requirements Engineering for Trusted Embedded Systems

2010 ◽  
Vol 20 (1) ◽  
pp. 490-502
Author(s):  
José L. Fernández ◽  
Rubén Alonso ◽  
Francisco Gómez ◽  
Christophe Jouvray ◽  
Yann Rouxel ◽  
...  
Keyword(s):  
Embedded Systems ◽  
Requirements Engineering

Non-Functional Requirements and UML Stereotypes

2005 ◽  
pp. 2135-2140
Author(s):  
Guadalupe Salazar-Zarate ◽  
Pere Botella
Keyword(s):  
Requirements Engineering ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Functional Requirements ◽  
Research Issues ◽  
Unified Modeling ◽  
Open Research ◽  
The Future ◽  
Systems Requirements

In Nuseibeh and Easterbrook (2000), an overview of the field of software and systems requirements engineering is presented. Therein is highlighted some key open-research issues for the future of the Requirements Engineering (RE). Some of the major challenges mentioned there, are related with the necessity of richer models for capturing and analyzing non-functional requirements. This paper draws some possible extensions of Unified Modeling Language (UML) (Booch, G., Jacobson, I. and Rumbaugh, J., 1998) in order to include non-functional requirements.

Sign in / Sign up

Export Citation Format

Share Document