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

By -
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 processes; 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 the process in Automotive SPICE or CMMI, please write to us contact@iqiconsulting.com 

Comments

Post a Comment

Popular posts from this blog

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...
Read more

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

Online training on "Understand ASPICE to Improve Product Quality"

By -
IQI Consulting is organizing online ASPICE Training that will primarily focus on Implementation aspects of ASPICE, the Know-how that will help you to understand / better implement the Base practices and face the assessment. Below are Key challenges that are faced by practitioners when implementing ASPICE and this training and will help you to a greater extent. Establishing Bi-directional traceability across the V-Life cycle Identifying System elements and Software components and establishing Interfaces between them Implementation of Model-Based Design vs. Manual Design to demonstrate ASPICE compliance Defining Strategy across the V-Life cycle. How and Why? System and Software Integration Testing - A Missing piece in OEMs and Tier1? Definition of Resource consumption goals and collecting the data to understand the need for Architecture Design optimization. Register today and get your answers on how the challenges can be overcome by Implementing ASPICE. https://l...
Read more