Software Engineering Requirements Engineering 2

Question 1

Which requirements elicitation method involves creating a working model of the system to gather user feedback?

Accepted Answer

Prototyping

Answer

Prototyping creates a preliminary working version of the system to help users visualize, evaluate, and refine their requirements.

Question 2

In a requirements document, what is the distinction between 'shall' and 'should'?

Accepted Answer

'Shall' indicates a mandatory requirement while 'should' indicates a desirable but optional one

Answer

In requirements documentation, 'shall' denotes a mandatory requirement while 'should' denotes something desirable but not strictly required.

Question 3

What is a 'stakeholder' in the context of requirements engineering?

Accepted Answer

Any person or organization with an interest in or affected by the system

Answer

A stakeholder is any person, group, or organization that has an interest in the system or is affected by its development, deployment, or operation.

Question 4

The MoSCoW method is used in requirements engineering to:

Accepted Answer

Prioritize requirements into Must have, Should have, Could have, and Won't have

Answer

MoSCoW is a prioritization technique that categorizes requirements into Must have, Should have, Could have, and Won't have (this time).

Question 5

What is 'requirements volatility'?

Accepted Answer

The tendency of requirements to change during the project lifecycle

Answer

Requirements volatility refers to how frequently requirements change during the project, which significantly impacts planning, design, and budget decisions.

Software Engineering Practice Test

Software Engineering Practice Test

Software Engineering Requirements Engineering 2