Static Testing The Static Testing rely on the manual examination and automated analysis (Static Testing) of the code or other project documentation without the execution of the code. Reviews are a way of testing software works products and can be performed well before dynamic test execution. Any software work product can be reviewed, including requirements specifications, design specification, code, test plans, test specifications, test cases, test scripts, user guides. The Static Testing means testing software without executing the code. Their is two types of Review & Static Analysis. This type of Static Testing mostly performed by many IT Companies.
Review Review is a systematic examination of work product of documents. It has main aim to find out & remove the error or defects from the documents. Review process done by using Software Requirement Specification (SRS), Business Requirement Specification (BRS), Use Case, Test Plan Documents, Test Case Documents.
Advantage 
Improve the development productivity & time scale is reduced.

Testing Cost & Time is reduced.
Maintenance cost reduced.
Improve the communication between team member.
Types of Defect Found in Review
Deviation from Standard
Improper Requirements
Improper Design
User interface issue
Activities of Formal Reviews
Planning
kick off
Individual Preparation
Review Meeting
Rework
Follow up
Planning :
Defining the review criteria
Selecting the personnel
Allocating roles
Defining the entry and exit criteria for more formal reviews types
Selecting which parts of documents to review
Checking entry criteria
kick off :
Distributing documents
Explaining the objective, process and documents to the participants
Individual Preparation
Preparing for review meeting
Noting defects, questions and comments
Review Meeting
Discussing or logging with documented results
Noting defects & making decisions
Rework
Fixing defects found
Recoding updated status of defects
Follow up
Checking that defects have been solved
Gathering metrics
Checking exit criteria