best thing is still to come up with something you are genuinely interested in: that way you won't loose motivation to work on it.
also: you told us nothing about your course, what you've learned, what (if any) limitations you were given, ..
a number of professors I've had used the 'choose your topic yourself' as a way to see whether we were capable to choose on a project, in which we could use the techniques taught, and whether we were capable to estimate the time needed to get the project done.
stultuske
Posting Sensei
3,108 posts since Jan 2007
Reputation Points: 1,114
Solved Threads: 432
stultuske is right we would not want to advise you without knowing the points stated
you told us nothing about your course, what you've learned, what (if any) limitations you were given, ..
Would really need to know your discipline, because the project choice can change vastly between Computer Science, Software Engineering and Computer Forensics.
mikulucky
Junior Poster in Training
85 posts since Jan 2012
Reputation Points: 41
Solved Threads: 13
and how much have you learnt of all these subjects?
for instance, I'm a java developer, so a question I could ask is: what have you learnt from java?
J2ee, struts, ejb, gwt, spring, hibernate, ... ?
what exactly is this end project for? for your entire course, for one subject, ...
stultuske
Posting Sensei
3,108 posts since Jan 2007
Reputation Points: 1,114
Solved Threads: 432
I'm not talking about the subject, I 'm talking about the techniques you are able to use. if this project should cover all your classes, I would try to fit in techniques/languages/tools from as much courses as you can (provided it makes sense to use them)
stultuske
Posting Sensei
3,108 posts since Jan 2007
Reputation Points: 1,114
Solved Threads: 432