Students are expected to have:
- Basic knowledge of relational databases and NoSQL databases
- Interest working with big data
- Interest in the Game of Thrones show
- Interest in challenge 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 and communicated and approved well in advance.
New This Semester: The Game of Thrones Edition
For instance consider the following toy project - I wanted to analyze the balance of power in Westeros right around the period discussed in the "A Clash of Kings" book. To do this I had to pull data from the wiki of ice and fire -- a wiki site that acts as the most comprehensive source of information about the world of Ice and Fire. The data from the wiki helped me construct a visualization that shows a network of allegiance (appear as edges in the network) of the great houses (appear as nodes in the networks). Here is the visualization - https://rostlab.org/~gyachdav/awoiaf/#/. clicking on nodes will give you detail information and you can use the mouse wheel to zoom and navigate the network.
- Check list to pass the seminar
- Register on TUM Online for this seminar
- use only the Google group for communication with tutors (expect huge delays in responses to emails sent to tutors’ private addresses otherwise). The tutors will use this group also for general announcements.
- check the mailbox of the email address you used to sign up to the Google group regularly!!!
- Upon acceptance to the Google group, send a notification with the group number you would like to join. The tutors will then update the ‘groups assignment’ table below with your name.
- Each group will be assigned one topic and one project to present in the week from March 14th to March 18th. 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: 1 week after the seminar.
Presentations are due for comments 1 week before the presentation date.
The mini web app should be ready and functional at the dat of the seminar. All code should be available for other class participants to check out. You are highly encouraged to use git hub as the repository for your code.
Tips for your presentation
The presentation should:
- focus on why you chose to use one technology over the other, if you tried more then one concept show the way you experimented and measured key software engineering metrics such as code performance, readability, reusability etc.
- while you are requested to show your work do not show us heaps of code, instead focus on the interesting parts of your code that highlight implementation decisions.
- A demo of the working app is required
VERY IMPORTANT INFORMATION
READ THIS PAGE: Hints and Rules for the seminar. Keep in mind that the rules on this page supersede any conflicting recommendation on the hints page.
|1||March 14||10:00||Language basics -- grammar, variables, data structures, control structures, conditionals, functions etc.|
|3||March 14||12:00||The module pattern and AMD|
|4||March 15||10:00||The event handling system using using anonymous functions, callbacks, promises etc.|
|5||March 15||11:00||Functional reactive programming frameworks|
|7||March 16||11:00||The MEAN stack|
|8||March 17||10:00||Web development basics: DOM, DOM manipulation, styles|
|9||March 17||11:00||Web development frameworks (Angular, Backbone, React)|
|10||March 17||12:00||Data visualization using SVG, Canvas and framework libraries|
|11||March 18||10:00||Build tools, continuous integration and distribution|
|12||March 18||11:00||EcmaScript 6 (es6) language features|
- RECOMMENDED VIDEO http://www.paulirish.com/2010/10-things-i-learned-from-the-jquery-source/