Peer Code Review: Difference between revisions
From Federal Burro of Information
Jump to navigationJump to search
(New page: == Parametres == ;severity : major, minor ;type : algorithm, documentation, data-usage, error-handling, input, output ; phase-injection : developer error, design oversight, requirements m...) |
No edit summary |
||
| Line 1: | Line 1: | ||
== | == 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 | |||
* pair prog | |||
* tool assisted: file gathering, combined display: diff comments defects, automated metric collection, review enforcement, | |||
* email pass around | |||
== Code Errors == | |||
;severity | ;severity | ||
| Line 8: | Line 19: | ||
: developer error, design oversight, requirements mistake, QA error | : developer error, design oversight, requirements mistake, QA error | ||
== biblio == | |||
best kept xsecrets of peer code review | |||
* code inspection - michael fagan ibm 1974 (29pgs) | |||
[[Category | [[Category:Computers]] | ||
Revision as of 20:50, 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
- pair prog
- 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
biblio
best kept xsecrets of peer code review
- code inspection - michael fagan ibm 1974 (29pgs)
