From 6b18b3439cf452b32b73c553ed1ecf528056b9f9 Mon Sep 17 00:00:00 2001 From: Jan Jambor Date: Mon, 13 Jan 2025 14:56:02 +0100 Subject: [PATCH] fix: Typo fixed in documentation. --- traceability-concept.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/traceability-concept.md b/traceability-concept.md index 2075bca..5731277 100644 --- a/traceability-concept.md +++ b/traceability-concept.md @@ -4,7 +4,7 @@ ## Description of the layers -**Stakehodler Requirements**: It's crucial to understand that we always start with the stakeholder requirements where regulations are an important input. This is the customer's point of view, defines “what” should be done. +**Stakeholder Requirements**: It's crucial to understand that we always start with the stakeholder requirements where regulations are an important input. This is the customer's point of view, defines “what” should be done. **System Requirements**: The system requirements are the answer to the stakeholder requirements. It describes “how” it is going to be implemented. Quality requirements, often called non-functional requirements, are part of the system requirements. They are stated as testable requirements e.g. latency time must be less than 200ms. Furthermore we also add potential risks at this level.