Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Problem statement (What problem are we trying to solve?)
  • Error conditions and handling
  • Input conditions
  • Inputs including pre populated fields
  • Other pre conditions
  • Process flow
  • Post conditions
  • UI outputâ€"any kindâ€"output--any kind--file, re-directs to other UI, etc
  • Assumptions
  • Process states
  • Logging

...

  • Since this is an external tool, do we have to skin it? Probably but as simply as possible.
  • How can an end user input grades, save and return to complete the final grade submission transaction?
  • How do we transfer data from the course converter tool to this landing page tool? Don't know yet.
  • Should the landing page write the final grade file to AFS? Should we use web services in this process?
  • Do we need the Final Grade Submission tool to change also?
  • What happens if the end user hits the back button while inputting grades?
  • Can the landing page tool look up the grading option for the student's enrollment information? We carry this information in one of our tables.
  • If we have the student's enrollment grading option for the course, can we reveal this to the end user? If not, we just pass along to the output file whatever grade the end user inputs.
    • Answer from the Reg Office: The faculty is not supposed to know about the option for Pass No Pass grading. The letter grade is supposed to be submitted to registrar's office. The option on the grading is handled when the grade rolls to history in Banner.
  • Does the landing page tool perform any other grade look up validation?
  • Can the landing page tool look up the grading mode for the course? We don't carry this information in our external database.  Need to determine if we can get this, and if so if how we would implement different drop-downs for the relevant grading mode.
  • What software development tools will be used for programming the landing page tool?

...