From 045d0f04b6662a23893398f3780119267e1ee487 Mon Sep 17 00:00:00 2001 From: Alice Date: Wed, 20 Sep 2023 10:21:49 +0100 Subject: [PATCH] vault backup: 2023-09-20 10:21:49 --- content/RAS/TP - Aula 1.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/RAS/TP - Aula 1.md b/content/RAS/TP - Aula 1.md index 17b770e..9782394 100644 --- a/content/RAS/TP - Aula 1.md +++ b/content/RAS/TP - Aula 1.md @@ -71,13 +71,15 @@ >[!help]+ Ex. 3.4 (Naveda and Seidman, 2006, pp. 57–58) >Which of the following arguments is the most solid/strong to justify the specification of the non-functional requirements of a system? > ->1. acceptance/validation procedures ->2. delivery plans ->3. quality attributes ->4. activities to guarantee the quality +>1. The non-functional requirements should only be considered in development contexts subject to tight restrictions (resources, budget, or deadlines). +>2. The non-functional requirements are only external characteristics of the system and can be obtained later. +>3. If a functionality is present in the system, the non-functional requirements determine how usable and useful it is. +>4. The non-functional requirements take less time to specify than the functional requirements. > >>[!hint]- Resolução +>>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 >> >> >>