Peer Code Review: Difference between revisions

From Federal Burro of Information
Jump to navigationJump to search
No edit summary
Line 3: Line 3:
;formal inspection
;formal inspection
: author
: author
; reveiwer (who ndoes the explained based on the review, no author input till meeting)
: reveiwer (who ndoes the explained based on the review, no author input till meeting)
; observer
: observer
* over-the-shoulder
 
* pair prog
; over-the-shoulder
* tool assisted: file gathering, combined display: diff comments defects, automated metric collection, review enforcement,
: one walks through the code while the other watches.
* email pass around
 
; pair programming
: like in XP/agile
 
; tool assisted
: file gathering
: combined display: diff comments defects
: automated metric collection
: review enforcement,
 
; email pass-around


== Code Errors ==
== Code Errors ==
Line 14: Line 24:
;severity
;severity
: major, minor
: major, minor
;type
;type
: algorithm, documentation, data-usage, error-handling, input, output
: algorithm, documentation, data-usage, error-handling, input, output
; phase-injection
; phase-injection
: developer error, design oversight, requirements mistake, QA error
: developer error, design oversight, requirements mistake, QA error


== biblio ==
== Bibliography ==


best kept xsecrets of peer code review
* Best Kept Secrets of Peer Code Review - Jason Cohen 2006
* code inspection - michael fagan ibm 1974 (29pgs)
* Code Inspection - Michael Fagan IBM 1974 (29 pages)


[[Category:Computers]]
[[Category:Computers]]

Revision as of 20:53, 17 November 2010

Types of code reveiw

formal inspection
author
reveiwer (who ndoes the explained based on the review, no author input till meeting)
observer
over-the-shoulder
one walks through the code while the other watches.
pair programming
like in XP/agile
tool assisted
file gathering
combined display: diff comments defects
automated metric collection
review enforcement,
email pass-around

Code Errors

severity
major, minor
type
algorithm, documentation, data-usage, error-handling, input, output
phase-injection
developer error, design oversight, requirements mistake, QA error

Bibliography

  • Best Kept Secrets of Peer Code Review - Jason Cohen 2006
  • Code Inspection - Michael Fagan IBM 1974 (29 pages)