This model is quite useful if the list of requirements isn't very long. The same list can be done quite conveniently with Excel, but it will soon lead to the complexity of documentation.
This model is quite useful if the list of requirements isn't very long. The same list can be done quite conveniently with Excel, but it will soon lead to the complexity of documentation.
When one environment is used to gather relevant information, it is easier to link them to each other and the information stays up to date better.
When one environment is used to gather relevant information, it is easier to link them to each other and the information stays up to date better.
# Business / Customers / Constraints
# Business / Customers / Constraints
**Customer Requirements**
**Customer Requirements**
| Requirement ID | Type | Description | Related feature |
| Requirement ID | Type | Description | Related feature |
|:-:|:-:|:-:|:-:|
|:-:|:-:|:-:|:-:|
| CUSTOMER-REQ-0001 | Customer Requirement | As a user I want to login using my Facebook credentials to avoid any hassle. | [Login ft1](ft1-ominaisuus.md) |
| CUSTOMER-REQ-0001 | Customer Requirement | As a user I want to login using my Facebook credentials to avoid any hassle. | [Example Feature 1](ft1-ominaisuus.md) |