Liability for software in safety-critical mechatronic systems: An industrial questionnaire

2012 2nd International Workshop on Software Engineering for Embedded Systems, SEES 2012 - Proceedings

Volumn , Issue , 2012, Pages 44-50

  Kienle, Holger M ^a   Sundmark, Daniel ^a   Lundqvist, Kristina ^a   Johnsen, Andreas ^a  

^a MÄLARDALEN UNIVERSITY   (Sweden)

Author keywords

[No Author keywords available]

Indexed keywords

CASE STUDY APPROACH; IN-DEPTH ANALYSIS; INDUSTRIAL PRACTICES; LEGAL LIABILITY; MECHATRONIC SYSTEMS; ON CURRENTS; SAFETY CRITICAL SYSTEMS; SAFETY-CRITICAL; SOCIOTECHNICAL;

EMBEDDED SYSTEMS; MECHATRONICS; RESEARCH; SAFETY ENGINEERING; SOFTWARE DESIGN; SURVEYS;

INDUSTRY;

EID: 84864140349     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/SEES.2012.6225490     Document Type: Conference Paper

References (26)

1. IEEE Trial-Use Supplement to IEEE Standard for Information Technology - Software Reuse - Data Model for Reuse Library Interoperability: Intellectual Property Rights Framework. IEEE Computer Society, Jun. 1999, withdrawn.
2. K. Mykytyn, P. P. Mykytyn, and C. W. Slinkman, "Expert systems: A question of liability?" MIS Quarterly, vol. 14, no. 1, pp. 27-42, Mar. 1990.
3. C. J. Palermo, "Software engineering malpractice and its avoidance," 3rd IEEE International Symposium on Software Reliability Engineering, pp. 41-50, Oct. 1992.
4. S. Dowlatshahi, "The role of product safety and liability in concurrent engineering," Computers & Industrial Engineering, vol. 41, no. 2, pp. 187-209, 2001.
5. L. Hoffmann, "Risky business," Communications of the ACM, vol. 54, no. 11, pp. 20-22, Nov. 2011.
6. C. Ackermann, R. Cleaveland, S. Huang, A. Ray, C. Shelton, and E. Latronico, 1st International Conference on Runtime Verification (RV 2010), ser. Lecture Notes in Computer Science. Springer-Verlag, 2010, vol. 6418, ch. Automatic Requirements Extraction from Test Cases, pp. 1-15.
7. M. Åkerholm, R. Land, and C. Strzyz, "Can you afford not to certify your control system?" iVTinternational, Nov. 2009, http:// www.ivtinternational.com/legislative focus nov.php.
8. F. E. Zollers, A. McMullin, S. N. Hurd, and P. Shears, "No more soft landings for software: Liability for defects in and industry that has come of age," Santa Clara Computer & High Technology Law Journal, vol. 21, no. 4, pp. 745-782, 2005, http://www.chtlj.org/sites/default/files/media/articles/ v021/v021.i4.Zollers.pdf.
9. C. Heckman, "Two views on security software liability: Using the right legal tools," IEEE Security & Privacy, vol. 1, no. 1, pp. 73-75, Jan./Feb. 2003.
10. J. Voas, G. McGraw, L. Kassab, and L. Voas, "A 'crystal ball' for software liability," IEEE Computer, vol. 30, no. 6, pp. 29-36, Jun. 1997.
11. P. Runeson and M. Höst, "Guidelines for conducting and reporting case study research in software engineering," Journal on Empirical Software Engineering, vol. 14, no. 2, pp. 131-164, Apr. 2009.
12. N. G. Leveson, Engineering a Safer World, Jul. 2009, http://sunnyday.mit. edu/book2.pdf.
13. J. Cosgrove, "Software engineering and the law," IEEE Software, vol. 18, no. 3, pp. 14-16, May/Jun. 2001.
14. C. Kaner, "Software liability," 1997, http://www.kaner.com/ pdfs/theories.pdf.
15. P. Aiken, R. M. Stanley, J. Billings, and L. Anderson, "Using codes of conduct to resolve legal disputes," IEEE Computer, vol. 43, no. 4, pp. 29-34, Apr. 2010.
16. T. DeMarco and T. Lister, "Both sides always lose: Litigation of software-intensive contracts," CrossTalk, vol. 13, no. 2, pp. 4-6, Feb. 2000, http://www.stsc.hill.af.mil/crosstalk/2000/02/demarco.html.
17. C. S. Tuner and F. Khosmood, "Rethinking software process: the key to negligence liability," 5th IASTED International Conference on Software Engineering and Applications, Aug. 2001, http://citeseerx.ist.psu.edu/viewdoc/ summary?doi=10.1.1.22.4208.
18. M. Hecht, "The role of safety analyses in reducing products liability exposure in "smart" consumer products containing software and firmware," IEEE Reliability and Maintainability Symposium (RAMS 2003), pp. 153-158, Jan. 2003.
19. C. Jones, Software Engineering Best Practices. McGraw-Hill, Oct. 2009.
20. C. Kaner, "Software negligence and testing coverage," 1996, http: //www.badsoftware.com/coverage.htm.
21. C. S. Tuner, D. J. Richardson, and J. L. King, "Legal sufficiency of testing processes," SAFECOMP'96, 1996, http://citeseerx.ist.psu.edu/ viewdoc/summary?doi=10.1.1.35.1464.
22. J. Armour and W. S. Humphrey, "Software product liability," Software Engineering Institute, Carnegie Mellon University, Tech. Rep. CMU/SEI-93-TR-13, Aug. 1993, http://www.sei.cmu.edu/reports/93tr013.pdf.
23. M. A. Cusumano, "Who is liable for bugs and security flaws in software?" Communications of the ACM, vol. 47, no. 3, pp. 25-27, Mar. 2004.
24. C. Kaner, "Liability for defective content," 22nd ACM International Conference on Design of Communication (SIGDOC '04), pp. 145- 151, Oct. 2004.
25. F. Bott, A. Coleman, J. Eaton, and D. Rowland, Professional Issues in Software Engineering, 3rd ed. Taylor & Francis, Aug. 2000.
26. D. M. German, J. H. Weber, and M. D. Penta, "Lawful software engineering," ACM Workshop on Future of Software Engineering Research (FoSER 2010), pp. 129-132, Oct. 2010.