Design maxims

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
m
m (Reverted edits by Ebybymic (Talk); changed back to last version by LukeRobinson)
 
(6 intermediate revisions by 4 users not shown)
Line 72: Line 72:
 
* [[Make constructors blocking]]
 
* [[Make constructors blocking]]
 
* [[No Peter Pan objects]]
 
* [[No Peter Pan objects]]
 +
* [[Avoid mixing inputs and outputs]]
  
 
=== [[Johnson and Foote's heuristics]]:===
 
=== [[Johnson and Foote's heuristics]]:===
Line 123: Line 124:
 
* [[Managing IT resources]]
 
* [[Managing IT resources]]
 
* [[Managing technology transfer]]
 
* [[Managing technology transfer]]
 +
 +
===[[Joshua Bloch]]:===
 +
* [[Joshua Bloch 2006 Bumper Sticker API Design | Bumper Sticker API Design]]
  
 
== See Also ==
 
== See Also ==

Latest revision as of 03:08, 25 November 2010

Contents

Object Oriented Design Maxims

maxim:: (noun) A general truth or rule of conduct expressed in a sentence.

Let's use the term maxim to mean all the rules, laws, guidelines, principles, heuristics, strategies, patterns and idioms that are named by a standard phrase.

Maxim Hierarchy - An attempt at creating a hierarchy of maxims can be found here.

Maxims

Clumps of Maxims

These are groups of Maxims, usually gathered by the developer(s) who proposed them.

COSC 427's:

Johnson and Foote's heuristics:

Riel's heuristics:

  • All of Riel's heuristics can be found here.

Bob Martin's principles:

Ken Auer 1995:

Alan Davis 1995:

To be completed...

William Brown 1998:

Joshua Bloch:

See Also

Personal tools