Europe DO-178C/ED-12C Training and Workshops in 2016

Practical DO-178C/ED-12C Training and Workshops Scheduled at Select European Technology Centers 14th – 15th November – London, UK 16th – 17th November – Madrid, Spain “Not just another basic DO-178C training session.” This is a practical, focused approach to understanding, implementing and successfully executing compliant plans, processes and required support data. A thorough understanding of the guidelines is important, but it is critical to understand how to efficiently satisfy the associated requirements. This training is designed to be fast-paced, dynamic, up-to-date, given by working industry experts with a shared goal: teaching attendees industry best practices that maximize efficiency in managing and delivering software under DO-178C. This workshop covers Continue Reading > > >

Reverse Engineering in DO-254

In either Top Down or Reverse Engineering, the design traceability and elemental analysis (from DO-254 Appendix B) ultimately provide the evidence of completion for this task. Requirements Decomposition Prerequisites System Level Functional Requirements complete and baselined System Design Constraints Requirements Decomposition Objectives Complete decomposition of System Level Requirements into Hardware Requirements. Decomposition implies that the newly developed requirements are traceable to the System Level; the requirements traceability will be the verification that this task is complete. Capture of design specific Derived Requirements as needed to fully define the functions and performance. Derived Requirements are defined as requirements that will not Continue Reading > > >

Here are differences between a Requirement and a Constraint in DO-178C or DO-178C. DO NOT mix the two together!

Requirements – Capture Features and Functions of a system or component. Constraints – Define the Non-Functional aspects of a system or component, such as restrictions on technology, resources or techniques to be used. Also Capture a requirement at the level where it will be tested. If the “requirement” cannot be tested at the level you are working, then it should be captured at a lower or higher level. Pay careful attention to the test aspects; capture any spinoff requirements for test stands or benches; so that when that time comes the test environment is ready. Capture the other decisions made at Continue Reading > > >

How to consider open source code in a DO-178C DAL-D project?

This question was asked in one of LinkedIn Groups: DAL-D requires High level requirements to be verified, but does not require code review. If a Project requires to integrate code from an open source project for a codec or a real time system like linux. How shall this code be considered?  DO-178C does not have Objectives on source code, coding standards, or where it comes from.  The developer is free to use it. Shall it be reversed engineered in High level requirements and design?  It is best to create corresponding High Level Requirements.  DO-178C does not imposes creating design for Continue Reading > > >