Which one of the following is not a step of requirement engineering ?

Answer: Requirement design is not a standard step in requirement engineering.

Reason: Requirement engineering focuses on identifying and managing what the system should do (eliciting, analyzing, documenting, validating, and managing requirements). Designing the system (architecture and detailed design) happens after the requirements are established.

1. Requirement elicitation: gathering requirements from stakeholders through interviews, workshops, observation, and other techniques.

2. Requirement analysis: refining, resolving conflicts, modeling, and prioritizing the gathered requirements.

3. Requirement documentation: writing a clear, consistent, and testable requirements specification that stakeholders agree on.

4. Requirement validation and verification: ensuring requirements meet stakeholder needs and are feasible.

5. Requirement management: handling changes to requirements throughout the project lifecycle.

Note: System or software design activities come after requirements are established; therefore, "Requirement design" is not listed as a standard requirement engineering step.