Static analysis
Apply pattern- and flow-based analysis for defects, coding standards, security weaknesses and organization-specific policies.
Parasoft C/C++test
Apply static analysis, unit testing, coverage and traceability in supported C/C++ build, compiler and target environments.
Static analysisUnit testingStructural coverageRequirements traceability
C/C++ verification pipeline
InputsSource, compiler & buildRequirements & rule policy
Engineering controlsStatic analysisUnit/component testHost/target coverage
OutputsReviewed findingsCoverage resultsStandards-oriented reports
Code-level verification for embedded, safety-sensitive and security-sensitive C/C++ development.
Supported compilers, targets, coverage modes, standards packs and qualification artefacts are release- and licence-dependent and must be confirmed for the selected release and deployment.
ParasoftSoftware quality
Core capabilities
Core engineering capabilities
Exact capabilities depend on the selected edition, release and deployment environment.
Unit testing
Create and execute isolated tests with supported stubs, mocks and host or target workflows.
Structural coverage
Collect supported metrics across unit, integration or system execution according to product configuration.
Requirements traceability
Associate tests and results with requirements through supported integrations and identifiers.
Developer and CI integration
Run in supported IDE, command-line, container and CI/CD workflows.
Reporting
Produce execution reports and publish selected data to Parasoft DTP for centralized analysis.
Implementation workflow
From evaluation to deployment
Validate the technology in the real build, target and reporting environment before wider rollout.
- 01Import build context
- 02Apply rule configuration
- 03Create or connect tests
- 04Execute on host/simulator/target
- 05Review findings and coverage
- 06Publish controlled evidence
Confirm the deployment fit
Compatibility depends on the actual toolchain, target environment, integration needs and assurance objectives.
- Compiler and build-system support
- Target, simulator and probe constraints
- Required static-analysis standards
- Unit-test framework and isolation strategy
- Coverage level and instrumentation impact
- Qualification kit and reporting needs
Where the technology adds value
Well suited for
- Embedded C/C++ with regulated verification needs
- Coding-standard enforcement across teams
- Host and target unit-testing programmes
- Coverage and traceability record generation
Important considerations
- Compiler, build and target compatibility must be validated.
- Waivers and remediation decisions remain engineering responsibilities.
- Code-level analysis does not prove all system behaviour.
- Product certification requires the complete project process and evidence set.
Relevant engineering frameworks
MISRA C/C++AUTOSAR C++14CERT C/C++CWEISO 26262IEC 61508IEC 62304DO-178CEN 50716
Related capabilities
Extend the software assurance workflow
Explore adjacent capabilities across requirements, verification, testing and embedded security.