To derive the anatomical application model we start with a variant of a standard 3-layer model derived from Model-View-Controller.

We want to put the non-programmers in the middle, where the use-case behavior is. (This is called the "application layer" in the standard model.) To make the middle layer friendly to non-programmers, we push all the stuff that makes programming hard (namely, the stuff that makes algorithms powerful) out to the other two layers.

The question then is: after removing all this power, is anything useful left in the middle?

The answer: with the anatomical application model, yes. The middle layer will be a wiring diagram.

Now, in the next three slides I’m going to derive the anatomical application model by removing the less relevant parts and bringing out the more relevant parts.

The Partitioning:

Put Non-Developers in the Middle Layer

Coded by

developer

colleagues

WIRING:

No iteration

No conditional

execution

Exists.

Available for

use

User