How to Engineer Software

Presented by Steve Tockey

Presentation Slides

Software can be engineered. Software should be engineered. But true engineering-in the sense of how it is practiced in civil engineering, chemical engineering, industrial engineering, etc.-of software requires more than just claiming "software engineer" as a job title. This presentation:

  • Defines what software engineering should really mean and shows why software needs to be developed this way

  • Presents the true nature of code-what lines of code actually mean-and draws out vital implications from that

  • Explains how the common difficulties experienced on mainstream software projects are avoided when this true engineering approach is applied

This presentation is based on a book of the same name.

Steve Tockey

Steve Tockey is the Principal Consultant at Construx Software. He has been employed in the software industry since 1977, and has worked as a programmer, analyst, designer, researcher, consultant, and adjunct professor. During his career, which has included stints at Lawrence Livermore National Laboratory, The Boeing Company, and Rockwell Collins, Inc., Steve has obtained an in-depth knowledge of software engineering practices, including project management, estimation, quality techniques, object-oriented development and distributed object computing. Steve has a Master's of Software Engineering from Seattle University as well as a Bachelor of Arts in Computer Science from the University of California, Berkeley. He is an IEEE Computer Society Certified Software Development Professional.

Steve is the author of Return on Software, a book designed to help software professionals maximize the return on their software investment.