From d964d5677d22ca1a3834c8ce1d98fab11368ae82 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marko=20Rintam=C3=A4ki?= <marko.rintamaki@jamk.fi> Date: Tue, 6 Apr 2021 18:50:19 +0300 Subject: [PATCH] Update template-requirementlist.md --- .../templates/template-requirementlist.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/20-Requirement-management/templates/template-requirementlist.md b/docs/20-Requirement-management/templates/template-requirementlist.md index 1354958..b987a24 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 ||| -- GitLab