From 2920370466bc37c5870c0cda37d3eda13e394ebf Mon Sep 17 00:00:00 2001 From: Alice Date: Wed, 20 Sep 2023 10:26:49 +0100 Subject: [PATCH] vault backup: 2023-09-20 10:26:49 --- content/RAS/TP - Aula 1.md | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/content/RAS/TP - Aula 1.md b/content/RAS/TP - Aula 1.md index 9782394..e091917 100644 --- a/content/RAS/TP - Aula 1.md +++ b/content/RAS/TP - Aula 1.md @@ -77,15 +77,7 @@ >4. The non-functional requirements take less time to specify than the functional requirements. > >>[!hint]- Resolução ->>Option 3. is the best justification.. +>>Option 3. is the best justification. >> ->>Non-functional requirements appear to be an enumeration of restrictions to the functional requirements being defined by a developing system. Non-functional requirements are the buffer of quality of the product - these cannot be defined later. Their determination may take even more time ->> ->> ->> ->> ->> ->> ->> ->> -> +>>Non-functional requirements are, colloquially, an enumeration of restrictions to the functional requirements being defined by a developing system. +>>Non-functional requirements are the buffer of quality of the product - these cannot be defined later. Their determination may take even more time than the definition of functional requirements since, sometimes, they can be even more implicit than their counterpart, the functional requirements. Their determination should also be independent of resources or budgets; otherwise, there can/will be consequences on the quality of the software.