BA - Intesa - Quizz 4

What is the purpose of requirements elicitation?

• Code system behavior
• Verify software modules
• Discover and understand stakeholder needs
• Write user manuals

According to IEEE 29148, what is the goal of requirements validation?

• Confirm that requirements are well written
• Confirm the right system is being built
• Confirm all code compiles
• Confirm system test coverage

What does requirements verification confirm?

• The system runs correctly
• Requirements are well-formed
• Project delivery date
• Stakeholder happiness

Which of the following is part of requirements management?

• Debugging errors
• Coding UI features
• Documenting and tracing requirements
• Building prototypes

What typically initiates the requirements process?

• Requirement validation
• Stakeholder interviews
• Identification of business needs
• Sprint planning

What is one goal of the requirements analysis phase?

• Write code from requirements
• Discover UI layouts
• Define how the system interacts with its environment
• Build hardware models

What’s a key activity during requirements specification?

• Designing system UI
• Describing system behavior to solve a problem
• Writing user stories
• Unit testing

Which is NOT a requirements elicitation technique?

• Brainstorming
• Interviews
• Prototyping
• Source code refactoring

What is the main goal of requirements modeling?

• Code reuse
• Market positioning
• Structure and analyze requirements
• Determine deployment tools

What should requirements validation include?

• Checking font styles
• Unit testing
• Fagan inspection
• Version control