O
odangelo
Hello,
I'm relatively new to this forum and I'm hoping that you might be able to help. The topic of witnessing an aerospace software build (a "black-label" build) for a DAL-E software project has come up in my organization and I'd like a better understanding of what this entails, and to poll what you're doing in your own organizations.
1. For DAL-E, is "witnessing" required or optional? At what level does it become mandatory? DO-178C defines Monitoring as "The act of witnessing or inspecting selected instances of test, inspection, or other activity, or records of those activities, to assure that the activity is under control and that the reported results are representative of the expected results." DO-178C also says in a note in section 8.2 that "monitoring of the activities of software life cycle processes may be performed to provide assurance that the activities are under control." The use of the word "may" seems to imply that this is optional.
2. What is involved with "witnessing"? Does it mean to sit through the actual build process to observe and record what happens, or is it an audit of the process used to ensure that the actual build complies with that process and that all required artifacts were produced?
Thank you,
Omar D'Angelo
I'm relatively new to this forum and I'm hoping that you might be able to help. The topic of witnessing an aerospace software build (a "black-label" build) for a DAL-E software project has come up in my organization and I'd like a better understanding of what this entails, and to poll what you're doing in your own organizations.
1. For DAL-E, is "witnessing" required or optional? At what level does it become mandatory? DO-178C defines Monitoring as "The act of witnessing or inspecting selected instances of test, inspection, or other activity, or records of those activities, to assure that the activity is under control and that the reported results are representative of the expected results." DO-178C also says in a note in section 8.2 that "monitoring of the activities of software life cycle processes may be performed to provide assurance that the activities are under control." The use of the word "may" seems to imply that this is optional.
2. What is involved with "witnessing"? Does it mean to sit through the actual build process to observe and record what happens, or is it an audit of the process used to ensure that the actual build complies with that process and that all required artifacts were produced?
Thank you,
Omar D'Angelo