Please enable JavaScript.
Coggle requires JavaScript to display documents.
Architecture-Based Runtime Software Evolution (Change management (that…
Architecture-Based Runtime Software Evolution
Runtime system evolution can mitigate the costs and risks associated with shutting down and restarting the system for an update
enable system evolution without recompilation by allowing new components to be located, loaded and executed during runtime
Tools supporting architecture-based evolution of software systems
Change management
that
helps identify what must be changed
provides context for reasoning about, specifying, and implementing change
controls change to preserve system integrity
Previous approaches to runtime change: 4 approaches
Runtime architectural changel
operates at the architectural level
4 benefits
3 characteristic types of evolution
corrective evolution
Runtime component removal
(: removes software faults)
Runtime component replacement
perfective evolution
Runtime component addition
(: enhances product functionality to meet changing user needs)
adaptive evolution
Runtime component replacement
(: changes the software to run in a new environment)
Runtime reconfiguration
Enabling runtime architectural change
Components
Connectors
Applying concepts to a specific architectural style