> For the complete documentation index, see [llms.txt](https://aeudoc.gitbook.io/compliance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aeudoc.gitbook.io/compliance/application-development/user-requirements.md).

# User Requirements

### How do we collect requirements?

Requirements engineering is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering. The domain of requirements engineering consists of two disciplines: *development* and *management of requirements*. The task of **requirements gathering** is to collect and define all features that the information system must have in order to fulfill the objectives that the customer has set. In the context of software development, requirements are whatever a product does and whatever a product has that its users need to reach their goals. Finally, requirements express those features of a product that enable its users to achieve specific objectives. This is an example of business requirements: 

<figure><img src="https://i.postimg.cc/MTbDkgMX/requirements2.png" alt=""><figcaption></figcaption></figure>

&#x20;

Throughout the course of the project, requirements are discovered and continually re-prioritized in Scrum. The project goals are transformed into the **product backlog** by the requirements. **Product Owner** chooses which requirements are executed and in what sequence and is accountable for the requirements.&#x20;