Jump to content

Unsolved problems in software engineering

Add links
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Ancheta Wis (talk | contribs) at 12:55, 30 January 2005 (a start). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

There is not a canonical list of unsolved problems in software engineering; however, there is

  • a list of antipatterns, which might be thought of as statements of poor practice, in contradistinction to the list of design patterns
  • the poorly predictable relationship of project duration to program functionality
  • the systematic detection of software defects
  • the current complexity of most programming languages, in general
  • the current complexity of most applications, to the extent that when programmers leave, companies fail, if those companies have no one else who understands what the programmers have done.
  • the arbitrariness of most software concepts, which is related to historical hardware and software implementation, lack of common standards worldwide, and economic pressures.

This article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Unsolved_problems_in_software_engineering&oldid=9793417"