White paper guide to Automotive Software Development: Automotive Standards, Security, and Emerging Technology



Download 401.3 Kb.
View original pdf
Page3/13
Date07.07.2023
Size401.3 Kb.
#61667
1   2   3   4   5   6   7   8   9   ...   13
whitepaper-qac-automotive-software-development
How to Achieve Coding Standard
Compliance
Achieving compliance to any coding standard takes knowledge, skill, and the right tools. Here are seven recommended steps to achieve compliance:

www.perforce.com
© Perforce Software, Inc. All trademarks and registered trademarks are the property of their respective owners. (0220RB21)
WHITE PAPER
4 | Guide to Automotive Software Development
1. Know the Rules
You need to know the coding rules pertinent to which version of Cor C+ you’re using.
2. Check Your Code Constantly
Continuously inspecting your code for violations is the best way to improve quality.
3. Set Baselines
Embedded systems come with legacy codebases. By setting baselines, you can focus on making sure your new code is compliant.
4. Prioritize Violations Based on Risk
You could have hundreds or even thousands of violations in your code. That’s why it’s important to prioritize rule violations based on risk severity. Some static code analysis tools can do this for you.
5. Document Your Deviations
Sometimes there are exceptions to the rule. But when it comes to compliance, every rule deviation needs to be well-documented.
6. Monitor Your Compliance
Keep an eye on how compliant your code is. Using a static code analyzer makes this easier by automatically generating a compliance report.
7. Choose the Right Static Code Analyzer
Choosing the right static code analyzer makes everything else easy. It takes care of scanning your code — new and legacy — for violations. It prioritizes vulnerabilities based on risk.
ISO 26262 and ASIL: Automotive
Functional Safety
ISO 26262 - Road vehicles — functional safety, is the major functional safety standard used in the automotive industry, and ASIL is a key component to determine safety requirements for software development. It is a risk-based safety standard and applies to electric and/or electronic systems in production vehicles. This includes driver assistance, propulsion, and vehicle dynamics control systems. It covers the functional safety aspects of the entire development process Requirements specification Design Implementation Integration Verification Validation Configuration

Download 401.3 Kb.

Share with your friends:
1   2   3   4   5   6   7   8   9   ...   13




The database is protected by copyright ©ininet.org 2024
send message

    Main page