Overview

Complex business IT solutions often break and have a short lifetime. Most of the time after some time too many complex solutions are regarded as a real disaster. And not only in terms of money.

Software for complex business IT problems becomes complex since simple principles for avoiding complexity are not followed.

This section gives an overview of the core nocomplexity principles that SHOULD be used when designing systems.

If you are short on time and do not like reading: Using the principles outlined here is enough. Discuss it. Rethink it. And if you do not agree: This is an open publication so your input is welcome!

Summary of the Øcomplexity architecture & design principles:

Principle

Put People first!

Principle

Only use what you understand

Principle

Define specific criteria that are tangible to measure complexity.

Principle

Create a model of your solution.

Principle

Separation of concerns.

Principle

Reduce all waste.

Principle

Problems should be fixed through simple solutions.

Principle

Design for change.

Principle

Make sure you can manage IT!

Principle

Privacy by design.

Principle

Never over engineer.

In the next sections, all principles are explained in depth. It is RECOMMENDED to read the rationale for every principle stated.