“Keeping you up to date with everything software engineering!”

INTERVIEW: Alan Wassyng

Interviews | January 15, 2005 | 0 comments

The CUSEC 2005 academic keynote will be given today by Dr. Alan Wassyng, from the Department of Computing and Software at McMaster University Dr. Wassyng has experience in real-time, embedded and safety-critical systems, and worked with one of last year’s keynote speakers on the software shutdown system at the Darlington Nuclear Generating Station. I’d like to thank Dr. Wassyng for his time to answer our questions, and if you are at CUSEC I hope to see you at his talk at 11:15.

---

Mark H Pavlidis: Dr. Wassyng, could you give us an overview of your background and how you got into the Software Engineering field?

Alan Wassyng: I graduated (B.Sc. and B.Sc. Hons.) in Applied Math and specialised in numerical mathematics and mathematical modeling. My masters was an analysis of stereo turntable reproduction (math modeling and numerical methods). My Ph.D. was on the solution of large systems of linear algebraic equations, especially those that arise in the application of boundary element methods to problems in rock mechanics. Focusing on using the computer to solve practical problems got me involved in looking for better ways to develop the software. I also started a project (at University of Minnesota) supported by IBM to develop software and techniques for using PCs to improve engineering education. Some of these packages were developed to IBM standards (and were reviewed by IBM), and so I started to see, first-hand, many of the problems that face developers of large software applications. We eventually developed 30 applications to teach elements of civil engineering, operations research, transportation engineering, etc. Soon after the completion of that project I moved to Toronto and started a computer consulting business. Alan Wassyng Consulting Ltd was incorporated in January 1987, and I spent the next 15 years developing a variety of software solutions for companies in the GTA, advising clients on computer related technologies, installing and maintaining computer systems. Much of my effort during those years went into developing safety-critical software with Ontario Power Generation.

MHP: What is your current role and area of research at McMaster University? What is some of the research you are currently working on?

AW: Acting Director of SQRL. SQRL’s mandate is to develop methods that enable us to produce high quality software. SQRL is also involved in application of these methods, development of related tools, technology transfer. An overriding interest is to maintain an industry focus. My research is mainly in hard real-time and embedded systems. I am particularly concerned with timing issues - their specification in requirements, their feasibility, and our ability to verify and test conformance to those requirements.

MHP: You have worked with Ontario Power Generation (previously Ontario Hydro) on highly safety critical projects. What do you see as some of the most important discoveries/innovations that came out of this work?

AW: The power of integrated methods and tools. Proof that industrial safety-critical projects can be undertaken. Technology transfer of academic theories into practical methodologies.

MHP: There is currently some disparity between the Software Engineering methods used in practice today, and Software Engineering methods developed in academia. How do you see this “methods gap” closing, and how long do you think it will take?

AW: Evangelists and newly graduated software engineers can help to close the gap. I think it will still take time, and it may even be delayed until there is a(nother) significant software failure that results in either massive financial hardship, or in loss of life.

MHP: As the Software Engineering profession matures, what types of changes do you think the industry will see?

AW: Software professionals taking responsibility for their advice and products. More reliable and more secure systems. Maybe even more efficient/predictable software development. Hopefully a few comprehensive development/maintenance methodologies together with good tool support.

MHP: What books should be on every Software Engineer’s shelf?

AW: I like the list(s) publicized by Steve McConnell (I also like his books). Parnas’s collected papers would also be good, although I think someone needs to now take those papers and produce a book for practising software engineers based on those papers (plus…).

MHP: Many in the software industry catch the entrepreneurial bug because of the low barriers to entry. What advice would you give those looking to start their own software business?

AW: Don’t get into it only because you think you can create the next Google etc. If you look at the successes over the years, they almost all come from people already in the field. They knew enough to have a great idea, know it was a great idea, and have some knowledge about how to develop it. There are two ways to do this: i) Join an existing company first and get experience and contacts in the industry (and capital); ii) Have an idea and sink all your efforts into developing and promoting the idea (product or service). If you are starting your own company, be prepared for a very slow start - it typically takes about 2 years to start producing non-neglible income, and that’s for the companies that succeed. Doing something on your own is tough. You have to convince everyone that you can deliver - and there’s only one of you. Most important - don’t do it if you don’t really believe in it AND really enjoy what you are doing.

MHP: What are some of your non-computing interests?

AW: Photography (but that is now merging with computing). Listening to classical music. Reading (non-technical) mysteries, historical novels. Love golf - but it does not love me back.

MHP: Could you give us a sneak peak about what you will be talking about in your keynote at CUSEC 2005?

AW: The talk is based on the experience of developing safety-critical software over a thirteen-year period. It focuses on and integrated approach to software development, and emphasises engineering discipline. It includes discussion on the dynamics of teamwork, and briefly looks forward to what will be expected from the current generation of graduating software engineers and computer scientists.

Related Links:

• CUSEC 2005
• Dr. Alan Wassyng
• McMaster University
• Darlington Nuclear Generating Station

Help Support Us By Visiting Our Sponsor

10% of our revenue from these ads go towards scholarships!

Comments

Post Your Comments

Comments:

Name:

Email Address:
(note: not displayed)

URL:
(note: displayed with comment)