Editing Automotive engineering (section)

===The V-approach===
One way to effectively deal with the inherent multi-physics and the [[control system]]s development that is involved when including intelligent systems, is to adopt the [[V-Model]] approach to systems development, as has been widely used in the automotive industry for twenty years or more.  In this V-approach, system-level requirements are propagated down the V via subsystems to component design, and the system performance is validated at increasing integration levels. Engineering of mechatronic systems requires the application of two interconnected "V-cycles": one focusing on the multi-physics system engineering (like the mechanical and electrical components of an electrically powered steering system, including sensors and actuators); and the other focuses on the controls engineering, the control logic, the software and realization of the control hardware and embedded software.<ref>{{cite journal|last1=Cabrera|first1=A.|last2=Foeken|first2=M.J.|last3=Tekin|first3=O.A.|last4=Woestenenk|first4=K.|last5=Erden|first5=M.S.|last6=De Schutter|first6=B.|last7=Van Tooren|first7=M.J.L.|last8=Babuska|first8=R.|last9=van Houten|first9=F.J.|last10=Tomiyama|first10=T.|title=Towards automation of control software: a review of challenges in mechatronic design|journal=Mechatronics|date=2010|volume=20|issue=8|pages=876–886|doi=10.1016/j.mechatronics.2010.05.003}}</ref><ref>{{cite journal|last1=Cabrera|first1=A.|last2=Woestenenk|first2=K.|title=An architectural model to support cooperative design for mechatronic products: a control design case|journal=Mechatronics|volume=21|issue=3|pages=534–547|doi=10.1016/j.mechatronics.2011.01.009|year=2011}}</ref>