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

vault backup: 2023-09-27 17:06:46

Browse source
This commit is contained in:
Alice 2023-09-27 17:06:46 +01:00
parent f3366c9db8
commit 24f9885d12
2 changed files with 15 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
.obsidian/workspace.json vendored
View file

@ -139,11 +139,12 @@
} }
} }
], ],
"currentTab": 4 "currentTab": 3
} }
], ],
"direction": "horizontal", "direction": "horizontal",
"width": 300 "width": 300,
"collapsed": true
}, },
"left-ribbon": { "left-ribbon": {
"hiddenItems": { "hiddenItems": {

12
4a1s/RAS/T - Aula 3.md
View file

@ -49,3 +49,15 @@ Process Scheme: [[process.excalidraw]]
12. persona 12. persona
### 3. Elaboration ### 3. Elaboration
- This activity aims to analyse and classify the elicited, but not yet handled, requirements.
- Organises the requirements in cohesive groups.
- The analyst must intervene, whenever the requirements: do not make sense; are in contradiction among them; are incoherent; are incomplete; are vague.
### 4. Negotiation
- Requirements engineering involves communication and negotiation among various stakeholders.
- It is inevitable that conflict situations arise among the requirements. One needs to promote negotiation mechanisms among the stakeholders. Its result can have a significant impact on the acceptance of the final system.
- Another form of handling conflicts consists in adopting prioritisation techniques, to sustain the choice of the requirements subset to be implemented at each instant.
### 5. Documentation
- Requirements documents serve as the principal reference to the subsequent phases of the development process.
-