Linking Requirements and Process Related Information to the MBT Model CT-MBT Practice Questions (Page 6)

Questions 26–27

1. 26foundation · easy

   Which of the following is an example of documenting a linkage decision?

   • ARecording that requirement REQ-42 was mapped to state 'Approved' because it describes the approval workflow
   • BReviewing the model for syntax errors
   • CExecuting test cases derived from the model
   • DDeleting the model after test generation
   Reveal Solution Discussion Select an answer first
2. 27application · medium

   A team is building an MBT model for a payment system. Requirement REQ-17 states: 'The system shall validate the card on every transaction.' The team discovers that 'every transaction' is ambiguous because some transactions are recurring subscriptions and some are one-time purchases. They decide to split REQ-17 into two model elements: one for subscription renewals and one for one-time purchases. What is the most important additional action to support future impact analysis?

   • ARecord the split decision and the rationale in the traceability documentation.
   • BCreate a single model element that covers both transaction types without splitting.
   • CAsk the product owner to reword REQ-17 to remove the ambiguity before modeling.
   • DDelete the original REQ-17 from the requirements repository to avoid confusion.
   Reveal Solution Discussion Select an answer first