21:39
VnV in MBD
KPIT ECoDe
Overview
This video introduces verification and validation (V&V) within the context of Model-Based Design (MBD) using Simulink. It explains the fundamental V&V workflow, differentiating between verification (checking against the model and requirements) and validation (checking against user needs). The segment details simulation-based testing as a primary V&V method, outlining its workflow from model preparation to reporting. It then uses an electronic throttle control system as a concrete example to demonstrate how requirements are linked to model components and how test plans are structured.
How was this?
Save this permanently with flashcards, quizzes, and AI chat
Chapters
- Model-Based Design (MBD) allows for early testing of system designs against requirements using Simulink.
- Verification confirms that the final product matches the model and that the model aligns with requirements.
- Validation ensures the final product meets user needs.
- Key V&V tasks include traceability (linking design artifacts), conformance (adhering to standards), and reporting.
Understanding V&V in MBD is crucial for building reliable systems by ensuring they are built correctly (verification) and that they are the right systems for the user (validation).
Testing a Simulink model against user-defined requirements before deploying code to hardware.
- Simulation-based testing involves running a model with various test cases and analyzing outputs to check requirements.
- This method is effective but may not uncover all hidden design errors.
- Formal verification uses mathematical analysis to detect design errors and generate test cases automatically, but it often requires simplifying assumptions and manual model decomposition.
Knowing the strengths and limitations of different verification methods helps engineers choose the most appropriate approach for their project's needs and constraints.
Manually creating test cases to simulate different driving conditions for a car's control system.
- Prepare the model by configuring solver options, inputs, and logging.
- Load test cases, which define input signals and parameter values, often from external data sources.
- Run tests, which can range from single simulations to more complex analyses like parameter sweeps.
- Process results by visualizing data, performing coverage analysis, or checking against criteria.
- Produce reports to document test outcomes and confirm design correctness.
Following a structured workflow ensures that testing is systematic, repeatable, and provides clear evidence of the system's compliance with its design and requirements.
After running a simulation, visualizing the throttle position output to see if it matches the expected behavior.
- The ETC system replaces mechanical throttle control with electronic sensors, actuators, and software logic.
- This allows for more flexible control strategies based on driving conditions.
- The Simulink model for the ETC includes components like pedal input, ADC, controller (PID, PWM), and throttle body.
- Project organization in Simulink involves dedicated folders for data, documents, libraries, models, and work files.
A concrete example like the ETC system makes abstract V&V concepts tangible and demonstrates how they are applied in a real-world engineering scenario.
A Simulink model representing an electronic throttle that controls airflow into an engine based on pedal input and cruise control signals.
- Requirements can be authored directly in Simulink or imported from external documents and linked to specific model elements (blocks, charts).
- Traceability is established by linking requirements to model components, allowing easy navigation between them.
- Test plans document the tests to be run, including input signals, expected outputs, and system parameters.
- Test cases, often stored in spreadsheets, provide specific input data and expected results for verification.
Effective requirements linking and test planning are essential for ensuring that all specified functionalities are tested and that the system's behavior can be systematically verified against its intended purpose.
Linking a requirement like 'duty cycle must be between 0 and 1' to the PWM conversion block in the ETC model and defining test cases in an Excel file to verify this.
Key takeaways
- Verification ensures a system is built according to its specifications, while validation confirms it meets user needs.
- Simulation-based testing is a core technique in MBD for verifying model behavior against requirements.
- A structured workflow (prepare, load, run, process, report) is essential for effective simulation-based testing.
- Traceability between requirements and model components is critical for systematic V&V.
- Test plans and test cases provide the necessary structure and data for executing verification activities.
- Organizing MBD projects into logical folders improves manageability and collaboration.
- Leveraging tools like Simulink's requirement linking and external data import enhances the V&V process.
Key terms
Model-Based Design (MBD)VerificationValidationSimulation-Based TestingFormal VerificationTraceabilityConformanceTest PlanTest CaseElectronic Throttle Control (ETC)
Test your understanding
- What is the fundamental difference between verification and validation in the context of MBD?
- How does simulation-based testing contribute to the verification process, and what are its limitations?
- Describe the key steps involved in the simulation-based testing workflow.
- Why is establishing traceability between requirements and model components important for V&V?
- How can external data sources like Excel spreadsheets be utilized within the simulation-based testing process?