Scenario Refinement Sample Clauses

Scenario Refinement. The purpose of a scenario is to facilitate agreement between eDIANA architects and developers with stakeholders. Scenarios are refined from high level scenarios representing generic interactions between users or other system actors with the eDIANA platform. High level scenarios must start by identifying initiating actors and by defining the basic sequence of interaction with the eDIANA platform. Scenarios must be created properly from early phases. Hence, actor identification and interaction storyboards must be as complete as possible. It must be noted that an actor is someone or something that interacts with the system. This means that in addition to users, administrators, etc. external systems providing or requiring information from the eDIANA platform must be identified as actors. On the other hand, to properly identify useful scenarios, the following questions should be answered: • What functionality does each actor expect from the eDIANA platform? • Do the actors need to be informed about the events occurring in the systems? • What information the actors need to supply/receive to/from the system? When refining scenarios, it is useful to split the interactions with the system in logical sequences of events. This may allow assigning detailed scenarios to specific parts of the eDIANA platform or to specific components. In the same way, optional or conditional paths within a sequence of events can be divided into separated detailed scenarios. In general the criteria should be to assign detailed scenarios coming from task T2.5 to other task of the eDIANA project dealing with concrete eDIANA aspects.