Hi there,<\/p>\n\n\n\n
I\u00b4m Denis<\/strong> and I want to welcome you <\/strong>on my first blog post. Purpose<\/strong><\/p>\n\n\n\n I want to start a series about A-SPICE and its containing processes. Explaining how I think the norm works and what my understanding of it is. Maybe this can give you an easier introduction to the norm than I had. If that has worked, than I\u00b4m already happy :).<\/p>\n\n\n\n What is A-SPICE?<\/strong><\/p>\n\n\n\n A-SPICE stands for: How can I measure my fulfillment?<\/strong><\/p>\n\n\n\n In this case your processes will be evaluated and rated. In the end your processes will get grades in %, showing you how well you have performed in certain areas. Based on that you will receive your A-SPICE Level. That\u2019s the short answer. Now the longer answer (sorry for that) Now behind all those process attributes there are again sub packages. But that\u2019s where I want to stop now. If you need more input on that I can recommend getting the A-SPICE Bible <\/a>.<\/p>\n\n\n\n
Why am I doing this?
In my job I often encounter the challenge of fulfilling or understanding several regulatories and its requirements (ISO\/norm).
And I must say. Its not an easy task!
Often I hear terms like ISO26262, A-SPICE, ISO9001 etc. But what does this actually mean?
From this wide area of challenges I want to take a closer look on A(utomotive)-SPICE. Explaining it with my own words and give you my thoughts to it.
But keep in mind, I\u00b4m not <\/strong>a expert <\/strong>or any kind of certified accessor<\/strong>.<\/p>\n\n\n\n
A = A<\/strong>utomotive
S = S<\/strong>oftware
P = P<\/strong>rocess
I = I<\/strong>mprovement
C = C<\/strong>apability
E = dE<\/strong>termination
It is the European answer to CMMI ->(What is CMMI<\/a>?)
And it describes basically two things:
\u2013 How your process should look like (V-Model)
\u2013 How you can measure your fulfillment (SPICE Level)
But before we dig to deep, maybe lets clarify first, what stakeholders are involved in this? A-SPICE applies to the whole development supply chain in the automotive segment. This means if you are a TIER 1 supplier, OEM, TIER 3 supplier, etc. You may be forced to fulfill a certain Automotive SPICE Level to continue as a part within the supply chain. A-SPICE focuses on the products involving software, which means you will see that the processes are more focused on that area<\/p>\n\n\n\n
<\/p>\n\n\n\n
To reach a certain Level you need to fulfill a set of capabilities and process attributes. Based on this your SPICE Level will be determined.
What kind of Levels do actually exist and how are they defined?
\u2013 Level 0: Incomplete process<\/strong>
So whatever you do and a product comes out at the end. You\u00b4ve successfully reached Level 0. That\u2019s something \ud83d\ude42
\u2013 Level 1: Performed process<\/strong>
Here you have defined the goal for your process which will be achieved at the end. From my point of view that also something which can be achieved very fast.
\u2013 Level 2: Managed process<\/strong>
Our process is now being managed, improved and observed. In addition your results (e.g. a Specification, Software, Requirements) are defined and managed as well.
\u2013 Level 3: Established process<\/strong>
Now we want to use our managed process and establish it so we can always reach our deliverables. This means your process should reach a quality of being a standard process for your development.
\u2013 Level 4: Predictable process<\/strong>
Your established process now works within determined boundaries to obtain its deliverables. From my perspective this means standardizing your process more and more and creating a controlled environment. This should prevent getting any bad surprises.
\u2013 Level 5: Optimizing process<\/strong>
Now we have reached the highest and last Level for A-SPICE. This is reached by continuously improving your process based on challenges and targets you have to fulfill in your projects.
Now to identify your Level you need to check the fulfillment of the capabilities of your process. Lets take a look what kind of process attributes we have:
Level 0:<\/strong> Does not contain any PA\u00b4s (process attributes).
Level 1:<\/strong>
PA1.1 Process performance
Level 2:<\/strong>
PA2.1 Performance management
PA2.2 Work product management
Level 3:<\/strong>
PA3.1 Process definition
PA3.2 Process deployment
Level 4:<\/strong>
PA4.1 Process measure
PA4.2 Process control
Level 5:<\/strong>
PA5.1 Process innovation
PA5.2 Continuous optimization
Now that you have your PA\u00b4s you can now evaluate your processes by using following rating scale.<\/p>\n\n\n\n