You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the lecture series mostly assumes neat and tidy proactive development. To reflect the wider product-line literature and prepare students for real systems, an additional lecture on the following topics would IMO be interesting in the long term (and separate to the evolution and maintenance lecture):
20min block: when is the migration to a product line warranted? -> : clone-and own versus platform engineering, cost estimation, scoping
20min block: how to extract/migrate to a product line? -> reengineering, feature identification/location, training
20min block: ??? (maybe discuss industrial case studies? e.g., one success and one failure story?)
This could be an optional thirteenth lecture. IMO, it would also be possible to make the sixth lecture optional (omit (micro-)services and merge frameworks/components into lecture two or seven, as components can be considered an architecture-level instantiation of the adapter/bridge pattern).
The text was updated successfully, but these errors were encountered:
Currently, the lecture series mostly assumes neat and tidy proactive development. To reflect the wider product-line literature and prepare students for real systems, an additional lecture on the following topics would IMO be interesting in the long term (and separate to the evolution and maintenance lecture):
(inspired by Krüger 2021)
This could be an optional thirteenth lecture. IMO, it would also be possible to make the sixth lecture optional (omit (micro-)services and merge frameworks/components into lecture two or seven, as components can be considered an architecture-level instantiation of the adapter/bridge pattern).
The text was updated successfully, but these errors were encountered: