|Institution:||Blekinge Institute of Technology|
|Keywords:||software engineering - general; shared understanding; software engineering|
|Full text PDF:||http://www.bth.se/fou/forskinfo.nsf/all/4bac5f2c38ab3246c1257da1006612c4?OpenDocument|
Shared understanding is essential for efficient software engineering when the risk of unsatisfactory outcome and rework of project results shall be low. Today, however, shared understanding is used mostly in an unreflected, ad-hoc way. This affects the quality of the engineered software solutions and generates re-work once the quality problems are discovered. In this article, we investigate the role, value, and usage of shared understanding in software engineering. We contribute a reflected analysis of the problem, in particular of how to rely on shared understanding that is implicit, rather than explicit. After an overview of the state of the art we discuss forms and value of shared understanding in software engineering, survey enablers and obstacles, compile existing practices for dealing with shared understanding, and present a roadmap for improving knowledge and practice in this area.