Abstract
In the problem frames approach to software development as its name indicates analysis of theproblem precedes construction of thesolution. The problem analysis rests on certain ideas of structure and simplicity, including a general recommendation that composition should be postponed until the parts to be composed are well understood in their preliminary isolated forms. These ideas are discussed in the light of Michael Polanyi’s notion of theoperational principle of a machine orcontrivance, and his account of the relationship between scientific knowledge and understanding of machines. Criteria are suggested for simplicity in problem decomposition. The outline structure of the associated development approach is sketched, and the relationship between formal development methods and problem structuring is clarified.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
In the usual presentation of the problem frames approach [6] the software and computer are regarded as together constituting themachine. Here we avoid this term because Polanyi uses it for what we consider to be the whole system, comprising both the software and the problem world.
- 2.
There is an exception to this statement, explained in the following section. In some cases a local variable of the software ofP is identified by whichS1 andS2 will communicate.
- 3.
An example of this transformation is theprogram inversion scheme described in [5].
References
Descartes, R.: Discourse on the Method of Rightly Conducting the Reason, and Seeking Truth in the Sciences. Leyden, 1637. Available as Project Gutenberg Etext #59 at http://www.gutenberg.org/etext/59 [accessed April 2009].
Harel, D.: Statecharts in the making: a personal account. Commun. ACM52(3), 6775 (2009).
Hoare, C.A.R., Jones., C.B.: Essays in Computing Science. Prentice Hall International, Hemel Hempstead, Herts, UK (1989).
Hoare, C.A.R.: The emperor’s old clothes. Commun. ACM24(2), 75–83 (1981). Reprinted in [3].
Jackson, M.A.: Principles of Program Design. Academic, Orlando, FL, USA (1975).
Jackson, M.: Problem Frames: Analyzing and Structuring Software Development Problems. Addison-Wesley Longman Publishing, Boston, MA, USA (2001).
Jackson, M., Zave, P.: Deriving specifications from requirements: An example. In ICSE ’95: Proceedings of the 17th International Conference on Software Engineering, pp. 1524 ACM, New York, NY, USA (1995).
Leibnitz, G.W.: In: Gerhardt, C.I. (ed.), Philosophical Writings (Die philosophischen Schriften) Volume IV, p. 331. 18571890.
Polanyi, M.: Personal Knowledge: Towards a Post-Critical Philosophy. Routledge and Kegan Paul, London (1958). Reprinted by University of Chicago & Press (1974).
Vincenti, W.G.: What Engineers Know and How They Know It: Analytical Studies from Aeronautical History. The Johns Hopkins University Press, Baltimore, MD (1993). Paperback edition.
Acknowledgements
This paper has been much improved by Daniel Jackson’s comments and suggestions.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer London
About this chapter
Cite this chapter
Jackson, M. (2010). The Operational Principle and Problem Frames. In: Roscoe, A., Jones, C., Wood, K. (eds) Reflections on the Work of C.A.R. Hoare. Springer, London. https://doi.org/10.1007/978-1-84882-912-1_7
Download citation
DOI: https://doi.org/10.1007/978-1-84882-912-1_7
Published:
Publisher Name: Springer, London
Print ISBN: 978-1-84882-911-4
Online ISBN: 978-1-84882-912-1
eBook Packages: Computer ScienceComputer Science (R0)