Comparison of Requirements Hand-off, Analysis, and Negotiation: Case Study

Fricker, Samuel; Glinz, Martin

doi:10.1109/re.2010.29

Cited by 18 publications

(22 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Many requirements led to follow-up questions about the requirements that were not solved with the video. This result is consistent with results from other studies that suggested that requirements understanding requires feedback between stakeholders and developers [46].…”

Section: B Laboratory Evaluationsupporting

confidence: 93%

See 1 more Smart Citation

Workshop videos for requirements communication

et al. 2015

View full text Add to dashboard Cite

Abstract-Shared understanding of requirements between stakeholders and the development team is a critical success factor for requirements engineering. Workshops are an effective means for achieving such shared understanding since stakeholders and team representatives can meet and discuss what a planned software system should be and how it should support achieving stakeholder goals. However, some important intended recipients of the requirements are often not present in such workshops: the developers. Thus, they cannot benefit from the in-depth understanding of the requirements and of the rationales for these requirements that develops during the workshops. The simple handover of a requirements specification hardly compensates the rich requirements understanding that is needed for the development of an acceptable system. To compensate the lack of presence in a requirements workshop, we propose to record that requirements workshop on video. If workshop participants agree to be recorded, a video is relatively simple to create and is able to capture much more aspects about requirements and rationales than a specification document. This paper presents the workshop video technique and a phenomenological evaluation of its use for requirements communication from the perspective of software developers. The results show how the technique was appreciated by observers of the video, present positive and negative feedbacks from the observers, and lead to recommendations for implementing the technique in practice.

show abstract

Section: B Laboratory Evaluationsupporting

confidence: 93%

“…Fricker evaluated the impact of such hand-off on requirements understanding and showed that the practice was problematic however [46]. According to the obtained results, the hand-off did not lead to good-enough requirements understanding.…”

Section: A Requirements Communicationmentioning

confidence: 99%

Workshop videos for requirements communication

et al. 2015

View full text Add to dashboard Cite

show abstract

“…2) Need for integrated RE and AD: Fricker and Glinz [26] present a case study analyzing and monitoring the hand-over and negotiation process between stakeholder and architect. Even though that study was not specifically targeted at NFRs, the results strongly confirm our position that proper NFR determination requires knowledge of the solution architecture.…”

Section: A Related Work 1) Negotiating and Uncertainty In Requirementsmentioning

confidence: 99%

Issues Dealing with Non-Functional Requirements across the Contractual Divide

Poort

Key²,

Vliet³

2012

2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture

View full text Add to dashboard Cite

Abstract-Agreement on Non-Functional Requirements between customer and supplier is crucial to a successful IT solution delivery project. In an ideal world, stakeholders and architects cooperate to achieve their common goals in a win-win situation. In a commercial setting, however, one dominant feature often introduces powerful forces from outside the technical realm. That feature is the customer/supplier relationship, usually formalized in bidding rules or as a delivery contract. Formal customer/supplier relationships often place severe limitations on information exchange between stakeholders and architects. In this paper, we explore the effect of such limitations on the interaction of architectural design with the quantification of Non-Functional Requirements, and explore a number of avenues to deal with them.

show abstract

“…Review of prototypes has been particularly effective in identifying usability concerns and refining user interaction design to reach user acceptance [21]. The construction of such prototypes allows a development team to capture assumptions about desired software characteristics and to validate these assumptions, for example by reviewing them as implementation proposals with concerned stakeholders [22,23].…”

Section: Related Workmentioning

confidence: 99%