Thesis TODOs

[informusica]

• Results chapter: first write rationale, setup & outcomes of various experiments. Only then add the figures.
• Then Results => Conclusions also considering original research questions. Future work only as backlog.
• Based on Results back to 'Tribler for mobile' & Design chapters
• Implementation (& Future Work)

[brussee]

• Problem description chapter reshuffle, ALLEEN duplicates deleten!
• Problem description chapter uitbreiden. Niet deleten!
• Geen enkele bullet meer, alleen hele zinnen in problem description chapter.
• Egaal aanvullen van problem description chapter.

[informusica]

• Use the order above in filling chapter content
• Set strict milestones per day and drop whatever can't be fixed by that milestone until the next iteration
• Don't forget to plan for LaTeX and presentation preparations
• When stalling on a particular point for too long, make a note but also drop and continue until the next iteration

[informusica]

And don't fix problems of others until after your defense. :)

[brussee]

FYI: de brief van de decaan lag gister in de brievenbus met goed nieuws!
(Nu fase 2: formulieren naar de DUO.)

[brussee]

• for chapters with unstructured content, reshuffle content WITHOUT REWRITING OR ADDING CONTENT.

Ma. 21:

• Conclusions & Future work iteratie; considering original research questions.
• Based on Results back to 'Tribler for mobile' & Design chapters.

Di. 22:

• Implementation (& Future Work) iteratie.
• Add Minimal viable Android app Tribler/tribler#2231 (comment)
• Results chapter iteratie.
• Add device specs table.
• Feedback Johan.

Wo. 23:

• Rewrite Intro to management summary.
• Tribler functionality chapter iteratie.

Do. 24:

• Print out.

---

• Split: Java GUI, Core started
• Possible additional experiment: measure transfer time between various phones of 25MB clips or show power consumption during phone-to-phone exchange (max. 1 day experiment)
• Possible additional experiment: Power consumption experiment (battery drain, 4x Galaxy Nexus)

[brussee]

• Merge design principles into requirements
• Sequence numbering of requirements
• Describe new architecture diagram (rework existing text) (find orig fig)
• Add intro of new architecture fig. in implementation
• Dedup intro
• Improve quality of intro (underline what can be improved first)
• Citations in intro + BIB

[brussee]

Zo. 11

• Higher level conclusions
• Future research plus setup
• Correct flow of entire thesis (connecting sentences, questions and answers over hele boog)
• Intro of Results chapter met rode lijn: problem desc.; grote plaatje: key questions en reden voor alle experiments
• Rewrite API results
• Rewrite CPU utilization
• Rewrite testing and coverage
• Improve intro
• Citations in intro
• Improve problem description
• Reference figure in problem description
• Describe all screenshots
• Link dependency tree to sys arch & build tool-chain
• Build toolchain beter inleiden
• Link sys arch to build tool-chain
• Improve about Tribler in depth and link problem desc
• Citations in problem description
• Citations in design
• Citations in implementation
• Citations in results
• Citations in conclusions and future work
• Stats PRs fill-in
• Update stats table about src

Ma. 12

• Start presentatie maken

Di. 13

• Give presentation

[synctext]

presentation draft ?

[brussee]

@synctext https://github.com/brussee/thesis/blob/master/defence/presentation.pdf