<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Verolt</title>
	<atom:link href="https://www.verolt.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.verolt.com/</link>
	<description></description>
	<lastBuildDate>Fri, 19 Jun 2026 05:06:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.10</generator>

<image>
	<url>https://www.verolt.com/wp-content/uploads/2024/03/verolt-favicon.svg</url>
	<title>Verolt</title>
	<link>https://www.verolt.com/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Qt/QML HMI Development for Embedded Automotive Interfaces</title>
		<link>https://www.verolt.com/blog/qt-qml-hmi-development-embedded-automotive-interfaces/</link>
		
		<dc:creator><![CDATA[Aditya Gosavi]]></dc:creator>
		<pubDate>Thu, 04 Jun 2026 13:31:57 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[HMI]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=3322</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/blog/qt-qml-hmi-development-embedded-automotive-interfaces/">Qt/QML HMI Development for Embedded Automotive Interfaces</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144af78a8c"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row top-level"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Modern vehicles need interfaces that do more than look good on a screen. Infotainment systems, digital clusters, navigation, media, climate controls, warning indicators, and vehicle settings must work together in real time, across embedded Linux and MCU-based platforms.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">That makes automotive HMI development a serious engineering challenge. The interface must be visually intuitive, fast to respond, stable on hardware, and synchronized with live vehicle data. This is where <strong>Qt/QML-based HMI development</strong> becomes valuable.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Because in the next generation of vehicles, the best HMI will not be the one with the most polished graphics. It will be the one that performs reliably when the vehicle is actually running.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af79ed9"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p style="text-align: justify;">Why Automotive HMI Development Is Getting More Complex<br />
Automotive HMI has moved beyond basic display screens. Earlier, a cluster showed speed and warnings, infotainment handled media, and climate controls often remained physical. Today, these boundaries are fading.<br />
Modern vehicles are moving toward integrated digital cockpits where multiple systems must work as one connected experience: infotainment, instrument clusters, navigation, media, climate control, vehicle settings, personalization, warning indicators, and vehicle status displays.<br />
For the driver, these are not separate software modules. They are one cockpit experience.<br />
This creates a deeper engineering challenge. The HMI must process live vehicle signals, respond to user inputs, manage multiple states, show priority alerts, and perform consistently on embedded hardware.<br />
A warning indicator cannot lag because an animation is running. A speed value cannot update inconsistently across screens. A climate control interaction cannot feel slow when the driver needs a quick adjustment. That is why automotive HMI development now sits at the intersection of <strong>UI architecture, embedded software, real-time data integration, rendering performance, and hardware validation.</strong></p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af7ab2b"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Where Qt/QML Fits in Embedded Automotive HMI<br />
Qt/QML gives automotive teams a practical way to build responsive, state-driven, and visually rich interfaces while keeping the UI layer separate from backend logic.<br />
In a typical embedded HMI architecture:</p>
<ul class="&#091;li_&amp;&#093;:mb-0 &#091;li_&amp;&#093;:mt-1 &#091;li_&amp;&#093;:gap-1 &#091;&amp;:not(:last-child)_ul&#093;:pb-1 &#091;&amp;:not(:last-child)_ol&#093;:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" style="text-align: justify;">
<li class="font-claude-response-body whitespace-normal break-words pl-2">QML manages the interface layer</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Qt Quick supports dynamic UI behavior, animations, and reusable components</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Modern C++ handles backend services, application logic, data processing, and performance-critical functions</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Qt signal-slot mechanisms support communication between application objects</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Qt D-Bus can support service communication in Linux-based environments</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Qt for MCUs and Qt Quick Ultralite support UI development for resource-constrained platforms</li>
</ul>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">This separation is important because cockpit systems are rarely static. They must respond to vehicle signals, user actions, service updates, system settings, localization, and hardware-specific behavior.<br />
The real value of Qt/QML is not just faster interface development. It is the ability to build <strong>HMI architecture that is modular, reusable, scalable, and connected to real-time embedded systems.</strong></p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p style="text-align: justify;">The diagram below illustrates how these layers connect in a typical Qt/QML-based automotive HMI application:</p>
	</div>
</div>



<div class="img-with-aniamtion-wrap center custom-size" data-max-width="100%" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img fetchpriority="high" decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="825" width="1024" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2026/06/QtQML_Automotive_Application_Architecture-1024x825.png" alt="Qt/QML Automotive HMI Application Architecture Diagram" srcset="https://www.verolt.com/wp-content/uploads/2026/06/QtQML_Automotive_Application_Architecture-1024x825.png 1024w, https://www.verolt.com/wp-content/uploads/2026/06/QtQML_Automotive_Application_Architecture-300x242.png 300w, https://www.verolt.com/wp-content/uploads/2026/06/QtQML_Automotive_Application_Architecture-768x619.png 768w, https://www.verolt.com/wp-content/uploads/2026/06/QtQML_Automotive_Application_Architecture-1536x1238.png 1536w, https://www.verolt.com/wp-content/uploads/2026/06/QtQML_Automotive_Application_Architecture-2048x1650.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" />
          </div>
        </div>
      </div>
    </div>
			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af7d989"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">From Infotainment to Instrument Clusters: Key HMI Use Cases</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Qt/QML-based HMI development supports a wide range of cockpit applications, each with different performance expectations.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Infotainment systems need media controls, navigation interfaces, phone connectivity, system settings, notifications, and personalization modules. Instrument clusters need speed display, fuel level, warning indicators, ride data, drive mode, and system status. Other HMI modules include climate control, vehicle status screens, navigation and media split-screen layouts, driver alerts, and system preferences.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">The challenge is that each screen behaves differently. Infotainment can support richer visuals and deeper interactions. A digital cluster needs fast updates, high reliability, and clear visual hierarchy. Climate HMI needs quick access and minimal driver distraction.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">This is where <strong>reusable QML components</strong> make a difference. Gauges, cards, warning indicators, sliders, media controls, and status modules can be built once and adapted across screen sizes, orientations, and vehicle variants.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">At Verolt, our embedded HMI capability spans infotainment interfaces, instrument clusters, system settings, personalization modules, navigation and media screens, climate HMI, vehicle status displays, warning indicators, and performance-critical data visualization across MCU and embedded Linux platforms.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af7e8df"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Real-Time Vehicle Data Integration in HMI Systems</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">A modern automotive HMI is only as strong as the data pipeline behind it. The interface must reflect vehicle signals such as speed, fuel level, warning indicators, navigation updates, media state, ride data, and system information — with low latency and high consistency.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">The system must also decide how data flows, how often the UI updates, how warnings are prioritized, and how different modules stay synchronized.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">A speedometer needs smooth, continuous updates. A fuel warning needs clear visibility and correct timing. Media updates can be lower priority than safety-related alerts. Navigation must stay responsive without disturbing critical vehicle signals.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Qt/QML-based systems support this through structured backend services, signal-slot communication, Qt D-Bus integration, and controlled data binding between C++ services and QML components.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">But <strong>implementation discipline matters.</strong> Poorly managed bindings, excessive UI refreshes, or blocking backend operations can affect responsiveness. The goal is not just to display vehicle data. It is to display it accurately, predictably, and without compromising the rest of the interface.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af7f666"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Embedded Linux and MCU Platforms Need Different HMI Thinking</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Not every embedded platform behaves the same way. Embedded Linux systems and MCU-based platforms have very different constraints.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Embedded Linux platforms are suited for advanced infotainment systems, multimedia applications, navigation, connectivity, service-based architectures, and larger, richer display environments.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">MCU-based platforms require more discipline around memory usage, processing load, graphics capability, runtime resources, asset size, animation complexity, screen transitions, and rendering behavior.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Qt for MCUs and Qt Quick Ultralite help teams build graphical interfaces for microcontroller-based systems. But the HMI still needs to be designed for the hardware.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">An interface that works well on a desktop or high-performance Linux environment may not perform the same way on an MCU-based cluster. <strong>The best embedded HMI projects consider the target platform early.</strong> Architecture, component design, rendering strategy, data refresh behavior, and validation plans must reflect hardware realities from the beginning.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af803a6"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Why Performance Optimization Matters in Automotive HMI<br />
In automotive HMI, performance is not just a technical metric. It directly affects usability and trust. A delayed screen transition, unstable animation, slow climate response, or late warning update can make the cockpit feel unreliable.<br />
Performance optimization in Qt/QML development usually focuses on:</p>
<ul class="&#091;li_&amp;&#093;:mb-0 &#091;li_&amp;&#093;:mt-1 &#091;li_&amp;&#093;:gap-1 &#091;&amp;:not(:last-child)_ul&#093;:pb-1 &#091;&amp;:not(:last-child)_ol&#093;:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" style="text-align: justify;">
<li class="font-claude-response-body whitespace-normal break-words pl-2">Reducing unnecessary QML bindings</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Optimizing UI assets</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Avoiding heavy component nesting</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Keeping animations lightweight</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Preventing backend services from blocking the UI thread</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Managing memory carefully</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Prioritizing critical data updates</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Maintaining stable frame rates</li>
</ul>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">This is especially important on constrained embedded platforms. <strong>Stable rendering is not achieved through visual design alone. It comes from disciplined implementation.<br />
</strong>At Verolt, our HMI development approach includes efficient QML design, Qt Quick and Qt Quick Ultralite usage, reduced bindings, asset optimization, memory management, low-latency data processing, and optimized data flow from backend services to QML-based UI across MCU and embedded Linux platforms.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af8158a"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Building Scalable and Reusable QML Components</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Automotive programs rarely involve one screen for one vehicle. The same HMI foundation may need to support multiple trims, regions, screen sizes, orientations, hardware configurations, and vehicle variants.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">A strong component library can include gauges, warning indicators, menu blocks, list views, settings controls, media widgets, navigation modules, status cards, and climate control elements. These components can be reused across screens and adapted through properties, themes, layouts, and data models.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">The advantage is not only speed. Reusability improves consistency, reduces regression risk, and helps teams scale across multiple programs.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">But reusable components need balance. <strong>If they are too rigid, they fail across variants. If they are too generic, they become difficult to maintain.</strong> Good QML architecture gives teams flexibility without losing platform-specific precision.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af822bb"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Validation Beyond the Desktop Environment</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Desktop testing is useful during early HMI development, but it is not enough for production-ready automotive systems. The real test is how the interface behaves on target embedded hardware.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">An HMI can look smooth on a development machine and still show issues such as frame drops, memory pressure, touch delays, rendering inconsistencies, signal latency, synchronization gaps, and slow screen transitions.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Validation should also test edge cases: What happens when a backend service is delayed? What if a signal is unavailable? Does the UI show a safe fallback? Are warning indicators prioritized correctly? Does the interface remain stable during rapid state changes?</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">At Verolt, validation includes real embedded hardware platforms, including MCU-based and embedded Linux systems. Simulation environments and test setups are also used to evaluate <strong>responsiveness, rendering performance, latency, and real-time behavior</strong> before deployment.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af82f4d"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Driver-Friendly UI/UX in Automotive HMI Development</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">A strong automotive HMI is not the one that shows the most information. It is the one that shows the right information with the least cognitive effort.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Driver-friendly UI/UX needs glanceable layouts, clear visual hierarchy, predictable interactions, distraction-minimized screens, smooth but restrained motion, easy access to essential controls, clear warning visibility, and readable navigation and vehicle status data.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">This requires careful design judgment. Not every feature should be one tap away if it creates clutter. Not every interaction needs animation. Not every data point deserves the same visual priority.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;"><strong>Automotive UI design must be shaped by driving context.</strong> What looks attractive in a design review may not be effective inside a moving vehicle. That is why HMI development must combine UI design, usability thinking, safety-conscious interaction design, and embedded performance validation.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af83bb9"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Common Engineering Challenges in Qt/QML HMI Projects<br />
Qt/QML gives teams a strong development foundation, but successful delivery depends on how well the engineering challenges are handled.<br />
Common challenges include:</p>
<ul class="&#091;li_&amp;&#093;:mb-0 &#091;li_&amp;&#093;:mt-1 &#091;li_&amp;&#093;:gap-1 &#091;&amp;:not(:last-child)_ul&#093;:pb-1 &#091;&amp;:not(:last-child)_ol&#093;:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" style="text-align: justify;">
<li class="font-claude-response-body whitespace-normal break-words pl-2">Backend integration across vehicle signals, media, navigation, warnings, and settings</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Data synchronization across multiple screens</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Rendering delays caused by complex layouts or excessive bindings</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Memory limits on constrained platforms</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">UI scalability across different screen sizes and vehicle variants</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Hardware-specific behavior that appears late in testing</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2">Validation gaps between desktop simulation and target hardware</li>
</ul>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;"><strong>The strongest HMI programs address these concerns early.</strong> They treat data flow, UI architecture, platform constraints, performance, and validation as one connected engineering problem.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af8486f"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Why Verolt? Embedded HMI Development Needs UI Intelligence and Platform Discipline</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">At Verolt, we support embedded automotive HMI development across Qt/QML, Qt for MCUs, Modern C++, Qt D-Bus, Yocto-based embedded Linux environments, and real-time vehicle data integration.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Our work spans infotainment systems, instrument clusters, system settings, personalization modules, navigation and media screens, climate HMI, vehicle status displays, warning indicators, and performance-critical data visualization.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">For us, automotive HMI development is not just about creating screens. It is about <strong>building embedded interfaces that are intuitive, responsive to live vehicle data, stable on target hardware, and optimized for platform constraints.</strong></p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">By combining reusable QML components, backend service integration, low-latency data flow, rendering optimization, hardware-level validation, and Agile execution, we help automotive teams move from HMI concepts to production-ready embedded applications with greater confidence</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af851dc"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">The Future of Automotive HMI Is Real-Time, Scalable, and Embedded-Ready</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">The future of automotive HMI will not be defined only by larger displays, sharper graphics, or more features. It will be defined by how well the interface integrates with the vehicle.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Next-generation HMIs must respond to real-time data, perform reliably on embedded hardware, adapt across platforms, and help drivers interact with the vehicle more intuitively. This requires more than UI design. It requires architecture, backend integration, validation, performance optimization, and production-aware development.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;">Qt/QML-based HMI development gives automotive teams a strong foundation for this shift. It enables reusable components, dynamic interfaces, embedded deployment, and real-time data-driven behavior. But the quality of the final HMI depends on engineering discipline.</p>
<p class="font-claude-response-body break-words whitespace-normal leading-&#091;1.7&#093;" style="text-align: justify;"><strong>Because the automotive cockpit is no longer just a screen environment. It is a real-time embedded system.</strong> And the interfaces that succeed will be the ones that are not only beautifully designed, but also built to perform when every signal, screen, and interaction matters.</p>
	</div>
</div>




			</div> 
		</div>
	</div> 
</div></div>
		<div id="fws_6ad144af85b5a"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/blog/qt-qml-hmi-development-embedded-automotive-interfaces/">Qt/QML HMI Development for Embedded Automotive Interfaces</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Digital Twin Of Conference Room</title>
		<link>https://www.verolt.com/case-studies/digital-twin-of-conference-room/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 26 Jun 2024 05:55:49 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Data Engineering]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1600</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/digital-twin-of-conference-room/">Digital Twin Of Conference Room</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144af882e8"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144af8b47f" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Highlights</strong></p>
<p>The Bihag Conference Room Digital Twin project aims to revolutionize the management and optimization of conference room environments through advanced sensor technology and real-time data analysis. This initiative seeks to create a comprehensive virtual representation of the Bihag Conference Room, leveraging an array of sensors to continuously monitor and simulate the room&#8217;s dynamic environmental conditions. By capturing data on atmospheric conditions, pollution levels, brightness, carbon footprint, and occupancy, the project provides valuable insights for optimizing the room&#8217;s settings. These insights are crucial for enhancing the quality of meetings and improving energy efficiency, ensuring a comfortable and productive environment for users.</p>
<p>The real-time data collected from the sensors is meticulously analyzed to maintain optimal atmospheric conditions, balancing factors such as air quality and lighting. This continuous monitoring helps create an ideal environment for productivity and comfort. Additionally, the project tracks the room&#8217;s energy consumption, identifying opportunities to reduce the carbon footprint and promote sustainable practices.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Problem Statement </strong></p>
<p>Traditional conference room management relies on static information and manual adjustments, leading to suboptimal meeting conditions and energy wastage due to the lack of real-time insights. The absence of dynamic control over factors like air quality, brightness, and occupancy further exacerbates these inefficiencies. There is a critical need for an innovative solution that addresses these shortcomings by providing real-time monitoring and dynamic adjustments to optimize conference room environments.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Solution</strong></p>
<p>A comprehensive solution was developed to create a Digital Twin of the Bihag Conference Room, addressing the need for real-time monitoring and optimization of conference room environments. Raw data was collected using a hybrid method combining machine learning (ML) algorithms with various sensors, such as temperature, humidity, light sensors, and cameras. These sensors were strategically placed to monitor ambient conditions and occupancy levels. The collected data was transmitted to a central database on a cloud platform or local server, enabling real-time access and visualization.</p>
	</div>
</div>



<div class="img-with-aniamtion-wrap  custom-width-600px " data-max-width="custom" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="1200" width="1000" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2024/06/data-sheet-image.jpg" alt="" srcset="https://www.verolt.com/wp-content/uploads/2024/06/data-sheet-image.jpg 1000w, https://www.verolt.com/wp-content/uploads/2024/06/data-sheet-image-250x300.jpg 250w, https://www.verolt.com/wp-content/uploads/2024/06/data-sheet-image-853x1024.jpg 853w, https://www.verolt.com/wp-content/uploads/2024/06/data-sheet-image-768x922.jpg 768w" sizes="(max-width: 1000px) 100vw, 1000px" />
          </div>
        </div>
      </div>
    </div>
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Results</strong></p>
<p>The Bihag Conference Room Digital Twin project achieved significant success, culminating in a comprehensive set of deliverables. These included detailed coverage reports, real-time sensor data visualizations, occupancy predictions, and insights into environmental conditions. The meticulous data collection, pre-processing, and visualization process demonstrated a strong commitment to quality assurance, ensuring the reliability and accuracy of the virtual representation.</p>
<p>The project effectively implemented and tested a range of components, including temperature, humidity, light sensors, and ML-based people counting algorithms. This extensive effort involved rigorous analysis and validation procedures, ensuring the robustness and efficiency of the Digital Twin. The user-friendly GUI/UX screen and 3D room view provided comprehensive real-time data visualization, enhancing meeting quality and energy efficiency through innovative digital solutions. The successful execution of these tasks underscored the potential of digital innovation in creating smarter, more sustainable, and efficient meeting spaces.</p>
	</div>
</div>




		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/digital-twin-of-conference-room/">Digital Twin Of Conference Room</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Chatbot</title>
		<link>https://www.verolt.com/case-studies/chatbot/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 26 Jun 2024 05:49:49 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Data Engineering]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1593</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/chatbot/">Chatbot</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144af90068"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144af906d1" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Highlights</strong></p>
<p>Our chatbot is designed to take user queries and respond with appropriate answers, simulating human-like conversation. It integrates NLP to process and understand natural language inputs, enabling it to handle a wide range of queries effectively. The use of Machine Learning algorithms ensures that the chatbot evolves and adapts to provide more accurate responses based on past interactions.</p>
<p>By employing HTML/CSS for the frontend, the chatbot offers a polished and engaging user interface. JavaScript drives the interactivity, ensuring that the chatbot responds in real-time to user inputs. JSON facilitates efficient data interchange, making the communication<br />
between the chatbot and backend systems seamless.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Problem Statement </strong></p>
<p>To streamline user interactions and provide quick, accurate responses, there is a pressing need to avoid the cumbersome process of scrolling through buckets of FAQs and manual searching. The development of an intelligent chatbot capable of understanding voice input, text input, and, in the near future, image input is essential. A recent user survey highlighted the demand for a centralized, interactive solution that can effectively interpret diverse input methods and deliver appropriate answers promptly.</p>
<p>To address this need, we are developing a chatbot that leverages Natural Language Processing (NLP), Machine Learning, and advanced input recognition technologies. This chatbot will not only respond to text-based queries but will also handle voice inputs and,<br />
eventually, image inputs, providing a comprehensive solution for user inquiries.</p>
<p>The challenge lies in ensuring the chatbot&#8217;s accuracy, context awareness, and adaptability to different input types. Our goal is to create a robust, user-friendly, and efficient chatbot that significantly enhances user experience by minimizing the effort required to find<br />
information and providing instantaneous, relevant responses.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Solution</strong></p>
<p>A comprehensive solution was implemented to address the need for an intelligent, centralized chatbot capable of understanding voice, text, and image inputs. The development cycle followed the Agile Scrum methodology, promoting iterative development and continuous improvement of the chatbot&#8217;s capabilities and user interactions. Regular requirement review meetings ensured complete understanding and eliminated ambiguities through techniques like completeness and consistency checks.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Chatbot</strong></p>
<p>We utilized TensorFlow for Natural Language Processing (NLP) and Machine Learning due to its open-source nature, extensive library support, and ease of integration with various input recognition tools. TensorFlow&#8217;s robust capabilities empowered the creation of sophisticated models for accurate and context-aware user query processing.</p>
<p>For the user interface, we employed a combination of HTML/CSS and JavaScript to build a responsive and user-friendly environment. The chatbot&#8217;s frontend was designed to handle real-time interactions seamlessly, ensuring a smooth user experience. JSON was used for<br />
data interchange, facilitating efficient communication between the frontend and backend systems.</p>
<p>Voice input processing was integrated using Google Cloud Speech-to-Text, enabling the chatbot to understand and respond to spoken queries. For future image input capabilities, we are developing models using TensorFlow&#8217;s computer vision tools to recognize and<br />
interpret visual information effectively.</p>
<p>Visual Studio Code, a versatile and open-source development environment, was chosen for its support of multiple programming languages and debugging tools. GitLab was selected for its CI/CD capabilities, issue tracking integration, and centralized storage of code, documentation, and test artifacts.</p>
<p>The development team employed established techniques like keyword extraction, sentiment analysis, and context-aware processing alongside advanced methods like deep learning, reinforcement learning, and natural language understanding to ensure the chatbot&#8217;s accuracy and responsiveness. Furthermore, the solution was equipped to handle complex scenarios involving multi-turn conversations and ambiguous queries. Regular regression testing was conducted to safeguard against regressions or defects</p>
	</div>
</div>



<div class="img-with-aniamtion-wrap  custom-width-700px " data-max-width="custom" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="483" width="836" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2024/06/cd-1.jpg" alt="" srcset="https://www.verolt.com/wp-content/uploads/2024/06/cd-1.jpg 836w, https://www.verolt.com/wp-content/uploads/2024/06/cd-1-300x173.jpg 300w, https://www.verolt.com/wp-content/uploads/2024/06/cd-1-768x444.jpg 768w" sizes="(max-width: 836px) 100vw, 836px" />
          </div>
        </div>
      </div>
    </div>
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Results</strong></p>
<p>The chatbot underwent extensive testing, resulting in the delivery of a comprehensive set of artifacts. This included detailed coverage reports, test results, test cases, defect reports, and summary reports. Additionally, a thorough overview of the entire testing process was provided. These deliverables demonstrate a strong commitment to quality assurance throughout the development lifecycle, ensuring the robustness and reliability of the chatbot.<br />
The project successfully implemented and tested the chatbot&#8217;s capabilities in understanding and responding to voice and text inputs. This included the integration of NLP, Machine Learning models, and voice recognition features. The chatbot&#8217;s performance was validated through rigorous testing procedures, ensuring accuracy, context awareness, and responsiveness in a variety of user interaction scenarios. Future enhancements are planned to incorporate image input capabilities, further expanding the chatbot&#8217;s versatility and utility.</p>
	</div>
</div>




		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/chatbot/">Chatbot</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Enhancing Automotive Software Quality: Unit Testing the BSW  Layer of AUTOSAR Using Google Test Framework</title>
		<link>https://www.verolt.com/case-studies/enhancing-automotive-software-quality-unit-testing-the-bsw-layer-of-autosar-using-google-test-framework/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 25 Jun 2024 13:46:44 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Embedded Software]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1586</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/enhancing-automotive-software-quality-unit-testing-the-bsw-layer-of-autosar-using-google-test-framework/">Enhancing Automotive Software Quality: Unit Testing the BSW  Layer of AUTOSAR Using Google Test Framework</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144af938a7"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144af93fa4" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Highlights</strong></p>
<p><span class="ui-provider bsf bsg ayn bsh bsi bsj bsk bsl bsm bsn bso bsp bsq bsr bss bst bsu bsv bsw bsx bsy bsz bta btb btc btd bte btf btg bth bti btj btk btl btm" dir="ltr">Unit testing of the BSW layer in AUTOSAR is critical for reliable, safe, and performant automotive software. It improves system reliability by catching issues early and ensures safety by eliminating failures. AUTOSAR&#8217;s modularity allows efficient unit testing of individual modules, improving maintainability. However, challenges exist. The BSW layer&#8217;s complexity and interdependence make test creation difficult. Real-time constraints and limited resources of embedded systems add to the challenge. Hardware dependencies can hinder testing in simulated environments. Finally, a lack of standardization can lead to inconsistent testing practices. By overcoming these challenges, developers can ensure a robust BSW layer, forming the foundation for successful AUTOSAR systems.</span></p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Problem Statement</strong></p>
<p>An automotive client utilizing its own custom developed AUTOSAR architecture stack faced significant challenges in achieving comprehensive unit test coverage for their Basic Software (BSW) layer. Tight coupling between BSW components and other software modules within AUTOSAR stack complicated the isolation required for effective unit testing. Furthermore, the BSW layer, especially modules like the communication stack, diagnostic stack, and system services, operate under stringent real-time constraints. Traditional unit testing methods struggle to replicate these real-time conditions, hindering the testing process. The inherent complexity of these BSW modules, which handle intricate interactions like message transmission and reception with demanding error handling procedures, further exacerbates the challenge.</p>
<p>The client seeks a cost-effective solution that leverages Specialized Testing Platforms. These platforms should be affordable and cater to the specific needs of real-time embedded system testing, including features like mocking and stubbing to facilitate component isolation. Additionally, the client desires to engage a team of testing experts with a deep understanding of AUTOSAR architecture, BSW functionalities, and best practices for unit testing real-time and complex software components.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Solution</strong></p>
<p><span class="ui-provider bsf bsg ayn bsh bsi bsj bsk bsl bsm bsn bso bsp bsq bsr bss bst bsu bsv bsw bsx bsy bsz bta btb btc btd bte btf btg bth bti btj btk btl btm" dir="ltr">Building upon the understanding of the client&#8217;s challenges, the Google Test framework emerged as a compelling solution due to its distinct advantages like,<br />
</span></p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<ul>
<li><strong>Automated Execution:</strong> Streamlines regression testing during development and CI pipelines.</li>
<li><strong>AUTOSAR Compatibility:</strong> Supports diverse development environments and target architectures<br />
commonly used in AUTOSAR projects, ensuring seamless integration within the existing client<br />
ecosystem.</li>
<li><strong>Mock Object Capabilities:</strong> Enables isolated unit testing of BSW components by simulating external<br />
dependencies and complex interactions. This facilitates efficient defect identification within the<br />
intricate BSW layer, addressing the challenge of tight coupling within the system.</li>
<li><strong>Customization Potential:</strong> Offers extensibility to address specific testing needs and project<br />
constraints within the AUTOSAR ecosystem, allowing for tailor-made solutions to the client&#8217;s unique<br />
requirements</li>
</ul>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p>A significant challenge arose with the Com module, where message transmission and reception needed thorough testing. Configuration data for messages and signals was retrieved from dedicated XML files. Leveraging Python Jinja3 templates within the test files facilitated the dynamic generation of test cases based on these configurations.<br />
The most challenging aspects were testing timing-related requirements and message transmission/reception.To address these complexities, the proposed approach involved:</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<ul>
<li><strong>Mock-Driven Unit Testing with Google Test:</strong><br />
Leveraging Stubs: Mock header files (.h) with stubs are incorporated in test files. Google Test&#8217;s built-in mocking functionality facilitates the creation of mock objects. These mocks simulate external dependencies or complex interactions within the BSW, enabling isolated unit testing of the target code by decoupling it from external components.</li>
<li><strong>Efficient Resource Management:</strong><br />
Constructor/Destructor Optimization: Constructors and destructors were employed for proper initialization and de-initialization of the module and its variables. This promoted efficient resource management and memory handling.</li>
<li><strong>Enhancing Reusability and Reliability:</strong><br />
Test Fixture Implementation: Test fixtures were utilized to establish and dismantle common resources and state across multiple test cases. This approach minimized code duplication and guarantees consistent testing environments.</li>
<li><strong>Parameterized Testing for Comprehensive Coverage:</strong><br />
Parameterized tests were introduced to automate the execution of test cases with varying input parameters. This approach ensured comprehensive testing across a wider range of scenarios. Within the Com module&#8217;s configuration file, we meticulously analyzed the transmission and reception Protocol Data Units (PDUs), along with their encapsulated signals. These configurations serve as the backbone for communication integrity.</li>
</ul>
	</div>
</div>



<div class="img-with-aniamtion-wrap  custom-width-650px " data-max-width="custom" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img loading="lazy" decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="800" width="1000" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2024/06/image-s-12.jpg" alt="" srcset="https://www.verolt.com/wp-content/uploads/2024/06/image-s-12.jpg 1000w, https://www.verolt.com/wp-content/uploads/2024/06/image-s-12-300x240.jpg 300w, https://www.verolt.com/wp-content/uploads/2024/06/image-s-12-768x614.jpg 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" />
          </div>
        </div>
      </div>
    </div>
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Results</strong></p>
<p>This comprehensive documentation demonstrates a commitment to quality assurance throughout the development lifecycle. By employing Google Test, we achieved thorough testing of over 32 AUTOSAR BSW modules, encompassing crucial components like the Com Stack, Safety-Critical Components, Memory Stack, and Diagnostic Stack. This rigorous testing approach, utilizing the capabilities of Google Test, ensures the robustness, safety, and reliability of the tested BSW modules.</p>
	</div>
</div>




		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/enhancing-automotive-software-quality-unit-testing-the-bsw-layer-of-autosar-using-google-test-framework/">Enhancing Automotive Software Quality: Unit Testing the BSW  Layer of AUTOSAR Using Google Test Framework</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Flash Image Authenticity for Low Resource Co-Controller</title>
		<link>https://www.verolt.com/case-studies/flash-image-authenticity-for-low-resource-co-controlle/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 25 Jun 2024 13:39:29 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Embedded Software]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1582</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/flash-image-authenticity-for-low-resource-co-controlle/">Flash Image Authenticity for Low Resource Co-Controller</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144af96f28"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144af9758c" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Highlights</strong></p>
<p>In the recent years, vehicles have begun to provide more and more advanced features and in turn have led to a massive rise in computing power and software complexity required to keep all the four wheels spinning and firmly on the ground. This in turn has led to vehicles<br />
becoming susceptible to cyberattacks and countries requiring stricter compliance from vehicle manufacturers to cybersecurity design principles and standards. The EU has made it compulsory for all vehicles manufactured after July 2024 to comply with UNECE WP.29<br />
regulations [1].<br />
A vehicle compromised on the field can have severe to fatal consequences ranging from financial losses to user due to theft or to the OEM due to theft of intellectual property to severe injuries due to failure of critical vehicle systems. This has led the OEMs to adopt security baselines across platforms ensuring not only the more robust zonal ECUs but also the peripheral controllers to achieve a certain level of security. The available resources on these peripheral controllers or the system constraints of these controllers often restrict the implementation of standard security measures derived from pre-existing global cybersecurity standards.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Problem Statement</strong></p>
<p>A customer faced several challenges in securing their Electronic Control Unit (ECU) co-controller. They required a signed and<br />
encrypted flash image for the co-controller, transmitted via the Controller Area Network (CAN) to comply with European security<br />
standards. However, two limitations hindered this process:</p>
<p><strong>Limited Memory on the Main Controller:</strong> The main controller, responsible for verifying the image signature, lacked sufficient RAM<br />
to handle the entire image for verification.</p>
<p><strong>Missing Cryptographic Libraries on Co-Controller:</strong> The co-controller, where the image needed to be flashed, completely lacked<br />
any cryptographic libraries, rendering it unable to handle the signed and encrypted format itself.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Solution</strong></p>
<ul>
<li>To address the customer&#8217;s CU co-controller security challenges, we took a two-pronged approach that focused on achieving<br />
the essential security goals while working within the limitations of the system.<br />
First, we conducted a thorough analysis to identify the core security objectives behind the requirement for a signed and<br />
encrypted flash image. This analysis revealed two critical aspects:</li>
<li>Authenticity of Header and Firmware: Ensuring that the header information and the firmware itself had not been tampered<br />
with during transmission.</li>
<li>Integrity of Header and Firmware: Verifying that the header and the entire firmware image remained unaltered during transit.<br />
Considering these objectives and the constraints of limited memory on the main controller and the absence of cryptographic<br />
libraries on the co-controller, we proposed an optimized solution: signing only the header. This approach had two key<br />
advantages:</li>
<li>Accommodating Limited Memory: By signing just the header, the verification process could be performed on the main<br />
controller within its available memory capacity.</li>
<li>Ensuring Integrity without Encryption: The header would include a CRC (Cyclic Redundancy Check) value calculated by the<br />
OEM over the entire firmware image. This CRC value acts as a fingerprint, allowing the main controller to verify if the firmware<br />
data has been tampered with during transmission. The signature on the header, using the OEM&#8217;s private key, guarantees that the<br />
header itself was generated by a trusted source (the OEM).<br />
In essence, this solution leverages the CRC for data integrity verification while relying on the signed header to confirm its<br />
authenticity &#8211; both crucial aspects for securing the ECU co-controller firmware update process.<br />
Our proposed solution, while effective, did come with some identified cybersecurity risks:</li>
<li>Bricked Co-Controller on Failed Flash: If the flash process failed, the co-controller would be left without any firmware,<br />
potentially disabling critical functions of the ECU. This risk was deemed acceptable since the ECU was not designed for Over-<br />
The-Air (OTA) updates. Reflashing, in case of such a failure, would only be possible at a service center or supplier facility.</li>
<li>Higher Collision Probability of CRC32: Compared to more robust cryptographic checksums like hash or CMAC, CRC32 has a<br />
higher chance of two different data inputs generating the same checksum value (collision). However, this risk was also<br />
considered tolerable given the infrequent nature of co-controller flashing. Additionally, the encryption of the firmware image<br />
itself further limited the potential for exploitation even if a collision occurred.</li>
</ul>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Results</strong></p>
<p><span class="ui-provider bsf bsg ayn bsh bsi bsj bsk bsl bsm bsn bso bsp bsq bsr bss bst bsu bsv bsw bsx bsy bsz bta btb btc btd bte btf btg bth bti btj btk btl btm" dir="ltr">Our approach yielded positive results:<br />
Security Controls and Feasibility Assessment: Through a thorough analysis of the<br />
system requirements, we were able to identify the necessary security controls and<br />
assess their feasibility within the existing system constraints. Early Vulnerability<br />
Detection and Solution: We effectively pinpointed a potential vulnerability at the system<br />
architecture level during the design phase itself. This allowed for a proactive solution to<br />
be implemented early on, mitigating the risk later in development. Constrained Solution<br />
Meets OEM Needs: We successfully designed a solution that adhered to the system<br />
limitations while still achieving all the security goals outlined by the OEM.<br />
References:<br />
[1) Automotive Cybersecurity: New Regulations in the Auto Industry<br />
(securityintelligence.com<br />
[2] Explanation of Security Overview (autosar.org)</span></p>
	</div>
</div>



<div class="img-with-aniamtion-wrap  custom-width-500px " data-max-width="custom" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img loading="lazy" decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="800" width="1000" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2024/06/log-het.jpg" alt="" srcset="https://www.verolt.com/wp-content/uploads/2024/06/log-het.jpg 1000w, https://www.verolt.com/wp-content/uploads/2024/06/log-het-300x240.jpg 300w, https://www.verolt.com/wp-content/uploads/2024/06/log-het-768x614.jpg 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" />
          </div>
        </div>
      </div>
    </div>
		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/flash-image-authenticity-for-low-resource-co-controlle/">Flash Image Authenticity for Low Resource Co-Controller</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Implementation of Widget Swiping  Feature in a Multi Display IVI System</title>
		<link>https://www.verolt.com/case-studies/implementation-of-widget-swiping-feature-in-a-multi-display-ivi-system/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 25 Jun 2024 05:42:15 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[HMI]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1523</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/implementation-of-widget-swiping-feature-in-a-multi-display-ivi-system/">Implementation of Widget Swiping  Feature in a Multi Display IVI System</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144af9a4d1"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144af9aab1" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Highlights</strong></p>
<p>In our rapidly advancing society, technology has become indispensable in our everyday routines. Nowhere is this more apparent than in the automotive realm, where infotainment systems have become paramount. With the increasing demands of car owners and safety requirements in the automotive industry, the role of human-machine interface solutions has grown as well – the HMI market size is projected to enlarge from USD 23 billion in 2023 to USD 49.43 billion by 2030. These advanced systems effortlessly integrate entertainment and information, elevating the driving journey for both drivers and passengers alike. Recognizing the evolving needs of consumers, there<br />
arises a pressing demand for enhanced usability and customization in the Multi-Display In-Vehicle Infotainment system. And we have implemented one of such features for it.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Problem Statement</strong></p>
<p>Our client, one of the European customers, aimed to enhance their in-vehicle entertainment experience by developing a sophisticated Multi-Display In-Vehicle Infotainment System. The primary challenge was to implement an interactive widget swipe feature that seamlessly communicate between the system&#8217;s three screens: the Central Display, serving as the hub for the widget gallery; the Passenger Display, dedicated to personalized entertainment for passengers; and the Instrument Cluster, providing vital vehicle information such as speed, RPM, charging status, etc.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p>Drawing on our proficiency in Android development, we embarked on the development of a cutting-edge Infotainment System using Android Studio and Jetpack Compose. Three distinct screens were designed – Passenger Display, Central Display, and Instrument Cluster – each catering to different functionalities and user interactions. Leveraging Jetpack Compose, a responsive and visually stunning user interface was ensured across all screens. The display specifications of the screens were Screen size: 15.6” x 15.6” x 15.6” Screen resolution: 3840x2160px<br />
To address the need for enhanced usability and customization in the Multi-Display In-Vehicle Infotainment System, we implemented a widget swiping feature. Leveraging intuitive touch gestures and responsive interface design, users can seamlessly transfer widgets between Central Display, Passenger Screen &amp; Instrument Cluster with ease.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<ol>
<li><strong>Intuitive Gesture Control:</strong> We incorporated intuitive touch gestures, such as swiping or dragging, to initiate the widget swiping action. This ensures a user-friendly experience that requires minimal effort from the user.</li>
<li><strong>Real-Time Transfer:</strong> Upon initiating the swipe gesture on a widget, the system responds in real-time, displaying visual feedback to indicate the widget is ready for transfer. Users can then swipe the widget towards the desired screen for<br />
placement.</li>
<li><strong>Visual Feedback and Animation:</strong> During the swiping action, users receive visual feedback through fluid animations and transition effects, enhancing the overall experience and providing clear guidance throughout the process.</li>
<li><strong>Automatic Adjustment:</strong> Once the widget reaches the target screen, the system automatically adjusts the widget&#8217;s position and size based on the screen layout and user preferences, ensuring a seamless integration into the new screen.</li>
</ol>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p>Also to meet the client&#8217;s need for personalization, multiple user profiles with different layouts and themes for male and female, allowing passengers to create customized experiences based on their preferences were implemented. Integration with popular streaming platforms such as Netflix, Prime Video, Apple Music, and YouTube Music was seamlessly achieved, providing passengers with access to a vast library of entertainment options. Also, a video swiping feature was developed where user could swipe the video from Central Display to Passenger Display. Additionally, Drive Mode and Parking Mode were incorporated to ensure a safe and distraction-free driving experience for driver and passengers.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Results</strong></p>
<p>The widget swiping feature was implemented for three screens and it has significantly enhanced the usability and efficiency of the Multi-Display In-Vehicle Infotainment System. With the ability to transfer widgets between screens using different gestures, users have gained greater control over their infotainment setup, tailoring it to their specific preferences and ensuring a personalized and enjoyable in-vehicle experience. The implementation of multiple user profiles with customizable layouts and themes has enhanced personalization, allowing passengers to tailor their experience. Additionally, the project was successfully delivered within a timeframe of three months, showcasing our team&#8217;s efficiency and commitment to meeting client expectations.</p>
	</div>
</div>




		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/implementation-of-widget-swiping-feature-in-a-multi-display-ivi-system/">Implementation of Widget Swiping  Feature in a Multi Display IVI System</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Advanced Industrial Monitoring Application: Optimizing  Efficiency with C++, Qt/QML, and MongoDB</title>
		<link>https://www.verolt.com/case-studies/advanced-industrial-monitoring-application-optimizing-efficiency-with-c-qt-qml-and-mongodb/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 25 Jun 2024 05:32:43 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[HMI]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1519</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/advanced-industrial-monitoring-application-optimizing-efficiency-with-c-qt-qml-and-mongodb/">Advanced Industrial Monitoring Application: Optimizing  Efficiency with C++, Qt/QML, and MongoDB</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144af9c9db"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144af9cf81" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Overview/Highlights</strong></p>
<p>In today&#8217;s technologically advanced landscape, characterized by intricate machinery and multifaceted operations, the importance of intuitive Human-Machine Interface (HMI) applications cannot be overstated. These applications play a pivotal role in simplifying machine operation, enhancing overall efficiency, and ensuring optimal performance.<br />
Acknowledging the significance of seamless operational processes, there arises a need for advanced HMI applications tailored to specific industrial needs. Such solutions are designed to analyze and calculate precise measurements, with a primary focus on delivering clear and accurate data representation. Emphasizing user-friendly interfaces and comprehensive graphical displays, these applications serve as essential tools for facilitating informed decision-making and maximizing operational effectiveness.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Problem Statement</strong></p>
<p>Our customer, a prominent player in the film manufacturing industry, requires an innovative film thickness gauge application with specific functionalities. They seek a solution that guarantees accurate measurements of film thickness, coupled with comprehensive tolerance analysis against predefined ranges to uphold product quality standards.<br />
Additionally, the application should feature live graphs and analytics for real-time process monitoring, alongside the flexibility to configure machine parameters as necessary.<br />
Furthermore, our client desires a robust reporting system capable of generating detailed reports to facilitate quality control measures and informed decision-making.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Solution<br />
</strong></p>
<p>Our solution represents the pinnacle of technological prowess, integrating advanced sensing technology, meticulous data integration, and an intuitive user interface. Developed on a robust stack comprising Qt, QML, C++, and MongoDB, our sophisticated Human-Machine Interface (HMI)<br />
Monitoring application serves as a critical interface, seamlessly bridging end-users and Programmable Logic Controllers (PLCs). Employing sophisticated TCP/IP protocols, it facilitates bidirectional data exchange with precision X-ray and Kappa sensors. This results in a finely tuned film thickness gauge application, meticulously tailored to meet our client&#8217;s exacting quality control standards and operational needs, thereby optimizing processes and bolstering overall performance.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>System Architecture:</strong></p>
<p>At its architectural core, the system architecture revolves around two indispensable PLCs: the gauge PLC, tasked with precise film thickness measurements utilizing proprietary algorithms, and the control PLC, responsible for real-time regulation of film thickness based on feedback from sensors. These PLCs operate synergistically, ensuring consistent film thickness levels critical for  maintaining operational uniformity and product quality.</p>
	</div>
</div>



<div class="img-with-aniamtion-wrap " data-max-width="100%" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img loading="lazy" decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="483" width="836" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2024/06/amcs.jpg" alt="" srcset="https://www.verolt.com/wp-content/uploads/2024/06/amcs.jpg 836w, https://www.verolt.com/wp-content/uploads/2024/06/amcs-300x173.jpg 300w, https://www.verolt.com/wp-content/uploads/2024/06/amcs-768x444.jpg 768w" sizes="auto, (max-width: 836px) 100vw, 836px" />
          </div>
        </div>
      </div>
    </div>
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Data Visualization and Analysis: </strong></p>
<p>The application boasts dynamic real-time data visualization capabilities, leveraging sophisticated graphing libraries to offer users a comprehensive array of graphical representations. From line plots to scatter diagrams, each graph is meticulously engineered to provide insightful data analysis, featuring customizable colour schemes and interactive elements for enhanced user engagement and interpretability.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Alarm Management:</strong></p>
<p>Furthermore, the application incorporates a robust alarm management system engineered to detect and notify users of process anomalies promptly. Leveraging threshold-based algorithms and historical data analysis, the system triggers notifications for deviations from predefined<br />
tolerance levels, allowing users to respond proactively and mitigate potential disruptions to production processes.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Security Measures:</strong></p>
<p>In addition to its advanced monitoring and analysis capabilities, the application places paramount<br />
emphasis on data security through stringent access control mechanisms. Employing industry-standard encryption protocols and multi-factor authentication, the system safeguards sensitive data and features, ensuring compliance with stringent regulatory requirements and safeguarding against unauthorized access and data breaches.</p>
<p>In conclusion, the HMI Monitoring application represents the pinnacle of technological innovation, seamlessly integrating cutting-edge programming paradigms and robust algorithms to deliver unparalleled performance and reliability in industrial environments. With its intuitive user interface, advanced data visualization capabilities, and stringent security measures, the application empowers users to monitor, analyze, and optimize manufacturing processes with unparalleled precision and efficiency.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Result</strong></p>
<p>Our robust application, powered by C++, Qt/QML, and MongoDB, ensures seamless industrial operations. With fail-safe mechanisms, it maintains system integrity amidst potential disruptions. It accurately measures film thickness, analyzes data against predefined tolerances, and visualizes live analytics through dynamic graphs. Users can effortlessly configure machine parameters and<br />
generate detailed reports for informed decision-making. Our solution embodies technological excellence, empowering users with efficiency and confidence in industrial settings.</p>
	</div>
</div>




		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/advanced-industrial-monitoring-application-optimizing-efficiency-with-c-qt-qml-and-mongodb/">Advanced Industrial Monitoring Application: Optimizing  Efficiency with C++, Qt/QML, and MongoDB</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>AP Communication Management  Test-Driven Development</title>
		<link>https://www.verolt.com/case-studies/ap-communication-management-test-driven-development/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 25 Jun 2024 05:18:27 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Embedded Software]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1515</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/ap-communication-management-test-driven-development/">AP Communication Management  Test-Driven Development</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144af9fa08"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144afa0028" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Highlights</strong></p>
<p>The AUTOSAR Adaptive Platform introduces a standardized approach for the Application Layer middleware within the automotive industry. This layer, analogous to the Classic Platform&#8217;s Runtime Environment (RTE), operates on top of a POSIXcompliant operating system like PSE51. This operating system runs on a machine (equivalent to the BSW layer in Classic AUTOSAR), which can be either native hardware<br />
or virtualized using a hypervisor on High-Performance Computing (HPC) platforms.</p>
<p>The core purpose of Adaptive AUTOSAR is to address the growing performance demands in areas like Advanced Driver-Assistance Systems (ADAS)/Autonomous Driving (AD), Vehicle-to-Everything (V2X) communication, and secure over-the-air<br />
(OTA) updates during runtime.</p>
<p>Within this framework, Adaptive Applications function as individual POSIX processes. These applications interact with Application Programming Interfaces (APIs) to access Functional Clusters and Adaptive Platform Services provided by the AUTOSAR Runtime<br />
for Adaptive Applications (ARA). This standardized approach facilitates the development and deployment of complex automotive software applications.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Problem Statement</strong></p>
<p>A Chinese Tier 1 supplier encountered several challenges when developing an AP Stack that adheres to AUTOSAR AP specifications and achieves desired performance levels. The customer aimed to build its own AP Stack solution based on the AP Communication Management (AP CM) functional cluster within the AUTOSAR Adaptive Platform Demonstrator (APD) provided by the AUTOSAR Consortium. It also required a gap analysis to identify discrepancies between the customer&#8217;s implementation and the official AP CM specifications. The analysis would encompass both static and dynamic behavior at the unit and integration levels.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Solution<br />
</strong></p>
<p>Constructing an AP Stack that aligns with specifications while meeting performance criteria is a complex task that demands significant resources. Also, the market offers a limited selection of AP Stack solutions that fulfill stability, safety, and security requirements, often at high costs. To overcome these challenges, following solution was proposed and implemented:</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Automated Unit Testing:</strong> GoogleTest was employed to create unit tests encompassing all AP CM specification items. These tests were seamlessly integrated within the AP stack build environment using Yocto layers, Docker, and CMake, enabling efficient and automated testing.</p>
<p><strong>Mastery of Communication Management Design Patterns:</strong> In-depth knowledge of communication managementspecific design patterns, including proxy-skeleton, service-oriented, and remote procedure call (RPC) architectures, was leveraged. A detailed test plan and specification were established, along with a custom mocking framework built upon GoogleTest and Google Mock (GMock) for enhanced testing capabilities.</p>
<p><strong>Code Generation and Design Support:</strong> Critical AP CM specification items and corresponding design elements were identified for potential code generation. The solution provided end-to-end support for the communication management functional cluster&#8217;s detailed design. This included deriving designs from AP software specifications and facilitating the creation of the ARXML metamodel, a key component for automated code generation.</p>
<p><strong>Deployment and Testing Integration:</strong> Yocto layers and Bitbake recipes were configured to embed test scripts and executables within the final AUTOSAR Adaptive Platform Demonstrator (APD) image. This image was then executed on the QEMU emulator, a virtual machine environment, built using Bitbake. This approach streamlined the deployment and execution of tests within the target environment.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p>By implementing this solution, the project successfully addressed the challenges associated with developing a robust and high-performing AP Stack while ensuring adherence to AUTOSAR AP specifications.</p>
	</div>
</div>



<div class="img-with-aniamtion-wrap  custom-width-600px " data-max-width="custom" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img loading="lazy" decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="800" width="1000" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2024/06/red-image-123.jpg" alt="" srcset="https://www.verolt.com/wp-content/uploads/2024/06/red-image-123.jpg 1000w, https://www.verolt.com/wp-content/uploads/2024/06/red-image-123-300x240.jpg 300w, https://www.verolt.com/wp-content/uploads/2024/06/red-image-123-768x614.jpg 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" />
          </div>
        </div>
      </div>
    </div>
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Results<br />
</strong></p>
<p>The BSW layer underwent rigorous testing, culminating in the delivery of a comprehensive set of artifacts. This included detailed coverage reports, traceability matrices, test results, test cases, defect reports, and summary reports. Additionally, a thorough overview of the entire unit testing process was provided. These deliverables demonstrate a firm commitment to quality assurance throughout the software development lifecycle, guaranteeing the robustness and reliability of the tested BSW components.</p>
<p>The project successfully executed unit tests for over 32 AUTOSAR BSW modules. This encompassed a wide range of components, including the Communication Stack (Com Stack), safety-critical components, the Memory Stack, and the Diagnostic Stack. This extensive testing effort involved meticulous analyses and validation procedures, ensuring the robustness, safety, and reliability of the BSW modules under test.</p>
	</div>
</div>




		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/ap-communication-management-test-driven-development/">AP Communication Management  Test-Driven Development</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Optimizing Unit Testing for AUTOSAR BSW  Components &#8211; Ensuring Compliance and Reliability</title>
		<link>https://www.verolt.com/case-studies/optimizing-unit-testing-for-autosar-bsw-components-ensuring-compliance-and-reliability/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 25 Jun 2024 05:05:42 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Embedded Software]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1506</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/optimizing-unit-testing-for-autosar-bsw-components-ensuring-compliance-and-reliability/">Optimizing Unit Testing for AUTOSAR BSW  Components &#8211; Ensuring Compliance and Reliability</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144afa27fe"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144afa2d8c" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p>The Basic Software (BSW) layer within the AUTOSAR architecture forms the bedrock of modern car electronics. It acts as a critical intermediary, facilitating communication between the numerous Electronic Control Units (ECUs) and managing essential functions like<br />
communication protocols, diagnostics, and operating system services. As car complexity increases, with a growing network of interconnected systems and sensors, the BSW layer becomes ever more crucial.<br />
Unit testing plays a vital role in ensuring the functionality and behavior of individual BSW modules, functions, and services. However, BSW component testing presents unique challenges due to their tight integration with sensor and actuator hardware. Isolating these components for testing necessitates emulating or simulating the hardware environment, which can be a complex endeavor to achieve with complete accuracy.</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Problem Statement</strong></p>
<p>To ensure compliance, dependability, and critical functionality in vehicles, the automotive industry requires effective testing of Basic Software (BSW) components within the AUTOSAR (Automotive Open System Architecture) framework. A recent customer inquiry highlighted the need for an automated, cross-platform and cost-effective testing solution to efficiently validate the BSW layer. Additionally, the client sought an independent testing team with expertise in conducting unit tests on BSW modules specific to AUTOSAR<br />
version 4.4.0</p>
	</div>
</div>




<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Solution<br />
</strong></p>
<p>A comprehensive solution was implemented to address the client s request for an automated, cross-platform and cost effective BSW layer unit testing solution within AUTOSAR. The development cycle followed the Agile Scrum methodology, which fostered iterative development and continuous improvement of both test suites and testing processes. Regular requirement review meetings ensured complete understanding and eliminated ambiguities through techniques like completeness and consistency checks.</p>
<p>Google Test (GTest) was chosen as the testing framework due to its open-source nature, cross-platform support, mocking capabilities, and seamless integration with Continuous Integration (CI) systems. GTest s utilization of C++ empowered the creation of robust and comprehensive test suites for precise code validation. Additionally, Python Jinja 3 templates were leveraged to dynamically generate configuration files, enhancing flexibility and streamlining the testing process.</p>
<p>Visual Studio Code, an open-source tool with debugging support for various programming languages, was selected as the development environment. GitLab, chosen for its CI capabilities, issue tracking integration and centralized storage of code, documentation, and test artifacts, served as the version control system.</p>
<p>The testing team employed established techniques like Equivalence Class Partitioning, Boundary Value Analysis, State transition testing and Decision table testing alongside advanced methods like vectors, assertions, and mock testing to ensure thorough validation. Furthermore, the solution was equipped to handle complex scenarios involving time-related requirements and infinite loop conditions. Finally, regular regression testing was conducted to safeguard against regressions or defects introduced by new code changes.</p>
	</div>
</div>



<div class="img-with-aniamtion-wrap " data-max-width="100%" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img loading="lazy" decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="259" width="921" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2024/06/Screenshot-2024-06-27-121917.png" alt="" srcset="https://www.verolt.com/wp-content/uploads/2024/06/Screenshot-2024-06-27-121917.png 921w, https://www.verolt.com/wp-content/uploads/2024/06/Screenshot-2024-06-27-121917-300x84.png 300w, https://www.verolt.com/wp-content/uploads/2024/06/Screenshot-2024-06-27-121917-768x216.png 768w" sizes="auto, (max-width: 921px) 100vw, 921px" />
          </div>
        </div>
      </div>
    </div>
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Results<br />
</strong></p>
<p>The BSW layer underwent rigorous testing, culminating in the delivery of a comprehensive set of artifacts. This included detailed coverage reports, traceability matrices, test results, test cases, defect reports, and summary reports. Additionally, a thorough overview of the entire unit testing process was provided. These deliverables demonstrate a firm commitment to quality assurance throughout the software development lifecycle, guaranteeing the robustness and reliability of the tested BSW components.</p>
<p>The project successfully executed unit tests for over 32 AUTOSAR BSW modules. This encompassed a wide range of components, including the Communication Stack (Com Stack), safety-critical components, the Memory Stack, and the Diagnostic Stack. This extensive testing effort involved meticulous analyses and validation procedures, ensuring the robustness, safety, and reliability of the BSW modules under test.</p>
	</div>
</div>




		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/optimizing-unit-testing-for-autosar-bsw-components-ensuring-compliance-and-reliability/">Optimizing Unit Testing for AUTOSAR BSW  Components &#8211; Ensuring Compliance and Reliability</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Journey Logger: Enhancing Your Travel By Capturing Your Moments</title>
		<link>https://www.verolt.com/case-studies/journey-logger-enhancing-your-travel-by-capturing-your-moments/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Mon, 24 Jun 2024 13:44:46 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Data Engineering]]></category>
		<guid isPermaLink="false">https://www.verolt.com/?p=1501</guid>

					<description><![CDATA[<p>The post <a href="https://www.verolt.com/case-studies/journey-logger-enhancing-your-travel-by-capturing-your-moments/">Journey Logger: Enhancing Your Travel By Capturing Your Moments</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></description>
										<content:encoded><![CDATA[
		<div id="fws_6ad144afa560c"  data-column-margin="default" data-midnight="dark"  class="wpb_row vc_row-fluid vc_row"  style="padding-top: 0px; padding-bottom: 0px; "><div class="row-bg-wrap" data-bg-animation="none" data-bg-animation-delay="" data-bg-overlay="false"><div class="inner-wrap row-bg-layer" ><div class="row-bg viewport-desktop"  style=""></div></div></div><div class="row_col_wrap_12 col span_12 dark left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col no-extra-padding inherit_tablet inherit_phone "  data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
			<div class="wpb_wrapper">
				<div id="fws_6ad144afa5d9a" data-midnight="" data-column-margin="default" class="wpb_row vc_row-fluid vc_row inner_row"  style=""><div class="row-bg-wrap"> <div class="row-bg" ></div> </div><div class="row_col_wrap_12_inner col span_12  left">
	<div  class="vc_col-sm-12 wpb_column column_container vc_column_container col child_column no-extra-padding inherit_tablet inherit_phone "   data-padding-pos="all" data-has-bg-color="false" data-bg-color="" data-bg-opacity="1" data-animation="" data-delay="0" >
		<div class="vc_column-inner" >
		<div class="wpb_wrapper">
			
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Highlights</strong></p>
<p>Journey Logger redefines the travel experience by providing a hands-free video recording solution, ideal for capturing and sharing memorable moments on the go. This innovative application leverages voice commands for starting and stopping recordings, ensuring drivers can focus on the road while documenting their journey. The intelligent curation feature distinguishes Journey Logger from traditional tracking solutions, as it analyzes audio and video content to highlight scenic routes and significant events while cropping out silent parts. Weather information is seamlessly integrated into the videos, adding context and enhancing the storytelling aspect. The application supports unlimited clip recording, merging them with smooth transitions, and stores them securely in the cloud, ready for social media sharing. This sophisticated combination of features ensures a comprehensive, visually engaging, and hands-free travel documentation experience.</p>
<p><strong>Problem Statement</strong></p>
<p>Drivers often face challenges in capturing and sharing their travel experiences due to the need to manually record videos, which can be distracting and unsafe. Existing solutions mainly focus on route tracking and vehicle data, lacking a comprehensive visual documentation tool that can operate hands-free. Additionally, the process of curating and editing recorded footage is time-consuming and requires technical expertise. There is a need for an application that allows drivers to safely and effortlessly record, curate, and share their journeys, with seamless video transitions, all managed through voice commands to ensure the driver&#8217;s focus remains on the road.</p>
<p><strong>Solution</strong></p>
<p>A robust solution was developed to meet the demand for a hands-free journey recording and curation application, following Agile Scrum practices for iterative development and continuous improvement. Voice recognition technology enables users to initiate and stop recordings with simple commands, ensuring safety and convenience. Real-time weather updates are integrated, enhancing the storytelling of each journey segment, with cloud storage ensuring secure access for editing and sharing on social media.</p>
<p>The development environment utilized Visual Studio Code for debugging and GitLab for CI capabilities and version control. Testing involved techniques such as Equivalence Class Partitioning, Boundary Value Analysis, and mock testing to validate functionality comprehensively. Regular regression testing ensured ongoing reliability, safeguarding against defects introduced during updates. This solution provides a streamlined, user-centric experience for documenting travels hands-free, combining technology advancements with rigorous testing to deliver a reliable and engaging application for users.</p>
	</div>
</div>



<div class="img-with-aniamtion-wrap " data-max-width="100%" data-max-width-mobile="default" data-shadow="none" data-animation="none" >
      <div class="inner">
        <div class="hover-wrap"> 
          <div class="hover-wrap-inner">
            <img loading="lazy" decoding="async" class="img-with-animation skip-lazy " data-delay="0" height="188" width="624" data-animation="none" src="https://www.verolt.com/wp-content/uploads/2024/06/akshay-new.png" alt="" srcset="https://www.verolt.com/wp-content/uploads/2024/06/akshay-new.png 624w, https://www.verolt.com/wp-content/uploads/2024/06/akshay-new-300x90.png 300w" sizes="auto, (max-width: 624px) 100vw, 624px" />
          </div>
        </div>
      </div>
    </div>
<div class="wpb_text_column wpb_content_element " >
	<div class="wpb_wrapper">
		<p><strong>Results</strong></p>
<p>Journey Logger was developed as a comprehensive solution to redefine travel documentation, built with advanced dual-camera recording capabilities capturing both in-cabin and environmental views. The application integrates an intelligent algorithm designed to seamlessly capture high-quality audio and video, with automated trimming of silent periods facilitated through voice commands, ensuring efficient editing processes.</p>
<p>Incorporating real-time weather updates enhances the narrative of recorded journeys, providing contextual information throughout. The development process followed Agile Scrum methodologies, fostering iterative improvements in functionality and reliability. Journey Logger offers intuitive controls and secure cloud storage, designed to facilitate easy sharing and storage across various platforms, emphasizing a user-centric approach to hands-free travel documentation.</p>
	</div>
</div>




		</div> 
	</div>
	</div> 
</div></div>
			</div> 
		</div>
	</div> 
</div></div>
<p>The post <a href="https://www.verolt.com/case-studies/journey-logger-enhancing-your-travel-by-capturing-your-moments/">Journey Logger: Enhancing Your Travel By Capturing Your Moments</a> appeared first on <a href="https://www.verolt.com">Verolt</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 

Served from: www.verolt.com @ 2026-10-15 21:25:03 by W3 Total Cache
-->