Barry Boehm
Sign in to saveAlso known as Barry W. Boehm, Barry William Boehm
American software engineer (1935–2022)
Person · Open Library
- Born
- 1935
- Died
- 2022
- Works
- 36
Top works
- Foundations of empirical software engineering
- Unifying the Software Process Spectrum
- Balancing Agility and Discipline
- Disciplinary Convergence in Systems Engineering Research
- Incremental Commitment Spiral Model
via Open Library + Wikidata
Music · MusicBrainz
- Type
- Person
- Gender
- Male
- Origin
- Austria
- Active from
- 1894-08-28
- Active to
- 1981-08-14
austrian conductorclassicalclassical periodconcertoconductoropera
Discography
- Die Zauberflöte1955
- Sinfonie Nr. 7 A-Dur / Coriolan-Ouvertüre1959
- Die Zauberflöte1960
- Sinfonie nr. 3 Es-Dur op. 55 (Eroica)1962
- Die Zauberflöte1964
- Kindertotenlieder / 4 Rückert-Lieder1964
- Symphonien Nr. 5 & Nr. 8 (Unvollendete)1966
- Piano Concerto No. 21967
- Le nozze di Figaro1968
- Sinfonie g-moll KV 550 / Sinfonie Es-dur KV 5431968
via MusicBrainz · CC0
Recent publications · Crossref
5 total works indexed
- One-step inactivation of chromosomal genes in
<i>Escherichia coli</i>
K-12 using PCR products
· 2000 · cited 14,093x
- <scp>CHARMM</scp>: A program for macromolecular energy, minimization, and dynamics calculations
· 1983 · cited 13,595x
- Click Chemistry: Diverse Chemical Function from a Few Good Reactions
· 2001 · cited 11,540x
- The Sequence of the Human Genome
· 2001 · cited 10,201x
- Seventh Report of the Joint National Committee on Prevention, Detection, Evaluation, and Treatment of High Blood Pressure
· 2003 · cited 10,088x
via Crossref · CC0
Quotes
- “Poor management can increase software costs more rapidly than any other factor. Particularly on large projects, each of the following mismanagement actions has often been responsible for doubling software development costs.”
- “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.”
- “If a project has not achieved a system architecture, including its rationale, the project should not proceed to full-scale system development. Specifying the architecture as a deliverable enables its use throughout the development and maintenance process.”
- “What we see in both software development and military operations is a tendency for the pendulum to swing back and forth between extremes. Yet in most cases, we need a balance between armor and discipline and between mobility and agility. Actually, though, I would say that the leaders in both the agile and plan-driven camps occupy various places in the responsible middle. It’s only the over-enthusiastic followers who overinterpret “discipline” and “agility” to unhealthy degrees.”
- “Agile development methodologies promise higher customer satisfaction, lower defect rates, faster development times and a solution to rapidly changing requirements. Plan-driven approaches promise predictability, stability, and high assurance. However, both approaches have shortcomings that, if left unaddressed, can lead to project failure. The challenge is to balance the two approaches to take advantage of their strengths and compensate for their weaknesses.”
- “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.”
via Wikiquote · CC BY-SA