edit: requirements capture

[oliver-sanders]

Note: #2647 captures current capabilities, this aims to better understand requirements.

List of specific questions to ask users (please add/comment):

1. Tabs
   • Do you find it useful to have multiple tabs?
   • How do you use tabs?
   • What problem are you trying to solve with tabs?
   • UI: Consider "bookmarks" as an alternative.
2. Purpose
   • When you open rose edit do you know what you want to achieve?
   • Or is there an element of "discovery" from exploring the config?
   • UI: Consider "favourites" as a solution to find commonly used configurations.
3. Scope
   • What proportion of the config do you normally edit (i.e. do you generally only work with a handful of configs or more)?
   • UI: Consider "favourites" as a solution to find commonly used configurations.
4. Presentation
   • Can you think of better ways to display your configurations?
   • Are there ways we can improve configuration rendering / interaction / layout?
   • UI: Consider widgets.
   • UI: Consider table & grid layouts.
   • UI: Consider approach to table sorting. 
   • UI: Consider grouping displayed results along with the use of accordions. 
5. File Orientation
   • Would a file-orientated (as opposed to suite-orientated) model work for you?
   • (i.e. editing one app at a time rather than having all apps in a single window).
6. Jupyter Lab Integration
   • Thoughts?
7. Comments
   • Do you use rose edit to edit comments associated with configurations?
8. Other points for consideration
   • Do you have anything further to add?

[aenglyst]

Understanding Users

It could be worth trying to get a better understanding of user type and by categorising them we'll get a better feel for how they use and want to use Rose Edit.

Although the depth of any research will be time permitting, a potential route for investigation includes:

• Segment into different types of user - Persona identification

• Identify needs of each persona. Consider general requirements for different personas, e.g:

      Persona 1 
      Ability to configure and run models from one UI. 
      
      Persona 2 
      Model integration tools / GUI (to get science out) 
      
      Persona 3 
      System integration tools / GUI (to put science in) 
      
      Persona 4 
      Advanced system interaction 
  

• Identify approx size of market for existing and potential users for each persona

• Identify target market for Rose Edit GUI

• Where can the market size be increased for:

    1. Increased science pull-through
    2. Improved model development and usage
  

User profiling

• What is required to enable the Rose Edit GUI to be more accessible to these potential users
• Focus requirements gathering towards meeting the needs of the identified target market.

[aenglyst]

Use of research methods

Consider conducting the following:

• Survey to understand users
• Semi-structured interviews to understand the needs of target users. (Some discussions have been had already, e.g with Harry Shepherd regarding global configurations, optional configurations, and archiving. Other people have also been recommended to potentially talk to as existing users, e.g Eric and Ben F.)

Turn this into functional requirements and functional spec.