Category Archives: 3.3.2 AMOS

Invitation to the 2015 AMOS Project Demo Day

On July 15th, from 10:15 to 11:45 Uhr, this year’s AMOS Projects will be demoing their project results to the public. The location is Room 00.136, which is a room on the ground floor of the Mensa building (located in the back). Please register using this form so that we can plan appropriately.


Time Content
10:15-10:20 Welcome by Prof. Riehle
10:20-10:30 By project, thank you to students and industry partners
10:30-11:45 Demos and posters, fair-style (wie eine Messe)

All projects welcome you at their booth for demos and questions and answers.

Continue reading Invitation to the 2015 AMOS Project Demo Day

This Summer 2015 Semester’s Industry Speakers

The summer semester 2015 is shaping up nicely with several industry guest speaker appearances in our AMOS and PROD courses. Below is the line-up. Typically, these presentations are open to the public. In this case, they are not, because out class rooms are too full to accommodate any guests.

  • 2015-05-19: Matt Richards of OwnCloud on “Hard Software Marketing Choices” in PROD
  • 2015-06-24: Rolf Kintscher of Senacor on “Challenging Scrum” in AMOS
  • 2015-07-01: Diamantis Gikas of Siemens Automation on “Lessons from the Agile Trenches” in AMOS
  • 2015-07-08: Felix Mannewitz of Siemens Legal on “Open Source Governance” in AMOS

We are grateful to our industry partners for providing such an amazing line-up of speakers and we can’t wait to see and hear them in action!

The AMOS Project Summer 2015 Line-up

We are happy to announce the following five AMOS projects for the upcoming semester:

  1. Cloud computing—Porting an existing software to all major cloud computing platforms (with DATEV)
  2. Consumer app—Developing a mobile app for ride sharing including a server component (with Elektrobit)
  3. Software engineering tool—Tracking changes and predicting impact for traceability (with Elektrobit)
  4. Business software—Developing a simple business software with secure communication (with DATEV)
  5. Cross-platform app—Developing a cross-platform app for five major platforms (with Develop Group)

More details can be found in the StudOn section of The AMOS Project (2015). (You need to log in.)

Teaching Time Slots for Summer 2015

For clarification purposes, here are the precise teaching time slots for the upcoming summer semester 2015:

  • AMOS—Wednesdays: Lecture 10:15-11:45 Uhr, Exercises: 12:15-15:45 Uhr
  • ARCH—Thursdays: Lecture + exercises 14:00-17:00 Uhr
  • KOLL—Mondays: Seminar 12:15-13:45 Uhr
  • PROD—Tuesdays: Lecture + exercises 14:00-17:00 Uhr

There is still inconsistent information flying around; we hope the systems will have sorted out themselves soon.

Heads-up on Summer 2015 Course Organization

During the upcoming summer semester (SS15) we will be teaching our usual courses AMOS, ARCH, and PROD. We will have 10 ECTS projects available for AMOS and ARCH, but not for PROD. We will post the project descriptions soon as we are nearing completion. If you are curious, you can already learn more about available projects on the StudOn sections of the courses.

All three courses are Master-level courses. For this coming summer semester, for the last time we will accept Bachelor students to support backwards compatibility, however, please be advised that these courses require performance on a Master student level. If you are a Bachelor student, you may want to delay participation until you started your Master’s degree.

Also, all our courses are available to all students across the engineering faculty, as well as IIS students. We welcome not only INF and IIS, but also MT, ME, CE, IUK, etc. students. In general, we are open to everyone who wants to take it, we simply may not have been able to figure out how to input this into UnivIS (yet).

If you liked MAD for your Bachelor, you’ll love AMOS for your Master’s Degree

Students: Several students asked us whether they could take AMOS in their Master program even though they had taken MAD for their Bachelor degree. Of course you can take AMOS! They are different courses. Expect AMOS to be the same fun and then some more! AMOS differs from MAD in a couple of key dimensions:

  1. We work with industry partners who bring real-world expertise to the classroom
  2. While projects are provided by industry, you will keep the rights to your work
  3. AMOS is taught in English (your team may choose their own language, e.g. German)

and most importantly:

  1. We choose industry projects and partners with the goal of creating startups!

If you are interested in taking AMOS with the goal of creating your own company after you finish your degree, please let us know in advance. We actively support and guide student startups through our structured Startupinformatik program.

2014 AMOS Project Testimonial by FAPS

FAPS was a university partner helping us teach agile methods as part of the 2014 AMOS projects. The FAPS-side project managers were Mr. Donhauser and Mr. Rackow, working for Prof. Franke.

Below please find their testimonial about their project experience:

Der Lehrstuhl für Fertigungsautomatisierung und Produktionssystematik—FAPS—ist die anerkannte Lehr- und Forschungseinrichtung für Automatisierungstechnik und mechatronische Systeme, die durch interdisziplinäre Entwicklung und ganzheitliche Optimierung dem Wohl des Menschen dient. FAPS kreiert und realisiert Innovationen durch die Integration von Wissen aus unterschiedlichen Bereichen und deren Vernetzung, insbesondere in den Fachdisziplinen Mechanik, Elektrik/Elektronik, Informationstechnik, Bionik und Optik. Im Rahmen der Zusammenarbeit des Lehrstuhl FAPS mit dem AMOS Projekt wurde ein Energie-Controlling-Tool entwickelt, welches die Analyse, Planung und Steuerung von Energieverbräuchen in produzierenden Unternehmen unterstützen soll. Durch die interdisziplinäre Besetzung des Projektteams aus Informatik- und Maschinenbaustudenten konnten die komplexen Sachverhalte gut aufgenommen, interpretiert und schließlich in dem Tool implementiert werden. Die Kommunikation zwischen den Lehrstühlen war stets angenehm und zielführend. Das Ergebnis der Arbeit stellt einen wichtigen Beitrag zu den angrenzenden Forschungsprojekten Green Controlling und KS-Sim dar. Wir bedanken uns bei allen Beteiligten für die Zusammenarbeit und würden uns freuen, wenn wir in den kommenden Semestern wieder an einem gemeinsamen Projekt arbeiten könnten.

Involving academic partners is a new development for the AMOS projects, partly explained in this open email to my colleagues about interdisciplinary work and student startups. We will of course continue to work with our regular industry partners as well, as this year’s AMOS demo day schedule shows.

Thank you for working with our students and inspiring this impressive team performance!

Impressions from the 2014 AMOS Demo Day

On July 9th the 2014 AMOS Demo Day took place, with a total of 50 students and industry partners in attendance.

Five teams presented the results of their hard work, supported by industry partners and members of the OSR Group, managed by Prof. Dirk Riehle and his team. To the students the AMOS Demo Day was an experience they would never want ot miss, working, discussing and developing in groups with different cultures and backgrounds.

We would like to say thank you to all participants of this special day.

Below, please find some photo impressions from the proceedings:

AMOS (74)

Continue reading Impressions from the 2014 AMOS Demo Day

Finished AMOS Demo Day In Appropriate Headwear

We finished the 2014 AMOS Demo Day (report to follow), wearing seasonally appropriate headwear. Sunday may come.

Requirements for Successful Participation in the AMOS Projects

Students participating in the AMOS projects perform a weekly sprint retrospective, which includes giving feedback to the lecturers. One information systems (Wirtschaftsinformatik) student unloads on us:

This whole thing seems to be some kind of bad joke of computer science people, which non-computer scientists seem not to get. It is absolutely ridiculous to use a code repository for planning documents, especially one like GitHub with its absolute horrible usability—or practical non-usability, needing half a dozen different programs to access it and hours to work out how to add a stupid PDF file which has nothing to do with the code. And to fail doing so because some of this half dozen git-tools may have had some tick mark set wrong, some parameter hidden in the endless amount of options which make no sense at all to a casual user or for whatever other reason this may not have worked out. Why the hell are we doing all that, just to learn how to commit PDF files to some awkward system nobody would use in real life anyway? I’m done with this git-thing, I’m done with the whole Scrum-nonsense and I’m especially done with Informatics people and their way of thinking, which seems to create more problems then the world would have had without. Never again.

We regret the bad experience this student is having, but we would like to remind future students to look at the course entry requirements which involve a minimum of technical expertise so that handling a configuration management system like git should not be a problem.

As to putting a PDF into git—we are managing requirements (product backlog, sprint backlog, etc.) using Google spreadsheets, of which we ask product owners take a weekly snapshot and track it on git. The reason why we are not using a dedicated tool is that students complain about having to learn too many tools. We may change this in the future.