Trustworthy software systems: a discussion of basic concepts and terminology

ABSTRACT

Basic concepts and terminology for trustworthy software systems are discussed. Our discussion of definitions for terms in the domain of trustworthy software systems is based on former achievements in dependable, trustworthy and survivable systems. We base our discussion on the established literature and on approved standards. These concepts are discussed in the context of our graduate school TrustSoft on trustworthy software systems. In TrustSoft, we consider trustworthiness of software systems as determined by correctness, safety, quality of service (performance, reliability, availability), security, and privacy. Particular means to achieve trustworthiness of component-based software systems - as investigated in TrustSoft - are formal verification, quality prediction and certification; complemented by fault diagnosis and fault tolerance for increased robustness.

REFERENCES

• 1: R. Achatz, J. Bosch, D. Rombach, T. Beauvais, A. Fuggetta, J.-P. Banatre, F. Bancilhon, S. De Panfilis, F. Bomarius, H. Saikkonen, H. Kuilder, G. Boeckle, B. Fitzgerald, and C. M. Olsson. The software and services challenge. Technical report, Technology Pillar on Software, Grids, Security and Dependability of the 7th Framework Programme, January 2006.
• 2: ATIS T1A1. Performance and Signal Processing. American National Standards Institute, ATIS Committee T1A1, 2001.
• 3: Ross J. Anderson, Security Engineering: A Guide to Building Dependable Distributed Systems, John Wiley & Sons, Inc., New York, NY, 2001
• 4: Algirdas Avizienis , Jean-Claude Laprie , Brian Randell , Carl Landwehr, Basic Concepts and Taxonomy of Dependable and Secure Computing, IEEE Transactions on Dependable and Secure Computing, v.1 n.1, p.11-33, January 2004 [doi>10.1109/TDSC.2004.2]
• 5: A. Avizienis and L. Chen. On the implementation of n-version programming for software fault tolerance during execution. In Proc. IEEE International Computer Software & Applications Conference (COMPSAC 77), pages 149--155, November 1977.
• 6: B. Bérard, M. Bidoit, A. Finkel, F. Laroussinie, A. Petit. L. Petrucci, Ph. Schnoebelen Ph, and P. McKenzie. Systems and Software Verification - Model-Checking Techniques and Tools. Springer-Verlag, 2001. ISBN 3-540-41523-8.
• 7: Larry Bernstein, Trustworthy software systems, ACM SIGSOFT Software Engineering Notes, v.30 n.1, January 2005 [doi>10.1145/1039174.1039176]
• 8: B. Boehm. Verifying and validating software requirements and design specifications. IEEE Software, 1(1): 75--88, 1984.
• 9: Robert S Boyer , J S Moore, Program verification, Journal of Automated Reasoning, v.1 n.1, p.17-23, 1985
• 10: Aaron B. Brown and David A. Patterson. Towards availability benchmarks: A case study of software raid systems. In Proceedings of the 2000 USENIX Annual Technical Conference, San Diego, CA, USA, June 2000.
• 11: Bundesamt für Sicherheit in der Informationstechnik. BSI Certification and BSI Product Information -- notes for manufacturers and vendors. http://www.bsi.bund.de/zertifiz/zert/7138_e.pdf, 2004. retrieved 3/1/2006.
• 12: Bytepile. BytePile.com - Definition of QoS, 2006. URL http://www.bytepile.com/definitions-q.php.
• 13: John Cheesman , John Daniels, UML components: a simple process for specifying component-based software, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 14: Roger C. Cheung. A user-oriented software reliability model. IEEE Transactions on Software Engineering, 6(2):118--125, March 1980. ISSN 0098--5589. Special collection from COMPSAC '78.
• 15: George Coulouris , Jean Dollimore , Tim Kindberg, Distributed systems (3rd ed.): concepts and design, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 16: Michael A. Cusumano, Who is liable for bugs and security flaws in software?, Communications of the ACM, v.47 n.3, March 2004 [doi>10.1145/971617.971637]
• 17: Rogrio de Lemos. ICSE 2003 WADS panel: Fault tolerance and self-healing, 2003. URL citeseer.ist.psu.edu/656379.html.
• 18: Department of Trade and Industry. Information technology security evaluation criteria. http://www.bsi.de/zertifiz/itkrit/itsec-en.pdf, 1991. retrieved 3/1/2006.
• 19: Klaus Echtle. Fehlertoleranzverfahren. Springer-Verlag, Berlin, 1990.
• 20: R. J. Ellison, D. A. Fischer, R. C. Linger, H. F. Lipson, T. Longstaff, and N. R. Mead. Survivable network systems: an emerging discipline. Technical Report CMU/SEI-97-TR-013, Software Engineering Institute, Carnegie Mellon University, May 1999. Revised.
• 21: C. Floyd. A systematic look at prototyping. In R. Budde, K. Kuhlenkamp, L. Mathiassen, and H. Züllighoven, editors, Approaches to Prototyping, pages 1--18. Springer-Verlag, 1984.
• 22: Svend Frolund and Jari Koistinen. QML: A language for quality of service specification. Technical Report HPL-98-10, Hewlett Packard Laboratories, February 10 1998. URL http://www.hpl.hp.com/techreports/98/HPL-98-10.pdf.
• 23: Svend Frolund and Jari Koistinen. Quality of service aware distributed object systems. Technical Report HPL-98-142, Hewlett Packard, Software Technology Laboratory, August 1998. URL http://www.hpl.hp.com/techreports/98/HPL-98-142.html.
• 24: Svend Frolund and Jari Koistinen. Quality-of-service specification in distributed object systems. Distributed Systems Engineering, 5(4):179--202, 1998. doi: 10.1088/0967--1846/5/4/005.
• 25: Wilhelm Hasselbring, Technical opinion: On defining computer science terminology, Communications of the ACM, v.42 n.2, p.88-91, Feb. 1999 [doi>10.1145/293411.293488]
• 26: W. Hasselbring and Simon Giesecke, editors. Dependability Engineering. Gito Verlag, Berlin, Germany, 2006. ISBN 3-936771-56-1.
• 27: Wilhelm Hasselbring , Ralf Reussner, Toward Trustworthy Software Systems, Computer, v.39 n.4, p.91-92, April 2006 [doi>10.1109/MC.2006.142]
• 28: Wilhelm Hasselbring. Component-based software engineering. In S. K. Chang, editor, Handbook of Software Engineering and Knowledge Engineering, Volume 2, pages 289--305. World Scientific Publishing, River Edge, NJ, USA, 2002.
• 29: IEEE 1012--1998. IEEE 1012--1998: Standard for Software Verification and Validation. IEEE, 1998. Published standard.
• 30: IEEE 610.12:1990. IEEE 610.12:1990: Standard Glossary of Software Engineering Terminology. IEEE, 1990. Published standard.
• 31: IEEE SWEBOK. SWEBOK: Guide to the Software Engineering Body of Knowledge. IEEE Computer Society Professional Practices Committee, Los Alamitos, California, 2004.
• 32: ISO 8402. ISO 8402 Quality Management and Quality Assurance: Vocabulary. ISO, 1994. Published standard.
• 33: ISO 9126--3. Software engineering - Product quality - Part 3: Internal Metrics. ISO/IEC, June 2001. Published standard.
• 34: ISO 9126--1. Software engineering - Product quality - Part 1: Quality model. ISO/IEC, June 2001. Published standard.
• 35: ISO/IEC 14598--1. ISO/IEC 14598--1: Information technology - Software product evaluation - Part 1: General overview. ISO/IEC, 1999. Published standard.
• 36: ISO/IEC 9126--1. ISO/IEC 9126--1: Software Engineering - Product Quality - Part 1: Quality Model. ISO/IEC, June 2001. Published standard.
• 37: Raj Jain. The Art of Computer Performance Analysis. John Wiley & Sons, 1991.
• 38: Pankaj Jalote, Fault tolerance in distributed systems, Prentice-Hall, Inc., Upper Saddle River, NJ, 1994
• 39: Donald E. Knuth, The art of computer programming, volume 1 (3rd ed.): fundamental algorithms, Addison Wesley Longman Publishing Co., Inc., Redwood City, CA, 1997
• 40: P. Koopman. Workshop on Architecting Dependable Systems (WADS'03), May 2003. URL www.ece.cmu.edu/~koopman/roses/wads03/wads03.pdf.
• 41: Leslie Lamport. Proving the correctness of multiprocess programs. IEEE Trans. Software Eng., 3(2):125--143, 1977.
• 42: J.C. C. Laprie , A. Avizienis , H. Kopetz, Dependability: Basic Concepts and Terminology, Springer-Verlag New York, Inc., Secaucus, NJ, 1992
• 43: Jean-Claude Laprie , Karama Kanoun, Software reliability and system reliability, Handbook of software reliability and system reliability, McGraw-Hill, Inc., Hightstown, NJ, 1996
• 44: J.C. C. Laprie , A. Avizienis , H. Kopetz, Dependability: Basic Concepts and Terminology, Springer-Verlag New York, Inc., Secaucus, NJ, 1992
• 45: Edward D. Lazowska , John Zahorjan , G. Scott Graham , Kenneth C. Sevcik, Quantitative system performance: computer system analysis using queueing network models, Prentice-Hall, Inc., Upper Saddle River, NJ, 1984
• 46: Nancy G. Leveson, Safeware: system safety and computers, ACM Press, New York, NY, 1995
• 47: William W. Lowrance. Of acceptable risk: science and the determination of safety. William Kaufman, Inc., 1976. ISBN 0-913232-30-0.
• 48: Michael R. Lyu. Software Reliability Engineering. McGraw-Hill, New York, 1 edition, 1996.
• 49: D. A. Menasce, V. A. F. Almeida, and L. W. Dowdy. Performance by Design. Prentice Hall, 2004.
• 50: Bertrand Meyer, Object-oriented software construction (2nd ed.), Prentice-Hall, Inc., Upper Saddle River, NJ, 1997
• 51: Performability evaluation: where it is and what lies ahead, Proceedings of the International Computer Performance and Dependability Symposium on Computer Performance and Dependability Symposium, p.50, April 24-26, 1995
• 52: John D. Musa , Anthony Iannino , Kazuhira Okumoto, Software reliability: measurement, prediction, application, McGraw-Hill, Inc., New York, NY, 1987
• 53: David Lorge Parnas. Software aging. In ICSE '94: Proceedings of the 16th international conference on Software engineering, pages 279--287, Los Alamitos, CA, USA, 1994. IEEE Computer Society Press. ISBN 0-8186-5855-X.
• 54: A. Pfitzmann and M. Hansen. Anonymity, unlinkability, unobservability, pseudonimity, and identity management - a consolidated proposal for terminology, 2005. URL http://dud.inf.tu-dresden.de/Anon_Terminology.shtml.
• 55: Charles P. Pfleeger, Security in computing, Prentice-Hall, Inc., Upper Saddle River, NJ, 1996
• 56: Brian Randell. System structure for software fault tolerance. IEEE Transactions on Software Engineering, SE-1(2):220--232, June 1975.
• 57: Matthias Rohr. Example of empirical research: N-version programming. In W. Hasselbring and Simon Giesecke, editors, Research Methods in Software Engineering, pages 39--62. Gito Verlag, Berlin, Germany, 2006. ISBN 3-936771-57-X.
• 58: Fred B. Schneider, Trust in Cyberspace, National Academy Press, Washington, DC, 1998
• 59: B. Schneier. Beyond Fear. Springer-Verlag, Berlin, Germany, 2003. ISBN 0-387-02620-7.
• 60: Performance solutions: a practical guide to creating responsive, scalable software, Addison Wesley Longman Publishing Co., Inc., Redwood City, CA, 2002
• 61: Ian Sommerville, Software Engineering (7th Edition), Pearson Addison Wesley, 2004
• 62: Neil R. Storey, Safety Critical Computer Systems, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1996
• 63: Clemens Szyperski, Dominik Gruntz, and Stephan Murer. Component Software: Beyond Object-Oriented Programming. ACM Press and Addison-Wesley, New York, NY, 2nd edition, 2002.
• 64: Andrew S. Tanenbaum , Maarten Van Steen, Distributed Systems: Principles and Paradigms, Prentice Hall PTR, Upper Saddle River, NJ, 2001
• 65: Kishar Shridharbhai Trivedi, Probability and Statistics with Reliability, Queuing and Computer Science Applications, Prentice Hall PTR, Upper Saddle River, NJ, 1982
• 66: Kishor S. Trivedi, Probability and statistics with reliability, queuing and computer science applications, John Wiley and Sons Ltd., Chichester, UK, 2001
• 67: US Department of Defense. Electronic Reliability Design Handbook, 1998. URL http://www.barringer1.com/mil_files/MIL-HDBK-338.pdf.