Sw expert at a manufacturing company with 5,001-10,000 employees
Real User
Top 20
2024-02-08T15:01:51Z
Feb 8, 2024
We use it for all projects where we write our own code. So, it could be vertical control, cluster infotainment, or competitor systems; we use it everywhere. We use it for smaller models and for Simulink models. However, it crashes when we have too many files/functions. When we use Code Prover on large applications, it sometimes crashes. I work with Simulink models, where Prover is fully integrated.
Senior Engineer at a manufacturing company with 10,001+ employees
Real User
Top 5
2023-04-03T07:44:56Z
Apr 3, 2023
We have some code files generated from the development, which we did for different vehicles. With the individual code files, there is a static analysis that we perform based on the checks. We look at what checks are violated. We look at what possible rules will be violated. From there we can make efficient fixes.
Specialist at a tech consulting company with 501-1,000 employees
Real User
Top 10
2023-03-31T13:27:00Z
Mar 31, 2023
I used this software for an online project, specifically for an automotive project. Polyspace Code Prover is a powerful static code analysis tool that can check for numeric or other data. The primary use case is for my unit testing part. My background is in automotive embedded software engineering, and we need to develop requirement-based components for automotive software applications. To test the functionality of these components, we need to check the generated code from the model or any hand-coded components before flashing it onto the processor. So, for that, we need to perform static code checks at the unit level. That's why I used Polyspace Code Prover as a tool for this purpose.
Polyspace Code Prover is a sound static analysis tool that proves the absence of overflow, divide-by-zero, out-of-bounds array access, and certain other run-time errors in C and C++ source code. It produces results without requiring program execution, code instrumentation, or test cases. Polyspace Code Prover uses semantic analysis and abstract interpretation based on formal methods to verify software interprocedural, control, and data flow behavior. You can use it on handwritten code,...
We are testing it.
We use it for all projects where we write our own code. So, it could be vertical control, cluster infotainment, or competitor systems; we use it everywhere. We use it for smaller models and for Simulink models. However, it crashes when we have too many files/functions. When we use Code Prover on large applications, it sometimes crashes. I work with Simulink models, where Prover is fully integrated.
We use the solution to check the runtime issues of our programming.
We use this solution to develop software components flashed on ECUs for electronic control units.
We have some code files generated from the development, which we did for different vehicles. With the individual code files, there is a static analysis that we perform based on the checks. We look at what checks are violated. We look at what possible rules will be violated. From there we can make efficient fixes.
I used this software for an online project, specifically for an automotive project. Polyspace Code Prover is a powerful static code analysis tool that can check for numeric or other data. The primary use case is for my unit testing part. My background is in automotive embedded software engineering, and we need to develop requirement-based components for automotive software applications. To test the functionality of these components, we need to check the generated code from the model or any hand-coded components before flashing it onto the processor. So, for that, we need to perform static code checks at the unit level. That's why I used Polyspace Code Prover as a tool for this purpose.