For writing scientific texts like bachelor or master thesis I have learned and used the following basic structure:
- Introduction
- Background
- State of research
- Methods
- Results
- Discussion
- Conclusions
I am currently writing my master thesis in computer science where I am developing an algorithm/workflow for a specific validation use case. For similar but more general use cases there already exist methods to do this validation. But for my specific use case those methods can not be used because they do not consider various needed regulations to achieve a reasonable result.
Basically this is my argumentation in my current introduction after talking about the more general background and where the underlying problem derives. I give a very brief overview of state of research (i.e. the already available methods and why they can not be used). After this argumentation as a reason I propose my research question and main research goals.
Now to the actual question: One of my supervisors does not like me mentioning things related to the state of research and (in my opinion) obvious technical terms in the introduction. Instead he wants me to do a more general introduction (without explaining the problem in details) and use a structure like the following for my introduction:
- Basic problem
- State of research (shall be discussed with focus on missing applicability for my use case)
- Research question and goals (as a result of 2.)
This really irritates me because I always discussed the state of research later on after giving basic theoretical backgrounds needed for understanding (this would not be possible when mentioning state of research in the introduction). I also do not think that generalizing the problem so much that it is not needed to use basic technical terms when defining the research question is useful at all.
I am really confused how to structure my thesis so that I can write an non "babble" introduction but also satisfy my supervisor. Can anyone help?