h1. Elicitation methodology
h2. Goal: elicit high level requirements from Use Cases using a +scenario-based approach+
* Using scenario enables requirements analysts to ground questions in context through the main events described in the scenario
* Definition of a *requirements taxonomy* relevant to SocEDA particular SOA/Large Scale context. Used to improve understanding, analysis and testing of the solution; to write clearer more focused requirements
h2. Example of elicited requirements at both the use-case and platform levels
!ScreenClip.png|align=center!
h2. Requirements deliverable
[Download deliverable|soceda:Work packages and deliverables^D1-1-1_Requirements_v0.9.pdf]
h2. Goal: elicit high level requirements from Use Cases using a +scenario-based approach+
* Using scenario enables requirements analysts to ground questions in context through the main events described in the scenario
* Definition of a *requirements taxonomy* relevant to SocEDA particular SOA/Large Scale context. Used to improve understanding, analysis and testing of the solution; to write clearer more focused requirements
h2. Example of elicited requirements at both the use-case and platform levels
!ScreenClip.png|align=center!
h2. Requirements deliverable
[Download deliverable|soceda:Work packages and deliverables^D1-1-1_Requirements_v0.9.pdf]