Jump to content

Master Szenografie + Komm. 3 Sem

Fast facts

  • Department

    Design

  • Stand/version

    2019

  • Standard period of study (semester)

    3

  • ECTS

    90

Study plan

  • Compulsory elective modules 1. Semester

  • Compulsory elective modules 2. Semester

Module overview

1. Semester of study

Konzeption + Entwurf: Szenografie + Kommunikation
  • PF
  • 4 SWS
  • 8 ECTS

  • Number

    MOD 02

  • Duration (semester)

    1

  • Contact time

    60 h

  • Self-study

    90 h


Learning outcomes/competences

Technical and methodological competence:

  • Be able to assess and evaluate the complexity of software projects
    • Analyzing the background and causes of project failures
  • Know software development procedure and process models and be able to select them for specific contexts
    • Waterfall and spiral model, prototyping, V-model XT, Rational Unified Process, agile models (Scrum)
  • Know and be able to apply processes and activities, roles and responsibilities in the area of software management

Interdisciplinary methodological competence:

  • Be able to organize and manage software projects
    • Project planning, effort estimation, effort and cost controlling
  • Know product management
  • Know and be able to apply process analysis, measurement and evaluation
    • Improvement of process quality (CMMI, GQM)

Self-competence:

  • Development and creation of software management-specific result documents
  • Independent creation and presentation of selected software management topics and content

Social skills:

  • Teamwork in groups of four over an entire semester

Professional field orientation:

  • Practical application and implementation of software management-specific processes and activities

Contents

  • Procedure and process models of software engineering (waterfall, concurrent and spiral model, V-Modell XT, Rational Unifed Process, Scrum)
  • Know and be able to apply processes and activities, concepts and methods of requirements management
  • Know and be able to apply risk management processes and activities, concepts and methods
  • Know and be able to apply project management (planning and control) processes and activities, concepts and methods
  • Know and be able to apply quality management processes and activities, concepts and methods
  • Know and be able to apply configuration management processes and activities, concepts and methods
  • Know and be able to apply product management processes and activities, concepts and methods
  • Know and be able to apply release management processes and activities, concepts and methods
  • Know and be able to apply processes and activities, concepts and methods of process improvement
  • Know and be able to apply framework models for process improvement

Teaching methods

  • Lecture in interaction with the students, with blackboard writing and projection
  • Exercise accompanying the lecture
  • Solving practical exercises in individual or team work
  • Internship accompanying the lecture
  • Group work
  • Exercises or projects based on practical examples
  • immediate feedback and performance review

Participation requirements

See the respective valid examination regulations (BPO/MPO) of the study program.

Forms of examination

written exam paper

Requirements for the awarding of credit points

passed written exam

Applicability of the module (in other degree programs)

  • Bachelor's degree in Software and Systems Engineering (dual)
  • Bachelor's degree in Software and Systems Engineering (dual)
  • Bachelor's degree in Business Informatics
  • Bachelor of Computer Science
  • Bachelor of Computer Science
  • Bachelor's degree in Medical Informatics
  • Bachelor of Computer Science Dual
  • Bachelor of Computer Science Dual
  • Bachelor of Medical Informatics Dual
  • Bachelor of Computer Science

Literature

  • Balzert, H. (2008): Lehrbuch der Softwaretechnik: Softwaremanagement, 2. Auflage, Heidelberg: Spektrum Akademischer Verlag.
  • Balzert, H. (2009): Basiskonzepte und Requirements Engineering, 3. Auflage, Heidelberg: Spektrum Akademischer Verlag.
  • Ludewig, J., Lichter, H. (2013): Software Engineering Grundlagen, Menschen, Prozesse, Techniken, 3. korrigierte Auflage, Heidelberg: dpunkt-Verlag.
  • Pichler, R. (2009): Scrum - Agiles Projektmanagement erfolgreich einsetzen, Heidelberg: dpunkt-Verlag.
  • Pohl, K.; Rupp, C. (2015): Basiswissen Requirements Engineering, 4. überarbeitete Auflage, Heidelberg: dpunkt-Verlag.
  • Sommerville, I. (2018): Software Engineering, 10. aktualisierte Auflage, München: Pearson.
  • Spitzcok, N.; Vollmer, G., Weber-Schäfer, U. (2014): Pragmatisches IT-Projektmanagement, 2. aktualisierte und überarbeitete Auflage, Heidelberg: dpunkt-Verlag.
  • Vollmer, G. (2017): Mobile App Engineering, Heidelberg: dpunkt-Verlag.
  • Vollmer, G. (WS 2019/2020): Unterlagen zur Lehrveranstaltung "Softwaretechnik C - Softwaremanagement".
  • Winkelhofer, G. (2005): Management- und Projekt-Methoden, 3. Auflage, Berlin, Heidelberg: Springer.

Projekt: 1 Szenografie + Kommunikation
  • PF
  • 0 SWS
  • 15 ECTS

  • Number

    MOD 01

  • Duration (semester)

    1


Wissenschaft 1
  • PF
  • 0 SWS
  • 7 ECTS

  • Number

    MOD 03

  • Duration (semester)

    1


2. Semester of study

Konzeption + Entwurf: freie Projekte
  • PF
  • 0 SWS
  • 8 ECTS

  • Number

    MOD 05

  • Duration (semester)

    1


Projekt 2: Szenografie + Kommunikation
  • PF
  • 0 SWS
  • 15 ECTS

  • Number

    MOD 04

  • Duration (semester)

    1


Wissenschaft 2
  • PF
  • 0 SWS
  • 7 ECTS

  • Number

    MOD 06

  • Duration (semester)

    1


3. Semester of study

Best Practice / Gründung
  • PF
  • 0 SWS
  • 2 ECTS

  • Number

    MOD 07

  • Duration (semester)

    1


Projektbegleitung Masterarbeit
  • PF
  • 0 SWS
  • 8 ECTS

  • Number

    MOD 08

  • Duration (semester)

    1


Masterarbeit/Kolloquium
  • WP
  • 4 SWS
  • 5 ECTS

  • Number

    MOD 09

  • Duration (semester)

    1

  • Contact time

    60 h

  • Self-study

    90 h


Learning outcomes/competences

Technical and methodological competence:

  • Know the definition of a DBS and the schema architecture of a DBMS
  • .
  • Develop, normalize and implement relational models 
  • .
  • Know and apply the transaction concept.
  • Know and apply SQL commands for setting up, storing and querying information (DDL, DML, DRL, DCL).
  • Perform administration of database systems by way of example.
  • Develop stored functions, procedures and triggers.

Social skills:

  • Developing, communicating and presenting relational models and database programs in teams of two
  • .
  • Collaboratively creating and evaluating learning posters or review questions on the course content.

Professional field orientation:

  • Know the requirements of different job profiles in the database environment (database administrator, database developer, application developer, data protection officer)
  • .

Contents

  • Database and transaction concept
  • Relational model, normalization and operations
  • SQL Data Definition Language and Database Integrity
  • SQL Data Manipulation Language
  • SQL Data Retrieval Language
  • SQL Views
  • Roles and rights management
  • Stored functions, procedures and triggers
  • Backup and recovery

Teaching methods

  • seminar-style teaching with flipchart, smartboard or projection
  • Solving practical exercises in individual or team work
  • Processing programming tasks on the computer in individual or team work
  • active, self-directed learning through tasks, sample solutions and accompanying materials
  • Exercises or projects based on practical examples
  • mini-exams during the semester for regular feedback
  • The lecture is offered as a video
  • Inverted teaching (inverted classroom)

Participation requirements

See the respective valid examination regulations (BPO/MPO) of the study program.

Forms of examination

The exam consists of two parts:
  • written examination paper, 60-90 minutes, accounting for 80% of the overall grade
  • project-related work with documentation and presentation as semester-accompanying examination performance with a share of 20% of the overall grade

Requirements for the awarding of credit points

  • passed examination consisting of written examination paper and project-related work, which together are assessed with an overall grade of 4.0 or better

Applicability of the module (in other degree programs)

  • Bachelor of Business Informatics
  • Bachelor of Software and Systems Engineering (dual)
  • Bachelor of Computer Science
  • Bachelor's degree in Medical Informatics
  • Bachelor of Medical Informatics Dual
  • Bachelor of Computer Science Dual

Literature

  • Beighley, L., SQL von Kopf bis Fuß, O'Reilly, 2008.
  • Kemper, A., Wimmer, M.; Übungsbuch Datenbanksysteme, Oldenbourg; 2. aktualisierte Auflage, 2009.
  • Saake, G., Sattler, K., Heuer A., Datenbanken - Konzepte udn Sprachen, 6. Auflage, mitp, 2018.

Notes and references

This site uses cookies to ensure the functionality of the website and to collect statistical data. You can object to the statistical collection via the data protection settings (opt-out).

Settings(Opens in a new tab)