Testing & Development Skills

AUTOSAR Classic BSW expert that operates in four modes: (1) BSW configuration — step-by-step config for Com, NvM, Dem, Dcm, Os, MemIf with dependency chain, container paths in EB Tresos / DaVinci, parameter table, and common error resolutions; (2) ARXML debugging — classify and locate consistency errors (missing references, type mismatches, ComSpec issues, runnable/event mismatches, duplicate short-names, schema violations) and produce a corrected ARXML fragment with prevention rule; (3) RTE generation troubleshooting — diagnose EB Tresos / DaVinci generator failures across pre-gen, contract-phase, implementation-phase, and post-gen build steps with concrete configuration fixes; (4) COM stack debugging — structured layer-walk through CanDrv → CanIf → PduR → Com → RTE for missing, wrong, stale, or intermittent CAN signals, both RX and TX directions, with bus-level pre-check and probe instrumentation.

AUTOSAR Classic SWC expert that operates in five modes: (1) Component design — decompose a feature into SWC types (Application / Sensor-Actuator / Service / CDD / Composition), define port interfaces, specify runnables and ExclusiveAreas, and produce a plain-text composition diagram; (2) Interface definition — specify SenderReceiver / ClientServer / ModeSwitch / Parameter interfaces with correct AUTOSAR data types, scaling, units, InitValues, and AliveTimeout, producing ARXML-sketch and matching C typedef header; (3) SWC development — generate a production-ready SWC skeleton (.c + .h + ARXML) with correct RTE API calls, AUTOSAR platform types, and MISRA-aligned style; (4) Diagram generation — produce plain-text box-and-arrow component / sequence diagrams and ASCII state machines (no Mermaid / PlantUML rendering dependency) with AUTOSAR layer boundaries, ISR / Task markers, and ASIL notes; (5) Integration review — audit C source and ARXML for SWC typing, port interface alignment, RTE API naming, runnable-to-event mapping, MCAL abstraction violations, and data-type compliance. Targets EB Tresos and Vector DaVinci Developer toolchains.

Change-management expert that operates in two modes: (1) CR analysis — take a change request / ECN / feature brief and produce affected-element list, ASIL impact, implementation plan with owner hints and complexity, test plan delta, and integration risks; (2) Impact analysis — trace a specific change through every layer (SWCs, BSW modules, ARXML interfaces, requirements, tests, safety artefacts), distinguishing direct impacts (must change) from indirect impacts (must review or retest), and recommend a regression scope (Minimal / Targeted / Full). Applies ASPICE SWE.6 and ISO 26262-6 §7.4 / -8 §8.4 change practices.

Senior embedded debugging expert that operates in two modes: (1) Problem-report triage — take a field PR / bug ticket and produce symptom classification, affected-element mapping, ranked hypotheses, data-collection plan, and step-by-step investigation; (2) Targeted fault debugging — accept a specific fault signature (watchdog reset, HardFault, wrong output value, Dem event, stack overflow, AUTOSAR OS error, linker hang) and give concrete debugging steps with GDB/TRACE32 commands, code patterns to inspect, ranked root-cause candidates, and a minimal reproduction strategy. Covers ARM Cortex-M/R targets, AUTOSAR OS (EB Tresos, Vector), and common BSW/RTE failure modes.

Embedded test-design expert that operates in two modes: (1) Unit-test generation — analyse a C function for decisions and conditions, produce test cases achieving MC/DC coverage (required for ASIL-C/D), add boundary and error-path tests, provide RTE/BSW stub declarations, and output a coverage matrix; (2) Boundary value analysis — compute MIN, MIN+1, nominal, MAX-1, MAX, and out-of-range points for every typed numeric parameter (uint8/sint8/uint16/sint16/uint32/sint32 and fixed-point), and identify overflow, wrap-around, truncation, and sign-extension risks with triggering inputs and safe fixes. Test output is compatible with Unity, CppUTest, and VectorCAST patterns.

ISO 26262 functional-safety expert that operates in two modes: (1) HARA / ASIL determination — enumerate hazardous events from item malfunctions × driving situations, rate Severity (S0–S3), Exposure (E0–E4), Controllability (C0–C3), look up ASIL from ISO 26262-3:2018 Table 4, and produce a HARA report with Safety Goals; (2) Safety Goals & FSC — translate hazardous events and ASIL into well-formed Safety Goals with safe state, Fault Tolerant Time Interval (FTTI = FDTI + FRTI), Emergency Operation Time Interval (EOTI), and high-level Functional Safety Requirements allocated to system elements. Both modes cover ASIL decomposition applicability per Part 9 §5.

MISRA C:2025 expert that operates in two modes: (1) Review — scan existing C code for violations across all ~223 guidelines (22 directives + ~201 rules), report findings with rule IDs, corrected code, and deviation justification templates; (2) Develop — generate new C functions, modules, or data structures that are MISRA-compliant from the first line, applying the essential type model, safe control flow, and banned-construct avoidance from the start. Covers C:2023 base (C:2012 + Amd1 security + Amd2/Amd3 C11/C18 + Amd4 multithreading) plus the four C:2025 additions (Rules 8.18, 8.19, 11.11, 19.3), Rule 15.5 disapplication, and 69 refined guidelines.