The increasing number of features and complexity of today's automotive software architectures bring new challenges to the product development cycle. As a product is being developed, there is a need for information created during the early phases to flow seamlessly into subsequent phases. For example, information defined for an ECU during the design phase should be re-used when that ECU is tested during manufacture. Challenges often arise from the fact that one vendor's tools may be appropriate for design, but a different vendor's tools are best suited for manufacturing test.
This paper discusses business and technical issues surrounding the transfer of information between such tools. Two case studies are used for discussion. One deals with databases describing signals transferred over an in-vehicle network and the other discusses simulation models as both transition from early designs through various test phases.