Files
Kill_LIFE/docs/workflows/systems_engineering.md
Clément SAILLANT d7ffbf14cf feat: Add workflows and templates for design reviews, release processes, and compliance checks
- 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.
2026-02-19 01:35:10 +01:00

45 lines
1.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Workflow — Bureau d’études / Ingénierie système (HW/FW)
## But
Produire une architecture endtoend : 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:plan` puis `ai:qa` (si tu veux injecter la test matrix)
### 4) Backlog (WBS)
- Livrables : epics/stories, tâches, critères dacceptation
- 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:spec` doit rester dans `specs/` + `docs/`
- `ai:impl` ne 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 (6090 min)
- ADR obligatoire pour : MCU/RTOS, bus, power architecture, radio stack