QuoteOriginally posted by: quantmehQuoteOriginally posted by: CuchulainnAll Java people should appreciate this.you mean 'I' prefixes in front interfaces?there is not a single way to classify/categorize entities. for instance, if I'm psudo theor physicist (aka cosmologist), then I could look at the symmetry group of a rectangle and square. they're D2 and D4 respectively. you can't flip the rectangle over diagonals or turn 90 degrees, but you can flip horizontally or turn 180 degrees. they belong to isometric symmetry group 'hierarchy'you could also have a regular polynomial class to model all of them at once, then rectangular won't be there at all. RegPol : Pol list<double> side;RegPol can be a subtype of Polynomial, to which rectangle belongs to. this way rectangle is an instance of Pol, but it's not a base type of square, which is also not a type but an isntance of RegPolWhat is being said here is that classes are context-sensitive and their behaviour is determined by their interaction. Even in graphical apps, a CAD designer and GUI widget maker view a Rectangle differently.What this is called is the Explanation based view in modelling; the other views are attribute-based (data-oriented).
Last edited by Cuchulainn
on September 28th, 2010, 10:00 pm, edited 1 time in total.