inspection team | can inspect about 200 lines of code per hour (including comments), or ten pages of text per hour | |
consists of software engineers with the following roles:- the author
- a moderator who calls and runs the meeting and makes sure that the general principles of inspecting are adhered to
- a secretary who records the defects when they are found
- paraphrasers who step through the document explaining it in their own words
| |
does not normally include manager so that participants can express their criticisms more openly, not fearing repercussions from the manager | |
has only goal finding defects | |
includes experienced software engineers, who are more likely to uncover defects | |
is a subtopic of 10.10 - Inspections | |
is a kind of team | |
may include a manager if there are not enough people to perform inspections in a small organization | |
performs inspecting | |
should avoid discussing how to fix defects because this is a design issue that can be left to the author | |
should avoid discussing style issues | |
should avoid getting tired | |
should be effective and efficient | |
should consist of between two and five people (including the author) | |
should ensure that all the defects in the log are resolved | |
should feel that they are all working together to create a better document | |
should inspect all aspects of code should be considered, including the comments | |
should inspect code, design documents, test plans and requirements | |
should inspect the most important documents of all types, not necessarily every single piece of code or every document | |
should keep logs of inspections | |
should not inspect documents that are not ready | |
should not rush | |
should not work for more than two hours at a time, or for more than four hours a day | |
should prepare for inspections by studying the code or other documents prior to the meeting and coming prepared with a list of defects | |
should re-inspect documents or code that is changed more than 20% for any reason | |