Req Documentation & Analysis

What is the purpose of documenting requirements?

• To delay project timelines

• To complicate the development process

• To ensure consistency, communication, and validation

• To confuse stakeholders

What is a characteristic of a good requirement?

• Vague and ambiguous

• Solution-oriented

• Clear and measurable

• Overlapping and duplicated

What does the 'MoSCoW' prioritization technique stand for?

• Main, Secondary, Critical, Worthwhile

• Major, Significant, Critical, Worthless

• Must, Should, Could, Would

• Mandatory, Optional, Conditional, Wasteful

What is the purpose of using the 'shall' keyword in requirements?

• To add ambiguity

• To prioritize requirements

• To avoid implicit prioritization

• To confuse stakeholders

What is the role of actors in a Use Case diagram?

• Represent the system boundary

• Define the system functionality

• Interface with the IT system

• Manage the project timeline

What is the purpose of acceptance criteria in requirements documentation?

• To confuse stakeholders

• To delay project timelines

• To complicate the approval process

• To demonstrate when a requirement is met

How should poorly expressed requirements be improved?

• By adding more ambiguity

• By providing multiple solutions

• By using clear and simple language

• By duplicating requirements

What is the main focus of Use Cases in requirements analysis?

• Technical implementation details

• Business process modeling

• User perspective and needs

• Project management tasks

What is the purpose of structuring requirements using a specific notation?

• To confuse stakeholders

• To prioritize requirements

• To ensure clarity and organization

• To delay project timelines

What is an Option that you should always consider within a Business Case?

• Do everything

• Option 1

• Do Nothing

• Last Option