Requirement

Requirements development is

• A process of analyzing requirements

• method of obtaining requirements

• A technique of gathering what the customer needs.

• All of the above.

Requirements validation is

• A technique to find requirements errors after design

• A method for testing requirements by software tools

• The process of testing requirements before coding

• A process to ensure requirements meet customer's needs

Which of the following is the requirements development sequence?

• Elicitation, Validation, Specification and Analysis

• Specification, Elicitation, Validation and Analysis

• Elicitation, Analysis, Specification and Validation

• Validation, Specification, Analysis and Elicitation

Requirement development process is

• Sequential process

• Iterative process

• Skipping process

• None of the above

Before design, requirements must be

• Analyzed

• Prioritized

• Documented

• All of the above

The list of what stakeholders' need is called

• Customer list

• User's requests

• Requirements documents

• Project lists

Most software requirements are written by

• Customers

• Software engineers

• Managers

• All of the above

Defective requirements can cause

• Project failure

• Expensive rework

• Late delivery

• All of the above

During requirements phase, Most customers are

• Knowledgeable about requirements process

• Understand Software Engineering

• Confuse between "Needs" and "Wants"

• Familiar with software process

During requirements phase, Software Engineer needs to

• Ask for solutions

• Collect all data to prepare for testing

• Ask for outcomes

• Gather all customer's wishes