Hello Sir,
>I don't know what are the hard requirements for the schedule, but >I would not make such delineation between coding, reviewing and >testing. The Elements Of A Quality Proposal in Google’s Guide (https://google.github.io/gsocguides/student/writing-a-proposal) state the following about deliverables and timelines: Deliverables Include a brief, clear work breakdown structure with milestones and deadlines. Make sure to label deliverables as optional or required. You may want your plan to start by producing some kind of white paper, or planning the project in traditional Software Engineering style. It’s OK to include thinking time (“investigation”) in your work schedule. Deliverables should include investigation, coding and documentation. I attempted to follow it in my implementation of the milestone timeline. What be your advice on improving/altering the timeline provided in the documentation ? >You could perhaps also mention that you'll need to compile the >"reference" implementations (in C probably), and most importantly >devote some time to looking for those (a.o. also compare several >implementations of the same algorithm (and with the algorithm >description), if there is no "authoritative" origin for the code (i.e. >when the person who wrote the code is not the person who >designed the algorithm). >Depending on when you actually find all the needed resources >for a given task, the schedule will be quite different... I’ll add those tasks and work on the schedule as required. Thanking You, Yours Faithfully, Abhishek
