Difference between revisions of "Category:Use-Cases-and-Stories"

From Epos WiKi
Jump to: navigation, search
Line 1: Line 1:
The Use Cases and User Stories are describing a typical workflow that the users typically work with. For designing the GUI of the EPOS web portal and its functionality, this information is crucial to be able to design a useful environment. During the Requirement and Use Cases Collection (January - March 2016) the typical user stories were collected by the WP6&7 team from TCS WP8-WP17. Each group provided several Use Cases and described their User Stories. Examples of two User Stories which were derived from those collected are presented here.  
+
 
 +
 
 +
The two use cases below describe a potential and typical workflow that an users might apply to EPOS. These use cases were used to help design the [http://nodedev.bgs.ac.uk/epos/epos-gui/master/search 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 WP6&7 team 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.
 +
 
 +
Further examples are provided on the [https://intranet.epos-ip.org/ EPOS intranet pages] and on the EPOS [https://github.com/epos-eu/documentation/ GitHub Technical Documentation pages].  
  
 
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 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).
 
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).

Revision as of 18:15, 19 July 2018


The two use cases below describe a potential and typical workflow that an users might apply to EPOS. 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 WP6&7 team 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.

Further examples are provided on the EPOS intranet pages and on the EPOS GitHub Technical Documentation pages.

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).

Pages in category "Use-Cases-and-Stories"

The following 2 pages are in this category, out of 2 total.