question bank-Standards
standard for strukturierte question banks, categories, Versionierung and quality from Quizfragen.
Quick overview
This page describes the working standard for question bank-Standards – with a focus on concrete decisions rather than general guidance.
The main focus here is namensschema and kategorietiefe and freigabeprozess for new fragen so that teams apply the same standard.
The standard only becomes traceable through linked evidence such as fragenpool-export / categories and through documented edge cases/exceptions.
When this page helps
Typical situations in which this page adds value as a working document, and where another document is more appropriate.
Typical use cases
- when question bank-Standards as a reusable Moodle standard with clear requirements for fragenpool-structure and categories should serve
- when authors or trainers work inconsistently on namensschema and kategorietiefe
- when Quality assurance and approvals with fragenpool-export / categories should be documented in a traceable way
- when Support- or course feedback points to a typical pitfall (e.g. fragen liegen in sammelkategorien)
Less suitable when
- when question bank-Standards only about a one-off individual case without need for standardization applies
- when a detailed project ticket or a technical step-by-step guide is the better fit
Recommended process
A pragmatic sequence that works in practice, from scope to review.
- Briefly describe the use case and target audience for question bank-Standards briefly describe; from that scope and expected learning outcome derive the scope and expected learning outcome.
- standard setup/configuration define, especially namensschema and kategorietiefe and freigabeprozess for new fragen.
- Use test users or a reference course to check whether fragenpool-structure and categories work in practice.
- Quality assurance/approval carry out and link evidence such as fragenpool-export / categories link.
- After Livegang feedback auswerten and error patterns such as „Fragen liegen in Sammelkategorien“ as pitfall add.
Decision rules
question bank-Standards is well documented, when rules, Edge cases and Evidence so clearly are, dass teams so that without additional coordination work can.
scope
For question bank-Standards first define the scope clearly: question bank-Structure and categories.
Priorities
decisions about namensschema and kategorietiefe and freigabeprozess for new fragen not implizit lassen, sondern roles and approvals explicitly benennen.
Exceptions
Allow exceptions only if they do not dilute the standard; especially relevant here are versionierung from fragen.
Evidence logic
Verifiable is the rule only, when fragenpool-export / categories and review-protokolle cleanly verlinkt are.
What should be documented
Here only the spezifischen Inhalte about question bank-Standards maintain; general documentation rules remain in the centraln guideline. Central guideline.
The page is good when a substitute can apply or review the standard without first collecting tribal knowledge.
scope & terms
terms, scope and boundaries about question bank-Standards specify in concrete terms, including fragenpool-structure and categories.
Binding rules
Den standard so record, dass namensschema and kategorietiefe and umgang with frageänderungen in laufenden tests eindeutig entschieden are.
Evidence & filing
Name and link evidence directly: question bank-Export / categories, review-Protokolle, Testversuche.
Exceptions & Historie
Aktive Exceptions, the latest change and the next review belong on the page—especially for topics with versionierung from fragen.
Common pitfalls
This section captures real-world pitfalls from question bank-Standards; general guidance belongs in the central guideline. Central guideline.
- scope driftet: Fragen liegen in Sammelkategorien.
- the rule is too abstract: Frageänderungen verfälschen ongoing Auswertungen.
- evidence is missing: Medien in Fragen fehlen or are instabil.
- the exception gets out of control: Zeitlimit fits not to the Aufgabenlänge.
Moodle reference (official docs 5.1)
Kurze Verweise on the offizielle Moodle documentation for question bank-Standards. So remains this Page AFANDI-spezifisch and vermeidet doppelte Grundlagen.
Official references
Documentation focus
- Fragenkategorien, Namensschema and reuse the Fragebank clear document.
- UI path, role and test case record explicitly (not only the desired target state).
- Mark deviations from AFANDI standards separatelyely so that updates remain easier to review.
Review & maintenance
Check this Page gegen reale processes about question bank-Standards – not only gegen the Wortlaut. Entscheidend is, ob standard, Exceptions and Evidence in the Alltag contribute.
- are categories functional appropriate?
- Gibt it Dubletten/Altfragen?
- Were approvals documented?
- Were Timing and Einsicht getestet?
Review focus for „question bank-Standards“: Fragenbank; check especially fragenpool-structure and categories.
Useful metrics
A few metrics are enough – what matters is that they trigger decisions or improvements.
For „question bank-Standards“ Kennzahlen directly an namensschema and kategorietiefe and the most frequent Praxisrisiken koppeln.
Fragen-review-Quote
Anteil neuer Fragen with fachlichem review
Interval: monthly
Dubletten in the question bank
Anzahl erkannter Doppelungen
Interval: quarterly
Fehler in Live-Tests
Fragenfehler in the produktiven Einsatz
Interval: monthly
Next steps
Add jetzt the concrete Entscheidung about namensschema and kategorietiefe incl. Verantwortlichen, Datum and Verweis on fragenpool-export / categories.
On „question bank-Standards“ make especially clear as the next step: which fragenpool-structure and categories apply in the standard case and which exceptions are time-limited.