Complex business IT solutions often fail and have a short lifespan. Over time, many complex solutions are deemed disasters—not only in terms of financial costs but also in other critical aspects.
Software for complex business IT problems becomes convoluted when simple principles for avoiding complexity are not followed.
This section provides an overview of the core nocomplexity principles that SHOULD be applied when designing systems.
Short on time and not a fan of lengthy reading? Simply applying the principles outlined here is a good start. Discuss them. Rethink them. And if you disagree, remember: this is an open publication, and your [input](help) is always welcome!
Summary of the Øcomplexity architecture & design principles:
::::{grid} 3 :class-container: text-center :gutter: 3
:::{grid-item-card}
:link: principles.html#put-people-first
:link-type: url
{octicon}people;1em;caption-text Principle
^^^
Put People first!
:::
:::{grid-item-card}
:link: principles.html#only-use-what-you-understand
:link-type: url
{octicon}bell;1em;caption-text Principle
^^^
Only use what you understand
:::
:::{grid-item-card}
:link: principles.html#define-specific-criteria-that-are-tangible-to-measure-complexity
:link-type: url
{octicon}book;1em;caption-text Principle
^^^
Define specific criteria that are tangible to measure complexity.
:::
:::{grid-item-card}
:link: principles.html#create-a-model-of-your-solution
:link-type: url
{octicon}book;1em;caption-text Principle
^^^
Create a model of your solution.
:::
:::{grid-item-card}
:link: principles.html#separation-of-concerns
:link-type: url
{octicon}book;1em;caption-text Principle
^^^
Separation of concerns.
:::
:::{grid-item-card}
:link: principles.html#reduce-all-waste
:link-type: url
{octicon}book;1em;caption-text Principle
^^^
Reduce all waste.
:::
:::{grid-item-card}
:link: principles.html#problems-should-be-fixed-through-simple-solutions
:link-type: url
{octicon}alert;1em;caption-text Principle
^^^
Problems should be fixed through simple solutions.
:::
:::{grid-item-card}
:link: principles.html#design-for-change
:link-type: url
{octicon}checklist;1em;caption-text Principle
^^^
Design for change.
:::
:::{grid-item-card}
:link: principles.html#make-sure-you-can-manage-it
:link-type: url
{octicon}blocked;1em;caption-text Principle
^^^
Make sure you can manage IT!
:::
:::{grid-item-card}
:link: principles.html#privacy-by-design
:link-type: url
{octicon}alert;1em;caption-text Principle
^^^
Privacy by design.
:::
:::{grid-item-card}
:link: principles.html#never-over-engineer
:link-type: url
{octicon}bell;1em;caption-text Principle
^^^
Never over engineer.
:::
:::: % End of grid
In the next sections, all principles are explained in depth. It is RECOMMENDED to read the rationale for every principle stated.