Talk:Use Case Scenarios

From Filtered Push Wiki
Jump to: navigation, search

Administrative Use Case Questions

Administrative use case questions:

The answers to questions starting with "who" might be "sysadmins," "developers," "collection managers", "end users" (i.e. someone in front of a web browser).

  1. Who obtains the software?
    1. --Bob Morris 23:57, 29 November 2012 (EST): sysadmins
    2. --Paul J. Morris 11:50, 2 January 2013 (EST): (1) Network node software, portal clients: sysadmins; (2) Collection management software: developers, collection managers.
  2. How is the software obtained? Download from SourceForge? Download from FP wiki? Private ftp site?
    1. --Bob Morris 23:57, 29 November 2012 (EST): Download from Sourceforge in a file for standard kinds of systems, e.g. ApplePie.zip
    2. --Paul J. Morris 11:50, 2 January 2013 (EST): (1) Network node software, portal client support software: download from souurceforge as deployable artifacts. (2) Collection management software: bundled with distribution from vendor.
  3. On what platforms will the software be installed? Linux/Mac/Windows? Server or workstation, laptop or mobile device?
    1. --Bob Morris 23:57, 29 November 2012 (EST): Linux perhaps with specified distribution(s); also perhaps as one or more fully configured VM images.
    2. --Paul J. Morris 11:50, 2 January 2013 (EST) : (1) Network node and portal client support software: Servers, most likely Linux, running J2EE containers. (2) Collection management software: workstations, laptops, multiplatform, mostly Win and Mac.
  4. Who is expected to do installs?
    1. --Bob Morris 23:57, 29 November 2012 (EST): sysadmins
    2. --Paul J. Morris 11:50, 2 January 2013 (EST): (1) Network node software, portal clients: sysadmins; (2) Collection management software: developers, collection managers.
  5. Should the install process be driven by a GUI ("setup wizard"), or be a command-line script? Should we create a package for some particular flavor of Linux?
    1. --Bob Morris 23:57, 29 November 2012 (EST): Command line script. Bigger community to contribute to the script quality.
    2. --Paul J. Morris 11:50, 2 January 2013 (EST): (1) Network node software, portal clients: command line script makes some sense; (2) Collection management software: embedded in distribution from vendor.
  6. How should updates be accomplished? Should the software check for updates?
    1. --Bob Morris 23:57, 29 November 2012 (EST): Notifications should be sent with opt-in.
    2. --Paul J. Morris 11:50, 2 January 2013 (EST): (1) Network node software, portal clients: sysadmin responsibility; (2) Collection management software: yes, automated, syncronized with vendor.
  7. Who deals with maintaining the software prerequisites (e.g. Glassfish)?
    1. --Bob Morris 23:57, 29 November 2012 (EST): Consider offering VM image and substrate to organizations who want to do no complex maintenance. Organizations with skilled sysadmin can manage a full local installation if they prefer.
    2. --Paul J. Morris 11:50, 2 January 2013 (EST): (1) Network node software, portal clients: sysadmins; (2) Collection management software: collection managers.
  8. How often will schema/ontology changes occur? E.g., how often will Apple Pie's rules change?
    1. --Bob Morris 23:57, 29 November 2012 (EST): Rule changes should be rare for deployed systems. There are lots of issues about changing rules in the middle of the game.
    2. --Paul J. Morris 11:50, 2 January 2013 (EST) changes to existing definitions should be rare, additions of new definitions might occur on 6 month to yearly basis in deployed systems.
  9. For the prerequisite software (e.g. Glassfish), will these components be available for use by other software, or are they private to Filtered Push?
    1. --Bob Morris 23:57, 29 November 2012 (EST): Only a skilled sysadmin should share components between FP and other software. If FP takes off big time, a community will arise that produces robust installations for shared component scenarios.
  10. How many software installations are required per network?
    1. --Paul J. Morris 11:50, 2 January 2013 (EST): (1) Network node software, portal clients: minimum 0 (FP-Lite), 1 (FP-medium+); (2) Collection management software: 1 per site.
  11. Who has access to install, configure, update, and add "capabilities?" Can this be done via web interface, or only by access to the machine?
    1. --Paul J. Morris 11:50, 2 January 2013 (EST): (1) Network node software, portal clients: sysadmins;
  12. How does one discover and add "capabilities?" Can capabilities be removed?
    1. --Paul J. Morris 11:50, 2 January 2013 (EST) Deploying jars or other artifacts? David has some more recent ideas here.
  13. Will all network members be known at install time?
    1. --Paul J. Morris 11:50, 2 January 2013 (EST) No.
  14. Can new members be added later?
    1. --Paul J. Morris 11:50, 2 January 2013 (EST) Yes. For clients, invovles adding their public key to list at an access point.
  15. Can members be removed?
    1. --Paul J. Morris 11:50, 2 January 2013 (EST) Yes. For clients, involves removing their public key from the list at all access points.
  16. Do we need to be able to move an installation from one machine to another? Do we need to have a mirror set up at install time? Do we need to have a way to export data? Do we need to have a way of selectively exporting data, or is it an all-or-nothing thing?
  17. Backwards compatibility?
  18. Will the different programs (client/driver/node) need to always operate with every version of each other program?
  19. Do we need to support removing annotations? For example, if someone wants to demonstrate how to use the software and puts in a "fake" annotation, do we need to be able to support removing single annotations?
    1. --Paul J. Morris 11:50, 2 January 2013 (EST) Yes.
  20. Do we need to support removing annotations made during a particular time frame? Do we need to support "trial runs," purging data used during an initial training period?
    1. --Paul J. Morris 11:50, 2 January 2013 (EST) Yes, we've already needed to do this.