The two use cases below describe potential typical workflows that EPOS users might follow. These use cases were used to help design the GUI of the EPOS web portal and its functionality. The information contained in the use cases was crucial in helping the developers to design a practical and useful environment. During the Requirement and Use Cases collection (January - March 2016) typical user stories were collected by the EPOS communications and development teams (WP6&7) from all the scientific communities (TCS WP8-WP17) involved in the EPOS project. Each community provided several Use Cases and described their User Stories. Examples of two User Stories which were derived from those collected are presented here.
The Simple User Story assumes that the user is searching for specific data related to his/her research area. Once the result is found it can be inspected (check details about the origin, etc.), visualized and downloaded afterwards.
The Complex User Story is a counterpart of the Simple User Story. It introduces a complex scenario with data from many (possibly all) TCSs, and expects that the user will do all the analysis of all datasets within the web portal environment, including usage of HPC or HTC (via ICS-D).