toward approved plans and procedures (e.g., planning, development,  integration/verification, or final software approval).  The following items may influence the level of the approval authority involvement in the software  review process:  The approval authority responsible for software approval must coordinate with the applicant to  assemble the review team. The review team should include at least one person knowledgeable  in software engineering, CM, and SQA and one person familiar with the system safety  assessment and system requirements. Due to the PO/developer relationship, the team should  consist of applicant and contractor complements for CM and quality assurance purposes.  The applicant must coordinate with the approval authority and the developer to propose an  agenda for the upcoming software review at least six weeks in advance. To optimize the  efficiency of the review team while on-site, the approval authority should request that software  plans identified in RTCA DO-278A, Section 4.3, be available at least 10 working days prior to  the review. Each team member should review the plans before arriving at the developer’s  facility. The approval authority should prepare a short initial briefing to introduce the team  members, restate the purpose of the review, and provide an overview of the agenda. The  applicant or developer should prepare a short briefing on the system under review; the software  lifecycle model, processes, and tools used; and any additional considerations made.  L_SRMGSA_202003  Originally published March 2020  Uncontrolled copy when downloaded  L-11  • The availability, experience, and authorization of software SMEs;  • The existence of issues in the project that are associated with Section 12 of RTCA  DO-278A; and  • The distribution of issue papers for software-specific aspects of the approval project.  • The applicant’s knowledge of and previous compliance with the objectives of RTCA  DO-278A and, as applicable, RTCA DO-330, RTCA DO-331, RTCA DO-332, and RTCA  DO-333;  • Proposals for novel software methods or lifecycle models;  • The use of new technologies or unusual design features;  • The product attributes (e.g., size, complexity, system functionality or novelty, and  software design);  • The AL, as determined by a system safety assessment;  3) The appropriate areas for approval authority involvement: the parts of the software  processes where the approval authority should focus involvement to ensure satisfaction  of the appropriate RTCA DO-278A objectives (e.g., focus on plans, design, or code).  2) The extent of approval authority involvement: how much and how often the approval  authority is involved in the project (e.g., how many on-site reviews are conducted; how  much oversight is delegated to the RTCA DO-278A SME; and how much and what types  of applicant data are reviewed, submitted, recommended for approval, and approved).  6.6  Preparing, Conducting, and Documenting the Software Review  6.6.1  Prepare for the Review 