A View of 20th and 21st Century Software Engineering
Monday, July 17, 2006
6:00 P.M. - 8:00 P.M.Join your colleagues at the next meeting of The San Diego Chapter of the Association for Computing Machinery (ACM), featuring Barry Boehm, creator and director of the Center for Software Engineering at USC. This meeting is a joint meeting between the San Diego ACM and San Diego SPIN, the Software Process Improvement Network, and the San Diego Chapter of the Society for Software Quality.
There will be light snacks courtesy of BAE Systems ... reserve your seat (see below) before it's too late!
This meeting will be held on Monday, July 17, 2006 at BAE SYSTEMS, 16250 Technology Dr., San Diego, in Rancho Bernardo , from 6:00 pm to 8:00 pm. The local contact there is Debra Roy, 858-592-5821. We will be in room 16250 that Debra has arranged. There will be light snacks and beverages provided courtesy of BAE SYSTEMS. This meeting is FREE.
The meeting is open to the public. For more information, call (858) 452-8701. Please forward this on to anyone whom you think may be interested. Please print and post either the attached color or black and white posters in a convenient place for your colleagues to observe.
(We are also pleased to acknowledge the generous support of Sun Microsystems, BAE Systems, Master Systems, That Technical Bookstore, O'Reilly Books, and UCSD Extension.)
Bring your colleagues and friends to this don't - miss event -- we hope to see you there!
Seat Reservations
As we are guests at SPIN's meeting, please use their website to register for this meeting.
RSVP is required for this meeting. Please contact Debra Roy at least one week prior to the meeting if you are not a US citizen so that your visit can be cleared. Thank you in advance.
Abstract:
George Santayana's statement, "Those who cannot remember the past are condemned to repeat it," is only half true. The past also includes successful histories. If you haven't been made aware of them, you're often condemned not to repeat their successes.
In a rapidly expanding field such as software engineering, this happens a lot. Extensive studies of many software projects such as the Standish Reports offer convincing evidence that many projects fail to repeat past successes. This presentation tries to identify at least some of the major past software experiences that were well worth repeating, and some that were not. It also tries to identify underlying phenomena influencing the evolution of software engineering practices that have at least helped the presenter appreciate how our field has gotten to where it has been and where it is.
A counterpart Santayana-like statement about the past and future might say, "In an era of rapid change, those who repeat the past are condemned to a bleak future." (Think about the dinosaurs, and think carefully about software engineering maturity models that emphasize repeatability.)
The presentation also tries to identify some of the major sources of change that will affect software engineering practices in the next couple of decades, and identifies some strategies for assessing and adapting to these sources of change. It also makes some first steps towards distinguishing relatively timeless software engineering principles that are risky not to repeat, and conditions of change under which aging practices will become increasingly risky to repeat.
This presentation is based on Dr. Boehm's keynote address at the International Conference on Software Engineering, held in May in Shanghai, China.
Presenter Bio:
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. 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. He worked at TRW from 1973 to 1989, culminating as Chief Scientist of the Defense Systems Group, and at the Rand Corporation from 1959 to 1973, culminating as Head of the Information Sciences Department. He was a Programmer-Analyst at General Dynamics between 1955 and 1959. His current research interests include software process modeling, software requirements engineering, software architectures, software metrics and cost models, software engineering environments, and knowledge-based software engineering. 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 and two advanced software engineering environments: the TRW Software Productivity System and Quantum Leap Environment. He has served on the board of several scientific journals, including the IEEE Transactions on Software Engineering, IEEE Computer, IEEE Software, ACM Computing Reviews, Automated Software Engineering, Software Process, and Information and Software Technology. He has served as Chair of the AIAA Technical Committee on Computer Systems, Chair of the IEEE Technical Committee on Software Engineering, and as a member of the Governing Board of the IEEE Computer Society. He currently serves as Chair of the Air Force Scientific Advisory Board's Information Technology Panel, and Chair of the Board of Visitors for the CMU Software Engineering Institute. His honors and awards include Guest Lecturer of the USSR Academy of Sciences (1970), the AIAA Information Systems Award (1979), the J.D. Warnier Prize for Excellence in Information Sciences (1984), the ISPA Freiman Award for Parametric Analysis (1988), the NSIA Grace Murray Hopper Award (1989), the Office of the Secretary of Defense Award for Excellence (1992), the ASQC Lifetime Achievement Award (1994), and the ACM Distinguished Research Award in Software Engineering (1997). He is an AIAA Fellow, an ACM Fellow, an IEEE Fellow, and a member of the National Academy of Engineering.
Meeting Charge
This meeting is free.
RSVP Policy
We strongly encourage you to let us know if you plan to attend this meeting. We expect this meeting to be very well attended, and we may run out of space. In that case, attendees with RSVPs will be given admittance and seating preference. See RSVP policy for more details.