Note: These are MY requirements - to those who are interested doing their projects under MY supervision.

Recommended development platform for all projects is Linux. I personally use and recommend Slackware. Devuan is also a good option. Projects that involve source codes (e.g. HDL, C, C++) are required to use source code management (SCM) software (git).

Update20171217 Beginning 2018, I will set milestones (i.e. mini-objectives) for each project title. I figure this would be a better way for students to actually see what I expect them to achieve while working on the project. My previous way of using scopes does not seem to work - although I thought that would make it more flexible on the outcome of the project.

Note: The following explains my previous method of describing projects. I'm keeping this around for now, but only for personal record. Students no longer need these.

For each project title, I've included some keywords, objective(s) and scope. The keywords are there for you to do some background research before you jump into this - I don't want you to give-up on me (it's a waste of everybody's time) towards the end of the project. I put in objectives and scope to let you know what is expected out of this project. So, your results will be based on these expectations.

I define an objective as the targeted final result. I usually set only ONE primary objective and optionally a secondary objective that will/should not affect your final results (though it usually gives you extra marks if completed) - too many objectives usually leads to unsatisfactory results. Meanwhile, scope visualizes how much work is expected - for example, one can say that the primary objective is to design an 8-bit microprocessor. So, the scope should mention maybe something like you're expected to produce schematics with instruction set that covers data transfer/processing and program control, complete with logic simulation results.