Conference Reports

Stories for the Veterinary project

Written by Andy Tinkham. Date of post: .

I’m working on the veterinary project. Brian has talked to a person he knows who is involved in giving this test, and talked about what they’re looking for in this application. We then talked about the user stories we could pull out of the description Brian gave us. Here’s the stories we’ve come up with for the application (in the extended entry). We did this by first listing them on a whiteboard (so we could all see them) and then transferred the stories to index cards.

We also identified a list of questions for Brian to go back to his contact to get answered.

Bill then had us try to come up with narrow stories so that we could show progress with each interaction (For example, the first three stories under the Questions & Answers section need to be partially implemented together so that we have an exam system, so we should reslice the stories into smaller stories that we use. The example he used was setting it up first to handle one case, with one test that you can choose to run or not, and one diagnosis. From there we would then grow the system in future interactions.)

3 big areas of stories (this list has story titles):

QUESTIONS & ANSWERS (the actual exam)

  • Show case summary
  • Show list of tests
  • Allow selection of ‘n’ tests & get results

    In further discussion, we changed the above three to :

  • (QA1) Show almost-trivial interface with case summaries, some tests, and some diagnoses with simple interactive results
  • (QA2) Elaborate to list of actual test/results
  • (QA3) Repeat above for up to 4 test orders per case
  • (QA4) Repeat above for 6 cases
  • (QA5) Allow navigation between cases
  • (QA6) Disallow repeat of same test for a case
  • (QA7) Select diagnoses from list of possible
  • (QA8) Different result types (textual, tabular, image)
  • (QA9) Case summary for all 6 cases (singlement — this is the front page)
  • (QA10) Make groupings of tests logical
  • (QA11) Make test groupings look like “real” lab form (reproduce current form look and feel)
  • (QA12) Resubmit diagnoses (or select but not submit)
  • (QA13) Allow review of all case info to date (initial information, test results, etc.)
  • (QA14) Each case or animal has customized list of tests (feed animals & horses)

    SCORING (IDENTIFICATION)

  • (S1) Some tests not worth extra points (e.g. urinalysis — 3 types of collection –> Can’t get extra points for doing all three types)
  • (S2) Student IDs (SSNs)
  • (S3) Each test has score in context of a given case
  • (S4) Each diagnosis has score in context of a given case
  • (S5) Present final overall score for student (possibly not to student)
  • (S6) Report on student scores/history
  • (S7) Determine optimal & minimal pathways
  • (S8) How many passing people did “what we thought they would do?” (matched the minimal path as identified by the case author)

    EXAM ADMINSTRATION

  • (EA1) Enter a new case as part of this year’s exam
    • Text
    • (EA2) Tables
    • (EA3) Pictures
  • (EA4) Set up list of examinees
  • (EA5) Reuse old cases (from previous exams) (but possibly update if needed)
  • (EA6) Confidentiality of answer key
  • (EA7)Automatically load Word files (make Esther’s job obsolete)