<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-04-18T07:53:37Z</responseDate><request verb="GetRecord" identifier="oai:www.recercat.cat:10459.1/468753" metadataPrefix="didl">https://recercat.cat/oai/request</request><GetRecord><record><header><identifier>oai:recercat.cat:10459.1/468753</identifier><datestamp>2025-10-09T18:36:35Z</datestamp><setSpec>com_2072_3622</setSpec><setSpec>col_2072_479130</setSpec></header><metadata><d:DIDL xmlns:d="urn:mpeg:mpeg21:2002:02-DIDL-NS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="urn:mpeg:mpeg21:2002:02-DIDL-NS http://standards.iso.org/ittf/PubliclyAvailableStandards/MPEG-21_schema_files/did/didl.xsd">
   <d:DIDLInfo>
      <dcterms:created xmlns:dcterms="http://purl.org/dc/terms/" xsi:schemaLocation="http://purl.org/dc/terms/ http://dublincore.org/schemas/xmls/qdc/dcterms.xsd">2025-10-09T18:36:35Z</dcterms:created>
   </d:DIDLInfo>
   <d:Item id="hdl_10459.1_468753">
      <d:Descriptor>
         <d:Statement mimeType="application/xml; charset=utf-8">
            <dii:Identifier xmlns:dii="urn:mpeg:mpeg21:2002:01-DII-NS" xsi:schemaLocation="urn:mpeg:mpeg21:2002:01-DII-NS http://standards.iso.org/ittf/PubliclyAvailableStandards/MPEG-21_schema_files/dii/dii.xsd">urn:hdl:10459.1/468753</dii:Identifier>
         </d:Statement>
      </d:Descriptor>
      <d:Descriptor>
         <d:Statement mimeType="application/xml; charset=utf-8">
            <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
               <dc:title>End-users perspective matters in ADAS: designing a blind-spot alert system from a user-centered approach</dc:title>
               <dc:creator>Pires, Felipe</dc:creator>
               <dc:creator>Lisboa, Pedro</dc:creator>
               <dc:creator>Ribeiro, Herick</dc:creator>
               <dc:creator>Campos, Pietro</dc:creator>
               <dc:creator>González Capdevila, Marc</dc:creator>
               <dc:subject>Notification System</dc:subject>
               <dc:subject>User Experience</dc:subject>
               <dc:subject>Advanced Driver Assistance System</dc:subject>
               <dc:description>The number of traffic accidents involving motorcycles has been increasing in Brazil recently. Many accidents are caused by drivers who do not see motorcycles approaching in the vehicle blind spots. Advanced Driver Assistance Systems (ADAS) installed in vehicles can be used to mitigate this problem. However, the development of ADASs often focuses on security issues and does not consider the user experience with the ADASs interface. In this paper, we present the design of an alerting system that warns drivers about collision risks when motorcycles are identified in vehicle blind spots. Our proposal alerts drivers by using visual and haptic interaction modes. In line with a user-centered design methodology, our initial action involved identifying the traits of the target users in order to create personas that embody their characteristics. The vehicle blind spot alert system was conceived in a co-design session using the personas elaborated previously. In the session, 9 end-users produced 3 low-fidelity (lo-fi) prototypes which were analyzed and compiled generating a single lo-fi prototype. After promoting a viability discussion, a high-fidelity (hi-fi) prototype containing haptic and visual alerting features was implemented and installed in a car for testing. The alert system was evaluated by 20 end-users concerning their experience with the different warning modes. The results showed that for both the visual and haptic modes, users could recognize and understand the alerts without employing a great effort in the information interpretation. This result reinforces the idea that ADASs should provide simple interpretative interfaces because drivers' interaction with these systems should be a secondary activity since their concentration must be on driving.</dc:description>
               <dc:description>This research was funded by Fundação de Desenvolvimento da Pesquisa (FUNDEP - Processo no.: 27192.02.01/2020.08-00). The Conselho Nacional de Desenvolvimento Científico e Tecnológico - Brazil (CNPq grant 309497/2022-1) provided partial financial support.</dc:description>
               <dc:date>2025-10-09T18:36:35Z</dc:date>
               <dc:date>2025-10-09T18:36:35Z</dc:date>
               <dc:date>2025</dc:date>
               <dc:type>info:eu-repo/semantics/article</dc:type>
               <dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
               <dc:identifier>http://hdl.handle.net/10459.1/468753</dc:identifier>
               <dc:relation>Reproducció del document publicat a https://doi.org/10.5753/jbcs.2025.4365</dc:relation>
               <dc:relation>Journal of the Brazilian Computer Society, 2025, vol. 31, núm. 1, p. 50–67</dc:relation>
               <dc:rights>cc-by (c) Felipe Pires et al., 2025</dc:rights>
               <dc:rights>Attribution 4.0 International</dc:rights>
               <dc:rights>info:eu-repo/semantics/openAccess</dc:rights>
               <dc:rights>http://creativecommons.org/licenses/by/4.0/</dc:rights>
               <dc:publisher>Sociedade Brasileira de Computação</dc:publisher>
            </oai_dc:dc>
         </d:Statement>
      </d:Descriptor>
   </d:Item>
</d:DIDL></metadata></record></GetRecord></OAI-PMH>