In traditional automotive electronic design, software update has been a component oriented manual process, rather than a systematic designed in capability suitable for automation. In recent days, as software content in vehicles are growing, need to update software in vehicles more frequently, is becoming a necessity. Moreover, additional attributes for software updates - timely delivery of security related update to vehicle, desire to reign in the increasing cost of software updates, etc., requires a system engineering perspective on software update aspect, rather than a component oriented approach. The paper reviews state of practice and state of art vehicle software update capability. In order to establish relevant system attribute that impacts software update capability, business driving forces are identified and reviewed. Comparisons to other domains that uses software update frequently – cellular, connected personal computers, etc., are also reviewed. Based on above, architectural models for software update are developed, and each model is evaluated against all system attributes established earlier. As automobile domain consists of various electrical architectural styles (Combustion Engine, Hybrid, Battery, Fuel cell, etc.) and various domains (Infotainment, Safety, Mobility, Telematics, ADAS, Autonomous, etc.), what becomes apparent that to reign in the cost of future software update need to introduce automation in the software update process. And to introduce automation need to have a systematic architecture, and standardized interfaces. However, there is not a single unified solution. One approach may not deliver the most effective solution. Depending on mix of architecture and domain a combination of approaches would be necessary, but automation using systematic architecture to get ahead of the ever increasing software update burden, becomes an enabler for survival.