Handshaking with Implementation Proposals: Negotiating Requirements Understanding March/April 2010 (vol. 27 no. 2) pp. 72-80
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2009.195
Requirements engineering focuses on good specification practices but has yet to find working solutions for effective requirements communication. Inadequate communication and tacit assent to a demanding customer's requests make it hard to fully understand a project's requirements. A negotiation process, called handshaking with implementation proposals, has been used to communicate requirements effectively—even in situations where almost no written requirements exist and where distance separates the customer from developers. Handshaking is an efficient, flexible technique that uses architectural options to understand requirements, to make implementation decisions that create value, and to establish the foundation for a stable project. This article describes the communication challenges, solutions, and lessons learned in developing the handshaking process and applying it in industrial practice. 1. S. Fricker, T. Gorschek, and P. Myllyperkiö, "Handshaking between Software Projects and Stakeholders Using Implementation Proposals," Proc. 13th Int'l Working Conf. Requirements Eng.: Foundation for Software Quality (REFSQ 07), Springer, 2007, pp 144–159.
Index Terms:
software engineering, requirements specification, software design, software methodologies
Citation:
Samuel Fricker, Tony Gorschek, Carl Byman, Armin Schmidle, "Handshaking with Implementation Proposals: Negotiating Requirements Understanding," IEEE Software, vol. 27, no. 2, pp. 72-80, Mar./Apr. 2010, doi:10.1109/MS.2009.195 Usage of this product signifies your acceptance of the Terms of Use. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||