2025年汽车软件开发状况报告_核心挑战_63页_5mb

2025 State of Automotive Software Development Report Summary

Core Content

This report highlights the current concerns and trends in automotive software development based on responses from over 650 professionals worldwide. It covers key areas such as quality, safety, security, team productivity, and testing, with a focus on how these concerns vary by region, organization type, and development focus.

Main Concerns

1. Quality

• Leading Concern: 29% of respondents cited quality as their top concern, consistent with 2024.

• Top Quality Issues:

  • "Our codebase is too complex" (28%)
  • "Our testing efforts are not exhaustive—and we do not have time to test more" (27%)
  • "It is difficult to enforce coding best practices" (21%)
  • "Peer code reviews are inconsistent" (8%)

• Experience Level Trends:

  • Less than 1 year: Most concerned with code complexity (57%)
  • 1–3 years: Top concern also code complexity (45%)
  • 3–5 years: Concerned with enforcing best practices (29%)
  • 5+ years: Testing not exhaustive (most experienced)

• Regional Trends:

  • Most regions cited code complexity as the top concern.
  • Middle East, Asia-Pacific, and Africa had more concern about testing resources.
  • Europe/UK and North America had code complexity and enforcing best practices as top concerns.

• Organization Type Trends:

  • OEMs: Most concerned with code complexity.
  • Tier 3 suppliers: Also concerned with code complexity.
  • Tier 1 suppliers: Most concerned with testing efforts.
  • Tier 2 suppliers: Most concerned with enforcing coding best practices.

2. Safety

• Leading Concern: 28% of respondents cited safety as their top concern, up from 22% in 2024.

• Top Safety Issues:

  • "It is difficult (and time-consuming) to fulfill every ISO 26262 requirement"
  • "Our customers expect us to comply with a safe coding standard (e.g., MISRA)"
  • "We are struggling to ensure safety across the supply chain"

• Experience Level Trends:

  • Less than 1 year: Concerned with fulfilling security requirements.
  • 1–3 years and 3–5 years: Concerned with unauthorized access to on-board/off-board systems.
  • 5+ years: Concerned with security training and team skills.

• Regional Trends:

  • Most regions cited difficulty in fulfilling ISO 26262 requirements.
  • Middle East and Africa: More concerned with customer expectations for safe coding standards.

• Organization Type Trends:

  • Small organizations: Most concerned with customer expectations for safe coding standards (40%).
  • Medium, Large, and Enterprise organizations: Most concerned with fulfilling ISO 26262 requirements.

3. Security

• Leading Concern: 22% of respondents cited security as their top concern, up from 19% in 2024.

• Top Security Issues:

  • "It is difficult (and time-consuming) to fulfill security requirements (i.e., IEC/ISO 21434)"
  • "Our development team lacks the skills needed to combat security threats"
  • "We are concerned with unauthorized access to on-board/off-board systems"
  • "We need to enable secure, efficient collaboration across globally distributed teams"
  • "Security testing takes too much time—it slows down development"

• Experience Level Trends:

  • Less than 1 year: Concerned with fulfilling security requirements.
  • 1–3 years and 3–5 years: Concerned with unauthorized access to systems.
  • 5+ years: Concerned with team skills and security training.

• Regional Trends:

  • North America, Middle East, and Asia-Pacific had higher concerns about fulfilling security requirements.
  • All regions reported distinct security concerns, emphasizing the need for a secure software development lifecycle.

4. Team Productivity

• Leading Concern: 10% of respondents cited team productivity as their top concern.

• Top Productivity Issues:

  • "Managing design/development/IP assets to ensure alignment across hardware and software teams in parallel development" (32%)
  • "Struggling to meet the performance and scalability demands of distributed developers and remote teams working with large, complex assets" (25%)

• Tools and Practices:

  • Software Bill of Materials (SBoM) is recommended to improve alignment and reduce rework.
  • Tools like Perforce IPLM are being adopted for managing IP and SBoM.

Key Trends and Insights

• Hybrid Work Model: Hybrid work remains the dominant model, with 54% of respondents practicing it. While some companies are pushing for return-to-office (RTO), the trend is mixed, with some reporting improved morale and others reporting diminished morale.
• Market Conditions:
  • The global economy was the top concern (50%).
  • Outsourcing talent and resources (34%) and ongoing conflict (31%) were also significant challenges.
• EV Development:
  • EV design is impacting most automotive professionals, though the extent varies by region.
  • North America leads in EV development, while China continues to drive EV sales growth.
• AI/ML Impact:
  • Safety has become a top concern due to the integration of AI and ML in connected and autonomous vehicles.
  • New standards like ISO/DPAS 8800 are emerging to address the challenges of functionally safe AI systems.
• Compliance and Training:
  • Compliance remains vital, with 53% of respondents using MISRA.
  • Training in security, compliance, and DevOps is increasingly emphasized to maintain competitiveness and improve software safety and security.

Conclusion

The automotive software development landscape in 2025 is marked by heightened focus on quality, safety, and security. While the global economy and workforce dynamics continue to influence development strategies, the adoption of secure practices, efficient collaboration tools, and robust coding standards is essential for addressing the evolving challenges in the industry.