Automotive SPICE - Structure

By -
Automtoive SPICE Model has been derived from ISO/IEC 15504 Part 5 (Exemplar Process Assessment for Information Technology). Out of 48 processes in Part 5, 26 processes are selected and described (with some changes) in Automotive SPICE & 5 new processes are added. Thus total 31 processes are defined in Automotive SPICE. The processes which are relevant to manage customer-supplier relationship in automotive industry (OEM-Supplier) has been described in Automotive SPICE.

Each process is defined with process purpose, outcome, base practices (BP) & output work product (WP). BP & WP is mapped with outcome of the processes with n-to-n relationship. Automotive SPICE model defines 5 Capability Level (CL). Each CL is characterized with Process Attributes (PA). CL-1 has 1 PA, CL-2 to CL-5 has 2 PA each. Each Process Attributes has been defined with "Result of full achievement", Generic Practices (GP) & Generic Work Product (GWP). GP & GWP are mapped with "Result of full achievement".

All xP are termed as process indicator. These indicator are sufficient to understnad the model for process improvement & conducting process assessment using Automotive SPICE model.

For more details please visit again for write to us info@iqiconsulting.com

Comments

Post a Comment

Popular posts from this blog

Automotive SPICE v3.0: Plug-in Concept

By -
Image
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
Read more

Maturity Level concept using Automotive SPICE

By -
CL & ML : Differences Characteristics Capability Level (CL) Maturity Level (ML) Result Applicability Process Organization unit Scope Process & CL §     Any number of processes can be selected (mostly – VDA Scope) . §     CL can be defined for respective process . §     Pre-defined set of processes for respective ML Scope Project §     Single project (mostly) OR §     Multiple projects §     Class 1: 4 instances (Minimum) §     Class 2: 2 instances (Minimum) §     Multiple projects to represent “organization unit” appropriately. §     Minimum number of sample shall satisfy “Class” of assessment rule. Rating Aggregation   §     No aggregation within project (mostly) §     For multiple projects - aggregation as per rule (R1/R2/R3) can be applied. §     Aggregation is done as rule rating rule o    R1 – Rate BP/GP & aggregate o  
Read more

Concept of SUP.9 Problem Resolution & SUP.10 Change Request Management

By -
Image
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.10 can be achieved. For more information on any of t
Read more