Online Quiz Interface Report

Five roles, question-bank versioning, autosave, partial credit and appeals, specified as numbered requirements with a permission matrix and measurable tests.

Try Deep Research

Loading preview...

Specify an online quiz system

Define roles, lifecycle, scoring, security, privacy, accessibility, integrity, recovery, and measurable acceptance tests without inventing a stack.

Make it formative practice

Change only assessment purpose from graded to formative.

Try Deep Research

Task: Write an implementation-neutral, acceptance-ready specification for a Moodle-like online quiz system. Center a graded attempt with visible question status and navigation, persistent timer controls, and clear low-time warnings while covering the full lifecycle.

Specification protocol: State assumptions and unresolved decisions; do not invent a stack or Moodle compatibility. Define learner, author, instructor/proctor, administrator, and support/auditor roles. Cover question-bank versioning, randomization, attempt states, autosave, timing and accommodations, submission, scoring, partial credit, manual grading, feedback, appeals, reporting, retention, export, and audit events. Address authentication, authorization, least privilege, file/input safety, encryption expectations, privacy/deletion, threat modeling, proportionate cheating deterrence, and false-positive review. Specify keyboard and screen-reader use, focus, semantics, contrast, reflow, non-color cues, and timing alternatives. Deliver numbered requirements, data concepts, state transitions, permission matrix, edge/abuse cases, and measurable tests for reconnects, concurrency, timer drift, grading, accessibility, security, privacy, load, and recovery. Separate requirements from implementation options.

Design high-stakes exams

Change only assurance level to high-stakes exams.

Try Deep Research

Task: Write an implementation-neutral, acceptance-ready specification for a Moodle-like online quiz system. Center a graded attempt with visible question status and navigation, persistent timer controls, and clear low-time warnings while covering the full lifecycle.

Specification protocol: State assumptions and unresolved decisions; do not invent a stack or Moodle compatibility. Define learner, author, instructor/proctor, administrator, and support/auditor roles. Cover question-bank versioning, randomization, attempt states, autosave, timing and accommodations, submission, scoring, partial credit, manual grading, feedback, appeals, reporting, retention, export, and audit events. Address authentication, authorization, least privilege, file/input safety, encryption expectations, privacy/deletion, threat modeling, proportionate cheating deterrence, and false-positive review. Specify keyboard and screen-reader use, focus, semantics, contrast, reflow, non-color cues, and timing alternatives. Deliver numbered requirements, data concepts, state transitions, permission matrix, edge/abuse cases, and measurable tests for reconnects, concurrency, timer drift, grading, accessibility, security, privacy, load, and recovery. Separate requirements from implementation options.

Support low connectivity

Change only delivery context to low-connectivity asynchronous classes.

Try Deep Research

Task: Write an implementation-neutral, acceptance-ready specification for a Moodle-like online quiz system. Center a graded attempt with visible question status and navigation, persistent timer controls, and clear low-time warnings while covering the full lifecycle.

Specification protocol: State assumptions and unresolved decisions; do not invent a stack or Moodle compatibility. Define learner, author, instructor/proctor, administrator, and support/auditor roles. Cover question-bank versioning, randomization, attempt states, autosave, timing and accommodations, submission, scoring, partial credit, manual grading, feedback, appeals, reporting, retention, export, and audit events. Address authentication, authorization, least privilege, file/input safety, encryption expectations, privacy/deletion, threat modeling, proportionate cheating deterrence, and false-positive review. Specify keyboard and screen-reader use, focus, semantics, contrast, reflow, non-color cues, and timing alternatives. Deliver numbered requirements, data concepts, state transitions, permission matrix, edge/abuse cases, and measurable tests for reconnects, concurrency, timer drift, grading, accessibility, security, privacy, load, and recovery. Separate requirements from implementation options.