Alice/my_digital_garden
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

vault backup: 2023-09-20 10:11:49

Browse source
This commit is contained in:
Alice 2023-09-20 10:11:49 +01:00
parent 6f2c60d5f8
commit 174670abe3
1 changed files with 11 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
content/RAS/TP - Aula 1.md
View file

@ -34,7 +34,7 @@
>>- Option 4. is a non-functional requirement. >>- Option 4. is a non-functional requirement.
>[!help]+ Exerc. 3.2 (Naveda and Seidman, 2006, pp. 33–34) >[!help]+ Ex. 3.2 (Naveda and Seidman, 2006, pp. 33–34)
>Which is the type of requirements that should not be included in a requirements document? >Which is the type of requirements that should not be included in a requirements document?
> >
>1. functional requirements >1. functional requirements
@ -42,7 +42,7 @@
>3. project requirements >3. project requirements
>4. performance requirements >4. performance requirements
> >
>>[!hint] Resolução >>[!hint]- Resolução
>>Option 3. should not be included. >>Option 3. should not be included.
>> >>
>>- Option 1. is essential. >>- Option 1. is essential.
@ -50,7 +50,8 @@
>>- Option 3. defines the circumstances around the project: it touches budget, the team members, other departments (than the development team), etc. It is too encompassing and it is not always about the development of the system. *The requirements document should be in the project documents*, not the other way around. >>- Option 3. defines the circumstances around the project: it touches budget, the team members, other departments (than the development team), etc. It is too encompassing and it is not always about the development of the system. *The requirements document should be in the project documents*, not the other way around.
>>- Option 4. is a non-functional requirement, therefore its inclusion is necessary. >>- Option 4. is a non-functional requirement, therefore its inclusion is necessary.
>[!help]+ Exerc. 3.3 (Naveda and Seidman, 2006, pp. 41–42)
>[!help]+ Ex. 3.3 (Naveda and Seidman, 2006, pp. 41–42)
>Which is the element that must be included in a requirements document? >Which is the element that must be included in a requirements document?
> >
>1. acceptance/validation procedures >1. acceptance/validation procedures
@ -58,9 +59,10 @@
>3. quality attributes >3. quality attributes
>4. activities to guarantee the quality >4. activities to guarantee the quality
> >
>>[!hint] Resolução >>[!hint]- Resolução
>>Option 3. is a must. >>Option 3. is a must.
> >>
>1. Option 1. pertains to the testing procedures. >>1. Option 1. pertains to the testing procedures.
>2. Option 2. pertains to the . >>2. Option 2. pertains to the expected plans of the delievery of the software (versions: version alpha, version beta, etc.).
>3. Option 3. is a syno >>3. Option 3. is a synonym for non-functional requirements.
>>4. Option 4. is the indicated protocol that dictates the quality.