Requirements Engineering
Requirements engineering is a fundamental part in the development of safety related embedded systems. Requirements engineering comprises eliciting, developing, analysing, validating, communicating and managing requirements. As the development of systems i
- PDF / 1,553,309 Bytes
- 75 Pages / 439.36 x 666.15 pts Page_size
- 51 Downloads / 257 Views
Requirements Engineering Markus Ortel, Marc Malot, Andreas Baumgart, Jan Steffen Becker, Ralf Bogusch, Stefan Farfeleder, Nora Gerber, Oystein Haugen, Stefan H¨ausler, Bernhard Josko, Jason Mansell, Andreas Mitschke, Roopak Sinha, Tor Stalhane, Niina Uusitalo, and Philip Rehkop
3.1 Introduction Requirements engineering is a fundamental part in the development of safety related embedded systems. Requirements engineering comprises eliciting, developing, analysing, validating, communicating and managing requirements. As the development of systems is based on the identified and developed requirements it is important that requirements accurately capture the stakeholder needs, are M. Ortel () P. Rehkop OFFIS, Oldenburg, Germany e-mail: [email protected] A. Baumgart J.S. Becker S. H¨ausler B. Josko OFFIS e. V., Oldenburg, Germany R. Bogusch CASSIDIAN S. Farfeleder, Language, Boilerplate Analyzes N. Gerber N. Uusitalo Infineon O. Haugen Stiftelsen SINTEF, Trondheim, Norway M. Malot Sagem D´efense S´ecurit´e, Paris, France J. Mansell Fundaci´on European Software Insitute, Donostia-San Sebasti`an, Spain A. Mitschke EADS Deutschland GmbH, Munich, Germany R. Sinha Institut National de Recherche en Informatique et en Automatique, Paris, France T. Stalhane Norwegian University of Science and Technology, Trondheim, Norway A. Rajan and T. Wahl (eds.), CESAR - Cost-efficient Methods and Processes for Safety-relevant Embedded Systems, DOI 10.1007/978-3-7091-1387-5 3, © Springer-Verlag Wien 2013
69
70
M. Ortel et al.
Elicitation Definition Analysis Definition
System
Analysis
Definition
Subsystem
Analysis
Definition
Module
Analysis
Management
Fig. 3.1 Basic understanding of the RE process
well-understood and verifiable. Due to that, requirements engineering guidelines and safety standards request several constraints on requirement statements like well-formedness, unambiguity and formalization. Moreover, requirements should be consistent and they should be satisfied by the proposed implementation (Fig. 3.1). The ISO standard 29148 [94] – cf. also [92, 93] – considers two main requirements engineering activities: (1) Requirements Development and (2) Requirements Management. Requirement Development is applied during the development process on all hierarchy levels starting from development of stakeholder requirements over development of system requirements down to development of module requirements. Each cycle contains the sub activities (1) Define Requirements (of the considered level) and (2) Analyze Requirements. The top-level Development of Stakeholder Requirements contains a sub-activity Elicit Stakeholder Needs, which are transferred in the subsequent sub-activity into stakeholder requirements. CESAR itself does not define a specific requirements engineering process – as such a process may be company- or project-specific – but CESAR provides specific methods and tools that can be used within a concrete requirements engineering process addressing the activities mentioned above. All elements are incl
Data Loading...
