Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 3: Static Techniques - Coggle Diagram
Chapter 3: Static Techniques
3.2 Review process
3.2.1 PHASES OF A FORMAL REVIEW
Planning
The moderator always performs an entry check and defines at this stage formal exit criteria.
Kick-off
To get everybody on the same wavelength regarding the document under review and to commit to the time that will be spent on checking.
Preparation
All issues are recorded, preferably using a logging form.
Review meeting
The meeting typically consists of the following elements (partly depending on the review type): logging phase, discussion phase and decision phase
Rework
Based on the defects detected, the author will improve the document under review step by step.
Follow-up.
The moderator is responsible for ensuring that satisfactory actions have been taken on all (logged) defects, process improvement suggestions and change requests.
3.2.2 ROLES AND RESPONSIBILITIES
Within a review team, four types of participants can be distinguished: moderator, author, scribe and reviewer.
-The moderator
-The author
-The scribe
-The reviewers
-The manager
3.2.3 Types of review
Walkthrough
-To present the document
-To explain
-To establish a common understanding of the document
-To examine and discuss the validity of proposed solutions and the viability of alternatives, establishing consensus.
Technical review
Assess the value of technical concepts and alternatives in the product and project environment.
Establish consistency in the use and representation of technical concepts.
Ensure, at an early stage, that technical concepts are used correctly;
Inform participants of the technical content of the document.
Inspection
Train new employees in the organization's development process;
Create a common understanding by exchanging information among the inspection participants;
Improve product quality, by producing documents with a higher level of quality;
Remove defects efficiently, as early as possible;
Help the author to improve the quality of the document under inspection;
3.2.4 Success factors for reviews
Find a 'champion'
Pick things that really count
Explicitly plan and track review activities
Train participants
MANAGE PEOPLE ISSUES
FOLLOW THE RULES BUT KEEP IT SIMPLE
CONTINUOUSLY IMPROVE PROCESS AND TOOLS
REPORT RESULTS
JUST DO IT
3.1 Reviews and the test process
Dynamic testing
Executed using a set of input values and its output is then examined and compared to what is expected.
Static testing
Software work products are examined manually, or with a set of tools, but not executed.
3.3 Static analysis by tools
3.3.1 Coding standards
Checking for adherence to coding standards is certainly the most well-known of all features.
The first action to be taken is to define or adopt a coding standard.
3.3.3 Code structure
There are several aspects of code structure to consider:
-Control flow structure
-Data flow structure
-Data structure
3.3.2 Code metrics
When performing static code analysis, usually information is
+calculated about structural attributes of the code
+such as comment frequency, depth of nesting
+cyclomatic number and number of lines of code