TestUstad

Which of the following is not a Requirement Management workbench tool ?

Correct answer: C. Rational Suite

  • A. RTM
  • B. DOORS
  • C. Rational Suite
  • D. RDD 100

Explanation

RTM usually means Requirements Traceability Matrix, a document or tracking artifact rather than a requirements-management workbench tool. DOORS, RDD-100, and Rational Suite are recognized software tools or suites used to support requirements work.

Written and checked by , MS Computer ScienceLast updated
Report an error

The more specific you are, the faster it gets fixed. A source beats an opinion.

Prefer email? [email protected]

Practise Requirements Engineering

125 free Requirements Engineering MCQs from Software Engineering, each with the correct answer and an explanation. Unlimited attempts, no account needed.

Start a free Requirements Engineering testAll Requirements Engineering MCQs

Discussion

Stuck on an option, or know a faster way to get there? Ask or explain it here.

No comments yet. Be the first to explain this one.

Exams that ask Software Engineering questions like this

Software Engineering is on this paper prepared for on TestUstad, and all of them draw the same bank, so this question is worth knowing for it.

Government Software Engineer Test Software Engineering60 MCQs

More Requirements Engineering questions

Requirements traceability is one of the most important part requirement management. It may also be referred to as the heart of requirement management?

Why is Requirements Management Important ? It is due to the changes___________________?

Which two requirements are given priority during Requirement Management of a product ?

What functionality of Requirement Management Tool (RMT) is depicted by the statement: "the tool should be able to automatically detect relations between artifacts. For example information retrieval techniques, monitoring of change history, naming schemas or model transformations________________________?

Requirements Management has a high initial start-up cost but does not need ongoing funding throughout a project ?

According to a statistical report: "over 30% of all software projects are cancelled before completion and over 70% of the remainder fail to deliver expected features". What must be the reason for such a situation ?