Practitioner Certificate in Requirements Engineering

0/2 checked

Q_01 domain/d1 · medium single discuss →

During the early stages of a project, a business analyst runs a workshop to compile business requirements. According to good practice, what is the recommended sequence of activities for turning stakeholder wishes into a usable requirements list?

A Brainstorm openly what stakeholders would want if they could have anything, then get them to be clear, ask the 'stupid' questions, and negotiate
B Establish a formal change control procedure first, then elicit only the requirements that can pass through it
C Draft the technical solution design, then confirm which requirements it already satisfies
D Publish a service catalog of available options, then let stakeholders select from it

Q_02 domain/d1 · medium single discuss →

A stakeholder complains after go-live that the delivered system does not match their expectations, even though they were given several chances to review the requirements document during the project. In a waterfall project, what is the appropriate route for them to now introduce new requirements?

A They must use the formal change control procedure to make alterations or add requirements to the project scope
B They can rely on the iterative development cycle to pick up and adapt to the new requirements automatically
C They should raise the changes informally with the build team, who will incorporate them without process
D They must wait until user testing to have their new requirements added to the test scripts

Practitioner Certificate in Requirements Engineering

Explanation

Explanation