Christopher Kirk Davey

Software Systems Engineering with Model-Based Design

Further, automotive software systems engineers must deliver features that cross multiple domains (body, chassis, powertrain, multimedia, driver assistance, personalization, and human machine interfaces) and reside on a distributed network of modules. These vehicle systems are also delivered through the cooperation of many automotive and non-automotive suppliers based in various geographic locations, which poses a significant project management challenge to the software systems engineering team. In addition to managing the initial project, the software systems engineer must also explicitly design for and support the re-use of stand-alone software features, mechatronic subsystems and entire vehicle-level, electronic-control-system electrical architectures. Finally, the traditional automotive software systems engineering lifecycle has expanded to include processes, methods, tools, and infrastructure (PMTI) that must integrate across all phases and domains of the technology innovation and product delivery- maintenance-disposal lifecycle.