Today I have read about few persons who dedicated their lives to develop and work on Software Engineering topics.
This is why I decided to dedicated this post to Barry Boehm, professor of Software Engineering at U.S.C (University of Soutern California).
information of Barry Bohen retrieved from: http://csse.usc.edu/csse/about/people/faculties/BarryBoehm.html
TRW Professor of Software Engineering, Computer Science Department
Director Emeritus, USC Center for Systems and Software Engineering.
Phone: (213) 740-8163
FAX: (213) 740-4927
Barry Boehm received his B.A. degree from Harvard in 1957, and his M.S. and Ph.D. degrees from UCLA in 1961 and 1964, all in Mathematics. He also received an honorary Sc.D. in Computer Science from the U. of Massachusetts in 2000.
Between 1989 and 1992, he served within the U.S. Department of Defense (DoD) as Director of the DARPA Information Science and Technology Office, and as Director of the DDR&E Software and Computer Technology Office.
His current research interests focus on value-based software engineering, including a method for integrating a software system’s process models, product models, property models, and success models called Model-Based (System) Architecting and Software Engineering (MBASE).
His contributions to the field include the Constructive Cost Model (COCOMO®), the Spiral Model of the software process, the Theory W (win-win) approach to software management and requirements determination, the foundations for the areas of software risk management and software quality factor analysis, and two advanced software engineering environments: the TRW Software Productivity System and Quantum Leap Environment.
1. ROCKET: Rand’s Omnibus Calculator of the Kinematics of Earth Trajectories, Prentice Hall, 1964.
2. Planning Community Information Utilities, co-edited with H. Sackman, AFIPS Press, 1972.
3. Characteristics of Software Quality, North Holland, with J.R. Brown, H. Kaspar, M. Lipow, G. McLeod, and M. Merritt, 1978.
4. Software Engineering Economics, Prentice Hall, 1981.
5. Software Risk Management, IEEE Computer Society Press, 1989.
6. Ada and Beyond: Software Policies for the Department of Defense (study chair), National Academy Press, 1996.
7. Software Cost Estimation with COCOMO® II, Prentice Hall, with C. Abts, A.W. Brown, S. Chulani, B.K. Clark, E. Horowitz, R. Madachy, D. Reifer, and B. Steece, 2000
8. Balancing Agility and Discipline: A Guide for the Perplexed, with R. Turner, Addison Wesley, 2004
This is an example why Software Engineering is an Art, A Science, and Engineering at the same time, not only development of code and that´s it.
The main thing is ti develop algorithms and techniques that makes the code able to anyone who want lo learn about to process. And one key word is that PROCESS.
For me specially, things get easier when you know how to traduce your code/algorithm/technique into a general and transferable knowledge. Thats what Science do.
Please take a special view of the algorithms mentioned Above, If you want to read/learn more visit: