skip to main content
10.1145/2486046.2486048acmotherconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
Article

The challenges of emerging software eco-systems (keynote)

Published:18 May 2013Publication History

ABSTRACT

New opportunities for software-intensive system configurations are arriving on the market; these include cyber-physical, cyber-social, and cloud structures. Because of the convenience and cost-savings opportunities they offer, these capabilities and configurations will be adopted, most likely quickly and at large scale. Some of these configurations, however, have the potential to create (or already are creating) significant unintended problems and vulnerabilities. The author identifies a range of such unintended problems and vulnerabilities, and indicates the types of research and new insights that will be needed so as to allow society to obtain the benefits promised by these emerging opportunities.

References

  1. President’s information technology advisory committee, report to the president. http://www.nitrd.gov/pitac/report/, 1999.Google ScholarGoogle Scholar
  2. Controller area network. http://standards.sae.org/j2411_200002/, 2000.Google ScholarGoogle Scholar
  3. Intel to phase out controversial processor serial numbers. http://www.networkworld.com/news/2000/ 0428intelnumber.html, 2000.Google ScholarGoogle Scholar
  4. Processor serial number questions & answers. http://www.intel.com/support/processors/ pentiumiii/sb/cs-007579.htm, 2003.Google ScholarGoogle Scholar
  5. Boeing aircraft company: Statistical summary of commercial jet airplane accidents. http://www. boeing.com/news/techissues/pdf/statsum.pdf, 2011.Google ScholarGoogle Scholar
  6. F-35 program continues to struggle with software. http://spectrum.ieee.org/riskfactor/aerospace/ military/ f35-program-continues-to-struggle-with-software, 2012.Google ScholarGoogle Scholar
  7. Fun facts about the f-35 fighter. http://www.publicintegrity.org/2012/03/27/ 8510/fun-facts-about-f-35-fighter, 2012.Google ScholarGoogle Scholar
  8. K. Ashton. That “internet of things” thing. RFiD Journal, 22:97–114, 2009.Google ScholarGoogle Scholar
  9. E. V. Bernstam and T. R. Johnson. Why Health Information Technology Doesn’t Work. The Bridge, 2009.Google ScholarGoogle Scholar
  10. B. Boehm. Some future trends and implications for systems and software engineering processes. Systems Engineering, 9(1):1–19, 2006. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. B. Boehm and J. Lane. 21st century processes for acquiring 21st century software-intensive systems of systems. CrossTalk, 19(5):4–9, 2006.Google ScholarGoogle Scholar
  12. B. W. Boehm. A spiral model of software development and enhancement. Computer, 21(5):61–72, 1988. Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. B. W. Boehm and R. Ross. Theory-w software project management principles and examples. Software Engineering, IEEE Transactions on, 15(7):902–916, 1989. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. F. Brooks. The Design of Design: Essays from a Computer Scientist. Pearson Education, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. J. den Haan. 8 reasons why model-driven development is dangerous. Pobrano, 8(23):2011, 8.Google ScholarGoogle Scholar
  16. E. W. Dijkstra et al. On the cruelty of really teaching computing science. Communications of the ACM, 32(12):1398–1404, 1989.Google ScholarGoogle Scholar
  17. A. Y. Gagarinskii. Blue ribbon commission on america’s nuclear future. Atomic Energy, pages 1–3, 2012.Google ScholarGoogle ScholarCross RefCross Ref
  18. L. Gold and N. Siegel. Proteomics-based individualized health-care. To appear.Google ScholarGoogle Scholar
  19. C. Jones, O. Bonsignour, and J. Subramanyam. The Economics of Software Quality. Addison-Wesley Professional, 2011. Google ScholarGoogle ScholarDigital LibraryDigital Library
  20. A. Kay, D. Ingalls, Y. Ohshima, I. Piumarta, and A. Raab. Steps toward the reinvention of programming. Technical report, Technical report, National Science Foundation, 2006.Google ScholarGoogle Scholar
  21. L. Kleinrock. personal communication, 2009.Google ScholarGoogle Scholar
  22. J. G. Koomey. Worldwide electricity used in data centers. Environmental Research Letters, 3(3):034008, 2008.Google ScholarGoogle ScholarCross RefCross Ref
  23. K. Koscher, A. Czeskis, F. Roesner, S. Patel, T. Kohno, S. Checkoway, D. McCoy, B. Kantor, D. Anderson, H. Shacham, et al. Experimental security analysis of a modern automobile. In Security and Privacy (SP), 2010 IEEE Symposium on, pages 447–462. IEEE, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  24. P. Mell and T. Grance. The nist definition of cloud computing — recommendations of the national institute of standards and technology. special publication 800-145, national institute of standards and technology, gaithersburg, 2011. csrc. nist. gov/publications/nistpubs/800-145/SP800-145. pdf, 2011.Google ScholarGoogle Scholar
  25. D. Metlay and D. Sarewitz. Decision Strategies for Addressing Complex, “Messy” Problems. The Bridge, 2012.Google ScholarGoogle Scholar
  26. S. Nixon. Wicked problems — the challenge of our ag. TTI Conference, 2011.Google ScholarGoogle Scholar
  27. C. Perrow. The Next Catastrophe: Reducing Our Vulnerabilities to Natural, Industrial, and Terrorist Disasters (New in Paper). Princeton University Press, 2011.Google ScholarGoogle Scholar
  28. E. Rechtin. Systems Architecting: creating and building complex systems, volume 199. Prentice Hall Upper Saddle River, NJ, 1991.Google ScholarGoogle Scholar
  29. K. Scarfone, M. Souppaya, and M. Sexton. Guide to storage encryption technologies for end user devices. NIST Special Publication, 800:111, 2007.Google ScholarGoogle Scholar
  30. B. Schatz, A. Pretschner, F. Huber, and J. Philipps. Model-based development. Technical report, Technical Report TUM-I0204, Institut fur Informatik, Technische Universitat Munchen, 2002.Google ScholarGoogle Scholar
  31. N. G. Siegel. Organizing complex projects around critical skills, and the mitigation of risks arising from system dynamic behavior. PhD thesis, University of Southern California, 2011. Google ScholarGoogle ScholarDigital LibraryDigital Library
  32. J. Wetmore. The value of the social sciences for maximizing the public benefits of engineering. Bridge, 42(3):40–45, 2012.Google ScholarGoogle Scholar
  33. D. J. Wheeler. Understanding variation. SPC press Knoxville, TN, 1993.Google ScholarGoogle Scholar

Index Terms

  1. The challenges of emerging software eco-systems (keynote)

        Recommendations

        Comments

        Login options

        Check if you have access through your login credentials or your institution to get full access on this article.

        Sign in
        • Article Metrics

          • Downloads (Last 12 months)2
          • Downloads (Last 6 weeks)0

          Other Metrics

        PDF Format

        View or Download as a PDF file.

        PDF

        eReader

        View online with eReader.

        eReader