{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

7_Requirements engineering for embedded system

7_Requirements engineering for embedded system -...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Requirements Engineering for Embedded Systems 1 ) Manfred Broy Technische Universität München, Institut für Informatik 80290 München e-mail: [email protected] FAX: +49 89 / 289 28183 Keywords: Requirements engineering, specification, dependability, real-time, safety critical Abstract In requirements engineering for embedded systems the fundamental functional and non-functional requirements for a system with an embedded software system are discussed, captured, analysed, validated, and documented. We suggest a stepwise proceeding. We advise to describe the requirements in terms of different system views obtained from an abstract logical architecture of an embedded system. By the logical architecture a system and its context are decomposed into four components. We discuss the nature of these components and the need and techniques to model their behaviours. 1. Introduction The general purpose of an embedded hardware/software system is to regulate a physical device by sending control signals to actuators in reaction to input signals provided by its users and by sensors capturing the relevant state parameters of the system. We therefore call an embedded system also a reactive system . The control is achieved by processing information coming from sensors and user interfaces and controlling some actuators that regulate the physical devices. The reliability of a system with an embedded software system depends on well-actuated reactions according to the users’ expectations, even in exceptional situations. This reaction of the overall system is to a critical extend determined by the embedded software system that is a part of the overall system. The task of the embedded system is to guarantee, as far as the physical parts function properly, the adequate behaviour of the overall system. Therefore the requirements for the embedded system have to be captured and formulated in terms of the behaviour of the overall system. In the development of embedded reactive systems the specification of the required functionality is a most critical issue. Statistics show that in typical application areas more than 1 ) This work was partially sponsored by the Sonderforschungsbereich 342 "Werkzeuge und Methoden für die Nutzung paralleler Rechnerarchitekturen", by the BMBF project KorSys, and the industrial research project SysLab.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
- 2 - 50 % of the problems (malfunctions) that occur within delivered systems and that are reported by the customers are not problems with the correctness of the implementation but with misconceptions in capturing the requirements (called conceptual requirements errors ). Embedded systems - especially when running in risk critical applications - demand a high degree of reliability. Basis of the reliability of a system is the careful capturing of the adequate user requirements. 2. The Requirements Engineering Process
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 11

7_Requirements engineering for embedded system -...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon bookmark
Ask a homework question - tutors are online