Software reviews and inspections in Software Engineering - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the main purpose of a software review.

Software Engineering

The main purpose of a software review is to [1] defects early in the development process.

Drag options to blanks, or click blank then click option'

Aintroduce

Bdelay

Cdetect

Dignore

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'introduce' because it sounds like adding something new.

Choosing 'ignore' because defects are not helpful.

The main goal of software reviews is to detect defects early, so they can be fixed before causing bigger problems.

2fill in blank

medium

Complete the code to name a common type of software inspection.

Software Engineering

One common type of software inspection is called a [1] review.

Drag options to blanks, or click blank then click option'

Acode

Bdesign

Cperformance

Dsecurity

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'performance' because it sounds important but is not a review type.

Choosing 'security' which is a concern but not the common review name.

A code review is a common inspection where developers check each other's code for errors and improvements.

3fill in blank

hard

Fix the error in the statement about software inspections.

Software Engineering

Software inspections are informal meetings where developers casually discuss their code. This is [1].

Drag options to blanks, or click blank then click option'

Asometimes

Btrue

Coptional

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking inspections are casual discussions.

Confusing inspections with informal peer chats.

This statement is false because software inspections are formal, structured meetings with specific roles and goals.

4fill in blank

hard

Fill both blanks to complete the description of a review step.

Software Engineering

During a software review, the [1] examines the work product while the [2] records defects found.

Drag options to blanks, or click blank then click option'

Areviewer

Bauthor

Cscribe

Dtester

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing the author with the reviewer.

Thinking the tester records defects during the review.

The reviewer looks at the work product to find issues, and the scribe writes down the defects and notes during the review.

5fill in blank

hard

Fill all three blanks to complete the process of a formal inspection.

Software Engineering

The formal inspection process includes [1], [2] meeting, and [3].

Drag options to blanks, or click blank then click option'

Aplanning

Bexecution

Cdefect

Dlogging

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'defect' as a stage instead of an action.

Mixing up the order of steps.

The formal inspection process starts with planning, then the execution meeting where defects are found, and finally logging the defects for correction.