Allgemeine Angaben |
|
Advanced Topics of Software Engineering (IN2309, IN2126) | | |
|
|
|
|
|
|
|
|
|
|
| ... |  |
|
|
|
|
|
|
Zuordnungen: 1 | |
eLearning[Neuen Moodle-Kurs im aktuellen Semester bereitstellen] |
|
|
|
Angaben zur Abhaltung |
|
A recap of the basics of Software Engineering (SE) - Software development life cycle (SDLC) models - Artifacts generated during the activities of SDLC processes - An overview of software quality attributes - Understanding which quality attributes are more dominant in different software systems (information systems and embedded systems) System design for meeting the requirements - Software architecture as the backbone of software systems - Using SE methods, tools, and guidelines to manage complexity in software systems - Component-based software engineering – the need for software components and interfaces - Reuse in software development (software product line engineering) - Model-driven software engineering A detailed overview on external and internal quality attributes - Safety and security (external attributes) - Testability (internal attribute) The quality trade-offs to be considered while choosing a specific architecture such as - Database-centric architecture - Message-oriented architecture - Object-oriented architecture - Component-based architecture - Service-oriented architecture Ensuring that the implemented system and changes to the system are continuously available to the stakeholders - Trends in DevOps - Continuous delivery - Using containers for system deployment - A discussion on software architectures for the cloud |
|
|
- Introduction to Software Engineering (IN0006) - Experience with at least one analysis and design technique (UML) - Thorough understanding of object-oriented programming constructs (Java) |
|
|
At the end of the course, students understand the central goals and methods of SE. They understand relevant software quality attributes. They know how specific quality attributes are reflected in architectures and conversely, how architecture influences these attributes. They acquire in-depth knowledge about different software architectures and understand when and when –not to use a specific architecture. Furthermore, they also understand how to deliver their implemented systems to their stakeholders in an efficient manner. |
|
|
|
|
This module comprises lectures and accompanying tutorials. The contents of the lectures will be taught by talks and presentations. Students will be encouraged to study literature and to get involved with the topics in depth. In the tutorials, concrete problems will be solved - partially in teamwork - and selected examples will be discussed. Note - Lecture and exercise material will be available on Moodle - Registration for the course in TUM Online is required - The lectures will not be recorded - For more details visit - https://wwwmatthes.in.tum.de/pages/c9ulr7t9nrqs/Advanced-Topics-of-Software-Engineering |
|
|
|
|
Für die Anmeldung zur Teilnahme müssen Sie sich in TUMonline als Studierende/r identifizieren. |
|
|
Zusatzinformationen |
|
McConnell, Code Complete: A Practical Handbook of Software Construction, 2nd edition, Microsoft, 2004 Summerville, Software Engineering 9, Prentice Hall, 2010 Brooks, The Mythical Man Month, Addison-Wesley Longman, 1995 Rombach, Endres: A Handbook of Software and Systems Engineering, Addispn Wesley, 2003 Bass et al., Software Architecture in Practice, Addison Wesley, 3rd edition, Addison Wesley, 2012 Clements et al., Documenting Software Architectures, 2nd edition, Addison Wesley, 2010 Clements et al., Evaluating Software Architectures, Addison Wesley, 2001 Reussner, Hasselbring, Handbuch der Software-Architektur (in German), 2006 Jackson, Problem Frames, ACM Press, 2000 Sommerville, Sawyer: Requirements Engineering: A Good Practice Guide, John Wiley, 1997 Lamsweerde, Requirements Engineering: From System Goals to UML Models to Software Specifications, John Wiley, 2009 Goucher, Riley, Beautiful Testing, O’Reilly, 2009 Wagner, Software Product Quality Control, Springer, 2013 Weitere Literatur wird in der Vorlesung bekanntgegeben. |
|
|
|
|
|