What will be the research methodology if you are developing a generic software I'm developing a generic software for the unorganised retail sector. The design is completely based on the literature review that has been conducted. The only problem is that since I'm not doing any interviews or surveys, what research methodology should I follow ? It can't be qualitative or quantitative. The end result is just the developed software. 
The aim is to study why the unorganised retail is behind than the organised one. And the solution is to present a software for them to use to help in decision making. It's completely based on literature and no surveys or interviews were conducted.
Writing software isn't research. Proving that a piece of software, written by yourself or others, can be research. How are you going to show that your software does what it set out to do? How are you going to show that it is better than the alternatives? For those questions you need methodology. Questionnaires? Observations? Objective measurements? Something. 

But the software itself is just a tool. Showing it is valuable is the research part. 

And, of course, if it is real research then you need to be prepared for the situation that you get evidence that the new tool isn't actually better. Research is a search for truth, not proof of a predefined statement.