Diagnosis and review

Architecture review

We read your system as it actually runs, and tell you what will break first.

Diagnosis and review

We are doing this in our own product right now — the practice comes from reviews we run on our own systems. We are not claiming a history of delivering it to other companies.

Ці сторінки доступні лише англійською мовою.

01

When you need it

  • 01

    changes take longer every month

  • 02

    one change keeps breaking something unrelated

  • 03

    you are about to invest in a system nobody has looked at from the outside

02

How it goes

  1. 01

    we get read access to the repository and to logs for an agreed period

  2. 02

    we map modules, dependencies and the path data takes

  3. 03

    we check claims about the system against traces, not documentation

  4. 04

    we write the report

  5. 05

    one session where we go through it with you and answer questions

03

What you get

A written report — a map of the system, every finding with what it costs you, and a repair plan in the order things must be done; plus that session.

What we need from you

Read access to the repository, logs for the period, two or three calls with the people who run the system.

04

What we do not do

We do not rewrite code as part of a review; we do not take over running the system; this is not a certified security assessment.

05

Formats

Remote, worldwide.

Written scope, agreed rhythm of calls, everything delivered into your repositories and accounts.

In person, in Chișinău.

The same work, with meetings face to face on an agreed rhythm. You work with the person who does the work, not with an account manager.

Price

Fixed or capped price, agreed before work starts. We quote after a 30-minute call — a scope we have not seen is a scope we will not price.

06

Ask about this work

The person who would do the work reads this, not a sales desk.

Ask about this work

The person who would do the work reads this, not a sales desk.

info@delionsoft.com