Handshaking: Negotiate to Provoke the Right Understanding of Requirements

Development teams that accept fragmentary and vague customer requirements have to cope with uncertainty and disorientation. Inadequate communication and submission to a dominating customer makes it hard to know if requirements are understood or not. Requirements engineering, with its focus on good s...

Celý popis

Uložené v:
Podrobná bibliografia
Vydané v:IEEE software s. 1
Hlavní autori: Fricker, Samuel, Gorschek, Tony, Byman, Carl, Schmidle, Armin
Médium: Journal Article
Jazyk:English
Vydavateľské údaje: IEEE 2019
Predmet:
Automation
C.0.e System architectures
C.0.f Systems specification methodology
D.2 Software Engineering
D.2.1 Requirements/Specifications
D.2.1.b Elicitation methods
D.2.1.e Methodologies
D.2.1.f Process
D.2.10.f Methodologies
D.2.17.b Code design
D.2.18 Software Engineering Process
D.2.18.c Process measurement
D.2.4.d Formal methods
D.2.5.k Testing strategies
D.2.8 Metrics/Measurement
D.2.8.c Process metrics
D.2.9 Management
D.2.9.h Productivity
Design methodology
Electrical equipment industry
Emperical
Hardware
integration and modeling
Process
Product design
Proposals
Quality Assurance
Requirements Engineering
Risk management
Software
Software design
Software engineering
SPI
Uncertainty
ISSN:0740-7459, 1937-4194
On-line prístup:Získať plný text
Tagy: Pridať tag
Žiadne tagy, Buďte prvý, kto otaguje tento záznam!
Popis
Shrnutí:Development teams that accept fragmentary and vague customer requirements have to cope with uncertainty and disorientation. Inadequate communication and submission to a dominating customer makes it hard to know if requirements are understood or not. Requirements engineering, with its focus on good specification practices, had yet to find working solutions for effective requirements communication. We are using a negotiation process called Handshaking with Implementation Proposals to make such requirements communication work – even in situations where written requirements are almost nonexistent and distance separates customers from developers. Handshaking is an efficient and effective technique that uses architectural options to achieve requirements understanding, to create value with implementation decisions, and to establish the foundation for a stable project. This article focuses on the interface between product management and the development organization in companies, where product management acts as a customer towards development. We describe the requirements communication challenges we encountered, explain how we addressed these challenges with the Handshaking process, and share the lessons we learned at European and Asian development sites from ABB and Danaher Motion.
ISSN:0740-7459
1937-4194
DOI:10.1109/MS.2009.195