The Electric/Electronic architecture (E/E architecture) as a set of interconnected services, software and hardware components constitutes the base for the development of new vehicle functions. Today, the development lifecycle has a duration of approximately three years in order to release an E/E architecture concept which is later on implemented, integrated, verified, and validated within the corresponding software and hardware engineering processes. However, the necessity to continuously redesign single functions or components with regard to the whole lifecycle of a vehicle claims for an adaption of this development pattern. The technical elements of the E/E architecture path the way for this trend by means of central computing platforms (that can be extended in a modular manner) as well as new forms of software logistics in respect of software updates over the air. In order to apply these technologies in reality, current processes and development methodologies have to be adapted. At its core, the support of frequent software and hardware releases has to be tackled. From an E/E architecture point of view, the implementation of planned software or hardware releases depends on their integratability into the overall system. Consequently, the intended continuous release process (especially for software) results into a continuous synchronization between (software) engineers and E/E-architects in the context of the E/E architecture development process. Based on this new development pattern, we suggest a model-based approach for the agile development of the E/E architecture. The frame of the methodology are two workflows which facilitate the assessment and release of changes on an existing E/E architecture. The methodology assumes a top down change proceeding where the initial change corresponds to the introduction of a new functional unit. Based on that, the impact of this introduction with regard to the overall functional E/E architecture is assessed. Emphasis in this context is put on functional testing of event chains as well as the verification of timing properties that an event chain features. Afterwards, the integration of newly introduced functionality on existing computing resources, i.e. the networking level of the E/E architecture, is considered. Depending on the output of both assessments, which reveal whether particular changes can be implemented from an architecture point of view, an E/E architecture release is realized.
展开▼
