bài ôn

Requirements development is:

• A) A process of analyzing requirements.

• B) A method of obtaining requirements.

• C) A technique of gathering what the customer needs.

• D) All of the above.

Requirements validation is:

• A) A technique to find requirements errors after design.

• B) A method for testing requirements by software tools.

• C) The process of testing requirements before coding.

• D) A process to ensure requirements meet customer's needs.

Which of the following is the requirements development sequence?

• A) Elicitation, Validation, Specification and Analysis.

• B) Specification, Elicitation, Validation and Analysis.

• C) Elicitation, Analysis, Specification and Validation.

• D) Validation, Specification, Analysis and Elicitation.

Requirement development process is:

• A) Sequential process.

• B) Iterative process.

• C) Skipping process.

• D) None of the above.

Before design, requirements must be:

• A) Analyzed

• B) Prioritized

• C) Documented

• D) All of the above.

The list of what stakeholders' need is called:

• A) Customer list

• B) User's requests

• C) Requirements documents

• D) Project lists

Most software requirements are written by:

• A) Customers

• B) Software engineers

• C) Managers

• D) All of the above.

Defective requirements can cause:

• A) Project failure

• B) Expensive rework

• C) Late delivery

• D) All of the above.

During requirements phase, most customers are:

• A) Knowledgeable about requirements process.

• B) Understand Software Engineering.

• C) Confuse between "Needs" and "Wants".

• D) Familiar with software process.

) During requirements phase, Software Engineer needs to:

• A) Ask for solutions

• B) Collect all data to prepare for testing

• C) Ask for outcomes

• D) Gather all customer's wishes