1. © 2016 LDRA Ltd The FACE Conformance Verification Matrix in Practice

2. FACE Adoption Challenges FACE conformance across multiple stakeholders Unifying artifacts across the lifecycle Achieving and maintaining conformance within iterative development Ease of adoption Simplify the verification process FACE conformance within a safety and security critical standards framework

3. FACE Approaches within the LDRA tool suite Scoping FACE requirements with filters for a given segment against the compliance verification matrix Easy to follow verification layout and placeholders for review artifacts and the FACE Test Suite Application of FACE coding standard to aid in conformance Cost effectively scoping requirements, verification artifacts, and performing verification for a given system Performing verification activities for conformance with both standard from within the LDRA tool suite Utilizing artifacts from the lifecycle for conformance to both standards Reconciling and leveraging DO-178B/C with FACE conformance

4. Traceability, Verification Workflow & Test Requirements Traceability Requirements traceability Impact Analysis Traceability Matrix Import/Export Report Generation Verification Workflow Process Unification and Enforcement Verification Workflow Management Test Automation Objective Fulfillment Audit trail LDRA Verification Coding Standards Unit Testing Code Coverage Quality Metrics Target Integration Data/Control Flow REDUCING COST ACROSS THE LIFECYCLE

5. FACE Technical Standard and CVM FACE CVM Spreadsheet version of the FACE Technical Standard with verification guidance FACE Requirement Verification Verified by test or inspection or both Test implies the FACE Conformance Test Suite Inspection entails inspecting relevant portions of project artifacts (SRS, SDD, STP, STR etc.) to verify requirements FACE Reference Architecture Excerpt from the Compliance Verification Matrix

6. Importing the CVM into LDRA TBmanager FACE CVM with identifiers. Ready for parsing into TBmanager CVM perspective within the TBmanager requirements grid Tailored import of the CVM into TBmanager Automated generation of conformance artifacts infrastructure Conformance Test Suite execution and artifact capture can be instantiated

7. Integrating the FACE Conformance Test Suite FACE Conformance Test Suite configuration CVM perspective within the TBmanager requirements grid FACE Conformance Test Suite (CTS) Supplied separately by Vanderbilt’s Institute for Software Integrated Systems (ISIS) and approved for conformance testing Configuration required is based on FACE segments, profiles, conditional requirements, and data model

8. Traceability from the CTS to Requirements FACE Conformance Test Suite (CTS) Supplied separately by Vanderbilt’s Institute for Software Integrated Systems (ISIS) and approved for conformance testing Configuration required based on FACE segments, profiles, conditional requirements, and data model Automation of Execution Execution of the CTS can be configured and automated from TBmanager to simply execution, traceability and regression Traceability from the CTS to FACE Requirements, simplifies the verification process and quickly isolates verification gaps FACE requirements, test suite, and associated conformance artifacts FACE Requirements to the FACE CTS configured for the TSS segment and general purpose profile

9. Mapping Conformance Artifacts to Requirements Artifacts association Providing the entire artifact Providing references to specific locations within an artifact How does the artifact and relevant sections verify the FACE requirement? Standalone and aggregated artifacts Some instances require a reference to a single artifact Other references require requirements, tests, and results and artifacts must be reviewed in aggregate

10. Utilizing Coding Standards Utilizing static analysis to detect non-conformant API calls Early detection of non-conformant Can be combined with internally recognized standards such as the MISRA, JSF- AV, HIC, CERT and other standards FACE requirements can explicitly specify interface details Detecting non-conformant calls statically

11. Impact Analysis Scenarios Assessing impact of conformance related changes Conformance related changes to source code and artifacts impact development activities Impact of changes from conformance activities can be easily assessed and reviewed

12. Objective Tracking Requirements Traceability Coding Standards Compliance Data & Control Coupling Analysis Structural Coverage Target Testing Object Code Verification Tool Qualification Reduce Time To Compliance And Market CERTIFICATE Of QUALITY Software has been tested and conforms to DO-178C Reduce Cost of Compliance Manage Distributed Team Challenges on the Path to DO-178B/C Compliance Management

13. Integrated FACE and DO-178B/C Solution Reduce the cost of adopting both DO-178B/C and FACE by unifying the verification environment and leveraging work across standards Enforce and manage FACE and DO-178B/C conformance across a distributed set of suppliers Predict and manage effort and progress to improve proposal to contract execution cost control Convergence of DO-178C and FACE standards Transition to DO-178C and increased rigor in use of the guidance Increasing number of RFI’s are requiring FACE conformance

14. For further information: www.ldra.com jeff.price@ldra-usa.com shan.bhattacharya@ldra-usa.com @ldra_technology LDRA Software Technology LDRA Limited