Professional Documents
Culture Documents
DO-178B Interview Que and Ans.
DO-178B Interview Que and Ans.
AeroSpace
You are here: Home > 2013 > December > DO178B Interview Questions
Primary Sidebar
Recent Posts
2) What is Software Life Cycle Process?
Ans:
Software Life Cycle process is
a)Planning Process
b)Development Process
i)Requirements
ii)Design
iii)Coding
iv)Integration
c)Integral Process
i)Verification
ii)Configuration Management
iii)Software Quality and Certification
d)Life Cycle definition.
Ans:
Objectives:
a)Process activities, plans,standards are defined.
b)Software Life Cycles,Development Environment, Methods, Toolsare defined,
c)Transition criteria betweenprocesses are established.
d)All Objectives on DO-178B Guidelines, Table A-1
Deliverables:
a)Plan for Software Aspects of Certification.
b)Software Development Plan.
c)Software Verification Plan.
d)Software Quality Assurance Plan.
e)Software Configuration Management Plan.
f)Software Requirements Standards.
g)Software Design Standards.
h)Software Coding Standards.
Ans:
Software Verification includes
a) Reviews
b) Analysis
c) development of test cases and procedures
d) execution of test procedures
The purpose of software verification process is to detect and report errors that may have
been introduced during the software development processes. Removal of the errors is an activity
of the software development processes.
The Verification process provides traceability between the implementation of the software
requirements and verification of those requirements
The traceability between software requirements and the test cases is accomplished by
requirements-based coverage analysis.
The traceability between the code structure and the test cases is accomplished by structural
coverage analysis
Inputs:
a) The relevant Process outputs to be reviewed.
b) The inputs used for generating the process output
c) Software Verification Plan
d) The relevant review checklist
Outputs:
a) Review record/ Defect Record
b) Analysis Reports.
Ans:
Objectives:
a) Configuration items identified.
b) Problems reported.
c) Changes controlled and reviewed.
d) Archival, retrieval, release managed.
e) Load control managed.
f) All Objectives on DO-178B Guidelines, Table A-8
Deliverables:
a) SCM Records.
b) Software Configuration Index
c) Problem Reports
d) Software Life Cycle Environment Configuration Index
Ans:
Objectives:
a) Processes comply with approved plans and standards.
b) Transition criteria for software life cycle processes are satisfied.
c) All Objectives on DO-178B Guidelines, Table A-9
d) Software conformity review is conducted.
e) Software life cycle processes are complete.
f) Software life cycle data is complete.
g) Executable Object Code is controlled and can be regenerated.
Deliverables:
a) Software Quality Assurance Records.
Ans:
Objectives:
a) Establish communication and understanding between applicant and certification authority (at
start).
b) Agreement on means of compliance is obtained (at start).
c) Compliance substantiation is provided (at end).
d) All Objectives on DO-178B Guidelines, Table A-10
Deliverables:
a) Plan for Software Aspects of Certification (? certification authority at start).
b) Software Configuration Index (? certification authority at end).
c) Software Accomplishment Summary (? certification authority at end).
d) Availability of all Software Life Cycle Data and producing up on request.
9) What is all the coverage of requirement based testing of all the levels?
Ans:
Level A: Modified Condition Decision Coverage (MCDC) + Level B.
Level B: Decision Coverage+ Level C.
Level C: Statement Coverage.
Levels D & E: Not needed.
Levels A-C: Data and Control Coupling.
Catastrophic Level
A(66 Objectives)
Hazardous/Severe-Major Level
B(65 Objectives)
Major Level
C(57 Objectives)
Minor Level
D(28 Objectives)
No Level
Effect E
18) Does DO-178B can be applied for both Civil and Military aircraft application?
Ans:
The guideline applies only for commercial aircraft’s and there are separate military
standards but and at times defense may use it.
Ans:
The design description is definition of the software architecture and the low-level
Requirements that will satisfy the software high-level requirements. This data should Include
Inputs:
a) SRS (Requirement data and other document)
b) Software Development Plan
c) Software Design Standard
d) High Level Design (software architecture)
e) Review feedback
Outputs:
a) Detailed Design Document defines software Low Level Requirements that will satisfy
Software High Level Requirements. Derived Low Level requirements are identified separately.
b) Updated Traceability.
Ans:
a) Software Planning review Stage of Involvement (SOI) #1
b) Software Development review – Stage of Involvement (SOI) #2
c) Software Verification review Stage of Involvement (SOI) #3
d) Final Certification review – Stage of Involvement (SOI) #4
Ans:
If an item, artifact is CC1 then it must have all those attributes in the table in section 7.
Meaning it needs to have baselines, change management, etc.
If an item/artifact is CC2 then it doesn’t need all of those items. It really only needs to
be retained. Simply put a CC1 item needs to be tracked where as a CC2 item needs to be
stored.Typically a CC2 items tends to be “one-shots” like meeting minutes, reports, problem
reports themselves, etc.Whereas CC1 items tend to be documents that need to be maintained,
tracked and base lined. Is it a big deal in DO178B, well yes. If you don’t maintain the CC1 data
as per the table, one isn’t following the process and hence can’t build the substantiation data
required.
25) What is ATA number?
Ans:
a) The ATA(Air Transport Association) 100 Chapter numbers was a common referencing
standard for all commercial aircraft documentation.
b) This commonality permits greater ease of learning and understanding for pilots, aircraft
maintenance technicians, and engineers alike
Ans:
1. MCDC
2. Source to Object code verification,(Refer 6.4.4.2 b in DO178B.PDF)
Ans:
We build systems to meet the requirements of our users. As we build systems, we take our user’s
requirements and derive more requirements from them. Derived requirements are lesser than user
requirements.It is easy, however, to forget this relationship, and this can cause many problems
for our projects.
A derived requirement is something that we infer or derive from a user requirement. (For this
article, let’s use the term user for the customer, user, and client. Let’s also use the term “user
requirement” for something that the user wants.)
For example, suppose a user requirement is “the system must work outdoors, 12 months a year in
Minnesota.”
Several derived requirements are (1) the system must work in temperatures below 10 degrees F
and (2) the system
must work in the snow. We derive these requirements by delving into the details of the user
requirement.
28)What are Planning Documents ?
Ans:
The Planning documents are
15 Comments
1. Mahadev.G.T
4 years ago Permalink
Thanks for making things in one place ..explaint clearly and covered all most every
thing ..expecting more on plans and different planning documents related FAQs…
Admin
4 years ago Permalink
Hi Mahadev,
jitendra
4 years ago Permalink
Thanks for creating this blog, this will help all level of avionics engineers.
admin
4 years ago Permalink
purushothama
3 years ago Permalink
what are the objectives of DO178b. for ex: for A level soft ware under colom “objectives” listed
as 66 & ” with independence as 25. could not understand. an you help
admin
3 years ago Permalink
Hi purushothama,
There are certain objectives defined for each level of software , the software should
meet/compliance with objectives to get certified.
Please refer the DO 178B Pdf for more information.
Nagendra N
3 years ago Permalink
Thanks for putting question on Do178 ,This question are really good.I want to PDF of Do178
question ,
Please send PDF to the email.
admin
3 years ago Permalink
Hi Nagendra,
Regards,
Sivaprasad.Ch
venkat
2 years ago Permalink
If you add independent objective in question # 16 software table, it will good for the beginners
admin
2 years ago Permalink
Hi Venkat,
Regards,
Siva
Nagendra N
2 years ago Permalink
Sai
2 years ago Permalink
Good website to learn DO-178.I have seen some interview questions like why to follow DO-178,
what happens if not followed and is it mandatory to follow the each and everything in DO-178.
Please list those type of questions also.
admin
2 years ago Permalink
Hi Sai,
Regards,
Siva
RAVI TEJA
6 months ago Permalink
thank you for these questions on DO178B. please forward the pdf document of DO178B. my
mail id is raviteja138438@gmail.com
Nagendra Puttachary
2 months ago Permalink
Leave a Reply
Your email address will not be published. Required fields are marked *
Comment
Name *
Email *
Next Post: ARINC 429 Protocol
Secondary Sidebar
Archives
December 2017
September 2017
June 2016
May 2016
April 2016
March 2016
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
March 2014
February 2014
December 2013
Search for:
Recent Comments
Aru on MCDC
Md Rakibul Islam on MCDC
Nagendra Puttachary on DO178B Interview Questions
Sivateja on MCDC
Ravi on DO 178B to DO 178C
Categories
Contact Us