document use cases and user stories

[bhpayne]

what are users expected to accomplish?

[bhpayne]

Use case is a goal or question. User story is a person has a goal and gets a result. Acceptance test focuses on a functionality. Regression test verifies code works and works consistently.

• use case: #242
  • user story: User adding a derivation supplies a sparse set of expression sequences and is provided the connecting expressions and inference rules
• use case: #238
  • user story: User has a symbol latex, queries the web interface, and it provided the symbol ID
    • acceptance test: input x, get back numeric value
      • regression test: input x, get back 9921
    • acceptance test: input x_1, get back numeric value
      • regression test: input x_1, get back 9239
  • user story: User has a symbol ID, queries the web interface, and gets the symbol Latex
    • acceptance test: input 1932, get back Latex string
      • regression test: input 1932, get back y
  • user story: User has multiple symbols in latex, queries the web interface, and is provided a list of expressions with those symbols
    • acceptance test: input x and y, get back Latex string and expression ID
• use case: #239
  • user story: User queries the web interface and is provided a list of all inference rule tuples. The list is ranked by number of times each tuple appears in the graph
• use case: #247
  • user story: User has two expressions, queries the web interface, and is provided the graph of expressions and inference rules that is the shortest connection between the two inputs.
• use case: #243
  • user story: User has a set of expressions, queries the web interface, and is provided a graph of the relations among all the inputs
• use case: #241
  • user story: User queries the web interface and is provided how many components are in the PDG, along with the relative size of each component.
• use case: analyze relative frequencies of inference rules
  • user story: User queries the web interface and is provided a list of all inference rules. The list is ranked by number of times each inference rule is used in the graph.
• use case: visualize the graph (of one derivation; of all content)
  • user story:
• use case: convert arxiv PDF to graph of steps
  • user story:
• use case: compete with other users for contribution stats
  • user story:
• use case: find novel relations with related content in scientific literature (rather than relying on the citation graph)
  • user story:
• use case: check correctness of derivation steps
  • user story: User enters a derivation consistent of multiple steps. User then sees on the webpage which steps are wrong.
  • user story: User reviews existing derivation steps and webpage shows which steps are not validated by the computer algebra system