Please enable JavaScript.
Coggle requires JavaScript to display documents.
Capítulo 8: Design and Code Reviews - Coggle Diagram
Capítulo 8: Design and Code Reviews
Reviews
Most important
step to improve
METHODS
Walk-throughs
Like a presentation
(developer and audience)
Inspections
structured procedure for the team
to review a software product
Personal reviews
You examine your own products
WHY
Programmers think re-writting a program
will end up with a high-quality program
Eficency
Debugging-
time to find a defect
Review vs inmediately
compile the program
PRINCIPLES
Follow a defined
review process
Entry criteria, set of tasks, exit criteria
Checklist
: Script for use in the
review process [ example pg242 ]
Measure and improve
your review process
improve the quality
of yor review
Establish defined
review goals
find anf fill all defects before
the first compile or test
MEASURES
Review time in minutes
Number of defects found
Size of the program
LOCS or
PAGES of DESIGN
Number of defects in the program
that were later found (
escapes
)
Design Reviews
Produce designs that
can be reviewed
Completeness, representation
notations, standards
Review the
design in
stages
Follow an explicit
design review strategy
Plan the order of your
design review
Verify the logic implements
the requirements
Review Yield
Percentage of defects in
design or code at the time of
the review that were
found by that review
Yield
= (100*Defects removed before compile)/(defects injected before compile)
Deffect Removal Leverage
Ratio of the defects removed per hour in any two phases
Provides a useful measure of
the relative effectiveness of various defect removal methods
Checklist
Forma para que no olvides ningun item durante las revisiones
Review vs Inspeccion = single vs team
Aproximadamente el 10% de los errores no son captados por el compilador