Course syllabus

Note: The Canvas Discussion pages will be used extensively to give guidance and hints for the home assignments and the project work, as well as for Peer-assisted learning (PAL). Please log in to Canvas several times per week to keep you updated on the discussions, and try your best to take part!

Course-PM

MMS210 Connected fleets in data-driven engineering - lp4 (7.5 hp)

The course is offered by the Department of Mechanics and Maritime Sciences in collaboration with the Department of Computer Science and Engineering.

Contact details

Please contact the course staff for any further questions about the teaching or course subjects. If a meeting is required, please make contact by email to request an appointment (during office hours).

Examiner and lecturer

Ola Benderius, 031-772 2086, ola.benderius@chalmers.se

Christian Berger, christian.berger@gu.se

Study administrator

Björn Friberg, 031-772 2088, bjorn.friberg@chalmers.se

Course purpose

The purpose of the course is to aid engineers in data-driven decisions connected to vehicle features and development. By also adding continuous experimentation and remote system monitoring, the course will be vital in engineering processes around functional safety. Finally, as fully connected fleets also represent structural changes to transportation in society, it also includes deep and thorough discussion around automated data-collection connected to human activities, as a way to shift previous collect-all strategies into sound ethical engineering principles as endorsed by our governments through recent legislation such as GDPR. 

Schedule

TimeEdit

Course literature

Lecture notes, video lectures, source code templates, and handouts. The material will be made available via the course web page.

Course design

The course consist of lectures and weekly home assignments. In the lectures the theoretical parts will be covered which will provide the students with a broad overview of the subject area. Then, the students are expected to apply the knowledge from the lectures in the home assignments.

The mandatory home assignments has to be carried out individually by each student. Please read further details regarding assessment and grading below.

Learning objectives and syllabus

• Describe properties of hardware components needed in each unit of a connected fleet, including their software life-cycles
• Describe properties of core software components needed in a backend environment, connected to the engineering process
• Apply and monitor over-the-air updates to a fleet of mobile systems, and describe limitations from different underlying technologies
• Apply software development connected to continuous integration and continuous deployment in heterogeneous ECU networks
• Apply large-scale fleet monitoring, and describe involved technologies and how logged data can be used in the engineering process, such as for continuous experimentation and functional safety
• Describe relevant cybersecurity measures to safeguard the connected fleet and the its generated data
• Describe ethical aspects of fleet monitoring and over-the-air updates, and how such concepts can be combined with ethical engineering related to governmental intentions as defined by, for example, GDPR
• Define complete engineering process involving all learning outcomes from the course

Link to the syllabus on Studieportalen

Study plan

Examination form

The examination consists of graded individual homework assignments. There is also a final individual assessment meeting in the end of the course, see below.

See the following subsections for details regarding assessment and grading. Refer also to the below section regarding plagiarism.

Grades

The grades that are given in this course are the following: 5, 4, 3, U (not passed).

Homework assessment

The homework consists of mandatory assignments. Each assignment will be graded and given the grade 3, 4, or 5. A minimum grade of 3 is required on each assignment in order to pass the course. Re-submissions of home assignments will be allowed, but then only to reach the lowest grade. Refer to the home assignments descriptions for details regarding their individual grading.

Final course grade

The student’s final course grade will be determined according to the mean grade of the home assignment grades (3, 4, or 5). The resulting value, rounded to the nearest integer value, is the final individual grade of the course.

Final individual evaluation

In the end of the course, an individual assessment meeting will be held with each student, where the examiner will ask detailed questions about the submitted work. If the student fails to give sufficient answers to these questions the grade might be lowered or blocked for further assessment. The questions will only assess the already approved work, and solely work as a final check for the grading. Therefore, the student should review all submitted content before the meeting, but is not expected to give further information than what was given in the submissions. Typically, this meeting will take place in the exam week based on the student's availability.

Course closure

The course will be open throughout September, and re-submissions given within this time frame will be graded. If all assignments are approved, the final individual evaluation will be offered. If all submission are not completed within the given time frame, then any missing submissions needs to be given the following year (the examiner is free to define an individual plan for completion, based on the current progress and learning outcomes).

Regarding plagiarism

Briefly, plagiarism occurs when someone present ideas, concepts, texts, or other structures from someone else, as their own. I.e. without appropriately acknowledging the original source. See further in the document about Academic integrity and honesty at Chalmers (link).

The reports (and other submitted materials such as e.g. programming code) should be original work in order to be passed. Therefore, all reports and texts that you submit for grading and examination will be checked with Ouriginal, a tool to detect plagiarism.

Note: All suspected cases of plagiarism (not only those detected by Ouriginal) will be reported to the university disciplinary committee (disciplinnämnden)!