Understanding of software diagnostics: module states and limitations, performance expectations, timing constraints, latency, reaction timing, accuracy, detection ranges, functional purposes, activation/deactivation conditions, driver override capability, transitions, environmental constraints, Diagnostic DTC/DID/RID definitions, detection condition, recovery rules, display/notification concepts, emergency operations. The feature/ function requirements decomposed to the module-level need to be captured and managed formally in QLAH, which will include subsystem block diagrams, main components, connectivity, power paths, communication buses, interface relationships, data/control flow, and a signal-level block diagram including all input/output signals.