Automotive SPICE : IQI India

Both processes leads to changing project work products which are already baselined. To update the baselined work products, change (control) management (part of Configuration Management Process) is called. However, before calling change management process, the analysis of defects / change request shall be completed. The concept of their implementation is shown below: Automotive SPICE defines two processe s; SUP.9 Problem Resolution Management (PRM) & SUP.10 Change Request Management (CRM) Process. Few organisation manages these two processes with same tool & combines the flow but identifies with categorisation.  Difficulty is seen when CMMI based organisation tries to fulfil the CRM requirements using SG2 requirement of CM Process Area of CMMI. Some of the activities are not get defined completely. By adding additional requirements as indicate above (also defined in Automotive SPICE SUP.10), the compliance to SUP....

Automotive SPICE v2.5 has Engineering Processes as ENG.1 ~ ENG.10 covering system & software domain processes. Automotive SPICE v3.0 has been upgraded with concept of "Plug-in" domain specific processes. System Engineering process have been separated with SYS.1 ~ SYS.5 on top level of architecture. Domain specific processes, i.e., Software Engineering have been defined as SWE.1 ~ SWE.6. The placeholder for Hardware Engineering (HWE.1 ~ HWE.4) & Mechanical Engineering (MEE.1 ~ MEE.4) have been created. In future, with the availability of Hardware engineering & Mechanical Engineering processes, Process scope can be enlarged.  For details visit www.iqiconsulting.com or write to us on contact@iqiconsulting.com