fix: Typo fixed in documentation.

This commit is contained in:
Jan Jambor 2025-01-13 14:56:02 +01:00
parent 2f632c6a08
commit 6b18b3439c

View file

@ -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.