d7ffbf14cf
- Introduced new documentation for design reviews (DR0/DR1) and release rituals. - Created templates for Architecture Decision Records (ADR), Design Reviews, Playtest Reports, and Validation Plans. - Established workflows for consulting, creative processes, systems engineering, R&D spikes, and compliance/QA. - Implemented GitHub Actions workflows for firmware and hardware CI with required checks strategy. - Added setup script for repository configuration, including label creation and branch protection. - Developed installation script for Kill_LIFE with system updates and environment setup.
1.4 KiB
1.4 KiB
Workflow — Bureau d’études / Ingénierie système (HW/FW)
But
Produire une architecture end‑to‑end : interfaces, budgets, risques, plan de validation, puis backlog.
Phases
1) Requirements engineering (requirements → spec)
- Livrables : RFC2119 + NFR + AC + matrice traçabilité (AC → tests)
- Label :
ai:spec
2) Architecture système (design → ADR)
- Livrables : diagrammes blocs, interfaces, budgets (power/memory/latency), modes de panne, ADR
- Label :
ai:plan
3) Design review (DR0/DR1)
- DR0 : cohérence + risques (pas de “dead ends”)
- DR1 : budgets + plan de validation + BOM
- Livrables : checklist review + décisions (ADR)
- Labels :
ai:planpuisai:qa(si tu veux injecter la test matrix)
4) Backlog (WBS)
- Livrables : epics/stories, tâches, critères d’acceptation
- Label :
ai:tasks
5) Exécution (impl + tests)
- Firmware : drivers + tasks + logs + watchdog
- Hardware : schéma/PCB + DRC/ERC
- Labels :
ai:impl/ai:qa
Gates
- Budgets explicités (power, mémoire, latence)
- Plan de validation (unit/integration/HIL/endurance)
- Scope guard :
ai:specdoit rester dansspecs/+docs/ai:implne touche pas aux workflows
Evidence pack
Voir docs/evidence/evidence_pack.md + exports (KiCad + BOM + logs CI).
Mode “BE” recommandé (cadence)
- Triage hebdo (30 min)
- DR0 et DR1 (60–90 min)
- ADR obligatoire pour : MCU/RTOS, bus, power architecture, radio stack