I have got a topic for a thesis that I'm interested in.
It's not a very difficult task and is well covered by the basic theory in the field. I'm not doing anything new and I'm not supposed to either. I'm convinced that a person knowledgeable in the field would consider it trivial.
Working on the task is mostly only software development, although there's also some hardware involved. Of course there's a huge open source software library that covers pretty much everything in the field.
In essence, I'm calling 2 to 3 functions of the library that are specifically made to solve the task that I have. What I spent most of my time on was writing software that makes some hardware talk to each other, deliver data to and from the library, doing some format conversions, etc. None of this is particularly interesting for the actual topic, it's only providing the logistics of using the library. The academically interesting part is already handled by the library.
I didn't do much except applying the provided functionality to solve the problem in the obvious way as I've been told. I don't really know what I should write about in my thesis.
It looks like my supervisor is very interested in seeing the functionality (of the library) "in action" for this particular application. I feel like an unpaid software developer disguised as a thesis student.
How do I come up with content?
from the comments
I'm convinced that a person knowledgeable in the field would consider it trivial. — So then, why would you choose it as your thesis topic?
I choose this topic because it
- is interesting to me. I like it. I have a positive mindset about it.
- is a topic that I estimated to be able to handle and it turned out I can.
- helps me gain more knowledge in its field that I was previously not very knowledgeable about.