All posts by Dirk Riehle

New Grading Scheme for Final Theses

We designed a new and simplified grading scheme for final theses, replacing the old one. A thesis still has to pass some basic [OK|NOK] checks like completeness of declaration of materials built on, relevant topic, no plagiarism, etc. However, this is a binary decision and does not affect the grade directly (except for failing if these criteria are not met).

The grade then is derived using only four main measures. These are:

  • Results quality
  • Method competence
  • Effort expended
  • Presentation quality

Each measure is taken on scale of [0..10], where 0 means not present at all and 10 means perfect, with a linear distribution around the mean. The four measures are combined using the geometric mean, from which a grade in the German 1,00 – 5,00 grading system is derived.

This new grading scheme has been put into effect starting the academic year of 2017/18.

GI AK workshop on microservices finished well

Yesterday and today we hosted the 2nd GI AK workshop on microservices and DevOps at SUSE, in Nuremberg. We had 37 registrations, 26 people showed up, and about half of them were from industry. Thank you SUSE, for having us!

Winter semester elective teaching off to a good start!

We kicked off our teaching of elective courses this week. Winter semester teaching comprises ADAP, NYT, PROD, and AMSE. Below please find a photo impression from PROD, our course on software product management.

Sivantos student job with Raspberry Pi as user agent (AMOS SS17 project follow-up)

Sivantos (former Siemens audiology) is looking for a Werkstudent to continue the AMOS SS17 project, in which it developed software for a Raspberry Pi as a user agent for testing hearing aids. Please see Sivantos career opportunities at Werkstudent (m/w) im Bereich Softwareentwicklung / Single Board Computer / Raspberry Pi (486).

GI AK Microservices and Devops workshop agenda finalized

We are organizing a meeting of the GI AK on microservices and devops on October 19-20th in Nuremberg. Suse has generously offered their event space for the workshop. The workshop is free and open to the professional public. The agenda has been finalized. It is still possible to register for the workshop. Despite this English-language announcement, the workshop is likely to be held in German.

Poster für den Tag der Technischen Fakultät

We will be talking about open source user consortia at the Tag der Technischen Fakultät of FAU on Nov 17, 2017. Please find our poster depicted below.

Newsletter (to FAU Students) 2017-04

Hello everyone, and welcome back to our Newsletter!

Table of Contents

Continue reading Newsletter (to FAU Students) 2017-04

GI AK Microservices and DevOps on Oct 19-20, 2017, in Nuremberg

Update: The agenda has been finalized and announced.

We are organizing a meeting of the GI AK on microservices and devops on October 19-20th in Nuremberg. Suse has generously offered their event space for the workshop. The workshop is free and open to the professional public. There is a preliminary agenda and you can make a talk suggestion. If you would like to participate, please don’t forget to register. Despite this English-language announcement, the workshop is likely to be held in German.

Show-casing the 2017 AMOS project “Simulating a car’s ECUs using a Raspberry Pi”

Project name Simulating a car’s ECUs using a Raspberry Pi
Project mission The mission of the project is to implement a scriptable Electronic Control Unit simulation environment that can siumlate diagnostic communication. Diagnostic Developers can model the diagnostic behaviour of single ECUs or whole cars inside a box such a Rasperry Pi. The communication protocol used in the vehicle diagnostic is Unified Diagnostic Services. It is a Request-Response Protocol. The ECU provides Services which can be called by the client. The mission of this particular project (in the context of the product vision).
Industry partner AVL DiTest
Team logo
Project summary Our task was to simulate ECUs from a car via Raspberry Pi. For the communication, the ECUs in a car are connected via CAN-Bus. We used the UDS-protocol for the communication of the ECUs. Which functions from the ECUs are supported is defined in the lua file. An example: If you are reading the name of the ECU, each lua file (ECU) should send another name back, e.g. engine, airbag… Because each ECU has a different task in in the car, all the definitions within the different lua files are different. Due to the fact that the Raspberry Pi is loading several lua files at the same time, a behaviour like in the car is simulated, because several ECUs are communicating with each other.
Project illustration
Project repository https://github.com/christian-reintges/amos-ss17-proj4

Show-casing the 2017 AMOS project “Raspberry Pi as user control board for multimedia evaluation boards”

Project name Raspberry Pi as user control board for multimedia evaluation boards
Project mission The mission of our project is to enhance the Sivantos Fitting Software System with a Raspberry Pi user control board to test the software efficiently and rapidly replacing the existing manual interaction with the system under test. Our project enables test engineers and manual testers at Sivantos to test their software faster, more comfortably, more efficiently and more thoroughly. By enabling one of the world’s leading manufacturers for hearing aids to increase the safety of their products, we provide value to patients suffering from hearing loss all around the world.
Industry partner Sivantos
Team logo
Project summary At first, we were not quite sure what our project was about. The subject was quite abstract and we had few experience with the hardware. The first sprints were needed to get familiar with the development environment, the hardware components and the protocols needed to talk to the RaspberryPi.
As soon as we got familiar with all the components, we were able to implement more actual features. Testing was a bottleneck, as we had to test the soft-/ hardware interaction but only had two fully functional breadboards. The close cooperation with our industry partner was helpful not only for defining the scope of the project and prioritize features, but also for debugging hardware related problems. We learned a lot, not only about software development in unknown terrain but also about Scrum in general and the importance of interaction and communication within the team in particular.
Project illustration

Team photo
Project repository https://github.com/varj888/amos-ss17-projSivantos