Object Oriented Software Engineering   View all facts   Glossary   Help
subject > person or group > team > inspection team
Next teamsoftware development team    Upteam

inspection team
subjectfact 
inspection teamcan inspect about 200 lines of code per hour (including comments), or ten pages of text per hour2001-08-30 14:55:58.0
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
2001-08-30 14:55:58.0
does not normally include manager so that participants can express their criticisms more openly, not fearing repercussions from the manager2001-08-30 14:55:58.0
has only goal finding defects2001-08-30 14:55:58.0
includes experienced software engineers, who are more likely to uncover defects2001-08-30 14:55:58.0
is a subtopic of 10.10 - Inspections2001-08-30 14:55:59.0
is a kind of team2001-08-30 14:55:59.0
may include a manager if there are not enough people to perform inspections in a small organization2001-08-30 14:55:59.0
performs inspecting2001-08-30 14:55:59.0
should avoid discussing how to fix defects because this is a design issue that can be left to the author2001-08-30 14:55:59.0
should avoid discussing style issues2001-08-30 14:55:59.0
should avoid getting tired2001-08-30 14:55:59.0
should be effective and efficient2001-08-30 14:55:59.0
should consist of between two and five people (including the author)2001-08-30 14:55:59.0
should ensure that all the defects in the log are resolved2001-08-30 14:55:59.0
should feel that they are all working together to create a better document2001-08-30 14:55:59.0
should inspect all aspects of code should be considered, including the comments2001-08-30 14:55:59.0
should inspect code, design documents, test plans and requirements2001-08-30 14:55:59.0
should inspect the most important documents of all types, not necessarily every single piece of code or every document2001-08-30 14:55:59.0
should keep logs of inspections2001-08-30 14:55:59.0
should not inspect documents that are not ready2001-08-30 14:55:59.0
should not rush2001-08-30 14:55:59.0
should not work for more than two hours at a time, or for more than four hours a day2001-08-30 14:55:59.0
should prepare for inspections by studying the code or other documents prior to the meeting and coming prepared with a list of defects2001-08-30 14:55:59.0
should re-inspect documents or code that is changed more than 20% for any reason2001-08-30 14:55:59.0

Next teamsoftware development team    Upteam