Plan for Software Aspects of Certification

Plan for Software Aspects of Certification

for the

<Company Name> <Program Name>

Document No: <Doc Number>

Revision: -

__________________________________________________ ___________
<Name>, Program Manager Date

__________________________________________________ ___________
<Name>, Technical Project Lead Date

__________________________________________________ ___________
<Name>, Engineer Date

__________________________________________________ ___________
<Name>, Quality Assurance Engineer Date

Notice
This document and the information contained herein are the property of <company
name>. Any reproduction, disclosure or use thereof is prohibited except as authorized
in writing by <company name>. Recipient accepts the responsibility for maintaining
the confidentiality of the contents of this document.

<Doc Number> Page 3 of 75 Rev. -

Plan for Software Aspects of Certification

REVISIONS
Requested/
Rev. Reason/Description Changed By Date

<Doc Number> Page 4 of 75 Rev. -

Plan for Software Aspects of Certification

Table of Contents

Section Page

1.0 INTRODUCTION ........................................................................................ 10

1.1 Purpose .......................................................................................................... 10
1.2 Scope ............................................................................................................. 10
1.3 Definitions ...................................................................................................... 10
1.4 Part Number and Nomenclature ......................................................................... 11
1.5 Deviations, Modifications & Updates ................................................................... 11
1.6 Team Members & Organization .......................................................................... 12
1.6.1 Program Manager .................................................................................... 13
1.6.2 Software Engineering ............................................................................... 13
1.6.3 Independent Validation & Verification (IV&V) .............................................. 14
1.6.4 Software Configuration Management .......................................................... 14
1.6.5 Software Quality Assurance ...................................................................... 15
1.6.5.1 QA and Organizational Independence ................................................... 15
1.6.6 FAA Software Designated Engineering Representative (Certification Authority) 15
1.6.7 Signature Authority Explained ................................................................... 16
1.7 Acronyms and Abbreviations ............................................................................. 16
1.8 Applicable Documents ...................................................................................... 18
1.8.1 External Documents ................................................................................. 18
1.8.2 Internal Documents ................................................................................. 19
1.8.2.1 Related Programs............................................................................... 19
1.8.2.2 This Program ..................................................................................... 19
1.9 Special Considerations Cross Reference .............................................................. 22

2.0 SYSTEM OVERVIEW ................................................................................... 24

2.1 Mechanical Systems Top-Level Diagram .............................................................. 24
2.1.1 System Functions Allocated to Mechanical Hardware .................................... 24
2.2 Electrical Systems Top-Level Block Diagram ........................................................ 24
2.3 HW/SW Interface ............................................................................................. 25
2.4 List of Major Functions Allocated to System-Level Hardware .................................. 25
2.4.1 List of Major Functions Allocated to Complex Hardware ................................ 25
2.4.1.1 FPGA #1 ........................................................................................... 25
2.4.1.2 FPGA #2 ........................................................................................... 25
2.5 List of Major Functions Allocated to Software ....................................................... 26
2.5.1 DSP #1 .................................................................................................. 26
2.5.2 Microcontroller #1 ................................................................................... 26
2.6 System Functional Description ........................................................................... 26
2.6.1 System Failure Conditions ........................................................................ 27
2.6.2 High-Level Hardware Functions and Contribution to Potential Failures ............ 27
2.6.3 Safety Features and Partitioning ................................................................ 27

3.0 SOFTWARE OVERVIEW .............................................................................. 28

3.1 Software Architectural Block Diagram ................................................................. 28
3.2 Modes of Operation .......................................................................................... 28
3.3 Processor #1 ................................................................................................... 28
3.3.1 States and Modes .................................................................................... 28
3.3.2 Tasks ..................................................................................................... 28

<Doc Number> Page 5 of 75 Rev. -

Plan for Software Aspects of Certification

3.4 Processor #2 ................................................................................................... 28

3.4.1 States and Modes .................................................................................... 28
3.4.2 Tasks ..................................................................................................... 28
3.5 Hardware/Software Interfaces ........................................................................... 28
3.6 COTS Identification .......................................................................................... 28
3.6.1 Real Time Operating System ..................................................................... 28
3.6.2 Board Support Package ............................................................................ 29
3.6.3 Compiler Provided Libraries ...................................................................... 29
3.7 Deactivated Code Partitioning ............................................................................ 29
3.7.1 USB Interface Code ................................................................................. 29
3.7.2 RS-232 Interface Code ............................................................................. 29
3.7.3 Ethernet Interface Code ........................................................................... 29
3.7.4 Boot Load Code Partitioning ...................................................................... 29
3.8 Safety and Partitioning ..................................................................................... 29
3.8.1 Safety Monitoring .................................................................................... 29
3.9 Resource Sharing ............................................................................................. 29
3.10 Redundancy .................................................................................................. 30
3.11 Fault Tolerance .............................................................................................. 30
3.12 Timing and Task Scheduling ............................................................................ 30
3.12.1 Timing ................................................................................................. 30
3.12.2 Task Scheduling ................................................................................... 30

4.0 SOFTWARE DESIGN LIFE CYCLE ................................................................ 31

4.1 Overview of Software Life Cycle Processes and Activities....................................... 32
4.2 System Processes ............................................................................................ 33
4.3 Planning ......................................................................................................... 34
4.3.1 Planning Inputs ....................................................................................... 34
4.3.2 Planning Outputs ..................................................................................... 34
4.3.3 Planning Activities ................................................................................... 34
4.3.4 Planning Documents and Data ................................................................... 35
4.3.5 Planning Transition Criteria and Reviews .................................................... 35
4.3.5.1 Transition Criteria for Entry into Planning Process .................................. 35
4.3.5.2 Transition Criteria for Exit from Planning Process ................................... 35
4.3.6 Technical Interfaces for Planning ............................................................... 36
4.3.7 Planning Process Tool Usage ..................................................................... 38
4.4 Software Requirements Process ......................................................................... 38
4.4.1 Software Requirements Inputs .................................................................. 39
4.4.2 Software Requirements Outputs ................................................................ 39
4.4.3 Software Requirements Activities............................................................... 39
4.4.4 Software Requirements Transition Criteria and Reviews ................................ 39
4.4.5 Software Requirements Process Tool Usage ................................................ 39
4.5 Software Design Process ................................................................................... 39
4.5.1 Software Design Inputs ............................................................................ 39
4.5.2 Software Design Outputs .......................................................................... 40
4.5.3 Software Design Activities ........................................................................ 40
4.5.4 Software Design Transition Criteria and Reviews ......................................... 40
4.5.5 Software Design Tool Usage ...................................................................... 40
4.6 Software Coding Process ................................................................................... 40
4.6.1 Software Coding Inputs ............................................................................ 40
4.6.2 Software Coding Outputs .......................................................................... 40
4.6.3 Software Coding Activities ........................................................................ 40

<Doc Number> Page 6 of 75 Rev. -

Plan for Software Aspects of Certification

4.6.4 Software Coding Transition Criteria and Reviews ......................................... 40

4.6.5 Software Coding Tool Usage ..................................................................... 41
4.7 Software Integration Process ............................................................................. 41
4.7.1 Software Integration Inputs ...................................................................... 41
4.7.2 Software Integration Outputs .................................................................... 41
4.7.3 Software Integration Activities .................................................................. 41
4.7.4 Software Integration Criteria and Reviews .................................................. 41
4.7.5 Software Integration Tool Usage................................................................ 41
4.8 Feedback to the Development and Integral Processes ........................................... 42
4.9 Integral Processes ............................................................................................ 43
4.9.1 Validation and Verification ........................................................................ 44
4.9.1.1 Verification and Validation Reviews Summary ........................................ 44
4.9.1.2 Validation and Verification During Planning............................................ 45
4.9.1.3 Validation and Verification During Requirements Phase ........................... 46
4.9.1.4 Validation and Verification During Design .............................................. 46
4.9.1.5 Validation and Verification During Code & Integration ............................. 46
4.9.1.6 Validation and Verification During Incremental Build & Testing................. 47
4.9.1.7 Validation and Verification at the Completion of the Compliance Process ... 47
4.9.2 Software Configuration Management .......................................................... 47
4.9.2.1 Configuration Management During Planning .......................................... 48
4.9.2.2 Configuration Management During Requirements Capture ....................... 48
4.9.2.3 Configuration Management During Conceptual Design ............................ 48
4.9.2.4 Configuration Management During Code & Integration ............................ 49
4.9.2.5 Configuration Management at the End of the Software Life Cycle ............. 49
4.9.2.6 Configuration Management During Testing ............................................ 49
4.9.3 Software Quality Assurance ...................................................................... 50
4.9.3.1 Quality Assurance During Planning ....................................................... 50
4.9.3.2 Quality Assurance During Requirements................................................ 50
4.9.3.3 Quality Assurance During Design ......................................................... 50
4.9.3.4 Quality Assurance During Coding & Integration ...................................... 51
4.9.3.5 Quality Assurance During Testing ......................................................... 51
4.9.4 Certification Liaison ................................................................................. 51
4.9.4.1 Certification Liaison During Planning ..................................................... 51
4.9.4.2 Certification Liaison During Requirements ............................................. 52
4.9.4.3 Certification Liaison During Design ....................................................... 52
4.9.4.4 Certification Liaison During Coding & Integration ................................... 52
4.9.4.5 Certification Liaison During Testing ...................................................... 52
4.9.4.6 Certification Liaison to Finalize Compliance ............................................ 53
4.10 Software Life Cycle Data ................................................................................. 53
4.10.1 Relationship of Life Cycle Data to Other System Data ................................ 54
4.10.2 Trace Data ........................................................................................... 54
4.10.3 Software Life Cycle Data to Be Produced and Controlled ............................ 54

5.0 CERTIFICATION CONSIDERATIONS........................................................... 57

5.1 Certification Basis and Means of Compliance........................................................ 57
5.2 Issue Papers and Certification Review Items (CRI) ............................................... 57
5.3 Software Level Determination ............................................................................ 58
5.3.1 Display DAL and Worst Case Failure Condition ............................................. 58
5.3.2 Command DAL and Worst Case Failure Condition ......................................... 58
5.3.3 Monitor DAL and Worst-Case Failure Condition ............................................ 58
5.3.4 Video Processor DAL and Worst-Case Failure Condition ................................ 59

<Doc Number> Page 7 of 75 Rev. -

Plan for Software Aspects of Certification

5.4 Compliance Matrix ........................................................................................... 59

5.5 Certification Authority Level of Involvement ........................................................ 67

6.0 ADDITIONAL COMPLIANCE CONSIDERATIONS .......................................... 69

6.1 Use of Previously Developed Software ................................................................ 69
6.2 Tool Qualification ............................................................................................. 69
6.3 Alternative Methods ......................................................................................... 70
6.4 Product Service History..................................................................................... 70
6.5 Field Loadable Software .................................................................................... 70
6.6 Option Selectable Software ............................................................................... 70
6.7 User Modifiable Software .................................................................................. 70
6.8 Multiple-Version Dissimilar Software ................................................................... 71
6.9 COTS Software ................................................................................................ 71
6.10 Use of Suppliers, Sub-Tier Suppliers and Off-Shore Facilities ............................... 71
6.11 Management of Open Problem Reports ............................................................. 71

7.0 DEMONSTRATION OF COMPLIANCE VIA PACT ........................................... 72

8.0 FINAL REVIEW AND COMPLIANCE STATEMENT ......................................... 73

9.0 SCHEDULE ................................................................................................. 74

List of Figures

Figure 1-1. Program Organization Chart ...................................................................... 12

Figure 2-1. Mechanical Diagram ................................................................................. 24
Figure 2-2. System Level Block Diagram ..................................................................... 25
Figure 2-3. System Functional Diagram....................................................................... 26
Figure 3-1. Software Architecture Block Diagram ......................................................... 28
Figure 4-1. Software Life cycle Processes and Activities ................................................ 33
Figure 4-2. Life Cycle Process Feedback Flow Diagram .................................................. 43
Figure 4-2. Reviews during Software Life Cycle Processes ............................................. 45

List of Tables

Table 1-1. Definitions ............................................................................................... 11

Table 1-2. Part Number and Nomenclature .................................................................. 11
Table 1-3. Team Members ......................................................................................... 12
Table 1-4. External Documents .................................................................................. 18
Table 1-5. Internal Documents Related to the System .................................................. 19
Table 1-6. Internal Documents................................................................................... 19
Table 1-7. Software Considerations References ............................................................ 22
Table 2-1. Mechanical Hardware................................................................................. 24
Table 2-2. System Failure Conditions .......................................................................... 27
Table 4-1. Roles and Responsibilities for Planning......................................................... 36
Table 4-2. Planning Process Tools............................................................................... 38
Table 4-3. Software Life Cycle Data ............................................................................ 55
Table 5-1. List of Compliance Documents .................................................................... 57

<Doc Number> Page 8 of 75 Rev. -

Plan for Software Aspects of Certification

Table 5-2. List of Issue Papers and CRI’s ..................................................................... 57

Table 5-3. Compliance Objectives and References ........................................................ 59
Table 6-1. Software Tools.......................................................................................... 69
Table 6-2. Options Selectable by PDI .......................................................................... 70
Table 9-1. Reviews, Dates, and Data .......................................................................... 74

<Doc Number> Page 9 of 75 Rev. -

Plan for Software Aspects of Certification

1.0 INTRODUCTION
This is a self-educating template. Note that blue italicized font is instructional text used to
educate the user of this template about how to use this template in terms of the intent or types of
content required for a section. This text should be deleted once this template is turned into a
real project document. Standard text provides sample content (and/or example content) that
can sometimes be used but must usually be customized for the specific project.

This PSAC document summarizes the processes used to develop, design, verify and control the
applicable software during the planning, development, verification and production phases.
References are made to the relevant planning, requirements, design, production, verification and
configuration control documents and data. The purpose of this document is to communicate
how the pertinent objectives of DO-178C and other certification criteria will be met and
reviewed for FAA/EASA (or other) certification/approval.

You need to tailor the content of this PSAC based on the DAL of your project. Refer to Table 5-3
to help you do this. Also, as you are preparing your planning documents from these templates,
please utilize the DO-178C supplement tables (i.e., file DO-178C_Supplement-Tables.xlxs,
provided with these templates) to ensure you are applying all the appropriate information that is
relevant to your project (if it uses the supplements DO-330, DO-331, DO-332, DO-333) into the
documentation set. The supplement tables will help you identify where this information goes in
the document set.

Note that all the relevant figures in this template set are available for editing and provided in the
free “drawio” format as part of this template set.

1.1 Purpose
This Plan for Software Aspects of Certification (PSAC) defines the processes, procedures,
methods, and standards to be used and the life cycle data to be produced in order to satisfy
the objectives of DO-178C and its pertinent supplements, along with any additional objectives
required to satisfy the certification basis of the aircraft. Once approved, this PSAC represents
an agreement between the applicant and the customer and/or certification authority.

1.2 Scope
Note that if this project will be using DO-331, 332, 333, this PSAC must describe how both DO-
178C and the supplement(s) will be used together, which objectives apply to which software
components, and how the planned activities will satisfy all applicable objectives. You can use the
DO-178C-Supp-Tables.xlxs spreadsheet to assist with this.
This plan will be used by the customer and/or certification authority to determine if the
Software Life cycle Process is commensurate with the rigor required for the level of software
being developed. Once approved, it is implemented during the software life cycle
development. This Plan for Software Aspects of Certification complies with the documentation
requirements of RTCA/DO-178C, Section 11.1.

1.3 Definitions
Modify this to include the terms used in your project.
The following table defines the key terms used in this project.

<Doc Number> Page 10 of 75 Rev. -

Plan for Software Aspects of Certification

Table 1-1. Definitions

Definition Meaning

COTS Graphical Processor Any COTS microcontroller specifically designed for graphical
applications. COTS graphical processors for airborne systems
are required to have built in mitigation against Hazardous and
Misleading information (HMI).
COTS Microcontroller Any IC which executes software in a specific core area (Central
Processing Unit) and implements peripheral hardware
elements such as, for example, input/output (I/O), bus
controllers… Such a peripheral element may be considered
simple (e.g., a UART, A/D, D/A) or complex (e.g., a bus
controller).
Highly complex COTS
Any microcontroller where at least one of the statements
microcontroller
below is true:
- more than one Central Processing Unit (CPU) is embedded
and they use the same bus (which is not strictly separated or
which uses the same single port memory)
- several complex interfaces are dependent on each other and
exchange data
- several internal busses are integrated and are used in a
dynamic way (for example, a dynamic bus switch matrix)
Microprocessor A single Central Processing Unit which executes software and
does not contain any additional integrated peripheral
hardware element such as a UART, A/D, D/A, bus controller,
Time Processing Unit, Memory Management Unit, watchdog,
etc.

1.4 Part Number and Nomenclature

Update with your own PN and nomenclature information.

This section includes the Part Number(s) of the software covered by this PSAC.
Table 1-2. Part Number and Nomenclature
Part Number Nomenclature

PC-XY-1234-56_FS Flight Software

PC-AB-5678-09_PDI Parameter Data Item (PDI)

1.5 Deviations, Modifications & Updates

DO-178C acknowledges that from time to time you will want to deviate from the agreed to and
approved plans. When this happens a defined method for how these deviations will be
communicated and agreed should be defined. This section provides an example concept for how
a company could chose to do this. Modify this section with the method you determine best suited

<Doc Number> Page 11 of 75 Rev. -

Plan for Software Aspects of Certification

for your company.

Deviations to this plan once it is approved will be documented in problem reports (PRs) against
this PSAC or any other lower level affected plan or standards. This PR will contain the “is”
and “was” changes for the deviation to the plan, standard, or process. Deviation PRs will be
communicated to the authority responsible for approving the deviation. Deviations that are
deemed “significant” will result in an update to this plan and a resubmittal for approval to the
certification authority. Significant changes to plans are those that affect tool qualification,
design and verification methodologies, and life cycles, such that a different methodology is
used.

1.6 Team Members & Organization

List all team members involved in the project, identifying those with signature authority, and
provide an organization structure demonstrating independence among the pertinent functions. The
text provided describes the typical job descriptions and responsibilities but should be updated to
reflect those in your organization who are involved in your program.
The Organization Chart shown in Figure 1-1 depicts the high-level organization involved in
this program.

Figure 1-1. Program Organization Chart

The scope of this project is an airborne software module, developed and verified by internal
resources from <COMPANY>. The Software Quality Assurance and Configuration
Management engineering responsibilities is being handled by a sub-contractor (Patmos
Engineering Services).

The following table identifies the team members and their roles. The subsections that follow
describe the roles in detail.
Table 1-3. Team Members
Name Title
Signature Authority:
<NAME> Project Manager
<NAME> Lead Software Engineer

<Doc Number> Page 12 of 75 Rev. -

Plan for Software Aspects of Certification

<NAME> Independent Validation & Verification Engineer

Jane Doe, Patmos Quality Assurance Engineer
Engineering
Team Members:
<NAME> Systems Engineer
<NAME> Reliability & Safety Engineer
<NAME> Software Design Engineer
John Doe, Patmos Configuration Management Engineer
Engineering
Tammy Reeve, Certification Authority / FAA Software Designated Engineering
DER, President Representative
Patmos
Engineering

Assigned project personnel will perform the various activities identified in this plan. Key
individuals are responsible for tasks assigned based on their respective area of expertise.
These include Program Management, Software Engineering, Software Configuration
Management, and Software Quality Assurance. Peer Reviews will be used for all Software
verification process activities requiring independence.

1.6.1 Program Manager

The Program Manager will support preparation and implementation of various planning,
requirements, and design descriptions for the project. Responsibilities include, but are not
limited to, the following:
 Chairing the Engineering Review
 Developing and maintaining the project schedule
 Managing all development activities
 Assigning personnel and priorities
 Ensuring readiness for scheduled project reviews
 Resolving all process- and product-related problems/concerns
 Ensuring that the necessary equipment and tools are available for development

1.6.2 Software Engineering

The Software Engineer supports the following tasks:
 Participate in Software requirements reviews
 Participate in Software architectural design reviews
 Participate in code reviews
 Participate in integration reviews
 Process Software Problem Reports, Change Requests, and Initial Baseline Items
 Develop and maintain all trace matrices involving requirements, design, and code
 Provide support for test case and procedure preparation

<Doc Number> Page 13 of 75 Rev. -

Plan for Software Aspects of Certification

 Support elemental analysis

 Support requirements coverage analysis

1.6.3 Independent Validation & Verification (IV&V)

The IV&V Engineer performs the following tasks:
 Participate in Software requirements reviews
 Participate in Software architectural design reviews
 Participate in code reviews
 Participate in integration reviews
 Process Software Problem Reports, Change Requests, and Initial Baseline Items
 Verify all trace matrices involving requirements, design, and code
 Create test cases and procedures
 Execute test cases
 Perform elemental analysis
 Perform requirements coverage analysis
 Work with Quality Assurance to ensure verification independence when necessary

Refer to the Software Verification Plan, <doc-ref#>_SVP, for details in terms of how
Verification Independence will be established.

1.6.4 Software Configuration Management

The Software Configuration Management Engineer performs the following tasks:
 Problem Reporting System Setup, Maintenance and Reporting:
Administer and maintain the PRS
 Configuration Management Software Library Setup, Maintenance, and Reporting:
Set up, configuration, and maintain the code management tool
 Revision Control:
Ensure that all product releases are reproducible, versioned, dated, and archived
 Software Configuration Index Preparation:
Ensure that a configuration index is created for the certifiable configuration
 Software Environment Configuration Index Preparation:
Ensure that an SECI is created for the certifiable configuration
 Data Configuration:
Configure the Software life-cycle data generated during development and
qualification
 Tool and Release Archival:
Perform backup and archival of all Software life-cycle data
 Release Builds:
Build release configuration for test and final release
 Archiving and safeguarding the production configuration
 Media recreation to ensure ability to reproduce the development and verification
environments, as well as the object code

<Doc Number> Page 14 of 75 Rev. -

Plan for Software Aspects of Certification

 Independently build released configuration for verification testing and production

 Load the Software configuration into production software

1.6.5 Software Quality Assurance

The Quality Assurance (QA) Engineer will provide independent review of all verification
activities and has review responsibility for related objective evidence. Throughout the
development life cycle, the QA engineer will conduct and/or participate in all project reviews
and audits. Details of the QA activities are identified in the Software Quality Assurance Plan
(SQAP).
Software Quality Assurance is responsible for the following verification activities:
 Approve Software life cycle data for transition through the development phases
 Performs and audits verification activities per the SQAP. The audits will include
verification test witnessing and spot-checking of the verification environment, in
addition to spot-checking the outputs of the verification activities
 Verifies that no conflicts exist between plans and standards
 Maintain checklists for Peer and Transition reviews
 Participate in high-level requirements reviews and Software design reviews
 Participate in code reviews as needed
 Conduct reviews of the outputs of the Integration and Test phase
 Conduct reviews of the test cases, procedures, and results
 Create Software problem reports and validate disposition
 Maintain all trace matrices involving testing
 Functional Analysis – Software Integration Analysis
 Verify Configuration Control

To provide greater robustness of the Software, the following verification activities may be
reviewed / witnessed by the QA during verification testing:
 Exercising all state transitions possible during normal operation
 System initialization will be exercised during abnormal conditions
 Determination of possible failure modes of the incoming data
 Execution of out-of-range loop counters
 Verification of power interrupts condition handling
 Exercising built-in test features with emphasis in the area of memory loss/recovery

1.6.5.1 QA and Organizational Independence

The Org Chart of Figure 1-1 shows that the Quality Assurance Organization is independent
from Engineering. QA is in fact being performed by a separate company. It also demonstrates
that the verification and test activities are performed independently by someone other than
the software development engineer.

1.6.6 FAA Software Designated Engineering Representative (Certification

<Doc Number> Page 15 of 75 Rev. -

Plan for Software Aspects of Certification

Authority)
A Software Designated Engineering Representative (DER) will be employed to perform reviews
and audits in order to find compliance with applicable 14 CFR's (where the FAA has delegated
authority). The Software DER's role on this project is summarized below:
 Ensure there is tangible evidence to show that the objectives of DO-178C, other
applicable guidance, issue papers, and so forth are satisfied
 Approve or recommend approval of software plans, data, and compliance findings by
issuing 8110-3 forms against regulations
 Ensure that the project plans are followed
 Ensure that the processes established are yielding the results desired – i.e., making
sure the development, verification, or integral processes are allowing the teams to
satisfy the DO-178C objectives
 Work closely with QA to ensure that processes and plans are being followed
 Follow FAA Orders and other applicable FAA policy documents related to the designee
system
 Ensure that all open problem reports have been evaluated to not negatively impact
safety prior to certification
 Perform routine reviews on projects that he/she will be approving
 Document the review results in writing
 Use the FAA Software Review Job Aid to assist in conducting reviews
 Inform the FAA when reviews are planned and encourage FAA involvement
 Ensure that the project team addresses review findings/observations
 Ensure that the ongoing verification process with project-level peers is being carried
out properly
 Prepare the development team for reviews by other designees or the FAA

1.6.7 Signature Authority Explained

“Signature Authority”, as used herein, is a project-level approval authority that is composed
of the following members at minimum:
 Project Manager
 Software Lead
 Independent Verification Engineer
 Software QA Engineer
Other team members may be required to sign specific documents in addition to this core
group, depending on the content of the document. For example, a Configuration Management
Specialist is required to sign the Software Configuration Management Plan to acknowledge
acceptance of the CM processes defined therein.

1.7 Acronyms and Abbreviations

The following acronyms are used within this DO-178C documentation set.
Add any of your own Acronyms that are pertinent. Its useful to make a note to come back to this
section when all the plans and standards are nearing completion to ensure this list is complete.

<Doc Number> Page 16 of 75 Rev. -