DO-178B Planning
If we look at model DO-178B
·
Planning
Process
·
Developing
Process
·
Confirmation
·
Configuration
Administration
·
Quality
Safety
·
Certification
we can list in order like that. Planning is a process
that is most critical and cogitated as a team in the guidance of DO-178B. Issue
that makes planning process critical is principle of DO-178B that everything is
guilty until proven innocent. Principle in modern approach to law “ innocent until proven guilty” is just the opposite in DO-178B processes,
and you have to defend and provide evidence relating that stated items are done
with the form of plans against the authority. Because many firms’ planning
processes’ output plan documents are created with make and forget principle (
mostly there is no change in change records in plan documents) , this situation
causes break out in a cold sweat during the certification process of project.
DO-178B planning process includes 5
plans and standard documents.
1- PSAC (Plan for Software Aspects of Certification)
Project’s purpose, processes, conditions of the transition of
process, used technology, developing tools are explained without detailing. It
is expected to answer the questions such as “How is project schedule? What kind
of operating system are involved in?” in PSAC. Not
detailing is modestly my suggestion, and writing PSAC confirmed at the
beginning and end of the project in detail may cause problems when considering nature of development. ( requests of consumers,technology).You can tell about which
vehicle do you use in your project, but if you explain details of this vehicle
and integrations with the other vehicles, it may be a problem even change of
version that you told in 2nd year of the project . 20-30 sheet PSAC
will be enough.
Overview of the document is like below
1. System Overview: System overview,
system functionality, software/hardware ratio, interface definitions, etc.
sections are explained here.
2. Software Overview: In this section, software
functions are defined taking into consideration the safety requirements. Source
administration, fault resistance, time constraints, etc.
3. Certification Considerations: Assigned DAL(design
assurance level) values are explained how to provide suitability.
4. Software Lifecycle : Applied software developing
process is explained in this section. Each process is defined as purpose of
process and how to achieve this purpose.
5. Software Lifecycle Data: Entry/exit conditions and
products (data) are explained for each process in the previous step.
6. Schedule:
Project schedule is explained and so overview dates are planned with
certification authority.
7. Additional Consideration: Issues such as vehicle
qualification , COTS products that may influence providing safety systems and
process of project are explained in this section.
To sum up , information that PSAC document should
involve is like above, I won’t share document template because it is provided
on the internet and I will try to explain the next plan documents, “QA Plan”
new quality administration plan.
Safety is not an option, it is a must.
2-
Quality Assurance Plan
QA plan is a plan that explains how to provide quality
assurance. CMMI is easy to produce and be understood for a firm, what should be
paid attention is that quality plan must not contradict with software
developing plan in 4th item. Independent qualifier is necessary in
the project in the guidance of DO-178B. It is because that being independent or
that quality substitute give a report to reference besides project
administration and different people who say “it is not done, do it again” is
good for everyone. Because saying “you are doing these and these” may be
discomfort. ;)
QA plan means that company’s plan and standards is
compatible with DO-178B. It consists evidences guaranteeing software developing
process is compatible with company’s plans, express how overviews will be made
and, how criteria for transportation between processes are.
We will continue with explaining CM plan in the next
step.
Hiç yorum yok:
Yorum Gönder