What is necessary for systematic control of software changes?

The correct choice is configuration management, as it plays a crucial role in systematically controlling software changes throughout the development lifecycle. Configuration management encompasses processes and tools that allow teams to efficiently manage, track, and control changes to software products. This includes keeping detailed documentation of the various versions of software components, ensuring that changes are made systematically rather than haphazardly, and maintaining records of what changes have been made and who made them.

With effective configuration management, teams can avoid inconsistencies and issues that may arise during software development, such as conflicts that occur when multiple changes are made by different developers simultaneously. It ensures that all changes are communicated and authorized, and it provides a framework for rolling back changes if necessary, thereby helping maintain software integrity and quality.

In other contexts, while versioning, technical support, and end-user feedback are all important facets of software development and maintenance, they do not specifically address the systematic approach needed for controlling changes to software. Versioning is part of what configuration management entails, but it alone does not cover the comprehensive process needed. Technical support is more focused on assisting users and resolving issues rather than managing changes. End-user feedback is invaluable for improving software but is not directly related to the systematic control of changes.