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...

Ausführliche Beschreibung

Gespeichert in:

Bibliographische Detailangaben
Veröffentlicht in:	IEEE software S. 1
Hauptverfasser:	Fricker, Samuel, Gorschek, Tony, Byman, Carl, Schmidle, Armin
Format:	Journal Article
Sprache:	Englisch
Veröffentlicht:	IEEE 2019
Schlagworte:	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
Online-Zugang:	Volltext
Tags:	Tag hinzufügen Keine Tags, Fügen Sie den ersten Tag hinzu!

Schreiben Sie den ersten Kommentar!