Maxim Hierarchy

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
(Defining the objects: One responsibility rule just redirected to Single responsibility principle anyway. No need to have them twice.)
m (Reverted edits by Ebybymic (Talk); changed back to last version by Lukas Korsika)
 
(One intermediate revision by one user not shown)

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