Digital system development and maintenance

Off-the-shelf software rarely matches the work on the ground. Bespoke systems are expensive to build, and become harder to maintain as the organisation changes.

How this work runs.

The run as one route: which tools get involved, in what order, and where the chain is not mechanised yet.

A SITUATION, NO SYSTEMRUNNING, AND IN STEPThe propositionApp configWhat changedApp statusA CLIENT PROBLEM ORREQUESTCOMPASSWRITTEN PROPOSITIONNOT MECHANISED YETFRAMESCRIBESPINERUNNING APPGAUGEFRAMEWORK CHANGEFORGE (MAINTAIN)RE-SHIP GATERE-SHIPPED APPCONSOLETHE TEAM BOARD

One run, start to finish. A box with an accent tick is a tool acting and opens its own page; a rounded box is an artefact or a record; a diamond is a decision the work cannot pass without. A dashed line is a hand-off the suite has not mechanised yet.

adds to a running record
A new entry on a record that only grows. Whoever needs it reads it later, and neither side waits.
reads what the other publishes
Nothing is sent. The next tool reads what the one before it has published, at the moment it needs it.
updates the current record
The record is overwritten with what is true now. The old value is replaced, not kept beside it.
opens a task for a person
A piece of work only a person can do, put on the team’s board.

What this work delivers.

A digital system shaped around the organisation’s work, with reusable infrastructure underneath and a defined path for maintenance.

  1. Understand the work

    Document the people, responsibilities, information and decisions the system must support.

  2. Build on a framework

    Forge assembles and extends the chosen framework under supervision. Frame is DAAC’s own framework; partner frameworks are separate.

  3. Verify and release

    Check behaviour and data against the agreed requirements. Release changes through the owner’s approval process.

  4. Maintain the system

    Carry improvements forward while checking that existing workflows and information still behave as intended.

Datastake’s framework and applications belong to Datastake and its clients. Forge’s work on that framework does not make them DAAC products.

See the application context

Which tools, in what capacity.

propose

Compass

Turns the request into a proposition and instructions

actuate

Forge

Composes the app, and re-syncs it when Frame changes

substrate

Frame

The app runs on it

actuate

Scribe

Conforms whatever data the app must take in

actuate

Spine

Gates any exchange of the app’s data

propose

Gauge

Checks the re-synced app before it ships again

observe

Console

Shows which apps are current and which have fallen behind

Put this to work in your context.

Tell us what you need to achieve and what you already have.