cau hoi req

QI) Requirements development is:

• A) A process of ana yzing requirements.

• A) A method of obtaining requirements;

• A) A technique of gathering what the customer needs;

• A) All of the above.

Q2) Requirements validation is:

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

• A) A method for testing requirements by software tools;

• A) The process of testing requirements before coding.

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

Q3) Which of the following is the requirements development sequence?

• A) Elicitation, Validation, Specification and Analysis;

• A) Specification, Elicitation, Validation and Analysis;

• A) Elicitation, Analysis, Specification and Validation;

• A) Validation, Specification, Analysis and Elicitation;

Q4) Requirement development process is:

• A) Sequential process.

• A) Iterative process( Quá trình 14p di läp hi)

• A) Skipping process;

• A) None of the above.

Q5) Before design, requirements must be:

• A) Analyzed•

• A) Prioritized:( ðê tru tiên)

• A) Documented

• A) All of the above,

Q6) the list of what stakeholders' need is called::

• A) Customer list;

• A) User's requests;

• A) Requirements documents

• A) Project lists;

Q7) Most software requirements are written by:

• A) Customers;

• A) Software engineers;

• A) Managers;

• A) All of the above

Q8) Defective requirements can cause:

• A) Project failure;

• A) Expensive rework

• A) Late delivery

• A) All of the above,

Q9) During requirements phase, Most customers are:

• A) Knowledgeable about requirements process;

• A) Understand Software Engineering;

• A) Confuse between "Needs" and "Wants";

• A) Familiar with software process

QIO ) During requirements phase, Software Engineer needs to:

• A) Ask for solutions;

• A) Collect all data to prepare for testing;

• A) Ask for outcomes;

• A) Gather all customer's wishes