If your question is to differentiate between Requirement Review and Requirement Analysis then, as a result of review of requirement, decision is taken to go ahead with these requirements or not. This is normally done by the Leads (both development and QA) or BAs.
As a result of requirement analysis, which should be done by developers and QA analysts to understand the reviewed requirements and come up with POC, understanding document, test strategy for the product to be developed and tested.
To explain this, let me get your attention to the requirement process.Initially the BSG team (Business Analysts) conducts meeting, workshops, interviews, etc with customer to collect requirements. Now these gathered requirements might be conflicting to each other in an application due to architectural / implementation constraints. An analysis of these scope items is described as Requirement Analysis. After Analysis you creates the solution document, which describes the requirement in detail. Review of this document is called Requirement Review ( review can be a group review internal to the project or a review with customer to finalize on the requirements)