Architects draw detailed blueprints before a brick is laid or a nail is hammered. Programmers and software engineers seldom do. A blueprint for software is called a specification. The need for extremely rigorous specifications before coding complex or critical systems should be obvious - especially for concurrent and distributed systems. This talk explains why some sort of specification should be written for any software.
This lecture was held on Tuesday 13 May 2014.
To receive information on the next lecture, email firstname.lastname@example.org