MBT in Sequential and Iterative Software Development Lifecycles CT-MBT Practice Questions (Page 5)

Questions 21–25

1. 21foundation · easy

   In a sequential SDLC, how does MBT integrate with development activities?

   • AMBT is not integrated with development activities
   • BMBT is integrated only during maintenance
   • CMBT is integrated as a distinct phase, with models from requirements and design feeding test generation
   • DMBT is integrated continuously with coding in each iteration
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A company is adopting MBT for a project with strict regulatory requirements. They are choosing between a sequential and an iterative SDLC. Which factor most strongly favors a sequential SDLC for MBT adoption?

   • AThe need for extensive documentation and traceability from requirements to tests.
   • BThe need to deliver a minimal viable product quickly.
   • CThe desire to incorporate user feedback quickly into the product.
   • DThe need to reduce the cost of test maintenance over time.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   What is a key difference in planning between MBT in sequential and iterative lifecycles?

   • ABoth plan MBT identically
   • BPlanning is not relevant to MBT
   • CSequential plans MBT per iteration; iterative plans it once
   • DSequential plans MBT as a one-time activity; iterative plans it per iteration
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   What role does continuous refinement play in MBT within an iterative SDLC?

   • AModels are frozen after the first iteration
   • BRefinement is not needed in iterative MBT
   • CModels are updated each iteration to reflect new requirements and feedback
   • DRefinement only occurs at the end of the project
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   An agile team is using MBT and has a model that is updated each sprint. They notice that the model is becoming too complex and difficult to maintain. What is the best strategy to address this?

   • ARefactor the model into smaller, focused sub-models for different features or components.
   • BIncrease the model's abstraction level to hide details, even if it reduces test coverage.
   • CUse a single, large model to capture all behaviors, even if it is complex.
   • DStop updating the model and rely on manual testing.
   Reveal Solution Discussion Select an answer first