## 4 Materials and Methods
### Management of Driver Preferences with Onto-CMS
#### 4.5.2 Use Case No. 2-Adjusting Emergency Pedal Icon for Enhanced Safety  
_Use case_: [PERSON] is a 60-year-old female with forty years of experience who drives cautiously and responsibly despite hearing loss and reduced peripheral vision. To overcome these difficulties, she is driving with the assistance of an ADAS using large, bright notifications and amplified audio alerts. To further improve her safety, she has customised the emergency pedal icon, increasing its size and contrast for better visibility. One afternoon, [PERSON] came across a junction that was very busy. Her ADAS system warned her of an approaching cyclist from one of the side streets. A large and bright hazard icon appeared on the central screen as an amplified audio warning pierced through the background noise of traffic and caught the attention of [PERSON]. A clear voice notification followed, emphasising the urgency and directing her attention to the obstacle. Algorithm 2 highlights how standardisation influences the reaction times in two driving simulations. In Scenario 1, the customised emergency pedal icon's high visibility allowed [PERSON] to react quickly, apply the brakes in time, and avoid an accident. In Scenario 2, the default icon's lower visibility delays her response, increasing the risk of a collision. _Objective_. This use case highlights how the Onto-CMS adaptively adjusts interface standardisation. While the emergency pedal icon is typically non-modifiable for safety reasons, the system recognised [PERSON]'s specific needs and selectively enabled her to customise the icon, enhancing its visibility and accessibility. _Use-case variants_. This scenario included two variations. In the first, **(A)**, the Onto-CMS identified [PERSON]'s visual and auditory requirements and dynamically allowed adjustmentsto critical elements like the emergency pedal icon, ensuring high visibility and quick response in emergencies. In the second, **(B)**, the Onto-CMS was not in use, preventing such adaptations and potentially compromising [PERSON]'s ability to respond effectively in critical situations. **Start Simulation**  
2: Initialise the Vehicle Assistance System  
**Scenario 1: [PERSON] modifies the emergency pedal icon (Large and High Contrast)**  
4: **Modify Icon:**  
**if** Icon size = large & Contrast = high **then**  
6: **Emergency Pedal Icon is highly visible:** \"Size = large, Contrast = high\"  
**Cyclist Detection:**  
**Algorithm 2** Output Simulation Use Case no 2  
**Algorithm 3** **Algorithm 4** Output Simulation Use Case no 2  
**Cyclicist Detection:**  
8: **if** Cyclist approaching from side street **then**  
Display visual warning: \"Warning: Cyclist approaching from a side street!\"  
10: **Display emergency pedal icon (size: large, high contrast)**  
**Action taken: Emergency brake activated! **  
12: **end if**  
14: **Scenario 2: [PERSON] does not modify the emergency pedal icon (Default visibility)**  
**Modify Icon:**  
16: **if** Icon size = default & Contrast = normal **then**  
**Emergency Pedal Icon is poorly visible:** \"Size = default, Contrast = normal\"  
18: **Cyclist Detection:**  
**if** Cyclist approaching from side street **then**  
20: **Display visual warning: \"Warning: Cyclist approaching from a side street!\"  
Display emergency pedal icon (size: default, normal contrast)**  
22: **Action delayed: Accident may occur. **  
**end if**  
**End Simulation**  
**Algorithm 4** Output Simulation Use Case no 2  
**(A)** _Correcting DVI Standardisation Through Onto-CMS Implementation_  
The Onto-CMS ensures compliance with safety-driven standardisation. However, it allows the driver to modify the features of the emergency pedal icon under specific conditions, such as visual impairments. When the Onto-CMS detects [PERSON]'s sensory challenges, it enables her to customise the emergency pedal icon for enhanced visibility and usability.