Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Abstraction

This chapter provides requirements for backup management functions.

Data needs to be secured in products to prevent data corruption due to failures. Backing up the necessary data on a regular basis will help maintain the reliability of the product.

Use case

In the following table, use cases which need the backup management for services are described.

#

Item

User

1

A user changes the language display of the IVI from English to Japanese. By backing up the configuration data in the system, the user does not have to set the language display to Japanese every time the user uses IVI.

Driver

2

If a user wants to delete the data backed up in the IVI, the user uses the system reset function.

Driver

3

Developers check during development if the backup data can be saved correctly.

OEM/Developer(Before product shipment)

Functional Requirements

This table includes the functional requirements of Persistent notification and backup management module.

#

Item

1

IVI needs the ability to back up the data it needs, when it needs it.

2

The required data in #1 includes, for example, the following, but each data is specified by each OEM.

(e.g., time display method, Bluetooth pairing information, IVI screen theme color settings, etc.)

3

The following are examples of required timing for #1, but each data shall be specified by each OEM.
(e.g., when IVI is turned off, periodic backups, etc.)

  • No labels