publication . Thesis . 2014

Virtual integration: A game-theoretic approach

Schorer, Michael;
Open Access English
  • Published: 14 Jul 2014
  • Country: Germany
Abstract
Embedded systems are playing a key role to enable the features of todays cars and other road vehicles. Advances in current hardware platforms of these embedded systems and growing implementation of features in software rather than in new hardware modules lead to new and continuously more complex automotive software systems. The integration process in the course of development of automotive software systems is a crucial and complex phase. An efficient combination of the set of components into a functioning whole is made difficult due to the fine granular and highly interconnected architectural structure of these systems. Also, the high cost pressure and strict sa...
Subjects
free text keywords: 004 Informatik, ddc:004
Related Organizations

8.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 8.2 Further Work . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 3.2 Compatibility Check process. SA = System Architecture, CR = Compatibility Check Result, SC = Source Code, SB = Software Build, TR = Test Report . . . . . . . . . . . . . . . . . . . . . . 3.3 Integration Planning process. RP = Release Plan, PP = Project Plan, SA = System Architecture, IP = Integration Plan, SC = Source Code, SB = Software Build . . . . . . . . . . . . . . . . 3.4 Integration monitoring process. IP = Integration Plan, SB = Software Build, IT = Integration Trace . . . . . . . . . . . . . 3.5 Integration administration process. IP = Integration Plan, SB = Software Build, TI = Ticket for Integration, IP = Changed Integration Plan . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 Build automation process. IP = Integration Plan, SB = Software Build, BR = Build Rules, IT = Integration Trace . . . . . 4.1 The research project VitaS3 and its main research areas, aligned to an instance of the iterated V-model (see section 2). 1: Top level integration support methodology; 2: Compatibility verification on architecture layers; 3: Optimization of integration plans; 4: Integration monitoring; 5: Integration Administration; 6: Automated Integration; 7: Tooling 42 4.2 Kuhlen's transformation model of knowledge and information. Adapted from Kuhlen, Seeger, and Strauch, 2004, p.

Powered by OpenAIRE Open Research Graph
Any information missing or wrong?Report an Issue