V - Model
The left side of the V-Model represents the system design and planning phase. It begins with requirement analysis, where we define the functional needs of the tool wear monitoring system—such as sensing vibration, simulating structural stress, and predicting wear conditions. Next comes the system design, where we identify major subsystems like the tool wear setup, sensor module, microcontroller, and analysis blocks. This is followed by architecture design, where we define how these components will communicate using signal buses, and plan the overall Simulink architecture. Finally, at the bottom of the V, we reach the detailed design stage, where we design the internal logic of each subsystem—such as filters in the sensor module, logic in the microcontroller, and FEA calculations in the analysis engine. These stages ensure a well-structured and modular system before any implementation begins.
The right side of the V-Model focuses on implementation, testing, and validation of the system. It starts with unit testing, where each block (like the Sensor Module or FEA block) is individually tested in Simulink for correct functionality. This is followed by integration testing, where subsystems are connected via bus signals and tested as a group to ensure smooth data flow and correct interactions. After that, system testing is performed to verify if the complete tool wear monitoring system works under different tool wear conditions and vibration inputs. Finally, acceptance testing or validation is done—comparing simulation results against expected outcomes (or real-world behavior if data is available), and checking if the system meets the original requirements. This systematic right-hand flow ensures the final model is reliable, accurate, and ready for deployment or further refinement.