The number of suppliers investing in process and infrastructure is rapidly growing and practitioner’s feedback is driving innovation and refining approaches. As a greater number of program awards promote interoperability utilising this standard, economical and scalable conformance and verification practices must be adopted to capture business opportunities and reduce conformance and schedule risk.

Why the FACE initiative is important

DoD Airborne systems are typically developed for a unique set of requirements by a single vendor

Long lead times, even for urgent needs

Platform-unique designs limit reuse of software and increase cost

Creates barriers to competition within and across platforms

Current DoD Acquisition structure does not support the process of software reuse across different programs

Aviation community has not adopted a common set of Open Architecture (OA) standards sufficient to allow the reuse of software components across the DoD fleet

Aviation community has failed to enforce conformance to any existing open standards that are in use

Platform PMAs are not funded to assume cost or schedule risk of multi-platform requirements

Putting a FACE on Safety and Security-Critical Application Development

How can I achieve FACE conformance?

LDRA’s verification workflow and software analysis technology provide a comprehensive solution for verification of the FACE requirements utilizing the FACE Conformance Verification Matrix (CVM). This includes regression of the FACE conformance test suite (CTS), traceability to conformance artifacts, and static analysis of source code, to automate and streamline conformance activities.

How can I achieve compliance to DO-178?

With 40 years of experience, LDRA works closely with both industry and on-staff Designated Engineering Representatives (DERs), expediting the path to software qualification and aircraft certification. Additionally, LDRA can provide its own comprehensive Compliance Management System consisting of process compliance documents (PCDs), process checklists, and a document review and approval infrastructure. This tightly integrated environment helps you manage the entire DO-178B/C compliance and FACE conformance processes from requirements through deployment, helping to eliminate or reduce labour-intensive and error-prone elements of the process while reducing cost and streamlining the overall development lifecycle.

LDRA solution for FACE conformance

Tailored import verification activities of the FACE CVM in TBmanager

Automated generation of conformance artifacts infrastructure

Automated FACE CTS execution and artifact capture

Traceability from the CTS and conformance artifacts to FACE Requirements, simplifies the verification process and quickly isolates verification gaps

Utilising static analysis to detect non-conformant API calls

Early detection of non-conformance

Can be combined with internally recognized standards such as the MISRA, JSF++ AV, HIC, CERT and other standards

In this Webinar, guest speaker Kirk Avery the FACE Technical Working Group Chair from Lockheed Martin will help us understand the requirements and goals of the FACE Technical Standard.

Speaker Biographies

Kirk Avery – Chief Software Architect and Fellow, Lockheed Martin

Kirk Avery is a Lockheed Martin Fellow and the Chief Software Architect for Lockheed Martin Mission Systems and Training (MST) Ship and Aviation Systems (SAS) with over 25 years’ experience in architecting, designing, developing, integrating, and deploying software solutions for military/commercial fixed and rotary wing aircraft systems and simulation systems. Over the course of his career, Kirk has developed and provided leadership in the creation and deployment of many modular, open, flexible, scalable, and portable complex software solutions, systems, and architectures. Kirk’s responsibilities include the implementation of the organization’s software engineering product-line strategy. Kirk also serves as the FACE Consortium’s Technical Working Group Chair, serving as the Chair or Vice-Chair for five consecutive terms.