What do we know so far?<\/strong><\/p>\n\n\n\n In our last post we\u00b4ve learned what A-SPICE roughly means, who is affected by it, what each Level means and how each Level is defined.<\/p>\n\n\n\n A-SPICE – Process<\/strong><\/p>\n\n\n\n Let\u00b4s get to the other half of A-SPICE, the process level<\/strong>. A-SPICE basically follows the approach of a V-Model, which means on the left hand side you define your requirements, architecture, software etc. and on the right hand side you deliver the proper testing\/evidence showing that your product is working as specified. The processes within A-SPICE are divided into three areas. Primary Life Cycle Processes<\/strong> Organizational Life Cycle Processes<\/strong> Supporting Life Cycle Processes<\/strong> V-Model<\/strong><\/p>\n\n\n\n As I mentioned the norm uses the V-Model, but there is much more! Within every group you will find sub-processes. So in the SYS process group you will find processes like \u201cSYS.1 \u2013 Requirements Elicitation\u201d or in MAN process group \u201cMAN.3 \u2013 Project Management\u201d. Those processes describe in a more granular way what you have to do to fulfill the process\/norm. So this looks like a lot of work, and it is! HIS\/VDA-Scope<\/strong><\/p>\n\n\n\n HIS (Hersteller-Initiative-Software) is a German automobile manufacturers working group who work together in the field of non-competitive issues relating to software development for control units, on the subject of process assessments. They have defined a subset of processes which describes the minimum set of assessed processes. Later it was renamed and taken over by the VDA, but both terms are being used today. So don\u00b4t get confused, they talk about the same stuff<\/p>\n\n\n\n But what processes do we now need Thank you<\/strong><\/p>\n\n\n\n so far for your time. I will continue in the next post with getting into each process and explaining the purpose and deliverables you need to fulfill.<\/p>\n\n\n\n NEXT UP<\/strong><\/p>\n\n\n\n Hi there, It\u00b4s Denis again and welcome back to my series of A-SPICE related thoughts and findings. In case you…<\/p>\n","protected":false},"author":6158,"featured_media":3345,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[495,494,501,496,503,29,459,505,504,502,497],"industry":[62,63,64],"product":[],"coauthors":[493],"class_list":["post-3344","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-a-spice","tag-denis","tag-his-vda-scope","tag-process","tag-project-management","tag-requirements-management","tag-software","tag-software-engineering","tag-system-engineering","tag-test-management","tag-v-model","industry-automotive-transportation","industry-automotive-oems","industry-automotive-suppliers"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/4\/2021\/07\/A-SPICE-second-pic..png","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/3344","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/users\/6158"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/comments?post=3344"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/3344\/revisions"}],"predecessor-version":[{"id":3346,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/3344\/revisions\/3346"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media\/3345"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media?parent=3344"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/categories?post=3344"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/tags?post=3344"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/industry?post=3344"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/product?post=3344"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/coauthors?post=3344"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
From my perspective the V-Model is not really a new development approach. A lot of companies do already know it or develop based on it. So you may ask \u201cwhy do we need A-SPICE, if V-Model is already established?\u201d. The challenge is that its being used differentially by everyone. With A-SPICE the purpose is to standardize it so a minimum set of deliverables is guaranteed throughout the development supply chain. So if a OEM receives a externally developed component, he knows that at least all relevant documentation work products were generated and can be invoked if needed.<\/p>\n\n\n\n
\u2013 Primary Life Cycle Processes
\u2013 Organizational Life Cycle Processes
\u2013 Supporting Life Cycle Processes<\/p>\n\n\n\n
They mainly contain processes in the area of acquisition and delivery of products. It includes the development processes like engineering, design, development, integration and testing. In A-SPICE language spoken it affects ACQ, SPL, SYS, SWE groups.<\/p>\n\n\n\n
It provides all relevant processes, resources, products to help the project achieve the companies business goals. It only uses the SUP group.<\/p>\n\n\n\n
As the name already lets you suggest it \u201csupports\u201d all the other processes within the A-SPICE universe. For this you will use MAN, PIM, REU groups.<\/p>\n\n\n\n
In general we have following groups within A-SPICE:<\/p>\n\n\n\n
But maybe let me visualize this a bit more so it gets clearer.
Based on how I understand it, it should look something like this:<\/p>\n\n\n\n![\"\"](\"https:\/\/bettersoftwarecode.files.wordpress.com\/2020\/11\/image-1.png?w=1024\")
<\/figure>\n\n\n\n
But I have some good news as well. From this set of processes there was a subset created which is being focused on when assessing. So from my understanding if you are being assessed than its possible that it only will happen on the so called HIS\/VDA scope.
\u201cWhat\u00b4s that?\u201d you ask. Let me help you.<\/p>\n\n\n\n
Based on our wonderful picture we can now see the red highlighted processes, which are relevant for the HIS\/VDA Scope.<\/p>\n\n\n\n![\"\"](\"https:\/\/bettersoftwarecode.files.wordpress.com\/2020\/11\/image-3.png?w=1024\")
<\/figure>\n\n\n\n