Dissertation plan, part 2

What follows is an email I sent to my lecturers, explaining exactly why I have decided to make a range of prototypes for my dissertation:

For my dissertation I want to put a large focus on learning C# and Unity. This is for two reasons:

One is that I haven't coded in C# yet, and in order to make mobile phone games in Unity, I've got to have some knowledge of it;

Two, if I happen to look for a job, it'll have to be programming, so a coding focused dissertation is probably what my employer will be looking for.

This is why my idea purposely doesn't include any design, or art work. My plan is to create a number of short game prototypes that instead of art, use place holders. Each prototype would let the player explore a different mechanic:

one could be jumping: http://www.youtube.com/watch?v=STHQFMd2bfY

the other could be tapping: http://www.youtube.com/watch?v=qEN99W8zBj4

another would be slicing: http://www.youtube.com/watch?v=TFFQNjJ5C5Q

and so on.

If I could show a set of 7-10 of them to an employer, or use the code I created them with to make my own smart phone games I would be happy.

So to answer all questions:

What do you intend to learn over the year?
I want to create a number of short prototypes for Android devices, and learn using Unity and coding in C#

What do you imagine you would be marked on?
The amount of prototypes I've created

How will your improvement be measurable?
The bigger variety of prototypes I make, the more code I'll learn

What are the benefits of reproducing existing games, and how many would you intend to reproduce?
Reproducing a number of prototypes that differ from each other gameplay wise, would show that I can universally code in many different mechanics. This would help me make my own simple games in the future, as well as prove that I can code to a potential employer. As to how many prototypes I'd be aiming to make - as I mentioned, probably between 7(one every month) to 10, but it is hard to calculate (might end up being much more if I get the hang of C# quickly).