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

—  Barry Boehm

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

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 "Throughout the software life cycle, there are many decision situations involving limited resources in which software en…" by Barry Boehm?
Barry Boehm photo
Barry Boehm 18
American software engineer 1935

Related quotes

Barry Boehm photo

“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 (1935) American software engineer

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

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

“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

Barry Boehm photo

“The dictionary defines "economics" as "a social science concerned chiefly with description and analysis of the production, distribution, and consumption of goods and services." Here is another definition of economics which I think is more helpful in explaining how economics relates to software engineering.
Economics is the study of how people make decisions in resource-limited situations.
This definition of economics fits the major branches of classical economics very well.
Macroeconomics is the study of how people make decisions in resource-limited situations on a national or global scale. It deals with the effects of decisions that national leaders make on such issues as tax rates, interest rates, foreign and trade policy.
Microeconomics is the study of how people make decisions in resource-limited situations on a more personal scale. It deals with the decisions that individuals and organizations make on such issues such as how much insurance to buy, which word processor to buy, or what prices to charge for their products or services.”

Barry Boehm (1935) American software engineer

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

Barry Boehm photo

“Economic principles underlie the overall structure of the software lifecycle, and its primary refinements of prototyping, incremental development, and advancemanship. The primary economic driver of the life-cycle structure is the significantly increasing cost of making a software change or fixing a software problem, as a function of the phase in which the change or fix is made.”

Barry Boehm (1935) American software engineer

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

“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

“The term Model-Driven Engineering (MDE) is typically used to describe software development approaches in which abstract models of software systems are created and systematically transformed to concrete implementations…. Full realizations of the MDE vision may not be possible in the near to medium-term primarily because of the wicked problems involved. On the other hand, attempting to realize the vision will provide insights that can be used to significantly reduce the gap between evolving software complexity and the technologies used to manage complexity.”

Bernhard Rumpe (1967) German computer scientist

Source: Model-driven development of complex software: A research roadmap (2007), p. 37: Abstract

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.

Related topics