Hier finden Sie wissenschaftliche Publikationen aus den Fraunhofer-Instituten.

Guidelines - creating use cases for embedded systems

: Denger, C.; Paech, B.; Benz, S.

urn:nbn:de:0011-n-187012 (948 KByte PDF)
MD5 Fingerprint: 832e09c5898d82673bf4a220c5026b45
Created on: 01.10.2003

Kaiserslautern, 2003, VIII, 58 pp. : Ill., Lit.
IESE-Report, 078.03/E
Reportnr.: 078.03/E
Report, Electronic Publication
Fraunhofer IESE ()
requirements specification; use case; QUASAR; monitored variable; controlled variable

In the automotive domain, the increasing complexity of software demands a requirements process that is tailored to the needs of the stakeholders involved in the development process. UCs and Statecharts are commonly used as specification techniques in many projects. In this report we present guidelines to derive UCs for embedded systems in a systematic, repeatable und verifiable way. We illustrate them with a case study for developing an electronic control unit for a car. These guidelines have been collected from literature and from several case studies. In the second part of the report we describe in detail an evaluation of these guidelines in the context of a Praktikum at the University of Kaiserslautern in summer term 2003.

Table of Contents S.vii-viii
1 Introduction S.1
2 General Guidelines for Text Documents S.2
3 Deriving Use Cases S.3-14
- 3.1 Step 1: Create list of actors S.3
- 3.2 Step 2: Create list of tasks of the actors and visualize as UC diagram S.3-4
- 3.3 Step 3: Define inputs (monitored variables) and outputs (controlled variables) of the function blocks and create context diagram S.4-7
- 3.4 Step 4: Refine tasks according to monitored/controlled variables and refine UC diagram and context diagram accordingly S.7-10
- 3.5 Step 5: Fill out UC template for each identified UC S.10-14
- 3.5.1 Preconditon S.12
- 3.5.2 Flow of events S.12
- 3.5.4 Rules S.13
- 3.5.3 Exceptions S.13-14
- 3.5.5 Quality constraints S.14
- 3.5.6 Monitored and controlled Variables S.14
- 3.5.7 Postcondition S.14
4 Evaluation of the Use-Cases Guidelines S.15-47
- 4.2 The Context of the Case Study S.15-23
- 4.2.1 The Empirical Approach in the Case Study S.16-17
- 4.2.2 The Subject's Qualification S.17-20
- 4.2.3 The subject's experiences in the field of Requirements Engineering S.20-23
- 4.3 The "Pre-Questionnaire" S.23-26
- 4.4 Evaluation of the UC Guidelines S.27-44
- 4.4.1 General information regarding the task S.27-29
- 4.4.2 Understandability of the UC guidelines S.29-31
- 4.4.3 Evaluation following the model of Davis S.31-42
- 4.4.4 Group Evaluation S.42-44
- 4.5 Limitations of the Case Study S.44-45
- 4.6 Conclusion and Lessons Learned S.45-47
- Acknowledgement S.47
References S.48
Appendix S.49-60