DO-178B Software Development & Certification - Project Planning Phase

Visit Certon on FacebookVisit Certon on TwitterVisit Certon on LinkedIn

What Phase is Your DO-178B Project In?

Planning  |  Validation & Verification  |  Requirements  |  Design & Architecture  |  Implementation & Integration  |  Delivery

Project Planning Phase

 

At the start of the DO-178B Software Development Lifecycle, the objective of the Project Planning Phase must be addressed for compliance. [DO-178B Table A-1] This Software Planning Process involves creating plans and standards to govern the development, verification, configuration management, quality assurance, and delivery of software in compliance with DO-178B guidelines. In this phase, the Software Development Plan (SDP), Plan for Software Aspects of Certification (PSAC), Software Quality Assurance Plan (SQAP), Software Configuration Management Plan (SCMP), Software Verification Plan (SVP), and Software Requirements, Design & Coding Standards (SRDCS) documents are written and reviewed in preparation for the first Stage of Involvement (SOI) Audit with the Certification Authority. These documents are explained in further detail below.

 

CERTON has the experience and expertise to help you develop the plans that will be approved by the Certification Authority and govern your successful DO-178B project.

 

 

Plan for Software Aspects of Certification (PSAC)

 

The purpose of the PSAC is to provide the primary means used by the Certification Authority for determining whether an applicant is proposing a software lifecycle that is commensurate with the rigor required for the DAL of software being developed (DO-178B Section 11.1). The PSAC should include the following, at a minimum:

 

  • System Overview
  • Software Overview
  • Certification Considerations
  • Software Lifecycle
  • Software Lifecycle Data
  • Schedule
  • Additional Considerations

 

Software Development Plan (SDP)

 

The purpose of the SDP is to identify the objectives, standards, and software lifecycle(s) to be used in the software development processes, ref. DO-178B Section 11.2. It can be included in the PSAC and should contain the following, at a minimum:

 

  • Standards
  • Software Lifecycle
  • Software Development Environment

 

Software Verification Plan (SVP)

 

The SVP is a description of the verification procedures to satisfy the software verification process objectives, ref. DO-178B Section 11.3. The procedures vary by software DAL as defined in the Tables of DO-178B Annex A. The SVP should contain the following, at a minimum:

 

  • Organization
  • Independence
  • Verification Methods
  • Verification Environment
  • Transition Criteria
  • Partitioning Considerations
  • Compiler Assumptions
  • Re-verification Guidelines
  • Previously Developed Software+
  • Multiple-Version Dissimilar Software

 

Software Configuration Management Plan (SCMP)

 

The Software Configuration Management Plan establishes the methods to be used to achieve the objectives of the software configuration management (SCM) process throughout the software lifecycle, ref. DO-178B Section 11.4. The SCMP should contain the following, at a minimum:

 

  • Environment
  • Activities
  • Configuration Identification
  • Baselines and Traceability
    • Problem Reporting
    • Change Control
    • Change Review
    • Configuration Status Accounting
    • Archive, Retrieval, and Release
    • Software Load Control
    • Software Lifecycle Environment Controls
    • Software Lifecycle Data Controls
  • Transition Criteria
  • SCM Data
  • Supplier Control

 

Software Quality Assurance Plan (SQAP)

 

The purpose of the SQAP is to establish the methods to be used to achieve the objectives of the software quality assurance (SQA) process, ref. DO-178B Section 11.5. The SQAP should contain the following, at a minimum:

 

  • Environment
  • Authority
  • Activities
  • Transition Criteria
  • Timing
  • SQA Records
  • Supplier Control

 

CERTON provides expert Quality Assurance assessment for compliance with DO-178B. Click here to view our Corporate Quality Assurance page.

 

Software Requirements, Design & Coding Standards (SRDCS)

 

The purpose the Software Requirements, Design, and Coding Standards is to establish a set of methods, rules, and tools that will be used in the development of the software item to promote consistency among processes, outputs, and artifacts. These standards will provide the constraints necessary to enforce clarity and consistency between developers and streamline the activities associated with requirements, design, and code development, validation, and verification throughout the software lifecycle to prevent errors that could cause safety issues, schedule impact, and budget overruns.