1 / 7

MiddlewareLab SS 2008 Lab Report

MiddlewareLab SS 2008 Lab Report. Christof Leng, Wesley Terpstra Databases and Distributed Systems Group Department of Computer Science Technische Universität Darmstadt. The Lab Report. To be delivered in two weeks (5.8.2008) No strict page limit As long as necessary, as short as possible

lynnea
Download Presentation

MiddlewareLab SS 2008 Lab Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MiddlewareLab SS 2008Lab Report Christof Leng, Wesley Terpstra Databases and Distributed Systems Group Department of Computer Science Technische Universität Darmstadt

  2. The Lab Report • To be delivered in two weeks (5.8.2008) • No strict page limit • As long as necessary, as short as possible • ≈15-30 pages in a compact layout • 30% of final grade

  3. Example Table of Contents • Overview • Important(!) top-level overview • User Guide • How to use your code in future projects • Implementation • Design decisions, package descriptions, protocol, libraries • Evaluation • Reflect on what has been learned • Benchmarking / performance evaluation • which abstractions useful / decisions good • Development History • Brief(!) description of progress and problems • Appendix • Scenario definitions, configuration, etc.

  4. Hints • Show mastery of material by discussing what’s important • Language / Style • Use spell-checker • Re-read final text (of other group members too) • Don’t overuse bullet point lists • Structure • Give introductions and overviews • Do not split a single topic between different chapters • Ensure reading flow, keep logical order • Figures • Figures are great, but not every figure is interesting • Figures should match text • Figures should be readable, but not unnecessarily big

  5. Level of Detail • Overview is more important than details • Source level documentation doesn’t belong in the report (it belongs in Javadoc) • Give a good introduction for each chapter • User guide is for future developers • Enable them to use and extend your code • Brief development history • Not every task and problem, but summary

  6. Theses / Hiwi Positions • We offer BSc. / MSc. / Diploma theses topics: • BitZipper Simulation • Integration of Bitzipper in P2P applications • Unstructured Rendezvous (BubbleStorm) • …many more • We have open Hiwi positions (40-80h/month): • P2P programming (Java, C/C++) • Website Development (HTML/XML, PHP)

  7. Thank you • We’re very happy with your work • We hope you also enjoyed it • Your feedback is appreciated: • Anonymous feedback form will be sent by email • Help us to improve the course

More Related