SNIP_CLASSIC_MEMIF_SECTION_6_Requirements_Tracing

6 Requirements Tracing The following tables reference the requirements specified in [6, SRS SPALGeneral], [7, SRS BSWGeneral], [8, SRS MemoryHWAbstraction] and links to the fulfillment of these. Please note that if column ”Satisfied by” is empty for a specific requirement this means that this requirement is not fulfilled by this document. Requirement Description Satisfied by [SRS_BSW_00323] All AUTOSAR Basic Software Modules shall check passed API parameters for validity [SWS_MemIf_00022] [SRS_BSW_00327] Error values naming convention [SWS_MemIf_00006] [SRS_BSW_00337] Classification of development errors [SWS_MemIf_00006] [SRS_BSW_00369] All AUTOSAR Basic Software Modules shall not return specific development error codes via the API [SWS_MemIf_00024] [SRS_BSW_00384] The Basic Software Module specifications shall specify at least in the description which other modules they require [SWS_MemIf_00047] [SRS_BSW_00385] List possible error notifications [SWS_MemIf_00048] [SRS_BSW_00386] The BSW shall specify the configuration and conditions for detecting an error [SWS_MemIf_00006] [SWS_MemIf_00023] [SRS_BSW_00392] Parameters shall have a type [SWS_MemIf_00037] [SWS_MemIf_00064] [SWS_MemIf_00065] [SRS_BSW_00407] Each BSW module shall provide a function to read out the version information of a dedicated module implementation [SWS_MemIf_00045] [SRS_MemHwAb_ 14010] The FEE and EA modules shall provide a write service that operates only on complete configured logical blocks [SWS_MemIf_00040] [SRS_MemHwAb_ 14019] The Memory Abstraction Interface shall provide uniform access to the API services of the underlying memory abstraction modules [SWS_MemIf_00017] [SRS_MemHwAb_ 14020] The Memory Abstraction Interface shall allow the selection of an underlying memory abstraction module by using a device index [SWS_MemIf_00011] [SWS_MemIf_00018] [SWS_MemIf_00035] [SRS_MemHwAb_ 14021] The Memory Abstraction Interface shall allow the pre-compile time configuration of the number of underlying memory abstraction modules [SWS_MemIf_00018] [SWS_MemIf_00019] [SWS_MemIf_00020] [SWS_MemIf_00022] [SRS_MemHwAb_ 14022] The Memory Abstraction Interface shall preserve the functionality of the underlying memory abstraction module [SWS_MemIf_00010] [SWS_MemIf_00017] [SWS_MemIf_00039] [SWS_MemIf_00040] [SWS_MemIf_00041] [SWS_MemIf_00042] [SWS_MemIf_00043] [SWS_MemIf_00044] [SWS_MemIf_00046] [SRS_MemHwAb_ 14023] The Memory Abstraction Interface shall only check those parameters that are used within the interface itself [SWS_MemIf_00022] ▽ △ Requirement Description Satisfied by [SRS_MemHwAb_ 14028] The FEE and EA modules shall provide a service to invalidate a logical block [SWS_MemIf_00044] [SRS_MemHwAb_ 14029] The FEE and EA modules shall provide a read service that allows reading all or part of a logical block [SWS_MemIf_00039] [SRS_MemHwAb_ 14031] The FEE and EA modules shall provide a service that allows canceling an ongoing asynchronous operation [SWS_MemIf_00041] [SRS_MemHwAb_ 14032] The FEE and EA modules shall provide an erase service that operates only on complete logical blocks containing immediate data [SWS_MemIf_00046] [SRS_SPAL_12078] The drivers shall be coded in a way that is most efficient in terms of memory and runtime resources [SWS_MemIf_00019] [SWS_MemIf_00020] [SRS_SPAL_12448] All driver modules shall have a specific behavior after a development error detection [SWS_MemIf_00023] Table 6.1: Requirements Tracing