A common software deployment model statically links all executable modules into a single application image. During system initialization, the entire executable image is loaded into memory and remains resident throughout runtime.

While this approach simplifies software management, it permanently allocates memory for every software feature regardless of actual usage. As the number of software modules increases, the memory footprint of the resident runtime environment also increases.

Examples of software components that may not be required continuously include

• Diagnostic functions

• Recovery utilities

• Factory test functions

• Service tools

• Feature-specific application modules

Keeping all such components resident simultaneously may lead to inefficient memory utilization.