Maxim Hierarchy
From CSSEMediaWiki
(Difference between revisions)
BenMcDonald (Talk | contribs) |
BenMcDonald (Talk | contribs) |
||
| Line 4: | Line 4: | ||
All those maxims related to the system itself. | All those maxims related to the system itself. | ||
== Separate and group system parts rationally == | == Separate and group system parts rationally == | ||
| − | === | + | ==== Defining the objects ==== |
| − | + | * [[Encapsulation boundary]] | |
| − | == | + | |
| − | + | ||
| − | * [[ | + | |
* [[Model the real world]] | * [[Model the real world]] | ||
| − | |||
* [[Behavioral completeness]] | * [[Behavioral completeness]] | ||
* [[Single responsibility principle]] | * [[Single responsibility principle]] | ||
* [[Separation of concerns]] | * [[Separation of concerns]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* [[One responsibility rule]] | * [[One responsibility rule]] | ||
| − | * [[ | + | ==== Object Behaviour ==== |
| − | ==== | + | * [[Avoid downcasting]] |
| + | * [[Avoid equals]] | ||
| + | ==== Object Interface ==== | ||
| + | * [[Encapsulate that which varies]] | ||
| + | * [[Encapsulation is hierarchical]] | ||
| + | * [[Dependency inversion principle]] | ||
| + | * [[Interface segregation principle]] | ||
* [[Fat interfaces]] | * [[Fat interfaces]] | ||
* [[Hide your decisions]] | * [[Hide your decisions]] | ||
| Line 28: | Line 25: | ||
* [[Program to the interface not the implementation]] | * [[Program to the interface not the implementation]] | ||
==== Inheritance ==== | ==== Inheritance ==== | ||
| − | |||
* [[Favor composition over inheritance]] | * [[Favor composition over inheritance]] | ||
* [[Avoid inheritance for implementation]] | * [[Avoid inheritance for implementation]] | ||
| Line 37: | Line 33: | ||
* [[Stable abstractions principle]] | * [[Stable abstractions principle]] | ||
* [[Open closed principle]] - ? | * [[Open closed principle]] - ? | ||
| − | * [[Design by contract]] | + | * [[Design by contract]] |
| − | === Mutability === | + | |
| + | ==== Object Mutability ==== | ||
* [[Don't expose mutable attributes]] | * [[Don't expose mutable attributes]] | ||
* [[Getters and setters]] | * [[Getters and setters]] | ||
| Line 46: | Line 43: | ||
== Avoid unnecessary complexity == | == Avoid unnecessary complexity == | ||
=== Reuse === | === Reuse === | ||
| + | * [[Common reuse principle]] | ||
* [[Software reuse]] | * [[Software reuse]] | ||
* [[Once and only once]] | * [[Once and only once]] | ||
| Line 62: | Line 60: | ||
* [[Common closure principle]] | * [[Common closure principle]] | ||
* [[Single choice principle]] | * [[Single choice principle]] | ||
| − | == | + | == Dependencies == |
| + | * [[Dependency injection]] | ||
| + | * [[Stable dependencies principle]] | ||
* [[Acyclic dependencies principle]] | * [[Acyclic dependencies principle]] | ||
* [[Coupling and cohesion]] | * [[Coupling and cohesion]] | ||
Revision as of 06:24, 28 September 2009
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
- Encapsulation boundary
- Model the real world
- Behavioral completeness
- Single responsibility principle
- Separation of concerns
- One responsibility rule
Object Behaviour
Object Interface
- Encapsulate that which varies
- Encapsulation is hierarchical
- Dependency inversion principle
- Interface segregation principle
- Fat interfaces
- Hide your decisions
- Information hiding
- Tell, Don't Ask
- Program to the interface not the implementation
Inheritance
- Favor composition over inheritance
- Avoid inheritance for implementation
- Don't burn your base class
- Law of leaky abstractions
- Liskov substitution principle
- No concrete base classes
- Stable abstractions principle
- Open closed principle - ?
- Design by contract
Object Mutability
- Don't expose mutable attributes
- Getters and setters
- Keep accessors and mutators separate
- Command query separation
- Avoid side effects
Avoid unnecessary complexity
Reuse
- Common reuse principle
- Software reuse
- Once and only once
- Don't repeat yourself
- Reuse release equivalence principle
Do only what is necessary
- Do the simplest thing that could possibly work
- You ain't gonna need it
- Premature optimization
- Keep it simple
- Establishing priorities
Readable Code is Good Code
Group Stuff To Reduce Complexity
Dependencies
- Dependency injection
- Stable dependencies principle
- Acyclic dependencies principle
- Coupling and cohesion
- Impedance mismatch
- Law of Demeter
Process & Organisation
All the maxims related to the development processes and management of the development team.
