Seminar: Architectures, Methods and Tools for Supporting Continuous Experimentat

58315103
4
Ohjelmistojärjestelmät
Syventävät opinnot
Vuosi Lukukausi Päivämäärä Periodi Kieli Vastuuhenkilö
2015 kevät 15.01-30.04. 3-4 Englanti Tomi Männistö

Luennot

Aika Huone Luennoija Päivämäärä
To 16-18 C220 Tomi Männistö 15.01.2015-26.02.2015
To 18-20 C220 Tomi Männistö 12.03.2015-26.03.2015
To 14-20 DK116 Tomi Männistö 16.04.2015-16.04.2015
To 14-20 CK111 Tomi Männistö 23.04.2015-23.04.2015

Yleistä

Continuous experimentation is a means for developing software in the manner that the new developments, e.g., different implementations of a particular feature, are experimented with users in order to see how the new feature or solution works in real, and consequently, to make informed decisions for guiding the development efforts.  Continuous experimentation essentially requires the cababilities of continuous deployment, i.e., being able to deploy changes to the users immediately once they are made. 

In the seminar, the particular point of view can be the architectural issues, software development tools or methods that support or are needed for succesful continuous experimentation. As continuous experimentation has not been around in software development that long, also the earlier steps towards it, such as continuous development, can be considered as a topic.

The seminar work can be based on literature, but searching for possibilities of investigating and reporting experiences or practices from real software companies or other development organisations are highly encouraged.    

 

Kurssin suorittaminen

The seminar will be organised close to the format of a scientific software engineering conference with peer-review practice. The course uses the conference acronym SASMOOTA 2015.

Each participant writes a scientific paper (at least in the form and style) and submits it to the "conference" of the course. The paper will be peer-reviews by course staff and other seminar participants. In addition, everyone presents the paper as in a conference, if the paper is accepted.

The course will use EasyChair conference management system (conference address: https://easychair.org/conferences/?conf=sasmoota2015in which paper, reviews and revised paper will be returned. Details on accessing and using the system will be given in the beginning of the course. 

The paper will be formatted using IEEE conference template, which can be found from http://www.ieee.org/conferences_events/conferences/publishing/templates.html. A suitable length of a seminar paper in this format is 6-10 pages.

The schedule for course sessions is initially as follows (these will be discussed in the first session and may change), lecture room C220. Participation to all sessions is compulsory.
  • Jan 15, Opening, introduction
  • Jan 22. Introduction to scientific writing in the seminar, conference submission and review process 
  • Feb 19, Feedback session
  • April 16, Conference day I 
  • April 23, Conference day II 

 

Instructions for Presentations 

Each presentation is exactly 20 minutes. Think carefully what to include and how much presentation material can be included. 

Discussion

After each presentation there are 20 minutes for discussion in which all are expected to actively participate.

 

Course Schedule (Deadlines)

The course has the following main phases and deadlines (to be confirmed). All deadlines are at 12 noon. The deadlines are strict!

  • Jan 29. Extended abstract deadline. Write an extended abstract of your topic and return it to EasyChair (fulfill the web form, as an pre-submission abstract). It is good idea also already to prepare the IEEE template (remove all comments and instructions from the template), but you need not necessarily submit that at this stage (just tickk the box cose to the bottom of the page about submitting the paper later). 
  • Feb 5. Bidding deadline. You should mark your interest to review other's papers, called bidding, based on the abstracts.
  • Feb 12. Allocation of reviews done by course staff based on your bidding. You will be invited to review the papers allocated to you through EasyChair. 
  • Mar 19. Full paper deadline. Return a complete version of your seminar work to EasyChair. In the IEEE template, 6-10 pages. Note that you should return your work as a "update" to your abstract, not as a new submission (if that for some reason were possible).
  • Apr 1. Review deadline. Read the papers allocated to you and return your evaluation to EasyChair as instructed at the beginning of the course. By this deadline, the course staff will also decide if some papers are rejected. 
  • Apr 16 and/or 23. Conference. The presentation sessions of seminar papers.
  • May 7. Optional revision deadline.  You have an opportunity to revise your seminar paper on the basis of the reviews from others and discussion at the presentation session. The final grading is done based on the versions that are in EasyChair at this deadline. (You may note that this deadline is different than in a typical conference, in which the camera-ready deadline is after the reviews but well before the conference so that the final, revised papers are already available at the conference)

Grading

The grade for the seminar is given based on the written paper (40%), reviews given to other students and activity in the course (30%) and presentation (30%).