Elective Seminar: Hackathon

None

• Tools of agile software development: Git, GitLab, Gulp
• Software architectures: procedures, technical concept, quality and documentation
• Software design: fundamentals (modules, abstraction, consistency), principles (DRY, SOLID), methods (DDD, WAM, QSDA, top-down / bottom-up), interfaces, patterns
• Methods of implementation (Extreme Programming, Scrum ...)
• Reflection of concepts and methods
• Selected frameworks

Hackathons are aimed at software and hardware developers and aim to develop new ideas and concepts in multidisciplinary teams that promote the innovative power of companies. Based on a specific task, the team discusses solution approaches and concepts and implements them in prototypes. The teams are accompanied by coaches and experts. At the end, the winning teams will be chosen. The aim of the course is to recognize the added value of hackathons and to establish a network with developers, especially from other departments.

Theoretical and methodological know-how (T/M):

• In small groups, the students can design, implement, document and present a prototype (MVP) based on an idea (PoC). In addition, they can critically evaluate and reflect on collaboration, learning progress, work outcome, and documentation.

In addition, social and communicative skills (S/C) such as teamwork/willingness to cooperate, critical faculty, motivation, reliability and self-competences (S) such as learning and motivation, decision-making, responsibility, perseverance, expressiveness, appearance trained.

Participation in one or more hackathons as a participant, i.e. as a developer or coach. Please note that no course times are planned for this course in the timetable. The students can choose the hackathons, but they have to find them on their own. Participation in hackathons within the minimum of 48 attendance/online hours (= hack/working time) is required for positive completion. This must be documented by the organiser in the form of a confirmation of participation (incl. announcement of the hackathon). Furthermore, the lecturer of the course must be informed in advance about the planned participation. For this purpose, the following information must be sent to the lecturer:

• Name of the hackathon
• Link to the event website
• Duration of the hackathon in hours
• Role (participant or coach)
• Objective or development project (especially if participation is not planned as a coach)

Documentation of the work activities, project results or coaching activities and lessons learned per hackathon is required for the award of marks. The documentation must follow scientific criteria (sources, evidence, argumentation structure,...) and provides the basis for the grading. The documentation must be submitted by 31 May for the first examination date.

• Documentation of working progress including individual reflection (100 %)

Currently, students are invited to a variety of hackathons. Credit for this course is examined by the program director in each case.

Depending on their selected topic.

Participation in one or more hackathons with a total of at least 48 hours on-site / online hacking time. This is followed by documentation of the project result and reflection on the learning and working process (= assessment document of academic standard).