![]() ![]() He found out through his observation that a person without any knowledge of the respective field will ask exactly the right questions to identify these unstated assumptions. Moreover he postulates that no two people will have the same set of assumptions and that as a result, conflicting assumptions may be overlooked. In his view, this can be explained by the understanding that there are unstated assumptions among domain experts that – due to being unstated - are not noticed by anyone. He discusses an observation from the year 1979 (first described in a paper published in 1983), in which he found out that it was precisely the lack of application domain knowledge that led to the success of the project. The first relevant articles that was identified was written by Berry (Berry 1995). ![]() Since the articles displayed some redundancy in their findings, only the two most significant studies will be presented below. In the end, eight articles were found which deal – to differing degrees – with the topic to be discussed. After reviewing the results in order to find relevant articles, the sources of the articles were also examined, as well as articles citing the results. The search was carried out on Maby using both Google search and the search portal DigiBib with the same key words. 2 Literature research 2.1 Research design Finally, Chapter 5 draws a conclusion from the lessons learned. Chapter 4 then focuses on the author’s own experience by examining his roster of projects handled over the last couple of years and analyzing whether or not he was able to benefit from his domain knowledge. The goal at this point is to compare and contrast the results gleaned from the scientific literature with the experience and opinions of requirements engineering practitioners. The third chapter then proceeds to challenge these advantages and disadvantages by means of a survey that was conducted within the author’s company. The paper is structured as follows: First, Chapter 2 gives an overview of the views and opinions expressed in scientific literature on the topic „requirements engineering and domain knowledge”, summarizing both the advantages and disadvantages discussed in the source material. This theory will be discussed in this paper. At a second glance, however, one might start to wonder about possible negative side effects of acquiring specific domain knowledge that might even become an obstacle for the requirements engineer. ![]() Furthermore, his prior knowledge will most likely enable him to ask more targeted and specific questions during an interview. Initially one might expect this domain knowledge to help him be more efficient in future projects that deal with the same subject matter. By applying this, the requirements engineer naturally builds up domain knowledge over time. The IREB Foundation Level courses emphasize the fact that a requirements engineer is expected to familiarize himself with the application domain of the stakeholder (Pohl and Rupp 2015, p. Faßold Requirements Engineering and Domain Knowledge A study concerning the question of whether domain knowledge is rather conducive, or rather hindering, for a requirements engineer ![]()
0 Comments
Leave a Reply. |