Abstract
[Context and motivation] In interdisciplinary requirements engineering, stakeholders need to understand how other disciplines think and work (mutual understanding) and agree on the system they develop (shared understanding) in order to collaborate effectively. [Question/problem] In this paper we analyse extent and forms of (lacking) mutual understanding according to the periods in the process of conceptual change. [Principal ideas/results] We analyse the communication of a multidisciplinary team while developing a mobile application. Although the team tried to resolve differences in meaning early on by applying approaches for clarification, questions for consolidation, exploration and elaboration occurred at different points in time throughout the process. Even when artefacts were already agreed upon, the development team explored lack of mutual understanding to underlying concepts or relationships. A revised shared understanding led to adjustments of the artefacts and thus hampered the process. [Contribution] We therefore call for research that explores ways of systematically building mutual and shared understanding in the development process.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.