What do you do?
What do you do?
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=fe375697-de8a-4e6a-8fd5-53e296a39d8a)
Expanding Scope of DO-178C
11 years ago
Saturday, November 29, 2008
To Do Or Not To Do
You have completed your delivery of all software verification results. It is late Friday evening. Weekend ahead. Time to go home after a satisfactory day's work when your colleague comes in and tells you that one of the deliveries has a defect. It is not so obvious but if someone were to audit it they would find out that there has been an error on our part. Your first reaction is to find out who screwed up. But then you rationalise: "The defect is minor error in the test result. The product has no defect. It is unlikely that this unit will be picked up for audit. Even if it is picked up you can always apologise and fix it. Or you can come back on Monday and fix the small problem and then inform the customer. All the engineers are gone. You will have to call them. They have worked very hard and they deserve their weekend." But at the back of your mind there is a small tussle going on: "If the customer catches this, he might suspect that we have done a bad job. They have pointed out similar errors in the past and we had promised them that similar error will not occur."
What do you do?
What do you do?
What do you do?
What do you do?
Subscribe to:
Post Comments (Atom)
Posts
2 comments:
If "They have pointed out similar errors in the past and we had promised them that similar error will not occur.", then I would see to it that its fixed before delivery.
Yes but will you get it done in the weekend or on Monday? What if your customer decides to audit in in the weekend? And what would be your follow up action? Are there any process issues here? Why are similar errors occurring? Why didn't the review catch the error before delivery? Question! Questions!
Post a Comment