Surprisingly there's not a single post related to ASPICE here, even more concerning because the majority of people are in the SF Bay area, and I've seen a bunch of people wondering about Autonomous vehicles related jobs.
I've seen how SW developers don't believe in "development processes", I've seen how SW is developed most of the times and why it is buggy, and for the same reason I like how ASPICE is defined to avoid a non structured way of developing.
It's sad how many people are working on Autonomous vehicles at least in the Bay Area without knowing what ASPICE is, or keep believing it is a piece of paperwork that someone else will take care of.
#auto #autonomous
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
Process to create a requirements elicitation procedure. Process to review the requirements elicitation procedure. Process to approve the requirements elicitation procedure. That's just definition. Now add documentation of all of this. Then rinse and repeat for every step of the process; requirements analysis, architectural design, product design, unit testing, integration testing, qualification testing, product release, configuration management, change request management, problem resolution management, and on and on. And when that's done, establish upward and downward traces between requirement, architecture, design, test case, and test result.
It's not surprising that people don't want to do it. You need 50% more resources just to handle the documentation. It adds cost to a product which customers aren't always willing to pay for.
Having gone through 2 assessments and a recent global reorg to support ASPICE L3, I can see where and how it's useful. But I also know how much work is involved. It's very useful once established, but it's thousands and thousands of hours and millions of dollars to get there.
As for who is using it, VW (VAG), Daimler, Stellantis, and any of their suppliers wanting to win new business. They're starting to require L3 on new programs and use their own assessment teams to evaluate suppliers.