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 ?
Correct answer: B. Poor requirements management
- A. Poor change management
- B. Poor requirements management
- C. Poor quality control
- D. All of the mentioned
Explanation
Poor requirements management allows unclear, incomplete, conflicting, or changing requirements to propagate through the project, causing cancellation or missing features. Change management and quality control also matter, but the cited pattern is most directly associated with requirements-management failure.
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.
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.
More Requirements Engineering questions
Requirements Management has a high initial start-up cost but does not need ongoing funding throughout a project ?
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________________________?
Which of the following is not a Requirement Management workbench tool ?
How many steps are involved in Feature Oriented Domain Analysis (FODA) ?
How is CORE different from IBIS ?
What is the major drawback of CORE ?