Maxim Hierarchy

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
m (Reverted edits by Ebybymic (Talk); changed back to last version by Lukas Korsika)
 
(3 intermediate revisions by 3 users not shown)
Line 10: Line 10:
 
* [[Single responsibility principle]]
 
* [[Single responsibility principle]]
 
* [[Separation of concerns]]
 
* [[Separation of concerns]]
* [[One responsibility rule]]
+
 
 
==== Object Behaviour ====
 
==== Object Behaviour ====
 
* [[Avoid downcasting]]
 
* [[Avoid downcasting]]
Line 17: Line 17:
 
* [[Encapsulate that which varies]]
 
* [[Encapsulate that which varies]]
 
* [[Encapsulation is hierarchical]]
 
* [[Encapsulation is hierarchical]]
* [[Once and only once]]
+
* [[Option-operand separation]]
 
* [[Dependency inversion principle]]
 
* [[Dependency inversion principle]]
 
* [[Interface segregation principle]]
 
* [[Interface segregation principle]]

Latest revision as of 03:08, 25 November 2010

This is an attempt to categorise maxims.

Contents

Design & Implementation

All those maxims related to the system itself.

Separate and group system parts rationally

Defining the objects

Object Behaviour

Object Interface

Inheritance

Object Mutability

Avoid unnecessary complexity

Reuse

Do only what is necessary

Readable Code is Good Code

Group Stuff To Reduce Complexity

Dependencies

Process & Organisation

All the maxims related to the development processes and management of the development team.

OO Developers are not perfect

Personal tools