Child pages
  • Administrative use cases
Skip to end of metadata
Go to start of metadata

Administrative use cases

  • Use cases involving the adminstration of the system

Adjust system settings

  • Goal: Change the way the system works for a single installation without changing code or modifying the database
  • Actors: Super user
  • Events:
    1. Login as super user
    2. Go to Administration view (only visible to super user)
    3. Adjust settings OR navigate to a sub view and adjust settings
    4. Save new settings (take effect immediately)
  • Implemented

Enable use of hierarchy

  • Goal: Turn on the hierarchy so it can be used in the system
  • Actors: Super User
  • Events:
    1. Login as super user
    2. Go to Administration view (only visible to super user)
    3. Check the box to enable the hierarchy controls
    4. Save the settings (this will enable the Control Hierarchy view)
  • Implemented

Control the layout of the hierarchy

  • Goal: Add/remove nodes to the hierarchy and control the structure of it
  • Summary: Super user needs to add nodes to the hierarchy or adjust how it is structured. Generally this does not happen very often as the structure reflects the university structure which rarely changes. They go into the hierarchy control view. They add nodes, adjust the names of existing nodes, and remove nodes which are no longer needed.
  • Actors: Super User
  • Events:
    1. Login as super user
    2. Go to Administration view (only visible to super user)
    3. Select the Control Hierarchy subview
    • Add Node
      1. Click on Add Node
      2. Enter information about the node
      3. Save the node
    • Remove Node
      1. Click on Remove next to the node to remove
    • Modify Node
      1. Click on the name of the node
      2. Adjust information about the node
      3. Save the node
    • Add groups to a node
      1. Click on the name of the node
      2. Select groups to add to the node
      3. Save the list of groups
  • Implemented

Control the Reporting system

  • Goal: Adjust the way results are reported to users
  • Summary: Institution wants to control the way results are presented (e.g PDF reporting allowed, Excel allowed, etc.). Super user goes into the adminsitration view and adjusts the types of data exports that are allowed and the options related to that.
  • Actors: Super User
  • Events:
    1. Login as super user
    2. Go to Administration view (only visible to super user)
    3. Select the Control Reporting subview
    4. Adjust the settings
    5. Save the settings
  • Implemented

Test the group provider

  • Goal: Test that the group provider is registered and working
  • Actors: Super User
  • Events:
    1. Login as super user
    2. Go to Administration view (only visible to super user)
    3. Select the Provider testing view (Test EvalGroupProvider)
      • If no provider is found then the view will explain this
    4. Enter test parameters and test the ability to resolve information
    5. Exit when done
  • Implemented

Control email sending and handling

  • Goal: Control how email is sent and handled for the installation
  • Summary: Super admin wants to control the handling of emails without having to reconfigure or recode parts of the eval system. Using the control interface they make adjustments to how often emails are sent and which sending method is used.
  • Actors: Super User
  • Events:
    1. Login as super user
    2. Go to Administration view (only visible to super user)
    3. Go to the email control view
    4. Adjust the settings for handling emails
    5. Save the settings
  • NotImplemented

Sample Template

SampleUseCase

  • Goal: goal
  • Summary:
  • Actors: user
  • Events:
    1. Login as super user
    2. stuff
  • ImplementedNotImplemented
  • No labels