University of Hawaii, USA
Dr. Rick Kazman is a Professor at the University of Hawaii and a Visiting Scientist at the Software Engineering Institute. His primary research interests are software architecture, design and analysis tools, software visualization, and software engineering economics. He is the author of over 100 papers, and co-author of several books, including "Software Architecture in Practice", and "Evaluating Software Architectures: Methods and Case Studies". Kazman was one of the creators of the SAAM (Software Architecture Analysis Method) and the ATAM (Architecture Tradeoff Analysis Metohd). Dr. Kazman received B.A. and M.Math degrees from the University of Waterloo, a M.A. from York University, and a Ph.D. from Carnegie Mellon University.
As a long-time researcher and educator in software engineering, I take great pride in being associated with this dynamic and exciting field. Software is a fascinating profession because your imagination is, in principle, your only limiting factor--if you can dream it, you can build it. That's the principle. The reality, as we all know, if quite different. One of my long-term goals is to bring the reality closer to the dream. And this can only be done by making a true engineering profession of software.
To me, there are four areas that need to be pursued to make this happen:
1) underlying science. A sufficient body of theoretically sound underlying science is the foundation for any engineering discipline. I believe that computer science provides a portion of this necessary background, but software engineering needs to add to this foundation a firm basis in empirical study. Every engineering discipline must be ground in empirical results that "road-test" the theory.
2) education and training. Software engineering needs to be taught as a distinct discpline, and not as an afterthought to a computer science education. And, given that the field is quite dynamic, we need to focus on continuing education and professional training, as well as our traditional focus on university-based education. And we need to encourage underlying research in education, so that we can continually improve in effectiveness.
3) creation of professional handbooks. Every mature engineering discipline has a set of handbooks that catalog the basic principles and properties, and known contruction and analysis techniques of the field. This allows an engineering of average abilities to create high-quality products, predictably and rigorously. Software engineering desperately needs just such a set of handbooks.
4) cross-disciplinary interaction. Software is everywhere in society, embedded in the fabric of our lives. As such, we need to work with many different trades and professions--from end users to business professionals to psychologists to industrial designers to graphic artists--to ensure that the software that we create is appropriate. Software it is not an end in and of itself.
I would like the IEEE to support and encourage research, publication, and practice in all four of the above areas. As part of the TCSE I will work to see that these objectives are pursued.
Finally, I have had consider experience with the practical side of the IEEE. I have served on the TCSE Executive Committee for the past 4 years. I was general chair of a recent IEEE Conference (WICSA 2009) and have assisted in the organization of several other conferences. This insight from the trenches is invaluable in making the TCSE better serve the needs of its members and constituents.