Implicit Shared Understanding

Introduction
The main purpose of the paper is to give us an idea on shared understanding in software engineering and why it is essential for efficient software engineering. It is greatly needed to ensure the outcome of a software development project is a success and is with very less bugs to no bugs when it goes live. We will also look at its significance in software development and its contribution towards shared understanding. This report will also provide you with the implications that are involved in software development which will highlight the key aspects of shared understanding. On the topic paper, the authors talk about explicit shared understanding and implicit shared understanding which we will discuss further in this critique report.
This understanding is widely used these days as it is easy to follow and agreed by most of the people.
Implicit shared understanding (ISU):
In implicit shared understanding, all the group members have difference ideas and possess different levels of knowledge and values; each one has their own opinion on the development of the software. Often there is no need to communicate and also it greatly minimises the chance of misunderstanding a concept or a process.
Significance and Contribution
Both the authors have done a good job in bringing up the concepts and have researched very well on shared understanding. They have prepared this paper by researching various literatures on shared understanding, software development and other closely related areas. They have used the reflection and introspection as their research method though this is not one of the standard approaches that are followed. Their main goal for this research was to provide an overview of shared understanding in the field of software development and do a survey of the processes and methods that are used and practiced at the moment. In terms of applying the concepts of shared understanding in User Centred Design (UCD), it relates to barriers and enablers which are used in
By practicing various enabling approaches and building a model of the software, it helps in identifying the areas that needs improvement and require changes to work as expected. They have used different variety of practices to accommodate the concepts and to prove that their study is acceptable.
We must agree to the fact that both types of shared understanding is very important and should be used appropriately in software development to get the best outcome as both are equally important. The paper gives us various methods and ways to get more information on shared understanding by asking relevant questions and answering them appropriately.
They have discussed about the traditional waterfall model and agile methodology in software development process and provided with some examples. However, the author supports the process of developing a prototype which is similar to the approach we have followed in UCD. They have validated their study by means of conducting surveys and by referring various documents which support their research paper. Shared understanding is a flexible approach and so it should be widely used in the