How can one write a thesis in Computer Science, without actually providing the solution, but researching it and explaining how it's being solved right now but not for the specific problem (research area) identified by the researcher.
For instance, imagine that you spend your first year doing a literature review on the subject matter.
Now in your second year you're expected to build this solution, what if you cannot build it, or it requires too much code/time/investment. Obviously, I'm going to try to build the solution, but what if I fail building it, because it will require a lot of advanced code and algorithms.
Is there a way to survive that? Are there methodologies that can be used when you have done a literature review, and then tried to build a solution, potentially failed.
How can one continue and research the topic, write the thesis, or even get published, without having all the code to a solution? Will graphics/images combined with some kind of methodology be a way of actually conducting that research?
Very anxious and need help, motivation and support in order to know how to tackle that period when building the solution is required.