Skip to main content
Top

2011 | OriginalPaper | Chapter

18. The Roles of Software in Society

Author : Derek Partridge

Published in: The Seductive Computer

Publisher: Springer London

Activate our intelligent search to find suitable subject content or patents.

search-config
loading …

Abstract

IT systems have a life-cycle in which maintenance is the dominant activity. Maintaining (i.e. extending and debugging) an IT system that you did not develop exacerbates all of the IT-system problems, and is the major programming effort. At a certain point in IT-system complexity, further debugging is a self-defeating exercise. We all live within a mesh of IT systems: some offer conveniences that we can either accept or reject, others do not give us a choice. The outputs of an IT system may be viewed as a useful guide to be accepted cautiously, or as the ultimate truth to be accepted blindly; the reality of all IT systems will lie somewhere in between these two extremes. IT systems are not extended or amended lightly, because change is so dangerous; hence, we tend to ‘work around’ their failings. Many IT systems improve our lives. Some IT systems have negative impacts, all the way from minor aggravation to life threatening. There are no easy answers (as far as we know). So for IT systems in safety-critical roles where failures have the potential to cause deaths and/or disasters, the best advice is too lessen the criticality of their roles and to limit expectation of what they can deliver.

Dont have a licence yet? Then find out more about our products and how to get one now:

Springer Professional "Wirtschaft+Technik"

Online-Abonnement

Mit Springer Professional "Wirtschaft+Technik" erhalten Sie Zugriff auf:

  • über 102.000 Bücher
  • über 537 Zeitschriften

aus folgenden Fachgebieten:

  • Automobil + Motoren
  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Elektrotechnik + Elektronik
  • Energie + Nachhaltigkeit
  • Finance + Banking
  • Management + Führung
  • Marketing + Vertrieb
  • Maschinenbau + Werkstoffe
  • Versicherung + Risiko

Jetzt Wissensvorsprung sichern!

Springer Professional "Technik"

Online-Abonnement

Mit Springer Professional "Technik" erhalten Sie Zugriff auf:

  • über 67.000 Bücher
  • über 390 Zeitschriften

aus folgenden Fachgebieten:

  • Automobil + Motoren
  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Elektrotechnik + Elektronik
  • Energie + Nachhaltigkeit
  • Maschinenbau + Werkstoffe




 

Jetzt Wissensvorsprung sichern!

Springer Professional "Wirtschaft"

Online-Abonnement

Mit Springer Professional "Wirtschaft" erhalten Sie Zugriff auf:

  • über 67.000 Bücher
  • über 340 Zeitschriften

aus folgenden Fachgebieten:

  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Finance + Banking
  • Management + Führung
  • Marketing + Vertrieb
  • Versicherung + Risiko




Jetzt Wissensvorsprung sichern!

Footnotes
1
Even this is to overstate the scope of proof in its technical sense: theorems are the certificates of mathematical proof, and yet many a theorem has been, and always will be, shown to be invalid after years of acceptance as a proof. So even this strongest manifestation of the notion of proof is ultimately a matter of faith: faith that a proof is valid because many other mathematicians accept that it is; or faith that every step in the theorem is a valid one as claimed.
 
2
See next note for full details of article which states that the basic message in “The widely used document of the Radio Technical Commission for Aeronautics, RTCA/DO-178A … is that designers must take a disciplined approach to software … That is, the best assurance of reliability is to verify that utmost care was used in the design” (p. 66).
 
3
Bev Littlewood and Lorenzo Strigini, leading researchers in the quest for formal assessment of IT-system reliability at London’s City University, published these views in their article “The Risks of Software” in Scientific American (vol. 267, no. 5, pp. 62–75, November 1992). They present a comprehensive, yet accessible, guide to the challenge and the problems of quantifying software-failure risks. Their answer for safety-critical IT systems is to make the role of such software “not too critical” or “to accept the current limitations of software and live with more modest overall system safety.”
 
4
Another quotation provided by David Lubar on page 48 of his compendium It’s Not a Bug: It’s a Feature (Addison–Wesley, 1995). He is quoting “Paul Bonner, reviewing Windows 4.0, or Chicago, or Windows 95, or whatever it’s called this week, 1994.”
 
5
This phenomenon, as we have seen earlier, appears to be a universal of programming; recall the Second Law of Program Evolution:
The entropy of a system increases with time unless specific work is executed in order to maintain or reduce it.
which can be paraphrased as:
IT systems become more chaotic every time they are changed unless the changes are introduced with great care and wisdom.
Given that it is an empirical fact that IT systems always become less maintainable over time, we must assume that either this law is too optimistic, or there is never enough care and wisdom put into the changes. Most likely, Murphy wasn’t the only law-making optimist. Our knowledge of the fragile technology and the excessive demands for detailed understanding occasioned by a large IT system, both further exacerbated in the maintenance context (rather than initial development), give weight to the view that this Law needs toughening.
The source is M.M. Lehman and L.A. Belady in a book entitled Program Evolution (Academic Press, 1985). This information is clearly not new, but perhaps still the best we have. The difficulty of collecting empirical evidence about IT systems is that the IT systems themselves have to be realistically large ones, and the number surveyed must also be large enough to give the results some validity. In depth analysis of the long-term behaviour of a large number of large IT systems is a very demanding exercise.
 
6
Once more, the quotation is from an entertaining series of essays on large-scale software development, entitled The Mythical Man-Month (Addison–Wesley, 1975, with valuable additions, 1995) by F.P. Brooks, the project manager working for IBM on one of the largest software systems constructed at the time.
 
Metadata
Title
The Roles of Software in Society
Author
Derek Partridge
Copyright Year
2011
Publisher
Springer London
DOI
https://doi.org/10.1007/978-1-84996-498-2_18

Premium Partner