FM 2006

August 21 - 27, 2006
McMaster University
Hamilton ON, Canada

Submission Dates

Technical Papers, Workshops and Tutorials

Friday February 24, 2006

Posters and Tools, Doctoral Symposium

Friday May 26, 2006


Notification Dates

Technical Papers

Friday April 28, 2006

Workshops and Tutorials

Friday March 10, 2006

Doctoral Symposium

Wednesday June 14, 2006

Posters and Research Tools

Monday June 12, 2006

Contact Information

General Inquiries

General Chair

Emil Sekerinski

Program Chairs

Jayadev Misra,
Tobias Nipkow

Workshops Chair

Tom Maibaum

Tutorials Chair

Jin Song Dong

Tools & Poster Chair

Marsha Chechik

Industry Day Chairs

Volkmar Lotz,
Asuman Suenbuel

Doctoral Symposium Chair

Ana Cavalcanti

Augusto Sampaio

Jim Woodcock

Sponsorship Chair

Jürgen Dingel

T8 The Use of Precise Documentation in Software Development
David Lorge Parnas
University of Limerick, Ireland
McMaster University, Canada
August 22, 2006
9:00-12:30, 2:00-5:30, 1/2hr break at 10:30 and 3:30
ITB 201


Documentation that is well-structured, complete and precise can speed up the development of software and increase both its trustworthiness and maintainability. Poor documentation is simply a waste of time. It may satisfy some contractual requirements, but unless it is easier to get information from the documentation than from the code it will not be used. If it is not accurate and complete it will cost more time than it saves. This tutorial describes an approach to documentation that results in highly structured documentation that the programmers consider valuable. The same documents assist in review, inspection, testing, preparing user material, and maintenance.


Participants will learn how to produce more useful documentation and how to use that documentation better.


Participants should be experienced software developers who are familiar with basic logic. They need not know special logics or "formal methods".

Biography of Tutor:

Professor David Lorge Parnas (IEEE/ACM Fellow) has been studying and publishing ideas on software development for more than 30 years. He has worked in both industry and academia, using his time in industry to understand "the real problems" and his time in academia to find fundamental solutions.