D0-278 Software Integrity Assurance Standard: Software Development Objectives and Stage of Involvement (SOI) Audit Readiness
D0-278 Software Integrity Assurance Standard: Software Development Objectives and Stage of Involvement (SOI) Audit Readiness
DO-278 is the Software Integrity Assurance Considerations for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems: (FAA) Software and Hardware Integrity Assurance Standard. ROC® has direct experience working on Certifiable Product (i.e., Embedded Flight Operational Software and Fight Hardware Test Software) with dedicated DER Type – Systems and Equipment Engineering. The DER is the liaison between the Organization who is developing the Certifiable Product and the FAA. DERs are certified annually by the FAA and legally liable for all actions. A DER is the Gate Keeping, Plan Approver and many other critical roles.
ROC® mentors and provides focused software design assurance client tailored learning sessions with real examples enhancing the development team understanding and implementation of DO-278 processes, objectives and verification requirements. ROC® has direct successful experience working, leading and satisfying FAA Designated Engineer Representative (DER) requests and improvement suggestions.
ROC® will guide your Software Development Team to develop the roadmap and implementation:
5 TOP Level Implementation Road Map:
ROC® mentors, reviews and provides focused client tailored learning sessions. ROC® shares real certifiable product development and SOI lessons enhancing the audience understanding
- The Positioning Signal Integrity and Continuity Assurance (PSICA) Plan and development of 5 Key Governing Plans. These plans are required Certification Documentation: How will I meet the DO-278/178 Objectives for a certifiable product ? For example, the Plan for Software Aspects of Assurance (PSAA) describes how software development team plans to comply with DO-278/DO-178 objective.
- Risks/strategies identification:
- GAP Analysis and process engineering guidance in making your Software Development Lifecycle Plans and Processes DO-278 compliant. If your organization is CMMI® DEV Maturity Level 3, your Document Process Library System has a solid foundation, but lacking Software Safety Objectives. ROC® mentors and drives the upgrade and refinement of your current internal processes to comply with System and Requirement Writing, Software Design, Software Testing and Bi-directional Traceability – > DO-278 Objectives and Output.
- Peer Review (PR) Process and PR Training – PR is a CMMI® best practice. However, ROC® includes the PR process because of the benefits a well-planned and conducted peer review augment to your performance. PR process will include DO-178B/C Objectives.
- Refer to Service Section 3, Figure 1. ROC® Gap Analysis; Figure 2. DO-278 Certifiable Product Software Development Life Cycle.
- Identity 3rd Party Tools/Products: FAA Approved Commercial-Off-The-Shelf Software (COTS)
- Tool Qualification: an inhouse developed tool undergoes a Certification Process
- Coordination of FAA or Certified Agency
Figure 2. ROC® DO-278 Certifiable Product Software Development Life Diagram
ROC® mentors and works hand in hand with the organization, ensuing they understand and learn how to do the work themselves.
ROC® Sample Focused Learning Sessions
- Safety Standard History
- Differences between DO-278 to 278A – DO-178B (67 Objectives) to DO-178C(71 Objectives)
- DO-178B/C Certifiable Product Software Development Life Cycle
- Criticality Levels, Assurance Levels, Software Categories
- Vital terminology
- GAP Analysis and Software Assurance Development Processes
- PSICA Plan and 5 Governing Plans
- Testing Objectives
- Ensuing DO-278 Objectives Bi-directional Traceability is maintained as planned
- Tool Qualification
- FAA Certified Commercial-Off-The-Shelf Software Tools
- Lessons learned and common mistakes to avoid