Mixed Criticality User Interface Layer Decomposition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current user interface development systems face challenges in efficiently developing both safety critical and non-safety critical components within the same system, as existing tools require separate design processes, limiting the use of high-performance and high-quality visuals for safety critical content.
Innovation Solution
A method and system for mixed criticality user interface development that allows end users to designate objects as safety critical, decomposing the interface into separate layers for prioritized safety critical and non-safety critical components, enabling efficient co-design and deployment with improved runtime processing speed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If safety critical content is designed separately from non-safety critical content, then safety critical requirements are met, but design efficiency and integration capability deteriorate
Solution Approach 1:
The system automatically segments the user interface into distinct safety critical and non-safety critical layers through script-based decomposition. This segmentation allows each layer to be processed according to its specific requirements while maintaining overall system integration, resolving the contradiction by enabling separate handling of safety-critical components without requiring complete separate design processes.
Solution Approach 2:
The system applies different processing qualities and standards to different portions of the interface. Safety critical objects receive rigorous validation and compliance checking, while non-safety critical objects can use optimized development paths. This local differentiation allows the system to meet safety requirements where needed without applying unnecessary constraints elsewhere, thereby improving overall design efficiency.
2Reliability
If non-safety critical content is designed according to safety critical requirements, then safety compliance is ensured, but visual quality and performance capabilities deteriorate
Solution Approach 1:
The system segments the interface into safety critical and non-safety critical layers, allowing non-safety critical content to be developed with full visual quality capabilities without safety constraints. This segmentation eliminates the need to apply safety requirements universally, preserving visual quality where safety concerns do not apply.
Solution Approach 2:
Different quality standards and development approaches are applied locally to different portions of the interface. Safety critical portions receive appropriate validation and compliance processing, while non-safety critical portions can utilize advanced visual features and optimized rendering pipelines, thereby maintaining high visual quality without compromising safety compliance where needed.
3Device complexity
If the same development process is used for both safety critical and non-safety critical components, then process simplicity is maintained, but processing speed and resource utilization deteriorate
Solution Approach 1:
The system dynamically adjusts the development and processing approach based on the safety critical designation of each object. During runtime, the system can prioritize processing of safety critical layers while optimizing resource allocation. This dynamic adaptation allows the system to maintain relative process simplicity while achieving improved processing speeds through intelligent resource management and prioritization.
Data Source
AI summary
A method for mixed criticality user interface development includes storing at least one set of safety critical requirements along with a corresponding safety critical designation and designating an object according to the safety critical designation for deployment along with other objects in a user interface. The method further includes responding to an end user executing a request to deploy the user interface by automatically decomposing the user interface into a safety critical layer including the designated objects and a non-safety critical layer including the other objects, building the critical safety layer according to the set of safety critical requirements of the safety critical designation of the object, building the non-safety critical layer and deploying the critical safety layer and the non-safety critical layer as an overlay view in the user interface.