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

.obsidian/workspace.json

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

4a1s/RAS/T - Aula 3.md

@@ -49,3 +49,15 @@ Process Scheme: [[process.excalidraw]]
 	12. persona
 
 ### 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.
+-