Steve Di Camillo

Steve Di Camillo

  • Technical Marketing and Business Development Manager
  • LDRA

Steve Di Camillo has over 30 years’ experience in embedded systems and software development, focusing on model-based engineering and standards compliance. He has worked with many customers around the world in the automotive, aerospace, rail, medical, telecommunications, energy, and industrial equipment industries. Throughout his career, Steve has helped engineering organizations to adopt new processes, tools, and technologies to improve the efficiency and effectiveness of their systems and software development and testing efforts, while maintaining compliance with evolving and emerging technical standards.
Steve earned his Bachelor of Science degree at Cornell University. He now works as Technical Marketing and Business Development Manager with LDRA Software Technology.

Sessions

  • FACE Developing Technical Standards & Updates

    The Future Airborne Capability Environment (FACE) is an open real-time standard for making safety-critical computing operations more robust, interoperable, portable and secure in the aerospace domain. The FACE approach is a government-industry software standard and business strategy for acquisition of affordable software systems that promotes innovation and rapid integration of portable capabilities across programs, including standardized approaches for using open standards within avionics systems and standards that support a robust architecture and enable quality software development for portability of applications across multiple FACE systems and vendors. What are the latest standards and how are the FACE standards developing for future programs? How do these standards affect programs such as Pyramid and ECOA?

  • Multi-core and Multi-systems

    The complexity of multi-core and multi-system architectures, often built using heterogeneous components like Systems on Chip (SoC), and the mixing of multi-core processors with Open Systems Architecture, provide challenges to test avionics systems, and make it difficult to understand their behavior and define comprehensive testing requirements. Traditional testing methods, designed for single-core systems, are not adequate for verifying the correctness and behavior of multicore systems. Issues like data control coupling, safety critical multicore timing analysis, determinism and the need for extensive coverage testing further complicate the process. What are the latest AMC20-193 guidelines, having replaced CAST-32A? It is important to understand the underlying hardware and software components to effectively test and verify multicore and multisystem avionics systems.