is able to select and to use appropriate cost estimation methods and project management software in practical projects. He or she is able to apply
methods for risk management and to use maturity models for improving
processes.

Index

 Brief recap of software project management basics (e.g. work break
down structure, project organization)
 Methods for planning and controlling projects
 Estimation methods: efforts, costs
 Network planning techniques
 Project management software
 Testing methods
 Risk management
 Maturity models

Pre-Exam Requirements Presentation in class
Method and Extent ofExaminationOral Examination, 20 minutes

Media

Blackboard, Powerpoint, Computer Demonstration, moodle

Recommended Literature (Excerpt) Ahren, D.M., A. Clouse, R. Turner: CMMI Distilled 2nd Edition. Addison
Wesley, 2003.
 Futrell, R.T., D.F. Shafer, L.I. Shafer: Quality Software Project Management. Software Quality Institute Series. Prentice Hall, 2002.
 IEEE Guide to the Software Engineering Body of Knowledge (SWEBOK);
IEEE, 2004.
 PMI Standards Committee: A Guide to the Project Management Bodyof Knowledge (PMBOK); Project Management Institute, 3rd edition,2004.
 subject specific additional literature, project management software

4 Software Architecture
CourseMaster Software Technology, Digital Processes

Name of Module

Software Architecture

Abbreviation

SWASemester

1Responsible

Prof. Dr. Deininger

Lecturers

Prof. Dr. Deininger, Prof. Dr. Wanner, Prof. Dr. Speiser

Elective / compulsory

Compulsory module

Frequency

Every year

Syllabus Software Technology (23-09).docx

Page 7 of 27

Weekly Contact Hours

4h (3h Lectures + 1h Exercises)

Method of Teaching

Lecture with theoretical and practical exercises

Student Work Load –Lectures68h

Student Work Load –Self Studies

112hEuropean Credit Transfer Points

6 ECTS Points

Necessary Previous
Knowledge

Software Engineering, Object Oriented Software Implementation

Final Knowledge andSkills

Index

Knowledge and understanding
On completion the student knows the different interrelationships between
requirements and design and architectural choices. He or she knows theprinciples of software design and the different design views and knows howa system design affects the testability of a system.
Disciplinary / professional skills
On completion the student is able to develop different design views and select fitting patterns for certain problems and draw from architecturalchoices. He or she is able to select and use appropriate modeling techniques. He or she can rate the consequences of certain design decisions
Students can earn the official iSAQB certificate at the end of the semester.
Based on iSAQB Certified Professional for Software Architecture Foundation
Level (https://www.isaqb.org/): Basic Concepts
 Roles, Responsibilities, and Activities of Architects
 Deriving Quality Goals and Design Constraints
 Design Principles
 Patterns
 Additional design considerations
 Design Approaches and Methods Documentation and Communication
 Software Architecture Evaluation
 Domain Driven Design
 QA-Architecture

Pre-Exam Requirements Assignments
Method and Extent ofExamination

Written examination, 120 minutes

MediaBlackboard, Powerpoint, Computer Demonstration, moodle

Recommended Literature (Excerpt) Bass, L., P. Clements, R. Kazman: Software Architecture in Practice, 3ndedition, Addison-Wesley Professional, 2012.

Syllabus Software Technology (23-09).docx

Page 8 of 27

 Buschmann, F., R. Meunier, H. Rohnert, P. Sommerlad, M. Stal: Pattern-Oriented Software Architecture: A System of Patterns, John Wiley& Sons, 1996.
 Clements, P., F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord,J. Stafford: Documenting Software Architectures, 2nd edition, AddisonWesley, 2010.
 Evans, E.: Domain-Driven-Design, Addison- Wesley, 2008.
 Fowler, M.: Patterns of Enterprise Application Architecture; AddisonWesley, 2014.
 Gamma, E., R. Helm, R. Johnson, J. Vlissides: Design Patterns: Elementsof Reusable OO Software. Addison-Wesley, 1997.
 Martin, R.C.: Clean Architecture: A Craftsman's Guide to Software
Structure and Design: A Craftsman's Guide to Software Structure andDesign Addison-Wesley, 2018
 Meyer, B.: Object-Oriented Software Construction. Prentice Hall, 1997.
 Shaw, M., P. Clements: The Golden Age of Software Architecture, IEEESOFTWARE, March/April 2006, 31-39.

5 Intercultural Training
CourseMaster Software Technology

Name of Module

Intercultural Training

Abbreviation

ICTSemester

1 and 2Anmerkung: Intercultural Training 1 und 2 wird zu Beginn des ersten und zweiten Semesters als Blockveranstaltung durchgeführt und dient im Wesentlichen zur Integration der neuen Studenten und insbesondere der Quereinsteiger in die bestehende Gruppe. Aus diesem Grund überschneiden sich auchdie Inhalte der beiden Module.
CourseMaster Software Technology

Name of Module

Intercultural Training (Part 1)

Abbreviation

ICT1

Semester

1

Responsible

Course Director Software Technology

Lecturers

External Lecturer

Elective / compulsory

Compulsory module

Frequency

Every year

Weekly Contact Hours

1h (held as a Block-course)

Syllabus Software Technology (23-09).docx

Page 9 of 27