# Requirements Engineering

> “Requirements are the wants and needs of stakeholders clearly defined with acceptance criteria” — Association for Project Management (APM)

Requirements engineering is the framework for working through the whole requirements process, and it’s made up of five distinct phases/stages:

1. **Elicitation**: Sourcing the wants and needs of users and stakeholders.
2. **Analysis**: Ensuring your requirements are comprehensive, viable, prioritised and consistent.
3. **Documentation**: Recording your requirements in a neat, ordered package ready to communicate.
4. **Validation**: Ensuring the requirements are actually what users and stakeholders want/need, and accurately represent the solution you’re building.
5. **Management**: Maintaining and controlling the requirements, especially any changes.

#### Further Reading

{% embed url="<https://medium.com/design-bootcamp/a-guide-to-requirements-engineering-572193bd2739>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.designreference.xyz/ux-methods/discovery/requirements-engineering.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.