t 110 5130 mobile systems programming 5cr
play

T-110.5130 Mobile Systems Programming (5cr) Practical issues, - PowerPoint PPT Presentation

T-110.5130 Mobile Systems Programming (5cr) Practical issues, course arrangements 21.1.2011 Antero Juntunen antero.juntunen@aalto.fi Course basics (1/2) Responsible teacher Sakari Luukkainen, course assistant Antero Juntunen + tutors for


  1. T-110.5130 Mobile Systems Programming (5cr) Practical issues, course arrangements 21.1.2011 Antero Juntunen antero.juntunen@aalto.fi

  2. Course basics (1/2) • Responsible teacher Sakari Luukkainen, course assistant Antero Juntunen + tutors for group work • Contact information: antero.juntunen@aalto.fi • 5 credits, periods III-IV • Registration closed, only those who have already registered through Oodi can attend the course • T-106.3101 or equivalent as a prerequisite; basically, you should already know how to program

  3. Course basics (2/2) • No exam, only a programming project done in groups • 5 lectures on Fridays – Check the times in Noppa (4.2. we start at 9:15) – Lectures here in T2 – Mandatory • Ignore old information in Noppa (no video lectures from Tampere, no course book, no Symbian) • Giving course feedback is mandatory, link to feeback form will be published later in Noppa

  4. Group work (1/2) • Five topics: 1. Event Experience (Tutor: Vesa Suikkola) 2. Location-based services (Tutor: Alberto Vila Tena) 3. Ringle (Tutor: Tatu Toivio) 4. Mobile offloading (Tutor: Yrjö Raivio) 5. Mobile Kassi / Ride sharing (Antti Virolainen) • Groups of 5-6 people, 2 groups per topic • On topics Event Experience and Kassi, groups under the same topic will collaborate • Group formation: Send me an email at antero.juntunen@aalto.fi with your topic preferences by Monday 24.1. 23:59. If you don’t send your topic preferences, you’re considered to have dropped out of the course! • Example email subject: ”T - 110.5130 topic preferences 3, 2, 1, 5, 4” – List topics by number from most to least preferred • We will take into account your preferences, create the groups and publish them next in Noppa

  5. Group work (2/2) • Each group is assigned a tutor who guides the group work • The tutor will contact the group by email to set up the first group meeting • First task: project plan – Selected technologies, tools, planned time table, etc. – Return by email to tutor by Thursday 17.2. 23:59 – 5 minute presentation of project plan on Friday 18.2. lecture • Final report & code submission – Return report by email to tutor latest Wednesday 11.5. 23:59 – Code submission arranged with tutor • Demo sessions (Friday 13.5.) • More details about the deliverables and demo will be published in Noppa during the next week • Grading: 30% project plan, 30% final report, 40% project outcome / application demo

  6. Schedule • Lectures (all in T2 ): – 21.1. (13:15-15:00) Course introduction – 28.1. (12:15-14:00) Development environments, version control, and Google App Engine – 4.2. (9:15-11:00) Qt Development 1/2 – 11.2. (12:15-14:00) Qt Development 2/2 – 18.2. (12:15-14:00) Group project plan presentations / Amazon Web Services • Deadlines: – Topic preferences: Monday 24.1.2011 23:59 by email – Project plan submission by email 17.2. 23:59 & presentation 18.2. – Final report by email 11.5. 23:59 , code submission arranged with tutor – Demo date (in T5 ): 13.5.

  7. Next • Presentation of the topics by the tutors 1. Event Experience (Vesa Suikkola, vesa.suikkola@aalto.fi) 2. Location-based services (Alberto Vila Tena, alberto.vilatena@gmail.com) 3. Ringle (Tatu Toivio, tatu.toivio@qbitech.com) 4. Mobile offloading (Yrjö Raivio, yrjo.raivio@tkk.fi) 5. Mobile Kassi / Ride sharing (Antti Virolainen, antti.virolainen@iki.fi)

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend