Scribd
Upload
208 views

SOI JobAid Extract

The document describes the activities and objectives of four stages of involvement (SOI) in reviewing software development according to DO-178B: 1. Planning review ensures plans meet objectives and software will comply with standards. Data like development plans are reviewed. 2. Development review assures data meets objectives and requirements are documented and traceable. Plans, standards, code and results are reviewed. 3. Verification review checks tasks are complete and data meets objectives, and verification satisfied coverage. Tests, code, results and coverage are reviewed. 4. Final review determines compliance and all items are addressed, and reviews accomplishment summary and indexes. Software conformity and indexes are checked.

Uploaded by

Prem K
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
208 views

SOI JobAid Extract

The document describes the activities and objectives of four stages of involvement (SOI) in reviewing software development according to DO-178B: 1. Planning review ensures plans meet objectives and software will comply with standards. Data like development plans are reviewed. 2. Development review assures data meets objectives and requirements are documented and traceable. Plans, standards, code and results are reviewed. 3. Verification review checks tasks are complete and data meets objectives, and verification satisfied coverage. Tests, code, results and coverage are reviewed. 4. Final review determines compliance and all items are addressed, and reviews accomplishment summary and indexes. Software conformity and indexes are checked.

Uploaded by

Prem K
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

ACTIVITIES FOR STAGE OF INVOLVEMENT #1 – PLANNING REVIEW

What is done:
To ensure that plans and standards meet objectives in DO-178B Annex A tables A-1, A-8, A-9, A-10, and that
the software will comply with other applicable software policy and guidance.
When Review Occurs
Shortly after completion of the software planning process, or any other necessary point. Plans and standards
may not be fully completed; however, they should be fairly mature prior to the review and under configuration
control.

Data Reviewed Prior to Review


Plan for Software Aspects of Certification (PSAC), Software Verification Plan (SVP), Software Development
Plan (SDP), Software Configuration Management Plan (SCMP), Software Quality Assurance Plan (SQAP), and
Software Development Standards (Requirements, Design, and Coding).

Data Reviewed at Review

PSAC, SVP, SDP, SCMP, SQAP, findings/observations/issues from pre-review activities by


designees/applicants/developers (if applicable), software development standards, safety assessment, system architecture,
software level justification, safety features, tool qualification plans (if applicable), company policy and work instructions
referenced in the plans and standards, and other data deemed necessary

ACTIVITIES FOR STAGE OF INVOLVEMENT #2 – DEVELOPMENT REVIEW


What is done:
Assure that software life cycle data meets DO-178B objectives from tables A-2, A-3, A-4, A-5, A-8, A-9, and A-10.
When Review Occurs
When the software design is sufficiently mature to support ongoing software change without degrading safety or
architecture, or when deemed necessary. Some things that should be in place prior to this review are:

 High-level requirements are documented, reviewed, and traceable to system requirements


 Low-level requirements are documented, reviewed, and traceable to high-level requirements.
 Source code implements and is traceable to the low-level requirements and has been reviewed.

Data Reviewed Prior to Review


Report from Stage of Involvement #1 (SOI #1); open items from SOI #1; and all plans (PSAC, SVP, SDP, SCMP, SQAP (as a
refresher after SOI #1 or to review changes to plans since SOI #1)).

Data Reviewed at Review


Standards for Software Requirements, Design, and Code; Software Requirements Data; Design Description; Source Code;
Software Verification Results (as applied to Tables A-2 to A-6); Problem Reports; Software Configuration Management
Records; Software Quality Assurance Records; Trace Matrix/Tool; and Designees’ findings/observations from pre-review
activities.
ACTIVITIES FOR STAGE OF INVOLVEMENT #3 – VERIFICATION REVIEW
What is done:

 Check the completion of all associated SCM and SQA tasks.


 Ensure that the software life cycle data meets DO-178B objectives from Tables A-6, A-7, A-8, A-9, and A-10.
 Ensure that the verification activity satisfied the coverage requirements found in DO-178B, Table A-7.
When Review Occurs

When the following activities are in place:

 Test procedures and results are documented and reviewed


 Executable object code satisfies software requirements
 coverage analysis indicates the structural coverage requirements are met (for levels A, B, C)
Note: Testing is where many applicants have problems. It is best to perform this review early enough that major retest will
not be required if issues are found, but late enough to see some trends in the test program.

Data Reviewed Prior to Review


Reports from SOI #1 and SOI #2, open items from SOI #1 and SOI #2, and all plans (PSAC, SVP, SDP, SCMP, SQAP (as a
refresher after SOI #1 & SOI #2 or to review changes to plans since SOI #1 & SOI #2)).

Data Reviewed at Review


Software Requirements Data; Design Description; Source Code; Software Verification Cases and Procedures; Software
Verification Results; Problem Reports; Software Configuration Management Records; Software Quality Assurance Records;
Trace Matrix/Tool; and Designees’ findings/observations from pre-review activities.

Evaluation Activities and Questions


During SOI #3 a trace is performed on a sampling of system requirements allocated to software to see if they are
adequately tested. Likewise, test cases are traced up to the system requirements to verify traceability

ACTIVITIES FOR STAGE OF INVOLVEMENT #4 – FINAL REVIEW

Purpose

 Determine if final compliance to all of the DO-178B objectives has been achieved and all open items
addressed/dispositioned.
 Assess the Software Configuration Index, Software Life Cycle Environment Configuration Index, Software
Accomplishment Summary, and any other documents not previously reviewed.
When to Perform
When the software life cycle is completed, and the following items have been completed by the applicant (or when deemed
necessary):
 Software conformity review has been performed
 Software Accomplishment Summary and Configuration Indexes have been reviewed and are correct.
 Formal signature process has been completed

Data to Review Prior to the Review


Reports from SOI #1, SOI #2, and/or SOI #3; open items from SOI #1, SOI #2, and/or SOI #3; all plans; Software
Accomplishment Summary; and Configuration Index

Data to Review at the Review


Software Life Cycle Environment Configuration Index; Software Configuration Index; Problem Reports; Software
Accomplishment Summary; Designees’ findings/observations from pre-review activities; and any data that had issues in
previous reviews

Evaluation Activities and Questions


During SOI #4 the Software Accomplishment Summary and Software Configuration Index are evaluated. Additionally, open
items from previous reviews are evaluated to ensure that all of the DO-178B objectives and project issues are addressed.

You might also like