The introduction of Software concepts into the vehicle and its’ surrounding ecosystem lead to the (R)evolution of E/E Architectures at the car manufacturers. The journey begins for most OEMs at a decentralized or Domain centric architectures where functions realized on single special purpose ECUs are connected together, over a Server Zone architecture where a less strict allocation of functions and the introduction of Zones and HPCs (High Performance Computers) is done, to a Central Compute or Zero Edge architecture in which most of the functionality is centralized in a kind of board computer and Sensors and Actuators are hosting no Software or a very small, more “firmware” like, software. While the journey is ongoing in most OEMs E/E architecture evolutions the destination of the journey and the speed of travel is different. This leads to the challenge that the Functions developed in the industry based on decades of Domain Know-How have to be deployed to different vehicle architectures. Therefore, the approach of developing functions must be changed: Following a pattern that allows the re-use of the functions in the three beforementioned architectures and hybrids of them, that allow an easier migration of the OEMs to new architectures and aims to increase the re-use through different vehicle lines and generatons. The pattern consists of 3 levels of standardized interfaces and is realized over 4 levels of Software and is based on existing and proposed standards. This can lead to innovative products and solutions that allow for virtual development and end to end testing. With COVESA VSS can be used for semantic API and the COVESA Community can look into standardizing other interfaces and shaping existing and new standards to increase the exchangeability and re-use of Hardware and Software components in the industry.