[SystemSafety] Agile methods

[RICQUE Bertrand (SAGEM DEFENSE SECURITE)]

Yes I encountered the case and it never worked. It seems very difficult to me to reconciliate approaches (with deficiencies I agree) requesting a complete spec in the beginning, with approaches tending to solve the probleme when and if you encounter them.


Bertrand RICQUE
Program Manager, Optronics and Defense Division

T +33 (0)1 58 11 96 82
M +33 (0)6 87 47 84 64
23 avenue Carnot
91300 MASSY - FRANCE
http://www.sagem-ds.com<http://www.sagem-ds.com/>

[cid:image001.jpg at 01CEA7C3.F3C35850]

From: systemsafety-bounces at lists.techfak.uni-bielefeld.de [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de] On Behalf Of René Senden
Sent: Friday, August 30, 2013 7:30 PM
To: 'Nancy Leveson'
Cc: systemsafety at techfak.uni-bielefeld.de
Subject: Re: [SystemSafety] Agile methods

I appreciate your input, however, my question addresses a specific situation that some of you may have encountered in practice...
It is such practical experience I am interested in...
Let me rephrase... I was not very clear/accurate in describing my query...
Have you encountered a situation, in industrial practice, in which an organization developing software following an agile methodology
has to comply with a safety standard which has specific requirements on the software development process? A typical example of
such safety standard, with respect to its requirements on the sw-dev, would be IEC-61508 Part 3 or DO-178...

Rene

From: Nancy Leveson [mailto:leveson.nancy8 at gmail.com]<mailto:[mailto:leveson.nancy8 at gmail.com]>
Sent: vrijdag 30 augustus 2013 19:14
To: René Senden
Cc: systemsafety at techfak.uni-bielefeld.de<mailto:systemsafety at techfak.uni-bielefeld.de>
Subject: Re: [SystemSafety] Agile methods

Definitions always differ among the users of terms. But if the Agile methods being considered do not start with a complete and thorough specification of all the system/software safety requirements before anything else, then the system resulting system/software design will almost surely be less safe than one that does. Whether it coincides with other standards (most of which are very deficient with respect to safety) is not really important, is it?

Nancy

On Fri, Aug 30, 2013 at 1:02 PM, René Senden <rene.senden at gmail.com<mailto:rene.senden at gmail.com>> wrote:
Dear all,

Do any of you have practical experience with reconciling established agile
software development with software safety requirements (e.g. IEC-61508 or
DO-178..) ?

Best regards,
Rene

_______________________________________________
The System Safety Mailing List
systemsafety at TechFak.Uni-Bielefeld.DE<mailto:systemsafety at TechFak.Uni-Bielefeld.DE>



--
Prof. Nancy Leveson
Aeronautics and Astronautics and Engineering Systems
MIT, Room 33-334
77 Massachusetts Ave.
Cambridge, MA 02142

Telephone: 617-258-0505
Email: leveson at mit.edu<mailto:leveson at mit.edu>
URL: http://sunnyday.mit.edu
#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles ou ayant un caractère privé. S'ils ne vous sont pas destinés, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque manière que ce soit le contenu. Si ce message vous a été transmis par erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20130902/81183770/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1835 bytes
Desc: image001.jpg
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20130902/81183770/attachment.jpg>