diff --git a/docs/20-Requirement-management/templates/template-requirementlist.md b/docs/20-Requirement-management/templates/template-requirementlist.md index 135495808bf864e4455f2aee52a7b21db32641f8..b987a2436b8649e9fedf30eb65388f635c76cd3b 100644 --- a/docs/20-Requirement-management/templates/template-requirementlist.md +++ b/docs/20-Requirement-management/templates/template-requirementlist.md @@ -1,19 +1,15 @@ -# Requirements as a list template - -[](http://www.youtube.com/watch?v=rp3DkiZ-Mkk "") +# Requirements as a list 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. - # Business / Customers / Constraints **Customer Requirements** - | 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) | | CUSTOMER-REQ-0002 | Customer Requirement ||| | CUSTOMER-REQ-0003 | Customer Requirement ||| | CUSTOMER-REQ-0004 | Customer Requirement |||