Hierarchical Validation of ECU Specifications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for validating electronic control unit (ECU) designs are computationally intensive and insufficient for ensuring compliance with standards, as they fail to effectively validate entire ECUs, particularly in the automobile industry where numerous electronic control modules are used for various features.
Innovation Solution
A hierarchical validation system and method that uses graphically based executable logic to validate ECU specifications, starting from the application level, feature level, and module level, with specific test cases to ensure structural and functional requirements are met, and allows translation between text-based and graphically based code, enabling comprehensive validation of entire ECUs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional validation methods are used to validate ECU designs, then validation coverage can be achieved, but computational resources and time are excessively consumed
Solution Approach 1:
The validation system segments the ECU design into a hierarchical structure with multiple levels (e.g., system level, module level, component level). Each level is validated independently using targeted test cases, allowing comprehensive validation coverage while reducing the computational burden compared to validating the entire system as a single unit. The segmentation enables parallel validation processes and focuses computational resources on specific areas that need validation.
2Measurement precision
If module level tests are performed to validate individual components, then specific component functionality can be verified, but the entire ECU cannot be validated
Solution Approach 1:
The validation approach uses a nested structure where module-level validation is embedded within hierarchical levels that lead up to ECU-wide validation. Each module is validated at its specific level with detailed test cases, and these validation results are then integrated into higher-level validations. This nesting allows both precise component-level verification and comprehensive ECU-level validation to coexist within a unified validation framework.
Solution Approach 2:
The system merges module-level validation results with system-level validation through the hierarchical structure. Validation test cases are designed to operate at multiple levels simultaneously, combining detailed component testing with overall system validation. This merging enables the validation process to achieve both precise component verification and comprehensive ECU validation without requiring separate independent processes.
3Reliability
If comprehensive validation of entire ECU is attempted, then complete system compliance can be ensured, but the validation process becomes computationally intensive and expensive
Solution Approach 1:
The hierarchical validation structure segments the complex ECU validation into manageable levels, where each level handles specific validation tasks with appropriate complexity. This segmentation reduces the overall system complexity by breaking down the validation process into smaller, more tractable components that can be developed, executed, and maintained more easily while still ensuring complete system compliance.
Solution Approach 2:
The validation approach adds a hierarchical dimension to the validation process, organizing test cases and validation activities across multiple levels rather than treating all validation as a single flat process. This dimensional organization allows the system to manage complexity by distributing validation tasks across different hierarchical layers, making the overall validation system more manageable while maintaining comprehensive coverage.
Data Source
AI summary
The present disclosure generally relates to improvements in validating control specifications and more particularly pertains to a system and method to hierarchically validate graphically based executable logic control specifications. This method may include identifying, by a processor for hierarchically validating a graphically based logic control specification, a functional hierarchy of a first application of the control specification comprising a first feature. The method may include executing, by the processor, a specific first feature test case on the first feature to at least one of validate a structure of the first feature and validate that a specific functional requirement of the first feature is met.