Lecture log
These notes are intended to record very briefly what I think happened at each
meeting -- in general, I expect to reflect what happened in the meeting in
the lecture notes, which is why I plan to give out lecture notes after the
lecture to which they belong.
Covered material of Note 1.
was replaced by playing with Rose
Covered material of Note 2.
Covered material of Note 3: beginning of use cases. You did the example on
the CS4 administration system.
Covered material of Note 4: end of use cases, beginning of discussion of
class diagrams.
Covered material of Note 5: generalisation and aggregation in class
diagrams. You did the exercise at the end of the notes: we'll discuss it
briefly next time.
Covered material of Note 6: semi-systematic ways of identifying objects and
classes, and CRC cards. You did an exercise with these, to be discussed
next time.
Covered material of Note 7: interaction diagrams. Talked briefly about
dependency structures, promising to talk next time about design patterns
which (among other things) document tried and tested techniques for
avoiding horrible dependency structures in some commonly arising cases.
Covered most of the material of Note 8: design patterns.
Finished design patterns, and covered the material of Note 9: statecharts
and activity diagrams.
Saw off UML, covering the material of Note 10.
You discussed what was meant by quality to a variety of different
organisations. I handed out two articles, What is a High Quality Software
System and How to Avoid Software Quality, see home page.
We talked about testing: see Note 11.
Social structures that affect quality: management, teams, leadership,
organisations. Notes 12.
Procedural structures that affect quality: planning, bidding, estimation,
tracking, metrics, quality assurance. Notes 13.
guest lecture by Dr Ian Redfern of Logica UK.
Reuse. Notes 14
