nerdexam
BCS-ISEB

ISEB-SWTINT1 · Question #66

Scenario 5 A rail services provider is upgrading its signalling systems, to allow train drivers and signallers to communicate securely and timely. This is seen as a safety critical system. The IT…

The correct answer is A. Walkthroughs of specifications would enable the individuals to learn more about the system being. Option A is correct because walkthroughs are specifically designed for knowledge sharing and learning - the author walks participants through the work product. Given that the rail provider has lost most of its development and test staff, walkthroughs of specifications would be…

Reviews

Question

Scenario 5 A rail services provider is upgrading its signalling systems, to allow train drivers and signallers to communicate securely and timely. This is seen as a safety critical system. The IT processes in place include many quality check points, including the use of the V-model for software development. The provider has recently lost many of its software development and test staff to other organisations. The management staff have been retained, including the project and development manager for this upgrade. A recruitment drive is underway. You have been brought in as a new test manager, and you have been asked to review the processes surrounding development and testing. Which of the following best describes the difference between the use of walkthroughs and inspections in this scenario?

Options

  • AWalkthroughs of specifications would enable the individuals to learn more about the system being
  • BWalkthroughs of signalling rules will be more cost effective than inspections.
  • CInspections of code should be carried out by the developers, whilst code walkthroughs should
  • DA walkthrough is an example of a static testing technique, whilst an inspection is an example of a

How the community answered

(46 responses)
  • A
    72% (33)
  • B
    17% (8)
  • C
    9% (4)
  • D
    2% (1)

Explanation

Option A is correct because walkthroughs are specifically designed for knowledge sharing and learning - the author walks participants through the work product. Given that the rail provider has lost most of its development and test staff, walkthroughs of specifications would be invaluable for onboarding new recruits, helping them understand the safety-critical signalling system quickly and efficiently.

Option B is wrong because cost-effectiveness is not the defining difference between walkthroughs and inspections; inspections, though more expensive, often find more defects per hour due to their structured rigor, making the comparison context-dependent rather than absolute.

Option C is wrong because it inverts reality: in a walkthrough, it is the author (developer) who leads the session, while inspections are led by a trained moderator, not the author - so developers should not be the sole conductors of inspections.

Option D is wrong because both walkthroughs and inspections are static testing techniques (they review work products without executing code); the distinction between them is not static vs. dynamic but rather informal/educational vs. formal/defect-focused.

Memory tip: Think of a WALKthrough as a guided tour where the author walks newcomers through the material to build understanding. An INSPECTION is like a formal audit - structured roles, checklists, and a trained moderator hunting for defects. When staff turnover is high, you walk new people in before you inspect.

Topics

#walkthroughs#inspections#static testing#reviews

Community Discussion

No community discussion yet for this question.

Full ISEB-SWTINT1 Practice