First Semester: Week 1(29th.Feb - 6th.Mar) Kick-off meeting with course coordinator Mano and all year 2016 BTech451 students.(1 hour) Reviewed all avaiable projects that provided by Mano and search online for each project (3.5 hours), and as a result of reviewing process, I preferrd to choose CodeRunner Extension as my BTech451 project and accepted by Mano (1 hour). Total Working hours: 5.5 hours Week 2(7th.Mar - 13th.Mar) During the course of this week, I was able to meet my mentor and supervisor, Dr Wannes van der Mark. During the meeting, Dr Wannes gave me an initial brief of my project and my focus part is that how to avoid cheating on CodeRunner.(1 hour) After meeting, Xampp was introduced to me, and I was also suggested to do some preparation before I start my project.(1.5 hours) During this week, I spent several days to finish the readings about CodeRunner Document which was provided by my supervisor as well as some previous reports about CodeRunner. Also, I successfully tried to use Xampp for localhost settings and learn PHP online tutorials.(13.5 hours) Total Working hours: 16 hours Supervisor signiture: Week 3(14th.Mar - 20th.Mar) During this working week, I followed the CodeRunner Document to install local Moodle in my PC, by discusing with Davis Dimalen who is currently working with University CodeRunner, we fixed the problems with local database settings and finally I successfully completed Moodle installation and made some practices at local machine. (3.5 hours) Complete the local CodeRunner installation, successfully added java,python questions into local host course page (2.5 hours). Had a quick meeting with Dr. Wannes to polish my first semester plan and I was introduced several ways to prevent cheating at CodeRunner by my supervisor. After that, I also talk to Mano to get a general idea about project and report structures.(2 hours) Total working hours: 8 hours Week 4(21st.Mar - 27th.Mar) Draft Table making to define different cheating types that I need to focus on for my project. Also generated some ideas for each cheating type, and will follow the ideas for doing research and code implementing. (1.5 hour) 1 hour meeting with Dr. Wannes to have a brief discuss about Cheating Table that I have done before. Also, decided the focus part for the following days.(1 hour) Doing the research in Computer science lab room to gather source code of CodeRunner that other students who have submitted and passed the test case, which is for further discussion. (4 hours) Total working hours: 6.5 hours Week 5 (28th.Mar - 3rd.Apr) Due to the Easter break, I didn't have weekly meeting with Dr.Wannes. However, during this week, I analyzed my research outcomings and focused on the small draft report based on my research result, will show it to Dr.Wannes next meeting. (7 hours) Total working hours: 7 hours Week 6 (4th.Apr - 10th.Apr) During this wokring week, I had an one-hour meeting with Dr.Wannes to talk about the first research report that I handed to him. Refer to his instruction, doing the research about programming-variation on Code Runner and Online source. (2.5 hours) Writing a part of small research report based on the research report by using Latex format(2 hours) Pratice some exercises at local Code Runner to try to add new users and allocate them to specific courses. (2 hours) Total working hours: 7.5 hours Week 7 (11th.Apr - 17th.Apr) Continue to polish and finalize the programming-variation report writing, handed it to Dr.Wannes.(2 hours) Had a weekly meeting with Dr.Wannes to talk about the report and task that need to do before next meeting. (1.5 hours) Started reading through files inside of CodeRunner directory to understand what role of each file plays in CodeRunner platform.(11 hours) Total working hours: 14.5 hours Semester break. Week 8 (25th.Apr - 1st.May) Weekly meeting to talk about questions and issues with Dr.Wannes, obtained more ideas about CodeRunner and the ways could be implemented.(1 hour) Continue reading through the files inside of CodeRunner directory. (6 hours) Tried code implementation to CodeRunner and successfully implemented, expected output had been generated. (4 hours) Total working hours: 11 hours Week 9 (2nd.May - 8th.May) Due to ugent family issues, haven't done project working during this week. Total working hours: 0 hours Week 10 (9th.May - 15th.May) During this week, I started implementing code as Java Programming, even though the main goal of project is about php at Code Runner, Java can be a language tool to see if the idea can be successfully implemented, and I am good at Java programming. Successfully done it.(9 hours) Weekly meeting with Dr. Wannes to talk about my Java implementation, and next step purpose.(1 hour) Tried to transfer from Java language to php language. (4 hours) Total working hours: 14 hours Week 11 (16th.May - 22nd.May) After GUI mock-up has been successfully implemented, functionality of prototype was implemented as well during this working week. By checking SQL schema of Code Runner and code programming, functionality of prortype has been successfully implemented. (10 hours) Meeting with Dr.Wannes to talk about the prototype that have done in this week and semester report.(1 hour) Total working hours: 11 hours Week 12 (23rd.May - 29th.May) During this working week, I focused on semester report writing.(not finished yet) (9 hours) Meeting with Dr. Wannes to talk about problems in my draft report and polish them.(1 hours) Based on the discussion, modified problems that indicated by Dr. Wannes.(2 hours) Total wokring hours: 12 hours Week 13 (30th.May - 5th.June) Continued to writing my semester report and finished the full version draft. (7 hours) Meeting with Dr. Wannes to fully polish my report.(1 hours) Modified problmes taht indicated by Dr. Wannes in this week meeting. (3 hours) Proof-reading and finalize my report.(1 hour) Total working hours: 11 hours Second Semester: Week 1 (18th.July - 24th.July) During this wokring week, I polished Semester report by referring to the feedback from Dr. Wannes. (2.5 hours) Meeting with Dr. Tariq (My new supervisor while Wannes is away) to talk about the project and some other details. (1 hour) Writing a draft plan for the project of new semester. (1.5 hours) Review project part have done in last semester.(2 hours) Total working hours: 7 hours Week 2 (25th.July - 31st.July) Weekly meeting with supervisor to talk about semester plan and confusion on semester report.(1 hour) Continue polishing semester report after meeting with supervisor.(2 hours) Code Runner revision.(4 hours) PHP programming learning.(2 hours) Write a short report to summarise weekly study outcomes.(1 hour) Total wokring hours: 10 hours Week 3 (1st.Aug - 7th.Aug) Keep learning on php programming language and code review of Code Runner and Moodle.(11 hours) Weekly meeting with supervisor to discuss my learning result and questions met.(1 hour) Started working in Code Runner.(2 hours) Total working hours: 14 hours Week 4 (8th.Aug - 14th.Aug) During this weeking week, I started focusing on modification of Code Runner UI, especially on question creation page, so that it will be suitable to my anti-cheat system. (21 hours) Weekly meeting with supervisor to talk about my new user interface.(1 hour) Total working hours:22 hours Week 5 (15th.Aug - 21st.Aug) In this week, I tried to make new UI be functional and create new database schema for my anti-cheat system.(20 hours) Weekly meeting with supervisor to demonstrate new functionality of Code Runner and how new database table works.(1 hour) Total working hours:21 hours Week 6 (22nd.Aug - 28th.Aug) To finish up my anti-cheat system in Code Runner, I changed the UI of student view for each question, and made sandbox work based on my question creation way. (17 hours) Weekly meeting with supervisor to show the working result and talk about the works need to do during semester break.(1 hour) Total working hours:18 hours Week 7 (12th.Sept - 18th.Sept) During this working week, search for new anti-cheat ideas avaiable from online source. Started anlysing the anti-cheat ideas and preparing research methodology based on the ideas. (15 hours) Weekly meeting with supervisor to discuss the works have done during semester break.(1 hour) Total working hours:16 hours Week 8 (19th.Sept - 25th.Sept) During this week, "Similarity checking with comments" has been chosen as the next implementable idea. Time penalty and coding performance testing has been done on PHP language, both acceptable. Started implementation in Code Runner.(17 hours) Weekly meeting with supervisor to discuss weekly working result.(1 hour) Total working hours: 18 hours Week 9 (26th.Sept - 2nd.Oct) Continued implementation in Code Runner, re-defined the database schema to make the idea become functional and useful. (31 hours) Weekly meeting with supervisor to demonstrate the result of implementation. (1 hour) Total working hours: 32 hours Week 10 (3rd.Oct - 9th. Oct) Research on question recycling in Code Runner, in order to reveal the question reused in Code Runner. (21 hours) weekly meeting with supervisor to discuss research result and how that would support previous implementation. (1 hour) Total wokring hours: 22 hours Week 11 (10th.Oct - 16th.Oct) Started writing Final report by combining all previous implementation and research together. (20 hours) Weekly meeting with supervisor to talk about Final report.(1 hour) Total wokring hours: 21 hours Week 12 (17th.Oct - 23.Oct) Continued writing to finalize the report, proof reading has been done during this week. Prepare the final presentation.(22 hours) Weekly meeting with supervisor to make a final discussion of ovrall workings and report quality.(1 hour) Total working hours: 23 hours.