vault backup: 2023-09-27 10:04:34
This commit is contained in:
parent
a8f8362bef
commit
b670a9c69c
4 changed files with 6910 additions and 11 deletions
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
dg-publish: true
|
||||
---
|
||||
|
||||
27 de Setembro 2023 - #RAS
|
||||
|
||||
>[!help]+ Ex 5.1
|
||||
|
@ -8,7 +12,7 @@
|
|||
>3. Interviews
|
||||
>4. Surveys
|
||||
>
|
||||
>>[!hint]- Resolução
|
||||
>>[!hint]- Resolution
|
||||
>>The option 1 should be the chosen one, since it allows .
|
||||
>>
|
||||
>>Option 2- The software already exists. Why would one create a prototype for an app that already exists?
|
||||
|
@ -53,6 +57,17 @@
|
|||
>8. Scenarios
|
||||
>9. Personnas
|
||||
>
|
||||
>>[!hint]- Resolução
|
||||
>>Order of importance:
|
||||
>>
|
||||
>>[!hint]- Resolution
|
||||
>>Most valid options:
|
||||
>>1. Domain Analysis
|
||||
>>2. Interviews
|
||||
>>3. Surveys
|
||||
>>4. Task analysis
|
||||
>>5. Observation
|
||||
>>6. Goal modelling
|
||||
|
||||
>[!help]+ Ex. 5.5
|
||||
>Explain the main reasons why the combined used of ethnographical techniques with prototyping is useful for eliciting requirements.
|
||||
>>[!hint] Resolution
|
||||
>>When the prototypes are handled by the users under the observation of the analyst, the combination of these two techniques has the potential to provide mush richer requirements, in relation bot
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue