As part of the development process for a new system, the organization plans to perform requirements analysis and risk assessment. The new system will replace a legacy system, which the organization…

Static code analysis and peer review are development-phase activities applied to application source code, which does not yet exist during the requirements and risk assessment phase.

Validating expectations around performance and security describes a broad outcome of requirements analysis rather than a specific, discrete activity that management performs to gather data during this phase.

During requirements analysis, load testing the current legacy system produces concrete, measurable data on existing response times, which management uses to define and validate stakeholder performance expectations before any new system design begins. For a data analytics workload, throughput and latency benchmarks are critical requirements inputs, and load testing is the specific activity that generates this evidence - making it a core management-driven deliverable in this phase.

Design reviews and user acceptance testing occur after the system has been designed and deployed, placing them in a later phase well beyond initial requirements gathering.

Regression testing for interoperability with the legacy system is a deployment-phase activity performed after the new system is built and integrated, not during initial requirements gathering.