Seminar: Data- and Value-Driven Software Engineering with Deep Customer Insight

58314308
4
Ohjelmistojärjestelmät
Syventävät opinnot
The goal of this seminar is to analyze existing approaches and experiences with respect to data- and value-driven software engineering, i.e., creating an R&D system that allows organizations to better decide what to develop, which business strategies to follow. In addition, data-based adjustments of the development process are considered. The students will get a comprehensive overview of modern experiment and feedback-driven software development.
Vuosi Lukukausi Päivämäärä Periodi Kieli Vastuuhenkilö
2014 syksy 01.09-08.12. 1-2 Englanti Jürgen Münch

Luennot

Aika Huone Luennoija Päivämäärä
Pe 12-14 C220 Jürgen Münch 12.09.2014-12.09.2014
Ma 14-16 B119 Jürgen Münch 15.09.2014-13.10.2014
Ma 14-16 B119 Jürgen Münch 27.10.2014-08.12.2014

Yleistä

The quantum leap in software development speed by incrementally building and deploying software with real-time customer feedback will facilitate the speed and flexibility needed […]. Upon delivering the product or service, the focus shifts to creating incremental improvements, so that development cycles can be shortened, progress can be evaluated, and customer feedback and insight can be used to measure the value of the improvement and fed back to development in real-time.” [1]

There is a need in many software-based companies to evolve their software development practices towards continuous integration and continuous deployment. This allows a company to frequently and rapidly integrate and deploy their work and in consequence also opens opportunities for getting feedback from customers on a regular basis. Ideally, this feedback is used to support design decisions early in the development process, e.g., to determine which features should be maintained over time and which features should be skipped. In more general terms, the entire R&D system of an organization should be in a state where it is able to respond and act quickly based in instant customer feedback and where actual deployment of software functionality is seen as a way of fast experimenting and testing what the customer needs [2].

Experimentation refers here to fast validation of a business model or more specifically validating a value hypothesis. Reaching such a state of continuous experimentation implies a lot of challenges for organizations. Selected challenges are how to develop the “right” software while developing software “right”, how to have an appropriate tool infrastructure in place, how to measure and evaluate customer value, what are appropriate feedback systems, how to improve the velocity of software development, how to increase the business hit rate with new products and features, how to integrate such experiments into the development process, how to link knowledge about value for users or customers to higher-level goals of an organization. These challenges are quite new for many software-based organizations and not sufficiently understood from a software engineering perspective.

The goal of this seminar is to analyze existing approaches and experiences with respect to data- and value-driven software engineering, i.e., creating an R&D system that allows organizations to better decide what to develop,  which business strategies to follow. In addition, data-based adjustments of the development process are considered. The students will get a comprehensive overview of modern experiment and feedback-driven software development.

 

Course News

Schedule

Seminar Schedule
Date Topic
Mon 1.9.2014 Opening of the academic year - no lecture
Mon 8.9.2014 Introduction moved to Friday same week - no lecture
Fri 12.9.2014

Introduction

Note special time and place, Exactum C220 12-14

Mon 15.9.2014 No lecture
Mon 22.9.2014 Scientific writing
Mon 29.9.2014 No lecture
Mon 6.10.2014 Scientific presentations and oral communication, selection of topics, scheduling of presentations
Mon 13.10.2014 5 minute short presentations of topics
Mon 20.10.2014 Exam week - no lecture
Mon 27.10.2014

No lecture / individual work

Midway milestone, preliminary submission (2-3 pages)

Mon 3.11.2014 No lecture / individual work
Mon 10.11.2014

Presentations I (Hirvikoski, Kolppo, Jaakkola)

Paper submission deadline

Peer review starts

Mon 17.11.2014

No lecture

Mon 24.11.2014

Presentations II (Blythe, Järvenpää, Ruonala)

Peer review deadline

Mon 1.12.2014 Presentations III (Vasilev, Zhou, Hyvönen)
Mon 8.12.2014

Presentations IV (Värä, Tallberg, Peuraniemi)

Final, revised paper version submission deadline

 

Seminar Paper Template

Seminar papers should be written using the IEEE conference template. Any writing tool can be used to write the paper as long as the outcome of the paper is PDF; IEEE templates are also offered in LaTex format for those interested. Download the template of your choosing, delete excess text from the template but preserve the format, input your information and start the graceful work of writing a paper.

EasyChair

Scientific conferences use conference platforms to facilitate the organization of conferences and manage paper submissions and anonymous reviews of program commitees. EasyChair is one of these platforms and this seminar will take advantage of conference services offered by EasyChair. Participants need to register an EasyChair account and access the seminar conference pages in EasyChair in order to submit and review seminar submission.

Moodle

This seminar will also take advantage of the Moodle education platform. Students should self-register (enroll as a student) to the seminar through the Moodle seminar page. A discussion forum is available and the final presentations should be uploaded through Moodle, i.e. EasyChair for papers and Moodle for presentations.

Kurssin suorittaminen

Each participant of the seminar will prepare a 6-8 page (IEEE template format) seminar paper on a topic related to data and value driven software engineering. Participants will finally give a 20-30 minute presentation about their topic. The grade for the seminar will be based on the seminar paper, the presentation and the quality and depth of the peer reviews written by the student.

All seminar papers have the same submission deadline Mon 10th November 2014. After the submission deadline, there will be a review round of the seminar papers. Other students and the course staff will give paper review comments and the authors should consider these comments for the final revised seminar paper which is due after the last seminar session. Seminar paper submissions will be done through the EasyChair conference platform. Seminar papers are available to the students from EasyChair so that participants can give feedback to presenters during the presentation sessions. Presentations should be uploaded on the day of the presentation.

Kirjallisuus ja materiaali

[1] Strategic Research Agenda for Need for Speed, 2013, http://bit.ly/1b6rSoH

[2] H. Olsson, H. Alahyari, and J. Bosch, “Climbing the stairway to heaven – a multiple- case study exploring barriers in the transition from agile development towards continuous deployment of software,” in Software Engineering and Advanced Applications (SEAA), 2012 38th EUROMICRO Conference on, 2012, pp. 392–399.

[3] A. Croll, B. Yoskowicz, "Lean Analytics: Use Data to Build a Better Startup Faster", O'Reilly, 2013.

[4] A. J. Smith, "The task of the referee." Computer 23.4 (1990): 65-71.

[5] David Lorge Parnas. 1998. Successful software engineering research. SIGSOFT Softw. Eng. Notes 23, 3 (May 1998), 64-68.

[6] Mary Shaw. 2003. Writing good software engineering research papers: minitutorial. In Proceedings of the 25th International Conference on Software Engineering (ICSE '03). IEEE Computer Society, Washington, DC, USA, 726-736.

[7] Andreas Zeller. How to Give a Good Research Talk. Master seminar presentation.

[8] B. Kitchenham and S. Charters, “Guidelines for performing systematic literature reviews in software engineering,” Keele University and Durham University Joint Report, Tech. Rep. EBSE 2007-001, 2007.

[9] Runeson, P., Host, M., Rainer, A., & Regnell, B. "Case study research in software engineering: Guidelines and examples", Wiley, 2012.