SNIP_CLASSIC_PLATFORM_SECTION_4_2_4_General_Requirements

4.2.4 General Requirements [SRS_Com_02037] AUTOSAR COM module shall be based on the functionality and APIs of ISO-17356-4 ⌈ Description: The AUTOSAR COM module shall be based on the functionality and APIs specified in [1]. Specifications not done there, respectively specifications of functionality different from that specified in the above mentioned document shall be defined in the AUTOSAR COM SRS and SWS specifications. Features of [1] which are not provided by the AUTOSAR COM module shall be defined in [3]. Rationale: This SRS is only an add-on to [1] as an existing standard. Use Case: – Dependencies: – Supporting Material: [10], [1] ⌋ [SRS_Com_02078] The AUTOSAR COM module shall support endianness conversion ⌈ Description: The AUTOSAR COM module shall support endianness conversion for the following data types: • uint16 • uint32 • uint64 • sint16 • sint32 • sint64 • float32 • float64 Rationale: ensure end to end data consistency Use Case: – Dependencies: – Supporting Material: [11], [6] ⌋ [SRS_Com_02086] The AUTOSAR COM module shall support sign-extension ⌈ Description: Sign-Extension means, to map negative values of signed signals correctly, if the bit-size of the signal in an I-PDU received and the bit-size of the signal used in the interface of the receiving software component differ from each other. In this case, the size of the signal received shall be extended to the size of the receiver interface. The AUTOSAR COM module shall support Sign-Extension for the following data types: • sint8 • sint16 • sint32 Rationale: ensure end to end data consistency Use Case: – Dependencies: – Supporting Material: [11], [6] ⌋