************
Introduction
************

In this chapter you can find information about the intended use, the addressed target group and information about safety and privacy related topics.

Intended Use
#####################

RTA-SQF (Safety Qualification Framework) is a static analysis tool that checks whether an ETAS RTA-CAR project 
fulfils the Assumptions of Use (AoU) defined in the RTA-CAR Safety Manuals. 

RTA-CAR is designed for use in safety-critical systems up to ISO 26262 ASIL D; 
the associated Safety Manuals define AoUs that the user must satisfy. 

RTA-SQF automates the verification of these AoUs and reports any violations or items requiring review.

.. note:: Supported AoUs

   The set of AoUs supported by RTA-SQF is not exhaustive. Additional AoUs are added with each new release. Refer to the release notes for the current list of supported AoUs.

Target Group
#####################

This product is intended for skilled and qualified personnel developing safety-critical ECU Software using RTA-CAR. A strong familiarity with both RTA-CAR and the specific ECU software is a prerequisite.

Related Documents
#####################

This document is intended to be read together with the RTA-CAR Safety Manuals and User Guides.

Document Conventions
#####################

.. note::

    Notes that appear like this describe special things and cases which are relevant in context of the topic where the note is placed.

In general examples or exemplary calling options of RTA-SQF will appear with *italic* notation. Relevant terms and items are set to **bold**.

Acronyms and Abbreviations
##########################

============= ====================================================================================
 **AUTOSAR**   AUTomotive Open System ARchitecture - a standardized software architecture
               targeted at automotive applications aimed at fostering the reuse of application
               software over multiple vehicle platforms. See :cite:t:`AUTOSAR`.
 **AoU**       Assumption of Use - individual requirement from the Safety Manual
 **ARXML**     XML eXtensible Markup Language used to describe AUTOSAR configurations
 **BSW**       An AUTOSAR Basic SoftWare module
 **LiMa**      ETAS License Manager, needed to run RTA-SQF
 **RTE**       AUTOSAR Run-Time Environment
 **RTEGen**    The ETAS AUTOSAR RTE generator tool responsible for reading the AUTOSAR XML
               configuration and generating the RTE and associated C header files
 **RTA-CAR**   RTA Classic AUTOSAR Solution: Integrated environment from ETAS GmbH to configure
               and generate the Classic AUTOSAR stack for ECUs
 **RTA-FSQP**  Functional Safety Qualification Package from ETAS GmbH
 **RTA-OS**    An AUTOSAR SC1-SC4 and OSEK 2.2.3 compatible operating system from ETAS GmbH.
 **RTA-RTE**   The ETAS AUTOSAR RTE Generator Product. This includes the AUTOSAR RTE Generator
               Tool responsible for reading the AUTOSAR XML configuration and generating the
               RTE and associated C header files. RTA-RTE distributions also include the RTE
               library, all user documentation and several example applications.
 **RTA-SQF**   Safety Qualification Framework
 **SchM**      BSW Scheduler (a BSW module defined by AUTOSAR)
 **SWC**       An AUTOSAR Software component
============= ====================================================================================

Data Protection
#####################

If the product contains functions that process personal data, legal requirements of data protection and data privacy laws shall be complied with by the customer. As the data controller, the customer usually designs subsequent processing. Therefore, he must check if the protective measures are sufficient.

Data and Information Security
##############################

To securely handle data in the context of this product, see the next sections about data and storage locations as well as technical and organizational measures.

Data and Storage Locations
##########################

The following sections give information about data and their respective storage locations for various use cases.

License Management
*********************

When using the ETAS License Manager in combination with user-based licenses that are managed on the FNP license server within the customer's network, the following data are stored for license management purposes:

**Data:**

* Communication data: IP address
* User data: User ID

**Storage location:**

* FNP license server log files on the customer network

When using the ETAS License Manager in combination with host-based licenses that are provided as FNE machine-based licenses, the following data are stored for license management purposes:

**Data:**

* Activation data: Activation ID
* Used only for license activation, but not continuously during license usage

**Storage location:**

* FNE trusted storage

  * Windows: C:\\ProgramData\\ETAS\\FlexNet\\fne\\license\\<hostID>
  * Linux: /usr/share/ETAS/LiMa/fne/license/<hostID>


Technical and Organizational Measures
******************************************

We recommend that your IT department takes appropriate technical and organizational measures, such as classic theft protection and access protection to hardware and software.