Loading [MathJax]/extensions/tex2jax.js

Eliciting Contextual Requirements at Design Time: A Case Study

Publikation: Beitrag in Buch/Bericht/Sammelwerk/KonferenzbandBeitrag in Buch/SammelwerkForschungPeer-Review

Autorschaft

Organisationseinheiten

Externe Organisationen

  • University of Victoria BC

Details

OriginalspracheEnglisch
Titel des Sammelwerks2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE)
UntertitelProceedings
Herausgeber (Verlag)Institute of Electrical and Electronics Engineers Inc.
Seiten56-63
Seitenumfang8
ISBN (elektronisch)9781479963379
PublikationsstatusVeröffentlicht - 2014
Veranstaltung2014 IEEE 4th International Workshop on Empirical Requirements Engineering - Karlskrona, Schweden
Dauer: 25 Aug. 2014 → …
Konferenznummer: 4

Abstract

The need to consider context in order to understand requirements is established in requirements engineering. Recently, this has been discussed more intensively for sociotechnical systems, which offer a rich spectrum of different operating contexts. Contextual requirements proved valuable to model requirements together with the context they are valid in, but there is a lack of research on how to derive them from stakeholder needs. Our goal in this paper is to explore the usefulness of existing requirements elicitation techniques for the identification of contextual requirements early, i.e. at design time. In a case study we investigate end-user viewpoints, together with interviews, scenarios, prototyping, goal-based analysis, and groupwork as a means to elicit and clarify contextual requirements already at design time. In our case study a certain combination of the applied requirements elicitation techniques stood out as most beneficial for the identification of contextual requirements. In addition, we discovered valuable indicators of differences in the operative context, for example when end-users cannot agree on refinements of specific requirements. Designers and operators of adaptive systems might benefit by taking such conflicts and resulting contextual requirements into account.

ASJC Scopus Sachgebiete

Zitieren

Eliciting Contextual Requirements at Design Time: A Case Study. / Knauss, Alessia; Damian, Daniela; Schneider, Kurt.
2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE): Proceedings. Institute of Electrical and Electronics Engineers Inc., 2014. S. 56-63 6890117.

Publikation: Beitrag in Buch/Bericht/Sammelwerk/KonferenzbandBeitrag in Buch/SammelwerkForschungPeer-Review

Knauss, A, Damian, D & Schneider, K 2014, Eliciting Contextual Requirements at Design Time: A Case Study. in 2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE): Proceedings., 6890117, Institute of Electrical and Electronics Engineers Inc., S. 56-63, 2014 IEEE 4th International Workshop on Empirical Requirements Engineering, Karlskrona, Schweden, 25 Aug. 2014. https://doi.org/10.1109/EmpiRE.2014.6890117
Knauss, A., Damian, D., & Schneider, K. (2014). Eliciting Contextual Requirements at Design Time: A Case Study. In 2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE): Proceedings (S. 56-63). Artikel 6890117 Institute of Electrical and Electronics Engineers Inc.. https://doi.org/10.1109/EmpiRE.2014.6890117
Knauss A, Damian D, Schneider K. Eliciting Contextual Requirements at Design Time: A Case Study. in 2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE): Proceedings. Institute of Electrical and Electronics Engineers Inc. 2014. S. 56-63. 6890117 doi: 10.1109/EmpiRE.2014.6890117
Knauss, Alessia ; Damian, Daniela ; Schneider, Kurt. / Eliciting Contextual Requirements at Design Time : A Case Study. 2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE): Proceedings. Institute of Electrical and Electronics Engineers Inc., 2014. S. 56-63
Download
@inbook{4131186f7e374b70a3f8f39c0274a5e5,
title = "Eliciting Contextual Requirements at Design Time: A Case Study",
abstract = "The need to consider context in order to understand requirements is established in requirements engineering. Recently, this has been discussed more intensively for sociotechnical systems, which offer a rich spectrum of different operating contexts. Contextual requirements proved valuable to model requirements together with the context they are valid in, but there is a lack of research on how to derive them from stakeholder needs. Our goal in this paper is to explore the usefulness of existing requirements elicitation techniques for the identification of contextual requirements early, i.e. at design time. In a case study we investigate end-user viewpoints, together with interviews, scenarios, prototyping, goal-based analysis, and groupwork as a means to elicit and clarify contextual requirements already at design time. In our case study a certain combination of the applied requirements elicitation techniques stood out as most beneficial for the identification of contextual requirements. In addition, we discovered valuable indicators of differences in the operative context, for example when end-users cannot agree on refinements of specific requirements. Designers and operators of adaptive systems might benefit by taking such conflicts and resulting contextual requirements into account.",
keywords = "adaptive systems, design time, exploratory, requirements engineering, socio-technical systems",
author = "Alessia Knauss and Daniela Damian and Kurt Schneider",
year = "2014",
doi = "10.1109/EmpiRE.2014.6890117",
language = "English",
pages = "56--63",
booktitle = "2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE)",
publisher = "Institute of Electrical and Electronics Engineers Inc.",
address = "United States",
note = "2014 IEEE 4th International Workshop on Empirical Requirements Engineering, EmpiRE 2014 ; Conference date: 25-08-2014",

}

Download

TY - CHAP

T1 - Eliciting Contextual Requirements at Design Time

T2 - 2014 IEEE 4th International Workshop on Empirical Requirements Engineering

AU - Knauss, Alessia

AU - Damian, Daniela

AU - Schneider, Kurt

N1 - Conference code: 4

PY - 2014

Y1 - 2014

N2 - The need to consider context in order to understand requirements is established in requirements engineering. Recently, this has been discussed more intensively for sociotechnical systems, which offer a rich spectrum of different operating contexts. Contextual requirements proved valuable to model requirements together with the context they are valid in, but there is a lack of research on how to derive them from stakeholder needs. Our goal in this paper is to explore the usefulness of existing requirements elicitation techniques for the identification of contextual requirements early, i.e. at design time. In a case study we investigate end-user viewpoints, together with interviews, scenarios, prototyping, goal-based analysis, and groupwork as a means to elicit and clarify contextual requirements already at design time. In our case study a certain combination of the applied requirements elicitation techniques stood out as most beneficial for the identification of contextual requirements. In addition, we discovered valuable indicators of differences in the operative context, for example when end-users cannot agree on refinements of specific requirements. Designers and operators of adaptive systems might benefit by taking such conflicts and resulting contextual requirements into account.

AB - The need to consider context in order to understand requirements is established in requirements engineering. Recently, this has been discussed more intensively for sociotechnical systems, which offer a rich spectrum of different operating contexts. Contextual requirements proved valuable to model requirements together with the context they are valid in, but there is a lack of research on how to derive them from stakeholder needs. Our goal in this paper is to explore the usefulness of existing requirements elicitation techniques for the identification of contextual requirements early, i.e. at design time. In a case study we investigate end-user viewpoints, together with interviews, scenarios, prototyping, goal-based analysis, and groupwork as a means to elicit and clarify contextual requirements already at design time. In our case study a certain combination of the applied requirements elicitation techniques stood out as most beneficial for the identification of contextual requirements. In addition, we discovered valuable indicators of differences in the operative context, for example when end-users cannot agree on refinements of specific requirements. Designers and operators of adaptive systems might benefit by taking such conflicts and resulting contextual requirements into account.

KW - adaptive systems

KW - design time

KW - exploratory

KW - requirements engineering

KW - socio-technical systems

UR - http://www.scopus.com/inward/record.url?scp=84928164799&partnerID=8YFLogxK

U2 - 10.1109/EmpiRE.2014.6890117

DO - 10.1109/EmpiRE.2014.6890117

M3 - Contribution to book/anthology

AN - SCOPUS:84928164799

SP - 56

EP - 63

BT - 2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE)

PB - Institute of Electrical and Electronics Engineers Inc.

Y2 - 25 August 2014

ER -

Von denselben Autoren