Which statement about databases is INCORRECT?

Communication databases (e.g., CAN DBC, LIN LDF, ASAM FIBEX) define the application-layer data content for a vehicle network. This includes specifying messages, the signals they contain, scaling factors, and the relationships between ECUs (Electronic Control Units). However, these databases do not define the implementation of the communication protocol itself. The protocol implementation, which covers the rules for data framing, bus arbitration, error handling, and physical signaling (OSI Layers 1 and 2), is dictated by standards like ISO 11898 for CAN and is realized in the hardware (transceivers) and low-level software drivers of the ECUs.

A. This is incorrect because the primary purpose of a communication database is to describe the signals (e.g., engine speed, wheel angle) and how they are encoded into messages for transmission over a communication channel.
C. This is incorrect because these databases explicitly map which ECUs send (output) and receive (input) specific signals, forming the basis for system-wide communication and integration testing.
D. This is incorrect because the Association for Standardization of Automation and Measuring Systems (ASAM) provides standards like FIBEX (Field Bus Exchange Format), an XML-based format used to describe automotive networks, as an alternative to proprietary formats like DBC. ---

1. ISTQB® Certified Tester Foundation Level Automotive Software Tester Syllabus, Version 1.0 (2018), Section 3.2.2 Bus systems, p. 26. This section states, "The communication is described in specific description files (e.g., DBC for CAN, LDF for LIN, FIBEX for FlexRay)." This confirms that databases describe the communication content (signals, messages), not the protocol's fundamental implementation.

2. Lawrenz, W. (2016). CAN and CANopen. Springer Vieweg. In Chapter 2, "The CAN Protocol," the text details the ISO 11898 standard which defines the protocol's data link and physical layers. In contrast, Chapter 4, "Higher Layer Protocols," discusses the application layer where signal and message definitions, typically stored in a DBC file, reside. This illustrates the clear separation between the protocol definition and the database content.

3. ASAM e.V. (2020). ASAM FIBEX V4.1.1, Field Bus Exchange Format. The introduction and scope sections of this standard specify that FIBEX is used for "describing automotive communication networks," including signals, messages, and network topology. It is a data description standard, not a protocol implementation standard.

4. Zimmermann, W., & Schmidgall, R. (2014). Bussysteme in der Fahrzeugtechnik (5th ed.). Springer Vieweg. Chapter 5, "CAN-Grundlagen," explains that the CAN protocol is defined by ISO 11898. Chapter 5.8, "Applikationsprofile und DBC-Dateien," clarifies that DBC files describe the application-specific data (signals and messages) transmitted using the underlying, separately defined CAN protocol. (DOI: https://doi.org/10.1007/978-3-658-02419-2)