Abstraction
This chapter provides requirements for the function of the System Logging Support.
In the use of IVI products, it is necessary to collect and centrally manage logs created in multiple places in the system, which are records of various events and times that occurred in systems. The reasons to keep logs are for security measures or information gathering and decision making in the operation, management and countermeasure for anomalies of the product system.
Use case
In the following table, use cases which need System Logging Support function are described.
As use cases, two cases need to be assumed: before and after product shipment.
| # | Item | User |
|---|---|---|
| 1 | Developers check the logs for implementation and evaluation to debug. | OEM/Developer(Before product shipment) |
| 2 | From a security perspective, OEM examines the logs to investigate whether there has been unauthorized access to the system from outside. | OEM/Developer(After product shipment) |
| 3 | When some anomaly in the system requires a measure to a product failure, OEM investigates the cause of the problem. | OEM/Developer(After product shipment) |
#1 : Before product shipment
#2, 3 : After product shipment
Functional Requirements
This table includes the functional requirements of System Logging support module.
| # | Item | |
|---|---|---|
1 | Use case #1, 2 | When ACC-OFF, log from system startup to shutdown should be saved in the defined directory. |
2 | Use case #1, 3 | When system anomaly is detected, error detection log should be kept. |
3 | Use case #1, 2, 3 | Where to store logs should be defined. |
4 | Use case #1, 2, 3 | Considering the endurance, the log should be recorded in the volatile memory and recorded in the non-volatile memory as necessary. |
System Logging Support in Basesystem
Reference implementation in Basesystem
The following functions are related to the System Logging Support function in Basesystem.
- Logger service
Logger Service
Logger service is the unit to collect the log, save in a non-volatile area (USB/SD). When receiving the storing request, Logger service reads the log generated by other modules and saves it.
Reference code
Logger service