< Previous | Contents | Next >

D.1 The "Plug-in" concept

image

SYS.4

SYS.3

SYS.5

SYS.2

SYS.1

MAN.3

ACQ.4

SUP.1

SUP.8

SUP.9

SUP.10

System level

The following figure shows the basic principle of the "plug-in" concept. The top-level comprises all system engineering processes organized in a system "V". Depending on the product to be developed the corresponding engineering disciplines with their domain-specific processes (e.g. hardware engineering HWE, mechanical engineering MEE, or software engineering SWE) can be added to the assessment scope. All other processes such as management processes and supporting processes are domain-independent and are therefore designed in a way that they can be applied to both the system level and the domain levels.




image

MEE.4

MEE.3

SWE.4

SWE.3

HWE.4

HWE.3

MEE.5

MEE.2

SWE.5

SWE.2

HWE.5

HWE.2

MEE.6

MEE.1

SWE.6

SWE.1

HWE.6

HWE.1

Examplary processes for other domains, neither developed

by VDA nor part of Automotive SPICE PRM/PAM

VDA scope as part of Automotive SPICE 3.1 PRM/PAM

SYS : System engineering SWE : Software engineering HWE : Hardware engineering

MEE : Mechanical engineering

Domain level

Figure D.1 — The "Plug-in" concept

All processes printed in bold are part of the Automotive SPICE 3.1 PRM/PAM whereas the other processes (mechanical engineering and hardware engineering) are not developed under VDA QMC mandate.