| | 1 | == xQTL workbench application user stories == |
| | 2 | |
| | 3 | === As a user I want to have an overview of my data === |
| | 4 | |
| | 5 | Acceptance criteria: |
| | 6 | |
| | 7 | * I want a place for a clear, immediate and complete overview of all my data |
| | 8 | * This screen must be very prominent, maybe even starting point of the app |
| | 9 | * It must function as a portal for browsing and adding data to the database, plus downloading of sections or a complete set |
| | 10 | * ... |
| | 11 | |
| | 12 | === As a user I want to be able to import data as quickly and easily as possible === |
| | 13 | |
| | 14 | Acceptance criteria: |
| | 15 | |
| | 16 | * The import must be a (semi) guides process where it is clear what I must do (next), and what I have done wrong or right |
| | 17 | * I would like import in various formats, and keep files in existing well-defined formats (eg. BAM, CEL, FASTA files) |
| | 18 | * I would also like to attach miscellanious files, such as images, videos, docs, machine output etc. |
| | 19 | * There must be help available, and examples of datasets I can edit and reuse |
| | 20 | * I would not want to loose progress during the import process |
| | 21 | |
| | 22 | === As a biologist I want to run analyses === |
| | 23 | |
| | 24 | * I would like a clear overview of analyses I can run, and what their purpose is |
| | 25 | * I do not want to be bothered with technical details |
| | 26 | * I would like to see help on the analyses I can run and their parameters |
| | 27 | * The application should make clear to me if my data is not complete for running a certain tool, and suggest how/where to fix it |
| | 28 | * If anything goes wrong, I want a clear error message with suggestions how to proceed, or who to contact |
| | 29 | * When a tool is finished running, I would like to go directly to my results |
| | 30 | * I want to be able to get a report of all the settings and software I used so I can report my provenance to others |
| | 31 | * ... |
| | 32 | |
| | 33 | === As a biologist I want to view results === |
| | 34 | |
| | 35 | * The place to view data (including results) should be reachable from multiple places so I never get lost |
| | 36 | * The viewer should provide a clear menu of things I can do with the data |
| | 37 | * I want useful viewers (plugins) that add meaning to my data and save me from using my own tools to e.g. make a graph |
| | 38 | * I would like to see help and instructions on how to use the more complicated viewers |
| | 39 | * ... |
| | 40 | |
| | 41 | === As a biologist I want to download my data === |
| | 42 | |
| | 43 | * I would like to retrieve the data in multiple formats, both 'generic' (Excel, CSV..) as 'specific' (FASTA, PDF) if the data allows it |
| | 44 | * I would like to make aggregated views on the data (ie. include annotation) and them download them |
| | 45 | * Downloading 'archives' is handy, where data is exported into a single file for backup/reuse in similar databases |
| | 46 | * ... |
| | 47 | |
| | 48 | === As a biologist I want to connect external tools |
| | 49 | |
| | 50 | * I want to have linkouts to popular databases, datatypes permitting |
| | 51 | * I want to manually add linkouts if they are not present |
| | 52 | * I want to able to export XGAP data immediatly into popular online tools, for example get a link for a DAS service that I can plug in elsewhere |
| | 53 | * It would be great if XGAP already featured integration or enrichment functions with popular database, for example map genes to KEGG and them visualize them |
| | 54 | * ... |
| | 55 | |
| | 56 | === As a bioinformatician I want to add new analyses === |
| | 57 | |
| | 58 | * I want a clear screen to add and configure new tools |
| | 59 | * I want to be able to testdrive the tools before people can use them |
| | 60 | * I want to be able to sort out technical details such as compute resource, batching, default parameters so the user does not have to deal with this |
| | 61 | * I would like information on who to contact if the application or computation server needs additional configuring or installing |
| | 62 | * ... |
| | 63 | |
| | 64 | === As a bioinformatician I want to add and configure workflows === |
| | 65 | |
| | 66 | * I want to be able to build workflows from analyses protocols using a helpful screen (may or may not be graphical) |
| | 67 | * I would like help connecting analyses in a meaningful way, ie. be sure the outcome is not nonsense, by having good documentation, ontologies, strict typing, etc |
| | 68 | * The screen not have to be extensive, a simple concatenation of a few steps is already very helpful (ie. normalization -> correction -> scan QTL -> make network -> visualize) |
| | 69 | * I want to be able to import workflows from tool such as Taverna or Galaxy, from files |
| | 70 | * I would like to be able to browse a catalog of workflows or services and incorporate those as well |
| | 71 | * I want to be able to export workflows in various formats |
| | 72 | * I would like to share workflows with others within the system, but also share them with the outside world (ie. MyExperiment) |
| | 73 | * ... |
| | 74 | |
| | 75 | === As an administrator I want user management and security === |
| | 76 | |
| | 77 | See all stories of [http://www.molgenis.org/wiki/AuthModuleUserStories auth]. |
| | 78 | |
| | 79 | === As an administrator I want to configure the application |
| | 80 | |
| | 81 | * I want a configuration screen for all kinds of application settings, such as: |
| | 82 | * View the status of the database, is it set up correctly, how much space am I using, how much is available, how fast are the queries, etc |
| | 83 | * View status of file storage, does the application have read/write rights, are backups being made, what kind of files do people store, how often are they retrieved, etc |
| | 84 | * I want the ability to restore backups of the database, additional files, other settings such as this panel, and view a history of changes/additions/deletions of these aspects |
| | 85 | * I would like to view user activity and registration, and be able to communicate with users by either email, messages inside the application, or otherwise |
| | 86 | * ... |
