The IEEE Computer Society is the world’s largest professional organization devoted to computer science and the TCSE—Technical Council on Software Engineering—is the voice of software engineering within the IEEE and the Computer Society. As such, it is the duty and responsibility of the TCSE to advance awareness of software engineering, and to support conferences, workshops, education, training, and other professional activities that contribute to the growth and enrichment of software engineering academics and professional. This is your organization. It should serve you in terms of your professional growth, but it should also serve your business, your government, your financial environment, your health, your home and family, and your social networks.
I believe that these are very exciting times. Software is absolutely critical to the economic, environmental, physical, and social well-being of our world. As software engineers we have incredible opportunities, and enormous responsibilities to society. We can not take these opportunities and responsibilities lightly. Software is everywhere, and software engineering has moved out of the “back room” and is now a vibrant, multi-disciplinary, and rapidly expanding field. The TCSE is in the fortunate and frightening position of potentially having enormous influence. What we do, or what we do not do, really matters!
Thus I think that the TCSE, to remain relevant, must continue all of the important work that it has been doing: showing leadership in organizing conferences and workshops, in sponsoring publications that both advance research and aid practitioners in their everyday jobs, and in providing training opportunities, particularly e-learning. However, more than just continuing existing work, the TCSE must show leadership in all these areas—working with other professional societies, working with government, working with academia, working with non-profits, and working with industry organizations—to create the resources and opportunities that will educate and inspire software engineers in the future. One of my goals as chair of the TCSE will be to increase cooperation between academia and industry. Our field is, first and foremost, about improving the practice of software engineering and to do that practitioners and researchers must closely cooperate. Fostering this cooperation and collaboration will be my most important goal as chair of TCSE.
Rick Kazman, is Professor in the Department of Information Technology Management at the University of Hawaii and Research Scientist at the Software Engineering Institute of Carnegie Mellon University. His primary research interests are software architecture, design and analysis tools, software visualization, and software engineering economics. Kazman has created several highly influential methods and tools for architecture analysis, including the SAAM (Software Architecture Analysis Method), the ATAM (Architecture Tradeoff Analysis Method), the CBAM (Cost-Benefit Analysis Method) and the Dali and Titan tools. These methods and tools are regularly employed in major corporations world-wide. He is the author of over 150 peer-reviewed papers, and co-author of several highly influential and highly cited books, including Software Architecture in Practice, Evaluating Software Architectures: Methods and Case Studies, and Ultra-Large-Scale Systems: The Software Challenge of the Future. His research publications have garnered almost 16,000 citations (according to Google Scholar).
Kazman has been active in the Executive Committee since 2006. He has also been active in conference organization, having been a general chair and program chair for the WICSA (Working IEEE/IFIP Conference on Software Architecture) series of conferences, and a member of the WICSA steering committee. He has also been the Software Technology Track co-chair at HICSS (Hawaii International Conference on System Sciences) for over 10 years. In addition he has chaired, co-chaired, and been on the program committees of dozens of other academic conferences and workshops.
Kazman received a B.A. (English/Music) and M.Math (Computer Science) from the University of Waterloo, an M.A. (English) from York University, and a Ph.D. (Computational Linguistics) from Carnegie Mellon University. How he ever became a software engineering researcher is anybody’s guess. When not architecting or writing about architecture, Kazman may be found cycling, playing the piano, practicing Tae Kwon Do and Jiu Jitsu, or (more often) flying back and forth between Hawaii and Pittsburgh.