Skip to main content

What Do Bridges and Software Tell Us about the Philosophy of Engineering?

  • Chapter
  • First Online:
Philosophy of Engineering, East and West

Part of the book series: Boston Studies in the Philosophy and History of Science ((BSPS,volume 330))

Abstract

One of the challenges in the emergent field of philosophy of engineering is to understand its position relative to philosophy of science. The call for a rigorous experimental methodology that has affected several fields in engineering should not make us equate good experimentation with traditional scientific experimentation. We have reason to believe that the primary role of artifacts and the human factor introduced by their designers affect the nature of experiments in engineering research and differentiate them from the traditional scientific method. We carry out our analysis with a specific focus on software engineering, a field in which the level of attention for scientific rigor in experiments has become very high in recent years.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Institutional subscriptions

References

  • Basili, Victor R. (1996). Editorial. Empirical Software Engineering, 1, 105–108.

    Article  Google Scholar 

  • Billah, K. Yusuf and Robert H. Scanlan. (1991). “Resonance, Tacoma Narrows Bridge Failure, and Undergraduate Physics Textbooks,” American Journal of Physics, 59(2), 118–124.

    Article  Google Scholar 

  • Brooks, Frederick P. (1996). “The Computer Scientist as Toolsmith II,” Communications of the ACM, 39(3), 61–68.

    Article  Google Scholar 

  • Bunge, Mario. (1966). “Technology as Applied Science,” Technology and Culture, 7(3), 329–347.

    Article  Google Scholar 

  • Cepeda Porras, Gerardo, and Yann-Gaël Guéhéneuc. (2010). “An Empirical Study On The Efficiency of Different Design Pattern Representations in UML Class Diagrams,” Empirical Software Engineering, 15, 493–522.

    Article  Google Scholar 

  • Dong, Jing, Sheng Yang, and Kang Zhang. (2007). “Visualizing Design Patterns in Their Applications and Compositions,” IEEE Transactions on Software Engineering, 33(7), 433–453.

    Article  Google Scholar 

  • Hacking, Ian. (1983). Representing and Intervening: Introductory Topics in the Philosophy of Natural Science. Cambridge, UK: Cambridge University Press.

    Google Scholar 

  • Hannay, Jo E., Dag I. K. Sjøberg, and Tore Dybå. (2007). “A Systematic Review of Theory Use in Software Engineering Experiments,” IEEE Transactions on Software Engineering, 33(2), 87–107.

    Google Scholar 

  • Franklin, Allan. (2012). “Experiment in Physics.” In Edward N. Zalta, ed., Stanford Encyclopedia of Philosophy. Retrieved from http://plato.stanford.edu/archives/win2012/entries/physics-experiment/.

  • Franssen, Maarten, Gert-Jan Lokhorst, and Ibo van de Poel. (2010). “Philosophy of Technology.” In Edward N. Zalta, ed., Stanford Encyclopedia of Philosophy. Retrieved from http://plato.stanford.edu/archives/spr2010/entries/technology/.

  • Gamma, Erich. (1997). “Applying Design Patterns in Java,” Java Report, 1(6), 47–53.

    Google Scholar 

  • Hartmanis, Juris. (1993). “Some Observations about the Nature of Computer Science,” Foundations of Software Technology and Theoretical Computer Science, 761, 1–12.

    Article  Google Scholar 

  • IEEE Technical Council on Software Engineering. (2002). Proceedings of the International Symposium on Empirical Software Engineering, (3–4 October), Nara, Japan.

    Google Scholar 

  • Juristo, Natalia and Ana M. Moreno. (2001). Basics of Software Engineering Experimentation. Boston: Kluwer Academic.

    Google Scholar 

  • McCarthy, Natasha. (2006). “Philosophy in the Making,” Ingenia, 26, 47–51.

    Google Scholar 

  • McKee, George. (1995). “Computer Science or Simply ‘Computics’? The Open Channel,” Computer, 28(12), 136.

    Google Scholar 

  • Morrison, Clayton and Richard Snodgrass. (2011). “Computer Science Can Use More Science,” Communications of the ACM, 54(6), 38–43.

    Article  Google Scholar 

  • Nielsen, Jakob and Thomas K. Landauer. (1993). “A Mathematical Model of the Finding of Usability Problems,” Proceedings of the INTERACT ’93 and CHI ’93 Conference on Human Factors in Computing Systems, ACM, 206–213.

    Google Scholar 

  • Schauer, Reinhard and Rudolf Keller. (1998). “Pattern Visualization for Software Comprehension,” Proceedings of the 6th International Workshop on Program Comprehension, IEEE Computer Society, 4–12.

    Google Scholar 

  • Skolimowski, Henryk. (1974). “The Structure of Thinking in Technology.” In Friedrich Rapp, ed., Contributions to a Philosophy of Technology (Dordrecht: D. Reidel), 72–85.

    Google Scholar 

  • Tedre, Matti. (2015). The Science of Computing: Shaping a Discipline. London: Chapman and Hall/CRC.

    Google Scholar 

  • Tichy, Walter. (1998). “Should Computer Scientists Experiment More?” IEEE Computer, 31(5), 32–40.

    Article  Google Scholar 

  • Westfall, Richard S. (1971). The Construction of Modern Science: Mechanisms and Mechanics. Cambridge, UK: Cambridge University Press.

    Google Scholar 

  • Zelkowitz, Marvin V. and Dolores Wallace. (1997). “Experimental Validation in Software Engineering,” Information and Software Technology, 39(11), 735–743.

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Viola SCHIAFFONATI .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2018 Springer International Publishing AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

SCHIAFFONATI, V., VERDICCHIO, M. (2018). What Do Bridges and Software Tell Us about the Philosophy of Engineering?. In: Mitcham, C., LI, B., Newberry, B., ZHANG, B. (eds) Philosophy of Engineering, East and West. Boston Studies in the Philosophy and History of Science, vol 330. Springer, Cham. https://doi.org/10.1007/978-3-319-62450-1_12

Download citation

Publish with us

Policies and ethics