Which phase might be included to handle ongoing updates after release?

Which phase might be included to handle ongoing updates after release?

• A. Maintenance phase
• B. Planning phase
• C. Design phase
• D. Implementation phase

Answer: (A)

Ongoing updates after release are handled in the maintenance phase. This phase is all about supporting the product once it’s in use: fixing defects reported by users, applying patches and security fixes, refining features based on feedback, and ensuring compatibility with new environments or systems. It keeps the product reliable and up-to-date without starting a new development cycle from scratch. Planning, design, and implementation happen before or during the initial release, focusing on deciding what to build, how it should work, and delivering it. They aren’t primarily about post-release updates, which is why the maintenance phase is the best fit for handling ongoing changes after launch.

Ongoing updates after release are handled in the maintenance phase. This phase is all about supporting the product once it’s in use: fixing defects reported by users, applying patches and security fixes, refining features based on feedback, and ensuring compatibility with new environments or systems. It keeps the product reliable and up-to-date without starting a new development cycle from scratch.

Planning, design, and implementation happen before or during the initial release, focusing on deciding what to build, how it should work, and delivering it. They aren’t primarily about post-release updates, which is why the maintenance phase is the best fit for handling ongoing changes after launch.