Items tagged with 'SoftwareInspection'

Glossaries

Terms

• Efficiency
• Software Inspection

Definitions

• Defect Detection Technique: "Technique used to improve individual defect detection effectiveness or efficiency. Often also referred to as reading technique or inspection method."
• Efficiency: "Efficiency in general, describes the extent to which time, effort or cost is well used for the intended task or purpose. In the case of software inspections this term relates to the number of de..."
• Software Inspection: "Inspection in software engineering, refers to peer review of any work product by trained individuals who look for defects using a well defined process. The traditional software inspection proce..."
• Team Defect Detection Effectiveness: "Share of defects found by one or more members of an inspection team."
• Individual Defect Detection Effectiveness: "Share of defects found by an inspector."
• Inspector Qualification: "Key criteria for the inspector selection are certainly the knowledge of the inspectors with respect to the inspected artifact and with respect to the inspection process and defect detection techniq..."
• Effectiveness: "Effectiveness is the capability of producing a desired result. When something is deemed effective, it means it has an intended or expected outcome. In the case of software inspections, effective..."
• Defect Overlap: "Share of defects that can be identified by two or more software inspection approaches."
• Inspection Effectiveness: "In context of controlled experiments, share of (true) defects detected and reported during an inspection (0 to 100%)."
• Inspection Efficiency: "The number of (true) defects detected per unit of effort, e.g., person hour (3 defects per person hour). Cost per defect is the inverse construct to inspection efficiency, i.e., the effort to find ..."
• Software Artifact Size: "Size of the software artifact in a unit that allows planning an inspection, e.g., lines of code, number of pages, number of diagrams."
• Inspector Effort: "Duration of the defect detection activity for one inspector, e.g., 3 person hours."
• Inspection Effort: "Invested defect detection effort during the software inspection process. Inspection effort includes a) individual inspection effort and (b) team meeting effort for inspection meetings."
• Individual Efficiency: "In context of controlled experiments, inspection efficiency focuses the number of identified defects per time interval, e.g. defects per hour."
• Team Meeting Effectiveness: "Share of (true) defects detected and reported by an inspection team either after a team meeting or as consolidated outcome of the defect reports from all team members in a nominal team."
• Team Size: "In context of software inspections, team size refers to the number of persons in an inspection team."
• Team Meeting Effort: "Effort from discussion of the individual defect reports in the inspection team. This effort can be 0, if the inspection process does not have a team meeting but uses a nominal (non-communicating) t..."
• Nominal Team: "A nominal team does not communicate/meet, individual inspection results are aggretated on team level."
• Real Team: "A real team can have a team meeting; individual inspection results are aggregaed on team level during discussion."
• Team Mix of Defect Detection Techniques: "Set of Defect Detection Techniques (DDTs) used in the team and number of inspectors using a specific DDT."
• Team Mix of Inspector Capabilities: "Set of inspector capability levels present in a team and number of inspectors per inspector capability level."
• Team Meeting Gain/Loss: "Number of true defects found or lost in comparison to the consolidated defect reports of the individual inspectors without a team meeting."
• Individual Effectiveness: "In context of controlled experiments, share of (true) defects detected and reported by an inspector."
• Inspector Defect Detection Technique (DDT): "The specific Defect Detection Technique (DDT) used by an inspector, e.g., “PBR perspective tester”."
• Cost per defect: "Cost per defect is the inverse construct to inspection efficiency, i.e., the effort to find a defect (e.g., 20 person minutes per defect)."
• Team Meeting Efficency: "Inspection Efficiency focusing on the team defect detection phase."
• Software Artifact Type: "Characteristics of the software artifact under inspection, e.g., requirements/design/code artifact, relevant languages used in the artifact, e.g., UML, ERD, C-code, English language, domain-specifi..."
• Defect Detection Characteristics: "From the true defect reports collected from inspectors and inspection team characteristics of defect detection activities can be calculated, such as the overlap in a group of inspectors (i.e., the ..."
• True Defect Number: "Number of true defects in an inspection object. This number is known in an experiment context but not in practice."
• Defect Set Characteristics: "Characteristics of the (expected) set of defects in a software artifact as basis for inspection planning: team size, mix of defect detection techniques."
• Defect Classes: "Classification of defects that may occur in an inspection object as a basis for designing and testing a defect detection technique."
• Inspector Capability: "Inspector capability level measured for an individual inspector, e.g., experience with the inspection process, the type of software artifact inspected, the language used in the software artifact."
• Defect Severity: "Classification of the risk or extra effort a defect is expected to bring into the project if the defect is not detected during inspection, e.g., minor, major, or critical defect. The rework effort ..."
• Opportunity Costs: "These costs measure an inspector’s benefits if he invests his time into inspection compared to the benefits she/he can create if not inspecting. If opportunity costs of inspection are high, inspect..."
• False Positive: "A defect report by an inspector, which is not rated as a true defect."