Kalender

Introduktion för studenter

We had an early morning meeting where I presented the sessions for the spring up until the public presentation in May. Here's the presentation.

We save this option till later. I would suggest that you instead consider booking a meeting with your supervisors to get some support, feedback or general good advice.

This will be a guest lecture by Gustav Taxén from Propellerhead. The lecture will for example include:

• Encapsulation
• Single responsibility principle
• Fragile base classes
• Object lifetime management
• Design by contract
• Invariant checking
• Exception safety
• Code documentation
• Unit tests, regression tests, integration tests
• Test Driven Design
• Code Reviews

Here are the lecture notes from Gustav.

Today we have presentations of you progress so far in the same way as previous presentations:

• Each group has a maximum of 10 mins, 6 min presentation + 4 min questions and comments
• Prepare a short status presentation based on the deliverable
• Assume nothing, give enough background information for a new audience
• What are you working on, what have you done, what will you be doing next
• In this ”friendly environment”, try out ways of presenting your project more efficiently

Hand in the draft 3 no later than 23.59 on Thursday Feb 13. Send it to me and to your respective supervisor.

-----------

This is the room/project distribution:

Room D2

14. U+2603

12. HoH

11. Församlingen

10. DT

8. SMAB

3. G1

2. Bismarck

1. BSoD

Room D3

16. Exchange

15. The Avengers

13. OGB

9. Void

7. FoL

6. Emil

5 A*

4. Placeholders

Här är dagens presentation.

Halvvägsmöte (halvtidsmöte) - Richard Nordberg

Halvvägsmöte (seminarium) - grupp 1 (Anders Askenfelt) och 2 (Per Austrin)

Halvvägsmöte (seminarium) - grupp 3 (Roberto Bresin) och 4 (Pawel Herman)

Halvvägsmöte (seminarium) - grupp 5 (Alex Kozlov) och 6 (Michael Minock)

Halvvägsmöte (seminarium) - grupp 7 (Vahid Mosavat), 8 (Gabriel Skantze) och 9 (Christian Smith)

Now we've reached the presentation of draft 4 and there's six weeks left of your projects! This presentation should of course include a progress report (what have you worked on and how has that been going) but also include your plans to finish the project at a logical point. Like the previous draft milestones, we want you to send in the document to Björn Thuresson and your respective supervisor before 23.59.

There are few opportunities to shift the groups around very much, but here's the distribution:

D2

4. Placeholders 7. Graph Visualization of Code Bärbel Janssen

16. Exchange 8. Videotelefon Bärbel Janssen

8. SMAB 16. Playhouse Björn Thuresson

11. Församlingen 5. Måla med ögonen Björn Thuresson

14. U+2603 26. Dr Maombi Björn Thuresson

15. The Avengers 17. Chaview Anders Lundström

7. FoL 1. Gapminder Mario Romero

9. Void 6. WebGL Mario Romero

V1

5 A* 23. Kattis Filip Kis

6. Emil 14. Bluetooth apps Filip Kis

10. DT 2. Instalert Aurélien Larcher

12. HoH 32. Distributed File Search Aurélien Larcher

13. OGB 22. Köhanteringssystem på CSC Cristi Bogdan

1. BSoD 9. Horror Game Chris Peters

2. Bismarck 10. Dynamic Audio Chris Peters

3. G1 29. Visualisering av grafdatabaser Chris Peters

Genomgång av presentationsteknik för studenter (hålls av Richard Nordberg)

Det preliminärt schemat finns på kurswebsidan.

Det preliminärt schemat finns på kurswebsidan.

As previoulsly discussed, here's that special event on the different legal aspects linked to software development. We'll get a presentation + Q&A with two legal specialist at KTH Innovation: Cecilia Sandell and Therese Wiksten. They'll cover:

IP – Intellectual Property

Definition of IP

IP has value = the results of your work has value

Protecting your Intellectual Property

Why protect IP?

Different models/ways that IP protection, e.g. patents, can create commercial value

Types of IP protection

Copyright.

Trademark.

Design.

Patent.

Business strategies

Cost vs. benefit

Agreements and contracts.

Agreements and contracts are always present in the innovation process

Agreements and contracts – Important aspects

Rights to results

Confidentiality obligations

Publications

Here's the full program incl descriptions!

Friday May 16

E1

13-17 + mingle in Ljusgården 17-18

Background

In this year’s course in software engineering (MVK13) 16 projects have been realized. The students have worked with external clients ranging from Ericsson, Tekniska Muséet, FOI and Gapminder to a number of internal clients from different schools at KTH.

The course goal is to via practical work get experience and insights in the best practices within software engineering. The course is project based and the students work together with the client to develop software solutions.

The students have all done excellent work and are eager to show it. All projects have also produced hands-on demos of different kinds.

Layout

The projects will be presented in groups of four/hour + demo session. All in all there will be four sessions. See program. Each presentation is 8 min + context switch. At the end of each session, the four presented projects show their demos simultaneously in the area at the front for 15-20 mins. Everyone in the audience is invited to interact, ask questions and discuss. There will be some kind of refreshments available during every demo session.

Preparations for the students

1. Description for the event programme

Send a text to Björn Thuresson thure@kth.se describing your project. It should be an efficient presentation of your process and results, written in an attractive and engaging manner in 2000 characters (incl spaces).

Send in 1-3 pictures and/or illustrations representing your project, the activities or the results, preferably in at least 150 dpi. Include contact information: name, e-mail and phone (if that's OK).

Deadline: May 9

2. The presentation

You have 8 mins to present your project. This is your opportunity to make yourself and your project justice. Use it well! There’s nothing you have to present, choose the parts you think are the strongest and the one’s you’re the most proud of. Remember that the audience is mixed and they, typically, know very little about your area. You’re the experts in the room! That means that you’ll have to give a background to the area, the challenges, the target groups, the use situations, etc. Also, after your presentation you’ll show the hands-on demo, so choose wisely what to present and what to refer to in the demo.

Be confident in your presentation. Do not make unsupported statements. You can motivate all the choices – be sure to do that! It’s a matter of credibility. You are the experts but you need to show that. We believe you if you give us reasons to do that.

In E1 there are two projectors (possibility to have different sources), a document camera, sound and microphones. What are you going to use? How are you going to test it? There’s very little time for context switch, so make sure you prepare. You could choose to use the same computer for all four projects in your session (contact them and test) or you could use Björn’s computer (contact him) or you could use your own equipment (test). 

3. The demo

At the end of each session (15-20 mins) all of the audience are welcome to try your hands-on demos. You set up all four project’s demos in the area at the front. Make sure you prepare the demo to work well as a public demo. Should it be automatic or do you give instructions? What are you going to say? Which technology do you need? Any print material (poster, logos, hand-outs)? Etc.

4. Invitations

This is your afternoon. Invite as many as you want, particularly the people involved (the client, user groups etc) but also others you would like to show what you’ve done (friends, family, future employers etc).

5. The final report

You’ve been working with drafts of the documentation of your projects continuously and we’ve discussed how to make them useful throughout for you (in your project groups), for your client/s (to understand and evaluate what you’ve been doing and what you should do), and for reporting to class (supervisors etc). Now it’s time to bring everything together.

I’ll instruct the supervisors to be extra careful when giving you feedback on draft 4 to make sure that all sections are in there and sufficiently presented and documented.

For the final report there is one extra section: reflections on the course, the project and the results. In there I want you to reflect on what you’ve been doing. What worked well and what would you’ve done differently? Think about your learning process and what you’ve learned. I’ll not give you more instructions, I’ll let you decide what to focus your reflections on, but try and take an outside perspective and observe and analyse your achievements in a systematic manner.

Deadline: May 23, send to your supervisor and Björn.

6. Code delivery

On numerous occasions I’ve told you to use this opportunity to build your portfolio, to have concrete examples of what you can do and what you’ve done. Later on, regardless if you pursue a career in industry or academia, you will be asked to show your abilities and what you know. A printout from Ladok is very rarely enough. I ask you to hand in or make available something concrete from your code creation. This could be, for example, in the form of:

• An .exe file
• A binary file
• Scenario video/s (clearly showing the functions and features)
• Tutorial video/s
• A website with all or selected material from this list
•  …

I’m aware that your project goals and outcomes are different; therefore you should pick the format/s that best represent your project and the results.

I would recommend you to make a website with descriptions, examples, videos, images, and downloads (or what make sense). This is an excellent opportunity to do that.

Deadline: May 23, send to your supervisor and Björn.