Requirements Elicitation Quiz

What is a core activity of requirements engineering?

• Deploying the software

• Designing the user interface

• Testing the system

• Eliciting requirements

Who are considered stakeholders in a system?

• Only the project managers

• Only the developers

• Only the testers

• Users and organizations that influence requirements

What type of documents can provide important information for requirements?

• Only legal documents

• Universal and organization-specific documents

• Only user manuals

• Only marketing materials

What can legacy systems provide during requirements elicitation?

• No useful information

• Only financial data

• A chance for stakeholders to try out the system

• Only outdated requirements

What is the consequence of not considering stakeholders?

• Lower project costs

• Undetected requirements leading to change requests

• Increased project speed

• Improved stakeholder satisfaction

What is a technique for identifying relevant stakeholders?

• Random selection

• Maintaining checklists

• Ignoring management suggestions

• Using only surveys

What should be documented about stakeholders?

• Only their past projects

• Only their names

• Their roles and contact data

• Only their opinions

What is the purpose of creativity techniques in requirements elicitation?

• To gather detailed requirements

• To develop innovative requirements

• To document requirements

• To analyze existing systems

What are dissatisfiers in the Kano model?

• Properties that delight users

• Requirements that are not important

• Requirements that are optional

• Self-evident properties that must be fulfilled

What is the main goal of survey techniques?

• To create prototypes

• To elicit precise and unbiased statements

• To gather vague ideas

• To analyze existing documents