“Software Engineering Economics is an invaluable guide to determining software costs, applying the fundamental concepts of microeconomics to software engineering, and utilizing economic analysis in software engineering decision making.”

—  Barry Boehm

Barry W. Boehm (1981) Software engineering economics. Abstract.

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Software Engineering Economics is an invaluable guide to determining software costs, applying the fundamental concepts …" by Barry Boehm?
Barry Boehm photo
Barry Boehm 18
American software engineer 1935

Related quotes

Barry Boehm photo

“If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers.”

Barry Boehm (1935) American software engineer

Source: Software engineering economics. (1984), p. 4

Friedrich Bauer photo

“[Software engineering is the] establishment and use of sound engineering principles to obtain economically software that is reliable and works on real machines efficiently.”

Friedrich Bauer (1924–2015) German computer scientist

Bauer (1972) "Software Engineering", In: Information Processing. p. 71

Barry Boehm photo

“Throughout the software life cycle, there are many decision situations involving limited resources in which software engineering economics techniques provide useful assistance.”

Barry Boehm (1935) American software engineer

Source: Software engineering economics. (1984), p. 4

Bjarne Stroustrup photo

“Far too often, "software engineering" is neither engineering nor about software.”

Bjarne Stroustrup (1950) Danish computer scientist, creator of C++

Bjarne Stroustrup's FAQ: Did you really say that?, 2011-04-11 http://www.stroustrup.com/bs_faq.html#really-say-that,

Grady Booch photo

“The amateur software engineer is always in search of magic, some sensational method or tool whose application promises to render software development trivial. It is the mark of the professional software engineer to know that no such panacea exist.”

Grady Booch (1955) American software engineer

Grady Booch, ‎Robert A. Maksimchuk, ‎Michael W. Engle (2007) Object-Oriented Analysis and Design with Applications Chapter 6.

Edsger W. Dijkstra photo

“As economics is known as "The Miserable Science", software engineering should be known as "The Doomed Discipline", doomed because it cannot even approach its goal since its goal is self-contradictory. (…) Software engineering has accepted as its charter "How to program if you cannot.”

Edsger W. Dijkstra (1930–2002) Dutch computer scientist

Dijkstra (1988) " On the cruelty of really teaching computing science http://www.cs.utexas.edu/users/EWD/transcriptions/EWD10xx/EWD1036.html (EWD1036).
1980s

N. R. Narayana Murthy photo

“Students are the future of this country. Quality software engineers will carve the way ahead for becoming a software global giant.”

N. R. Narayana Murthy (1946) Indian businessman

Narayana Murthy shocks with 'Mera Bharat Mahaan' quote, indicates Infosys Ltd on hiring spree, 16k jobs on offer

“Software engineering concerns methods and techniques to develop large software systems. The engineering metaphor is used to emphasize a systematic approach to develop systems that satisfy organizational requirements and constraints.”

Hans van Vliet (1949) Dutch computer scientist

Source: Software Engineering: Principles and Practice, 2007, p. 2

Grady Booch photo

“The entire history of software engineering is that of the rise in levels of abstraction.”

Grady Booch (1955) American software engineer

Grady Booch in his talk "The Limits of Software."; Cited in: Gerry Boyd (2003) " Executable UML: Diagrams for the Future http://www.devx.com/enterprise/Article/10717." published at devx.com, February 5, 2003.
The Limits of Software

“In all engineering disciplines nowadays, software engineering excluded, there exists an established engineering process to develop a system, which is accompanied by a number of suited modeling description techniques. Software engineering, being a rather new field, has not as yet established any clear methodical guidance or a fully standardized modeling notation.”

Bernhard Rumpe (1967) German computer scientist

Source: Executable Modeling with UML. A vision or a Nightmare (2002), p. 697

Related topics