Discuss ISQI IREB_CPRE_FL Exam Topic 4 Question 31

You are employed as a requirements engineer in a company that develops control software for electric motors. During your work it becomes increasingly evident that the developers are very well aware of the necessary requirements, even though the requirements are not documented in their entirety. Nevertheless, you decide to document requirements systematically. Which two of the following arguments justifies this step? (2 Points)

Documenting requirements systematically is important, because...

A... implementation without documented requirements is not possible.

B... non-documented requirements are difficult to negotiate between the stakeholders.

C... the coverage of the requirements by means of test cases cannot be checked.

D... documented requirements are also good requirements.

Suggested Answer: C, D

Get Premium IREB_CPRE_FL Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

11 comments · newest first

Keshia 11 months ago

Totally agree with B. Clear communication is key in any project!

Adolph 12 months ago

Wait, are we really saying D is true? Just because it's documented doesn't mean it's good!

Nada 12 months ago

C makes a lot of sense too. Testing needs clear requirements!

Raylene 12 months ago

I disagree, A seems more critical. Without docs, how can you even start?

Gaynell 1 year ago

B is spot on! Non-documented requirements can lead to chaos.

Jennie 1 year ago

I’m a bit confused about option A; I thought implementation could happen without documentation, but maybe it’s riskier that way?

Catherin 1 year ago

I practiced a similar question where we talked about the importance of documentation, and I feel like option D could be a valid choice.

Nan 1 year ago

I'm not entirely sure, but I think option C might be relevant too since testing relies on clear requirements.

Eric 1 year ago

I remember discussing how undocumented requirements can lead to misunderstandings among stakeholders, so I think option B makes sense.

Hubert 1 year ago

A dashboard seems like the obvious choice here to provide a high-level overview for the project sponsor and stakeholders.

Amber 1 year ago

I think this question is asking about the definition of a P3O, which is a Project, Programme and Portfolio Office. I'm pretty confident that the correct answer is C, as a P3O is supposed to provide integration with governance arrangements and other corporate support functions.

iSQI IREB_CPRE_FL Exam - Topic 4 Question 31 Discussion