Software reviews and inspections in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a software review?

A software review is a process where team members examine software products like code or documents to find mistakes and improve quality before final release.

intermediate

What is the main difference between a software review and an inspection?

A software review is usually informal and focuses on discussion, while an inspection is a formal, structured process with defined roles and checklists to find defects.

beginner

Name two common roles in a software inspection.

Two common roles are the Moderator, who leads the inspection, and the Inspector, who examines the software product for defects.

beginner

Why are software inspections important?

Inspections help find defects early, reduce costs of fixing bugs later, improve software quality, and increase team knowledge.

beginner

What is a checklist in the context of software inspections?

A checklist is a list of common errors or points to check during an inspection to help inspectors systematically find defects.

Which of the following best describes a software inspection?

A User feedback collection after release

B An informal team discussion about software

C Automated testing of software code

D A formal process with defined roles to find defects

Software inspection is a formal process with specific roles and steps to identify defects early.

What is the primary goal of software reviews?

A To find and fix defects early

B To write new code

C To deploy software to users

D To design new features

Software reviews aim to find defects early to improve quality and reduce later costs.

Who typically leads a software inspection?

A Developer

B Moderator

C Tester

D Project Manager

The Moderator leads the inspection process, organizing and guiding the team.

Which tool helps inspectors systematically find defects?

A Compiler

B Debugger

C Checklist

D Version control

A checklist lists common errors to look for during inspections.

Software reviews are usually:

A Informal and discussion-based

B Automated and code-only

C Formal with strict roles

D Done after software release

Software reviews are often informal meetings to discuss and improve software.

Explain the difference between software reviews and software inspections.

Think about how structured the process is and the roles involved.

Describe why software inspections are valuable in software development.

Consider the benefits of catching problems before release.

Practice

1. What is the main purpose of software reviews and inspections?

easy

A. To find and fix errors early in the software development process

B. To write new code faster

C. To increase the number of features in software

D. To delay the release of software

Solution

1. Step 1: Understand the goal of reviews and inspections

   They are used to detect errors early before software moves to later stages.

2. Step 2: Compare options with this goal

   Only To find and fix errors early in the software development process matches the goal of early error detection and fixing.

3. Final Answer:

   To find and fix errors early in the software development process -> Option A

4. Quick Check:

   Early error detection = To find and fix errors early [OK]

Hint: Focus on early error detection as the key goal [OK]

Common Mistakes:

• Confusing reviews with coding speed
• Thinking inspections add features
• Believing reviews delay release

2. Which of the following best describes a software inspection?

easy

A. Writing automated tests for software

B. An informal meeting to discuss code improvements

C. A formal, structured process to find defects in software artifacts

D. Deploying software to production

Solution

1. Step 1: Define software inspection

   It is a formal and structured review process focused on finding defects.

2. Step 2: Match options to this definition

   Only A formal, structured process to find defects in software artifacts describes a formal, structured defect-finding process.

3. Final Answer:

   A formal, structured process to find defects in software artifacts -> Option C

4. Quick Check:

   Inspection = Formal defect finding [OK]

Hint: Remember inspections are formal, unlike informal reviews [OK]

Common Mistakes:

• Confusing inspections with informal meetings
• Thinking inspections are about testing
• Mixing deployment with inspections

3. During a software review, the team finds 5 errors in the design document and 3 errors in the code. What is the total number of errors found?

medium

A. 3

B. 8

C. 5

D. 15

Solution

1. Step 1: Identify errors found in design and code

   Design errors = 5, Code errors = 3.

2. Step 2: Add errors to find total

   Total errors = 5 + 3 = 8.

3. Final Answer:

   8 -> Option B

4. Quick Check:

   5 + 3 = 8 [OK]

Hint: Add all errors found in different artifacts [OK]

Common Mistakes:

• Counting only one type of error
• Multiplying errors instead of adding
• Ignoring errors in design or code

4. A team performs a software inspection but forgets to document the defects found. What is the main problem caused by this mistake?

medium

A. The team will write more code

B. The software will automatically fix defects

C. The inspection becomes informal

D. Defects may not be fixed because they are not recorded

Solution

1. Step 1: Understand the role of defect documentation

   Documenting defects ensures they are tracked and fixed later.

2. Step 2: Analyze consequence of missing documentation

   If defects are not recorded, they may be forgotten and remain unfixed.

3. Final Answer:

   Defects may not be fixed because they are not recorded -> Option D

4. Quick Check:

   Missing defect records = defects unfixed [OK]

Hint: Always document defects to ensure fixes [OK]

Common Mistakes:

• Assuming software fixes defects automatically
• Confusing inspection formality with documentation
• Thinking more code solves inspection issues

5. A software team wants to reduce costs and improve quality by catching errors early. Which approach should they prioritize?

hard

A. Conducting formal inspections and informal reviews regularly

B. Skipping reviews to speed up coding

C. Only testing after software is complete

D. Adding more features before fixing bugs

Solution

1. Step 1: Identify approaches that catch errors early

   Formal inspections and informal reviews help find errors early.

2. Step 2: Evaluate options for cost and quality impact

   Conducting formal inspections and informal reviews regularly supports early error detection, reducing costs and improving quality.

3. Step 3: Check other options

   Options B, C, and D delay error detection, increasing costs and reducing quality.

4. Final Answer:

   Conducting formal inspections and informal reviews regularly -> Option A

5. Quick Check:

   Early reviews = lower cost and better quality [OK]

Hint: Prioritize early reviews and inspections to save cost [OK]

Common Mistakes:

• Choosing to skip reviews
• Relying only on late testing
• Adding features before fixing bugs