Category: 2. History
-
2000 to 2015: Lightweight methodologies[edit]
With the expanding demand for software in many smaller organizations, the need for inexpensive software solutions led to the growth of simpler, faster methodologies that developed running software, from requirements to deployment, quicker & easier. The use of rapid-prototyping evolved to entire lightweight methodologies, such as Extreme Programming (XP), which attempted to simplify many areas of software engineering,…
-
1990 to 1999: Prominence of the Internet[edit]
The rise of the Internet led to very rapid growth in the demand for international information display/e-mail systems on the World Wide Web. Programmers were required to handle illustrations, maps, photographs, and other images, plus simple animation, at a rate never before seen, with few well-known methods to optimize image display/storage (such as the use of thumbnail…
-
Software projects[edit]
Seemingly, every new technology and practice from the 1970s through the 1990s was trumpeted as a silver bullet to solve the software crisis. Tools, discipline, formal methods, process, and professionalism were touted as silver bullets:[citation needed] In 1986, Fred Brooks published his No Silver Bullet article, arguing that no individual technology or practice would ever make a 10-fold improvement in productivity within…
-
1985 to 1989: “No Silver Bullet”[edit]
For decades, solving the software crisis was paramount to researchers and companies producing software tools. The cost of owning and maintaining software in the 1980s was twice as expensive as developing the software.[citation needed]
-
1965 to 1985: The software crisis[edit]
Software engineering was spurred by the so-called software crisis of the 1960s, 1970s, and 1980s, which identified many of the problems of software development. Many projects ran over budget and schedule. Some projects caused property damage. A few projects caused loss of life.[14] The software crisis was originally defined in terms of productivity, but evolved to emphasize quality. Some used…
-
1945 to 1965: The origins[edit]
Early usages for the term software engineering include a 1965 letter from ACM president Anthony Oettinger,[6][7] lectures by Douglas T. Ross at MIT in the 1950s.[8] Margaret H. Hamilton is the person who came up with the idea of naming the discipline, software engineering, as a way of giving it legitimacy during the development of the Apollo Guidance Computer.[9][10] I fought to bring the…