Re: OpenChain and Automotive SPICE
Mary: Thanks for the answer!toggle quoted messageShow quoted text
I agree that an integration of OpenChain and ASPICE on a specification level makes no sense. They are two different topics and there are other domains than automotive obviously.
But, assuming world dominance of OpenChain ;-), some/most automotive suppliers may want to pass both OpenChain and ASPICE conformance assessments. Then the implementing processes overlap and you need to think about integration *at the specific company* (even if there is variation at the specific company).
So I was wondering about experiences with that integration. Without laying open specific processes, we can only talk about it on the spec level.
Here is an illustration of what I'm trying to say:
One might easily say that process Automotive SPICE ACQ.15 supplier qualification requires the supplier is OpenChain compliant.
Or that that process ASPICE SYS.1 requirements elicitation identifies (non-functional) open source requirements of the customer/market and that those match roles and competencies defined in OpenChain (OpenChain 2.1 18.104.22.168 + 2), the use cases (22.214.171.124), and so forth.
I was wondering whether anyone has spent cycles on this is and whether it is publicly accessible.
It might also be interesting to look at related domains.
On 05.01.21 14:24, Mattran, Mary wrote:
I do see a strong connection between ASPICE and Open Chain. ASPICE does not go into the topic of Open Source, and that is where Open Chain fills in. In fact, we are using our ASPICE assessors to help us with Open Chain compliance. We will need to educate our other assessors on Open Chain.