thongdt89/asr_bsw/autosar-ecuc-diff-reviewer

AUTOSAR ECUC Diff Reviewer

Workflow

1. Confirm baseline and candidate source, target ECU, AUTOSAR release, vendor tool export method, and intended change set.
2. Build inventory and reference baselines for both versions using autosar-arxml-inventory.
3. Compare semantic objects rather than file order, whitespace, UUID churn, or generated timestamps.
4. Classify every change as module enablement, container add/remove, parameter change, reference change, timing change, network/diagnostic/memory/system impact, or vendor-extension change.
5. Trace changed references and affected downstream modules, callbacks, generated code, test cases, and rollback requirements.
6. Escalate deleted, unresolved, redirected, or safety/security-relevant references.
7. Hand high-risk changes to the relevant domain reviewer and autosar-bsw-validation-tester.

Guardrails

• Do not treat formatting-only changes as functional changes.
• Do not infer compatibility from matching short names alone; verify destination and context.
• Flag changes whose effect cannot be assessed because the input set is partial.
• Never apply a candidate configuration while reviewing it.

Output

Provide scope, compared baselines, semantic change table, affected dependencies, risk-ranked findings, generated-code impact, regression recommendation, rollback considerations, and open questions.