- pre-meeting will take place on Wednesday, February 6 at 02:00pm in room 01.10.011
The students will be working in a highly agile environment, meaning that a collaborative work (communication!!) among all students will be essential for the successful completion of the project. Any results thus provided during the coding period of the seminar will need to be communicated and made available to peer coders asap!
Registration: Prior to registration on TUM Matching System, we would like to get to know you! Please send us an email to firstname.lastname@example.org and tell us about yourself a bit: your current current degree, program (e.g. informatics) and explain why you want to join the seminar, what prior course work you have. Also please name a TUM faculty member as a reference. Without this information we won't be able to secure a spot for you at the seminar.
'Project Description: TBA
Number of students/ groups: TBA Tutors: Dr. Guy Yachdav,
- Pre meeting: Wednesday, February 6 at 02:00pm in room 01.10.011
- Kick off meeting: TBD
- Coding period begins: TBD
- Feature freeze: TBD
- Beta release: TBD
- Release (hopefully): TBD
- Report Due: TBD
- Presentations week (in class, participation mandatory):
Students are expected to have:
- Knowledge in at least one functional OR Object Oriented Programming language
- Basic knowledge of relational databases and NoSQL databases
- Interest working with big data
- Interest in challenging themselves to do something totally cool
- Participation in all meetings throughout the presentation week is mandatory. We would only consider one absence that is justified, documented and approved well in advance.
Checklist to pass the seminar
- Register on TUM Matching System for this seminar
- Each group will be assigned one topic and one project to present in the presentation week. Please see the guidelines for topic and project presentations below.
- The slides for your topic presentation and the preliminary visualization of your project results are due for comments 1 week before the presentation date. Send your drafts to presentations to email@example.com.
- Make sure to read these Hints and Rules for great presentations
- Submit a 5 pages long report (one per group) describing solutions to your topic (4 pages) and the project (1 page). Due: 2 weeks after the seminar.
- RECOMMENDED VIDEO http://www.paulirish.com/2010/10-things-i-learned-from-the-jquery-source/