Looking a bit further - Chapter 3 of: http://sdmeta.gforge.inria.fr/FreeBooks/STandOO/Smalltalk-and-OO.pdf <http://sdmeta.gforge.inria.fr/FreeBooks/STandOO/Smalltalk-and-OO.pdf> (Smalltalk and Object Orientation - Hunt) gets me a bit closer, but still thinking I’ve seen better somewhere.
Tim > On 26 Mar 2019, at 09:16, Tim Mackinnon <tim@testit.works> wrote: > > Has anyone else got any thoughts? I checked out the Larman book - but it > seems very process heavy (probably excellent for a full blown course), while > I’m looking for something a bit lighter weight to guide students on the right > way of thinking/approaching the little problems in Exercism. > > Wasn’t there something that encouraged you to underline the nouns and circle > the verbs and then start to identify objects and responsibilities? Its that > kind of thing I am starting to see as the weak point in people approaching > problems. > > Tim > >> On 24 Mar 2019, at 22:47, Christopher Fuhrman <christopher.fuhr...@gmail.com >> <mailto:christopher.fuhr...@gmail.com>> wrote: >> >> On Sun, 24 Mar 2019 at 21:26, Tim Mackinnon <tim@testit.works >> <mailto:tim@testit.works>> wrote: >> Any good references come to mind? As I’ll build up a list that I can point >> people to, that hopefully puts them in a better place to solve these more >> interesting and hopefully rewarding problems. >> >> Since 2003 in one of my courses I've used Craig Larman's Applying UML and >> Patterns because it has an analysis approach (getting from a semi-complex >> problem to a working OO solution in iterations, with UML if you want). It's >> using the Point Of Sale (cash register) problem which is complex yet >> familiar enough for most people to grasp (no pun intended, GRASP are the >> patterns he pushes as underlying responsibility-driven principles). >> >> Otherwise, Cay Horstmann's 3rd edition of OO Design and Patterns (Java, but >> applies to any OO language) should be out soon (I provided feedback on a >> draft copy last year). It has some good coverage of OO qualities and also >> uses a realistic problem (Graphics Editing framework, Violet) as the basis >> of lots of examples. >
