Information on individual educational components (ECTS-Course descriptions) per semester

None

• Basic terms: system, system environment, system boundary; System purpose, system development and system stability
• Interactions between system and environment, and feedback (automation effects).
• Process models, in particular waterfall, unified process, extreme programming and scrum.
• Techniques of requirements modeling and system analysis for dealing with unsharp requirements / specifications and description in text form (use cases, user stories) and selected diagrams (use case, class, state machine, activity) of the UML (Unified Modeling Language).

Technical and methodological competence (F / M)

• The students know common procedural models and their advantages and disadvantages.
• They can classify requirements engineering in the overall context of software engineering, know the problem of the validity and consistency of requirements recording and know the limits of requirements engineering (sensemaking vs. problem structuring).
• The students have already carried out simple requirement analyzes using both textual (use cases and user stories) and graphic (various UML diagrams) methods with a focus on validity and internal consistency.

Through specifically selected forms of learning and teaching, this course also contributes to the training of the following general skills:

Social and communicative competence (S / K)

• Empathy: Show willingness and ability to understand people and their concerns
• Ability to motivate: Ability to get others excited about something
• Intercultural competence: Knowing the prevailing differences in different cultures and learning to appreciate them
• Conflict management: dealing constructively with different perspectives and interests, recognizing the causes in conflict situations and developing solutions
• Ability to negotiate and conduct discussions: Be confident and confident in negotiations and represent your own interests and those of the team well
• Reliability: Comply with rules and agreements and do your own work in the promised quality

English is the technical language of computer science. Students are familiar with the use of specialist literature in German and English. You can describe technical issues and processes in German and English.

Self-competence (S)

• Self-reflection ability: Knowing your own abilities and limits and reflecting on your own actions
• Learning competence and motivation: Ability and willingness to acquire new knowledge independently and to learn from successes and failures
• Adaptability: Engaging in changing conditions and being able to deal with changing situations
• Ability to make decisions: Knowing your own freedom of decision and the associated responsibility as well as obtaining the necessary information, developing alternatives, setting priorities and finding a solution in a reasonable time
• Ethical competence: Ability to perceive a fact or situation as ethically significant, to formulate normative rules of conduct and to justify them
• Entrepreneurial competence: Ability to understand entrepreneurial decisions and to think and act entrepreneurially
• Expressiveness: Ability to express and understand expressions and written language as well as a choice of words appropriate to the situation

Transfer Competence (T)

• Ability to analyze and present / communicate: Ability to grasp and arrange extensive and complex relationships in a short time, to filter out the essentials and to present them in a way that is easy to understand
• Assessment and problem-solving ability: assessing facts and being able to use them to derive consequences and approaches
• Customer orientation: Recognize the needs of customers, partners, etc. and address them appropriately in terms of service and quality

Integrated course with frontal instruction in lecture units on theory. Small method exercises with feedback rounds. Presentation and discussion of the solutions by the students.

70% (online) exam + 30% specification.

For a positive grade, a minimum of 50% of the possible points must be achieved in each part of the examination.

Non applicable

Balzert, Helmut (2010): Lehrbuch der softwaretechnik: Basiskonzepte und requirements engineering. Springer-Verlag.

Balzert, Helmut (2008): Lehrbuch der Softwaretechnik: Softwaremanagement. Spektrum Akademischer Verlag. 

Sommerville, Ian (2018): Software Engineering. 10., aktualisierte. Hallbergmoos: Pearson Studium.

Beck, Kent; Andres, Cynthia (2004): Extreme Programming Explained: Embrace Change: Embracing Change. 2nd edition. Boston, MA: Addison-Wesley Professional. 

Rubin, Kenneth S (2012): Essential Scrum: A practical guide to the most popular Agile process. Addison-Wesley. 

McLaughlin, Brett D; Pollice, Gary; West, David (2007): Objektorientierte Analyse und Design von Kopf bis Fuß. O'Reilly Germany.

Jacobson, Ivar u.a. (2013): The essence of software Engineering: applying the SEMAT kernel. Addison-Wesley.

Fowler, Martin (2004): UML distilled: a brief guide to the standard object modeling language. Addison-Wesley Professional. 

Larman, Craig (1998): Applying UML and patterns. Prentice Hall Englewood Cliffs, NJ.

Classroom teaching, attendance is mandatory.