CARNIQ’s Post

Project teams often fail to understand the difference between traceability and consistency or how one supports another. ASPICE 4.0 now combines 2 BPs into 1. What does it mean for you? Check out our discussion below. Love to hear your thoughts in the comments section...!!! #aspice #carniq #automotivecybersecurity

🚀 Join us on YouTube as we explore the evolution of ASPICE capability levels from 3.1 to 4.0! 🔄 What updates have been made? Let's dive in and discover together! Praveen Suvarna Ronak Ghodasara Dharmesh Patel Riva K. Bhoomika J #SoftwareDevelopment #ContinuousImprovement #carniq #ASPICE #ISO21434 📈💡

ASPICE 4.0 is not only an evolution, it is also a cleanup! so here are some introducing words : While waiting for the first ASPICE 4.0 update training I had to study the new PAM anyhow in order to prepare myself for the Agile SPICE working group. I started to build this overview for myself but it might help you as well to find all the changes at a glance.. You’ll always find one page for the outcomes and one for the base practices for every process area.  For a better readability I split it in several parts. Anyhow once all process areas are complete, I’ll upload the full file to my homepage www.a-spice.de Spoiler alert:  ASPICE 4.0 is not only an evolution from my perspective, it is also a cleanup. It becomes more readable, efficient and applicable. Anyhow, there are some unexpected surprises I found, especially in SYS.4 & 5 as well as in MAN.3. Stay tuned! #AutomotiveSPICE #PrincipalAssessor #ProblemResolutionManagement #munich #berlin #wolfsburg #stuttgart #software #process #quality #engineering #automotive #StefanReinhartConsulting #SeitzandReinhartConsulting

In few months time automotive organisations need to align their processes to ASPICE 4.0 and start living them in projects. We made an attempt to explain what has changed in comparison to ASPICE 3.1. Our next episodes to follow on what has changed in individual processes. Stay tuned.. #aspice #iso21434 # carniq # cybersecurity

Did you know automotive software projects gain a 30% efficiency boost with CI/CD in ASPICE 4.0? 82% of these projects achieve this with CI/CD under #ASPICE4. What’s your team doing to enhance software development? Ensuring quality and reliability in your processes? Adopting CI/CD in the ASPICE 4.0 framework isn’t just trendy; it’s a disciplined, comprehensive approach pushing the automotive industry forward. To maximize CI/CD in ASPICE 4.0, try these steps: 1. 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝗘𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴: Ensure each step is documented for better traceability and compliance. 2. 𝗥𝗲𝗴𝘂𝗹𝗮𝗿 𝗖𝗵𝗲𝗰𝗸-𝗨𝗽𝘀: Use the Process Assessment Model (PAM) to frequently assess and find improvement areas. 3. 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗖𝗮𝗽𝗮𝗯𝗶𝗹𝗶𝘁𝘆: Progress through ASPICE’s levels by targeting specific, unique improvements. 4. 𝗞𝗲𝗲𝗽 𝗧𝗿𝗮𝗶𝗻𝗶𝗻𝗴: Keep your team updated on ASPICE 4.0 and CI/CD to align everyone. By refining and adhering to these processes, your team can enhance efficiency, reliability, and the quality of your automotive software. #CI_CD #ASPICE #AutomotiveSoftware #DevelopmentEfficiency #QualityAssurance #ProcessImprovement #SoftwareDevelopment #Traceability #Compliance #PAM #Knot #knotconsulting Are you part of the 82% using CI/CD in ASPICE 4.0? Share how it’s boosted your project efficiency

𝐕𝐀𝐋.𝟏 - 𝐈𝐧𝐧𝐨𝐯𝐚𝐭𝐢𝐯𝐞 𝐨𝐫 𝐢𝐫𝐫𝐞𝐥𝐞𝐯𝐚𝐧𝐭? With ASPICE 4.0, Val.1 Validation has a counterpart to SYS.1 Requirements Elicitation. But what exactly does the process stand for? 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 𝐩𝐮𝐫𝐩𝐨𝐬𝐞 𝑇ℎ𝑒 𝑝𝑢𝑟𝑝𝑜𝑠𝑒 𝑖𝑠 𝑡𝑜 𝑝𝑟𝑜𝑣𝑖𝑑𝑒 𝑒𝑣𝑖𝑑𝑒𝑛𝑐𝑒 𝑡ℎ𝑎𝑡 𝑡ℎ𝑒 𝑒𝑛𝑑 𝑝𝑟𝑜𝑑𝑢𝑐𝑡, 𝑎𝑙𝑙𝑜𝑤𝑖𝑛𝑔 𝑑𝑖𝑟𝑒𝑐𝑡 𝑒𝑛𝑑 𝑢𝑠𝑒𝑟 𝑖𝑛𝑡𝑒𝑟𝑎𝑐𝑡𝑖𝑜𝑛, 𝑠𝑎𝑡𝑖𝑠𝑓𝑖𝑒𝑠 𝑡ℎ𝑒 𝑖𝑛𝑡𝑒𝑛𝑑𝑒𝑑 𝑢𝑠𝑒 𝑒𝑥𝑝𝑒𝑐𝑡𝑎𝑡𝑖𝑜𝑛𝑠 𝑖𝑛 𝑖𝑡𝑠 𝑜𝑝𝑒𝑟𝑎𝑡𝑖𝑜𝑛𝑎𝑙 𝑡𝑎𝑟𝑔𝑒𝑡 𝑒𝑛𝑣𝑖𝑟𝑜𝑛𝑚𝑒𝑛𝑡. While reading the purpose, I had two main questions in mind:  - What exactly is the end product, a simple control unit or the entire vehicle? - What is meant by direct user interaction, popping out the airbag or the interaction on the main display of the car? As often ASPICE is not precise enough with the definition and explanation of concepts and terms. 𝐌𝐲 𝐨𝐩𝐢𝐧𝐢𝐨𝐧  I believe that since the process is not listed in the ‘recommended VDA scope’ and the details leave a lot of room for interpretation, it will have a hard time being applied in practice. 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐲𝐨𝐮𝐫 𝐨𝐩𝐢𝐧𝐢𝐨𝐧 𝐚𝐛𝐨𝐮𝐭 𝐕𝐀𝐋.𝟏?

🚗 Looking for Feedback from ASPICE Experts! 🚗 Hi all! In the context of ECU software project involving ASPICE CL2 and ISO 26262 ASIL-B, and I’m exploring ways to OPTIMIZE the workflow for SHORTER lead times without compromising ASPICE CL2 compliance or functional safety (FuSa) requirements. I’m not an ASPICE expert, so I’d love to get feedback from those with more experience in this area. Here’s the proposed approach: 1️⃣ High-Level Design of the SW component(for each SWC) 2️⃣ Review and approval of the High-Level Design 3️⃣ Begin coding based on the reviewed design 4️⃣ Enhance the design with details during the coding phase 5️⃣ Review both the final code and the updated design for traceability and compliance While I understand ASPICE CL2 typically emphasizes having a detailed design reviewed before coding starts, I’m wondering if this incremental refinement approach could help ASPICE CL2 complaint development for ASIL-B projects. If you have experience or insights on balancing workflow optimization with ASPICE CL2 requirements, I’d greatly appreciate your thoughts. Please share your feedback or suggestions! Thanks in advance! 🙏 #ASPICE #ISO26262 #Automotive #SoftwareDevelopment #FuSa #LeadTimeReduction #QualityManagement

"Test cases are the foundation of tests for Quality Engineer, there are usually several aspects that need to be considered when designing cases, like test depth and breadth, test according to product source code and customer scenarios, test on bare metal and on clouds, etc. And there is usually limited resources for tests, so it is important to balance the test matrices. How do you balance test matrices when designing test cases? The presentation will show you a good practice to balance test matrices. It would take cloud-init as an example to show how to balance the test matrices when designing test cases, and would also show you a tool/framework that can maximize the completion of the test matrices under limited resources. More specifically focusing on: 1. Test matrices that need to be balanced a) Test depth, test breadth b) Test according to product source code, test according to customer scenarios c) Test on bare metal, test on clouds(test on which clouds) 2. The good practice of cloud-init 3. Introduce a good tool/framework to maximize the completion of the test matrices under limited resources" https://lnkd.in/eNEWRCi4

Day 6 ✅: The Waterfall Model Now that we are familiar with what the Software Development Lifecycle (SDLC) is and it's subset the Software Testing Lifecycle (STLC). Let's now look at one of the OG SDLC models, the Waterfall model. 👇👇👇👇 https://lnkd.in/drP6tweG #100DaysOfALXSE #ALX_SE #DoHardThings

Workflow for Step 6 (Standardization)