ABSTRACT
Stabilization of software frequently occurs in real-time systems that control a specific mechanism, for example, a car ignition. ‰e domain of the software is a particular car engine. Once the engine is produced and used, it does not change, and therefore, the domain is stable. ‰e only reason for evolution is the volatility of stakeholder knowledge, where the stakeholders are learning how to control this specific engine ignition. Once the stakeholders complete their learning and find the solution, there is no reason for further evolution.
