Joint Strike Fighter (JSF) Compliance

Parasoft Development Testing Platform for JSF compliance combines the industry’s broadest platform for Development Testing practices with Parasoft's groundbreaking infrastructure for development policy management. This provides organizations with unprecedented process visibility and control throughout the SDLC for all flavors of C, C++, Java, and .NET code. Development Testing practices featured include static code analysis, unit testing, code coverage analysis, peer code review, runtime error detection, and traceability.
  • The most comprehensive JSF++ AV compliance solution
  • Ingrain compliance tasks across the SDLC & into the team workflow
  • Find and fix issues rapidly, with minimal disruption
  • Achieve unparalleled process consistency, visibility & traceability
  • Leverage preconfigured templates for common industry standards

Streamline Joint Strike Fighter (JSF) Coding Compliance

Parasoft streamlines JSF Compliance with:
  • End-to-end quality management with the most comprehensive solution available
  • A continuous compliance process integrated into the workflow and across the SDLC
  • Unparalleled process consistency, visibility and auditability
  • Comprehensive requirements traceability
Parasoft Development Testing Platform for JSF compliance combines the industry’s deepest and broadest code analysis tools with Parasoft’s groundbreaking development management system. This provides organizations with unprecedented process visibility and control throughout the SDLC for all flavors of C, C++, Java, and .NET code. Development Testing practices featured include static code analysis, unit testing, code coverage analysis, peer code review, runtime error detection, and traceability.

Specific JSF++ AV Coding Standards Support

Parasoft’s core static analysis capability provides out-of-the box checking for the Lockheed Martin Joint Strike Fighter Air Vehicle C++ Coding standards. To promote fast remediation, each JSF violation detected is prioritized, assigned to the developer who wrote the related code, and distributed to his or her IDE with direct links to the problematic code and a rule description. Every rule description provides a description of the rule rationale and benefits, a sample violation, an explanation of how to correct the violation, and a demonstration of how to correct the sample violation.