Which of these is a common prioritisation method for requirements:

Which of these is a common prioritisation method for requirements:

a) Waterfall

b) MoSCow

c) StoCKhoLM


Answer: b

Which of these is a useful fit criterion for usability:

Which of these is a useful fit criterion for usability:

a) Less than 5% of users will complain about the background colour.

b) The system will be easy to use for most people.

c) One month's use of the product shall result in a total error rate of less than 1 percent.


Answer: c

User characteristics describe:

User characteristics describe:

a) How a user should look in the system

b) How the system should characterise the user

c) Expected characteristics of the user group.


Answer: c

Functional Requirements describe:

Functional Requirements describe:

a) What a system should do.

b) How the user can interact with the system.

c) What a developer should do.

Answer: a

Requirements should be:

Requirements should be:

a) Clear, unambiquous, specific and measurable.

b) Short, technically correct, and well written.

c) Creative, inspiring but not detailed.


Answer: a

The measure of whether a requirement has been fulfilled is called:

The measure of whether a requirement has been fulfilled is called:

a) A fit criterion

b) A fulfilment criterion.

c) A fit measurement.


Answer: a

Requirements work best when they consider:

Requirements work best when they consider:

a) What the customer tells the developer they want.

b) The designer's intuition

c) The needs of all stakeholders


Answer: c

Requirements are useful for developers because:

Requirements are useful for developers because:

a) Their manager told them they were.

b) They are very specific and detailed and can be directed developed from.

c) They specify what is needed and how to know if it has been delivered but allow for freedom in how they are implemented.


Answer: c

Why are requirements useful in the development process?

Why are requirements useful in the development process?

a) Reduce costs and time in development, reduce confusion in communication, and provide good testing criteria for the final product.

b) They reduce the creative space for developers, leading to fewer mistakes.

c) They make it possible to learn from mistakes in the development process.


Answer: a

A requirement is:

A requirement is:

a) A statement of something the developer should build.

b) A statement of what a product or systems should do or how it will do it.

c) A mandatory feature that all software must include.


Answer: b