Caveat
There has been broad agreement (within the students in this class, as well as others) that a common problem in software engineering is ill-defined requirements (and instable ones, too)
The approach Jackson uses to attack this question isn’t going to be easy for some of you to swallow
- It’s more focused on contract-style systems and less focused on desktop applications (he would strongly deny this, probably rightfully so)
- I believe the ideas are broadly applicable and worth seeing
- His results are intellectual, not technology results