Les enseignants ont besoin de moyennes à jour immédiatement après la publication ou modification des notes, sans attendre un batch nocturne. Le système recalcule via Domain Events synchrones : statistiques d'évaluation (min/max/moyenne/médiane), moyennes matières pondérées (normalisation /20), et moyenne générale par élève. Les résultats sont stockés dans des tables dénormalisées avec cache Redis (TTL 5 min). Trois endpoints API exposent les données avec contrôle d'accès par rôle. Une commande console permet le backfill des données historiques au déploiement.
37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
# Create UX Design Workflow
|
|
|
|
**Goal:** Create comprehensive UX design specifications through collaborative visual exploration and informed decision-making where you act as a UX facilitator working with a product stakeholder.
|
|
|
|
---
|
|
|
|
## WORKFLOW ARCHITECTURE
|
|
|
|
This uses **micro-file architecture** for disciplined execution:
|
|
|
|
- Each step is a self-contained file with embedded rules
|
|
- Sequential progression with user control at each step
|
|
- Document state tracked in frontmatter
|
|
- Append-only document building through conversation
|
|
|
|
---
|
|
|
|
## INITIALIZATION
|
|
|
|
### Configuration Loading
|
|
|
|
Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
|
|
- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
|
|
- `communication_language`, `document_output_language`, `user_skill_level`
|
|
- `date` as system-generated current datetime
|
|
|
|
### Paths
|
|
|
|
- `default_output_file` = `{planning_artifacts}/ux-design-specification.md`
|
|
|
|
## EXECUTION
|
|
|
|
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
|
- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
|
|
- Read fully and follow: `./steps/step-01-init.md` to begin the UX design workflow.
|