Acceptability-oriented computing

ABSTRACT

We discuss a new approach to the construction of software systems. Instead of attempting to build a system that is as free of errors as possible, the designer instead identifies key properties that the execution must satisfy to be acceptable to its users. Together, these properties define the acceptability envelope of the system: the region that it must stay within to remain acceptable. The developer then augments the system with a layered set of components, each of which enforces one of the acceptability properties. The potential advantages of this approach include more flexible, resilient systems that recover from errors and behave acceptably across a wide range of operating environments, an appropriately prioritized investment of engineering resources, and the ability to productively incorporate unreliable components into the final software system.

REFERENCES

• 1: Alfred V. Aho , Ravi Sethi , Jeffrey D. Ullman, Compilers: principles, techniques, and tools, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1986
• 2: Albert D. Alexandrov , Maximilian Ibel , Klaus E. Schauser , Chris J. Scheiman, UFO: a personal global file system based on user-level extensions to the operating system, ACM Transactions on Computer Systems (TOCS), v.16 n.3, p.207-233, Aug. 1998 [doi>10.1145/290409.290410]
• 3: Susan S. Brilliant , John C. Knight , Nancy G. Leveson, Analysis of Faults in an N-Version Software Experiment, IEEE Transactions on Software Engineering, v.16 n.2, p.238-247, February 1990 [doi>10.1109/32.44387]
• 4: George Candea , Armando Fox, Recursive Restartability: Turning the Reboot Sledgehammer into a Scalpel, Proceedings of the Eighth Workshop on Hot Topics in Operating Systems, p.125, May 20-22, 2001
• 5: Stefano Ceri , Piero Fraternali , Stefano Paraboschi , Letizia Tanca, Automatic generation of production rules for integrity maintenance, ACM Transactions on Database Systems (TODS), v.19 n.3, p.367-422, Sept. 1994 [doi>10.1145/185827.185828]
• 6: Stefano Ceri , Jennifer Widom, Deriving production rules for constraint maintenance, Proceedings of the sixteenth international conference on Very large databases, p.566-577, September 1990, Brisbane, Australia
• 7: J. Darley and B. Latane. Bystander intervention in emergencies: Diffusion of responsibility. Journal of Personality and Social Psychology, pages 377--383, August 1968.
• 8: W. Edwards Deming. Out of the Crisis. MIT Press, 2000.
• 9: Brian Demsky , Martin Rinard, Role-based exploration of object-oriented programs, Proceedings of the 24th International Conference on Software Engineering, May 19-25, 2002, Orlando, Florida [doi>10.1145/581339.581379]
• 10: Brian Demsky , Martin Rinard, Automatic detection and repair of errors in data structures, Proceedings of the 18th annual ACM SIGPLAN conference on Object-oriented programing, systems, languages, and applications, October 26-30, 2003, Anaheim, California, USA
• 11: Michael D. Ernst , Adam Czeisler , William G. Griswold , David Notkin, Quickly detecting relevant program invariants, Proceedings of the 22nd international conference on Software engineering, p.449-458, June 04-11, 2000, Limerick, Ireland [doi>10.1145/337180.337240]
• 12: Jim Gray , Andreas Reuter, Transaction Processing: Concepts and Techniques, Morgan Kaufmann Publishers Inc., San Francisco, CA, 1992
• 13: G. Haugk, F.M. Lax, R.D. Royer, and J.R. Williams. The 5ESS(TM) switching system: Maintenance capabilities. AT&T Technical Journal, 64(6 part 2):1385--1416, July-August 1985.
• 14: Timothy L. Kay , James T. Kajiya, Ray tracing complex scenes, ACM SIGGRAPH Computer Graphics, v.20 n.4, p.269-278, Aug. 1986
• 15: G. Kiczales, J. Lamping, A. Mendhekar, C. Maeda, C. Lopes, J. Longtier, and J. Irwin. Aspect-oriented programming. In Proceedings of the 11th European Conference on Object-Oriented Programming, Jyvaskyla, Finland, June 1997.
• 16: James R. Larus , Eric Schnarr, EEL: machine-independent executable editing, Proceedings of the ACM SIGPLAN 1995 conference on Programming language design and implementation, p.291-300, June 18-21, 1995, La Jolla, California, United States
• 17: B. Latane and J. Darley. Group inhibition of bystander intervention in emergencies. Journal of Personality and Social Psychology, pages 215--221, October 1968.
• 18: Samiha Mourad , Dorothy Andrews, On the reliability of the IBM MVS/XA operating system, IEEE Transactions on Software Engineering, v.13 n.10, p.1135-1139, October 1, 1987 [doi>10.1109/TSE.1987.232855]
• 19: P. Plauger. Chocolate. Embedded Systems Programming, 7(3):81--84, March 1994.
• 20: M. Rinard and D. Marinov. Credible compilation with pointers. In Proceedings of the Workshop on Run-Time Result Verification, Trento, Italy, July 1999.
• 21: Martin Rinard. Credible compilation. Technical Report MIT-LCS-TR-776, Laboratory for Computer Science, Massachusetts Institute of Technology, March 1999.
• 22: S. D. Urban , L. M. L. Delcambre, Constraint Analysis: A Design Process for Specifying Operations on Objects, IEEE Transactions on Knowledge and Data Engineering, v.2 n.4, p.391-400, December 1990 [doi>10.1109/69.63251]
• 23: James Womack, Daniel Jones, and Daniel Roos. The Machine that Changed the World: the Story of Lean Production. Harper Collins, 1991.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.3 Coding Tools and Techniques
      D.2.4 Software/Program Verification
      D.2.5 Testing and Debugging
  D.3 PROGRAMMING LANGUAGES
      D.3.3 Language Constructs and Features

General Terms:
Design, Languages, Reliability, Security

Keywords:
acceptability properties, monitoring, rectification, repair