Comments on: Fundamentals of Object-Oriented Design in UML: Book Review

By: Alexandre Gazola

Alexandre Gazola — Tue, 05 Jan 2010 23:08:05 +0000

“The idea is that while some information about our object will be viewable to other objects e.g. through attributes/getters, we can still hide the implementation of that information internally so that if we we want to change it in the future then we won’t have to change all its clients too.”

In their “Pickaxe” book, the pragmatic programmers describe that idea as “virtual attributes”, which are quite natural when programming in the Ruby idiom. The idea is that one cannot tell whether or not they are accessing a real attribute (eg.: car.direction = 45; in this case, direction is a setter and it hides the fact of whether or not there is the ‘direction’ attribute).

Cheers!

By: OOP: Behavioural and Structural constraints at Mark Needham

OOP: Behavioural and Structural constraints at Mark Needham — Thu, 31 Dec 2009 16:17:41 +0000

[...] Meilir Page-Jones language I think this would describe informative and imperative [...]

By: Mark Needham

Mark Needham — Tue, 01 Dec 2009 19:38:52 +0000

Yeh that’s probably an accurate observation. Need to try and spot some examples in real code bases of a lot of these to really understand the idea I find.

By: Peter Gillard-Moss

Peter Gillard-Moss — Tue, 01 Dec 2009 15:29:26 +0000

Rings of operation sounds to me like a load of classes waiting to be born.

By: Tweets that mention Fundamentals of Object-Oriented Design in UML: Book Review at Mark Needham -- Topsy.com

Tue, 01 Dec 2009 15:17:29 +0000

[...] This post was mentioned on Twitter by Mark Needham and planettw, Nuno Marques. Nuno Marques said: RT @markhneedham: thoughts on fundamentals of object oriented design http://bit.ly/8vgzCq [...]